Embedded Systems

1 - Introduction

© Lothar Thiele
Computer Engineering and Networks Laboratory
Lecture Organization

301

1-2
Organization
WWW: https://www.tec.ee.ethz.ch/education/lectures/embedded-systems.html
Lecture: Lothar Thiele, [email protected]
Coordination: Naomi Stricker <[email protected]>
Andreas Biri <[email protected]>
References:
 P. Marwedel: Embedded System Design, Springer, ISBN 978-3-319-56045-8, 2018.
 G.C. Buttazzo: Hard Real-Time Computing Systems. Springer Verlag, ISBN 978-1-4614-
0676-1, 2011.
 Edward A. Lee and Sanjit A. Seshia: Introduction to Embedded Systems, A Cyber-
Physical Systems Approach, Second Edition, MIT Press, ISBN 978-0-262-53381-2, 2017.
 M. Wolf: Computers as Components – Principles of Embedded System Design. Morgan
Kaufman Publishers, ISBN 978-0-128-05387-4, 2016.

Sources: The slides contain ideas and material of J. Rabaey, K. Keuzer, M. Wolf, P.
Marwedel, P. Koopman, E. Lee, P. Dutta, S. Seshia, and from the above cited books.

1-3
Organization Summary
 Lectures are held on Mondays from 14:15 to 16:00 via Zoom. Recordings will be
made available. The first lecture is on Monday, 21.09.2020.
 Exercises take place on Wednesdays and Fridays from 16:15 to 17:00 via Zoom.
On Wednesdays the lecture material is summarized, hints on how to approach
the solution are given and a sample question is solved. On Fridays, the correct
solutions are discussed.
 Laboratories take place on Wednesdays or Fridays from 16:15 to 18:00. On
Wednesdays the session starts with a short introduction via Zoom and then
questions can be asked via Zoom or in person in ETZ D 96. Fridays are reserved
for questions via Zoom or in person in ETZ D 96. Hardware for the laboratories
will be distributed in the first week of the semester on Wednesday, 16.09.2020
and Friday, 18.09.2020 from 16:15 - 18:00 in ETZ D61.2.

We urgently ask all students to do the laboratory on their own hardware.

1-4
Further Material

1-5
What will you learn?
 Theoretical foundations and principles of the analysis and design of embedded
systems.
 Practical aspects of embedded system design, mainly software design.

The course has three components:

 Lecture: Communicate principles and practical aspects of embedded systems.
 Exercise: Use paper and pencil to deepen your understanding of analysis and
design principles .
 Laboratory (ES-Lab): Introduction into practical aspects of embedded systems
design. Use of state-of-the-art hardware and design tools.

1-6
When and where?

1-7
Please read carfully!!
 https://www.tec.ee.ethz.ch/education/lectures/embedded-systems.html

1-8
What you got already…

1-9
Be careful and please do not …

1 - 10
You have to return the board at the end!

1 - 11
Embedded Systems - Impact

1 - 12
Embedded Systems
Embedded systems (ES) = information processing systems
embedded into a larger product

•Examples:

• Often, the main reason for buying is not information processing

1 - 13
© www.braingrid.org
© www.openpr.com
1 - 14
Many Names – Similar Meanings

© Edward Lee
1 - 15
The Hype Cycle

Peak of Inflated Expectations

© Gartner Inc.
https://www.gartner.com

1 - 16
The Hype Cycle
Sensors and Interfaces
Internet of Things

Connected Home

Edge Computing

© Gartner Inc.
https://www.gartner.com

1 - 17
 Embedded Systems are an essential component

Manyika, James, et al. Disruptive technologies: Advances that

will transform life, business, and the global economy. Vol. 180.
San Francisco, CA: McKinsey Global Institute, 2013.
1 - 18
Embedded System
Embedded System

Hardware & Computation

Software reasoning
deciding
big data

CYBER Communication
WORLD
observing influencing
PHYSICAL
WORLD physical/biological/social
processes

Nature
Use feedback to influence the dynamics of the physical
world by taking smart decisions in the cyber world
1 - 19
Predictability & Dependability

CPS = cyber-physical system

“It is essential to predict how a CPS is going to behave under any

circumstances […] before it is deployed.”Maj14

“CPS must operate dependably, safely, securely, efficiently and in

real-time.”Raj10

Maj14 R. Majumdar & B. Brandenburg (2014). Foundations of Cyber-Physical Systems.

Raj10 R. Rajkumar et al. (2010). Cyber-Physical Systems: The Next Computing Revolution.
1 - 20
Efficiency & Specialization
 Embedded systems must be efficient:
 Energy efficient
 Code-size and data memory efficient
 Run-time efficient
 Weight efficient
 Cost efficient

Embedded Systems are often specialized towards a certain

application or application domain:
 Knowledge about the expected behavior and the system environment at design
time is exploited to minimize resource usage and to maximize predictability and
reliability.

1 - 21
Reactivity & Timing
Embedded systems are often reactive:
 Reactive systems must react to stimuli from the system environment :

„A reactive system is one which is in continual interaction with is environment and

executes at a pace determined by that environment“ [Bergé, 1995]

Embedded systems often must meet real-time constraints:

 For hard real-time systems, right answers arriving too late are wrong. All other
time-constraints are called soft. A guaranteed system response has to be explained
without statistical arguments.

„A real-time constraint is called hard, if not meeting that constraint could

result in a catastrophe“ [Kopetz, 1997].

1 - 22
Comparison
Embedded Systems: General Purpose Computing
 Few applications that are known at  Broad class of applications.
design-time.
 Not programmable by end user.  Programmable by end user.

 Fixed run-time requirements (additional  Faster is better.

computing power often not useful).

 Typical criteria:  Typical criteria:

 cost  cost
 power consumption  power consumption
 size and weight  average speed
 dependability
 worst-case speed

1 - 23
Lecture Overview

1. Introduction to Embedded Systems

2. Software Development
3. Hardware-Software Interface
4. Programming Paradigms
Software Hardware-
5. Embedded Operating Systems
Software
6. Real-time Scheduling
7. Shared Resources
8. Hardware Components
Hardware 9. Power and Energy
10. Architecture Synthesis

1 - 24
Components and Requirements by Example

1 - 25
1 - 26
1 - 27
1 - 28
Components and Requirements by Example
- Hardware System Architecture -

1 - 29
 High-Level Block Diagram View
low power CPU higher performance CPU
• enabling power to the rest of the system • sensor reading and motor control
• battery charging and voltage • flight control
measurement • telemetry (including the battery voltage)
• wireless radio (boot and operate) • additional user development
• detect and check expansion boards • USB connection

UART:
• communication protocol (Universal
Asynchronous Receiver/Transmitter)
• exchange of data packets to and from
interfaces (wireless, USB)

1 - 30
 EEPROM:
• electrically erasable programmable
High-Level Block Diagram View read-only memory
Acronyms: sensor board • used for firmware (part of data and
software that usually is not
• Wkup: Wakeup signal changed, configuration data)
• GPIO: General-purpose input/output • can not be easily overwritten in
signal comparison to Flash
• SPI: Serial Peripheral Interface Bus
• I2C: Inter-Integrated Circuit (Bus)
• PWM: Pulse-width modulated Signal
• VCC: power-supply

Flash memory:
• non-volatile random-access memory
for program and data
1 - 31
1 - 32
High-Level Physical View

1 - 33
High-Level Physical View

1 - 34
 Low-Level Schematic Diagram View

LEDs

(1 page out of 3)
1 - 35
 Low-Level Schematic Diagram View

(1 page out of 3) Motors

1 - 36
High-Level Software View
 The software is built on top of a real-time operating system “FreeRTOS”.
 We will use the same operating system in the ES-Lab … .

1 - 37
High-Level Software View
The software architecture supports
 real-time tasks for motor control (gathering sensor values and pilot commands,
sensor fusion, automatic control, driving motors using PWM (pulse width
modulation, … ) but also
 non-real-time tasks (maintenance and test, handling external events, pilot
commands, … ).
Control System: PID controller (proportional–integral–derivative)

motors

pilot commands
(from wireless interface) sensors

update frequencies (periodic task execution)

1 - 38
High-Level Software View

The software architecture supports

 real-time tasks for motor control (gathering sensor values and pilot commands,
sensor fusion, automatic control, driving motors using PWM (pulse width
modulation, … ) but also

 non-real-time tasks (maintenance and test, handling external events, pilot

commands, … ).

1 - 39
High-Level Software View
Block diagram of the stabilization system:

sensor reading & transfer to cleaning and information

analog-digital processor preprocessing extraction from automatic control actuation
conversion sensors
on sensor
component 1 - 40
Components and Requirements by Example
- Processing Elements -

1 - 41
What can you do to increase performance?

1 - 42
From Computer Engineering 1

Intel 62-Core Xeon Phi

2015

1 - 43
From Computer Engineering 1:

AMD multicore RYZEN

1 - 44
From Computer Engineering 1

Intel Xeon Phi 7290

(8 Billion transistors,
14nm technology,
~ 650mm2 area,
1.5 GHZ clock frequency)
1 - 45
What can you do to decrease power consumption?

1 - 46
Embedded Multicore Example
Recent developments:
 Specialize multicore processors towards real-time processing and low power
consumption
 Target domains:

1 - 47
Why does higher parallelism help in reducing power?

1 - 48
 System-on-Chip
Samsung Galaxy S6
– Exynos 7420 System on a Chip (SoC)
– 8 ARM Cortex processing cores
•Exynos 5422
(4 x A57, 4 x A53)
– 30 nanometer: transistor gate width

1 - 49
How to manage extreme workload variability?

1 - 50
ARM big.LITTLE Architecture

1 - 51
Components and Requirements by Example
- Systems -

1 - 52
Zero Power Systems and Sensors

Streaming information to
and from the physical world:

• “Smart Dust”
• Sensor Networks
• Cyber-Physical Systems
• Internet-of-Things (IoT)

1 - 53
Zero Power Systems and Sensors

IEEE Journal of Solid-State Circuits, IEEE Journal of Solid-State

Jan 2013, 229-243. Circuits, April 2017, 961-971.
1 - 54
Trends …
 Embedded systems are communicating with each other, with servers or with the cloud.
Communication is increasingly wireless.

 Higher degree of integration on a single chip or integrated components:

 Memory + processor + I/O-units + (wireless) communication.
 Use of networks-on-chip for communication between units.
 Use of homogeneous or heterogeneous multiprocessor systems on a chip (MPSoC).
 Use of integrated microsystems that contain energy harvesting, energy storage, sensing,
processing and communication (“zero power systems”).
 The complexity and amount of software is increasing.

 Low power and energy constraints (portable or unattended devices) are increasingly important,
as well as temperature constraints (overheating).
 There is increasing interest in energy harvesting to achieve long term autonomous operation.

1 - 55