Vous êtes sur la page 1sur 72

Introduction to

Embedded
Systems
Sandeep K. Shukla, IIT Kanpur

TEQIP Course at IITK, Aug 29, 2016


2

Objectives

Introduction to embedded systems


Embedded system components
Hardware
Software
Embedded system Design Issues
Trends and Directions

Introduction to Embedded Systems


3

Communications

Telematics System for Automobiles

Hand-held GPS Units

Y. Williams Csci-339, Spring 2002 20

Slide credit Y Williams, GWU


Introduction to Embedded Systems
4

Introduction to Embedded Systems Slide credit Y Williams, GWU


5

More examples

Slide credit Y Williams, GWU

Introduction to Embedded Systems


6

Slide credit Y Williams, GWU


Introduction to Embedded Systems
7

Slide credit S. Kowalewski Aachen University


Introduction to Embedded Systems
8

Slide credit P Koopman, CMU


Introduction to Embedded Systems
9

Definition

Any sort of device which includes a


programmable computer but itself is not
intended to be a general-purpose computer
Marilyn Wolf

Introduction to Embedded Systems


10

Definition

Slide credit P Koopman, CMU

Introduction to Embedded Systems


11

Embedded systems overview


Computing systems are everywhere
Most of us think of desktop computers
PCs
Laptops
Mainframes
Servers
But theres another type of computing system
Far more common...

Slide credit Vahid/Givargis, Embedded Systems Design: A Unified Hardware/Software


Introduction, 2000

Introduction to Embedded Systems


12

Embedded systems overview


Embedded computing systems
Computing systems embedded within Computers are in here...

electronic devices and here...


Hard to define. Nearly any computing system
other than a desktop computer and even here...
Billions of units produced yearly, versus
millions of desktop units
Perhaps 50 per household and per
automobile
Slide credit Vahid/Givargis, Embedded Systems Design: A Unified
Hardware/Software Introduction, 2000

Lots more of these,


though they cost a lot
less each.

Introduction to Embedded Systems


13

A short list of embedded systems


Anti-lock brakes Modems
Auto-focus cameras MPEG decoders
Automatic teller machines Network cards
Automatic toll systems Network switches/routers
Automatic transmission On-board navigation
Avionic systems Pagers
Battery chargers Photocopiers
Camcorders Point-of-sale systems
Cell phones Portable video games
Cell-phone base stations Printers
Cordless phones Satellite phones
Cruise control Scanners
Curbside check-in systems Smart ovens/dishwashers
Digital cameras Speech recognizers
Disk drives Stereo systems
Electronic card readers Teleconferencing systems
Electronic instruments Televisions
Electronic toys/games Temperature controllers
Factory control Theft tracking systems
Fax machines TV set-top boxes
Fingerprint identifiers VCRs, DVD players
Home security systems Video game consoles
Life-support systems Video phones
Medical testing systems Washers and dryers

And the list goes on and on


Slide credit Vahid/Givargis, Embedded Systems Design: A Unified Hardware/Software
Introduction, 2000

Introduction to Embedded Systems


14

How many do we use?


Average middle-class American home has 40 to 50
embedded processors in it
Microwave, washer, dryer, dishwasher, TV, VCR, stereo, hair
dryer, coffee maker, remote control, humidifier, heater, toys,
etc.
Luxury cars have over 80 embedded processors
Brakes, steering, windows, locks, ignition, dashboard
displays, transmission, mirrors, etc.
Personal computers have over 10 embedded
processors
Graphics accelerator, mouse, keyboard, hard-drive, CD-ROM,
bus interface, network card, etc.
- Mike Schulte

Introduction to Embedded Systems


15

Types of Embedded Systems

Slide credit P Koopman, CMU


Introduction to Embedded Systems
16

Cyber Physical Systems vs. Embedded Systems

Slide credit S. Kowalewski Aachen University

Introduction to Embedded Systems


17

Typical Cyber Physical Embedded Systems


Are designed to be observed (through sensors)
and control something (through actuators)
E.g. air condition senses room temperature and
maintains it at set temperature via thermostat.

Introduction to Embedded Systems


18

Embedded System Block Diagram

Control
(Output) Motor/Light

System Bus
Observe Temperature
Processor (Input) Sensor

mem

Slide credit Y Williams, GWU

Introduction to Embedded Systems


19

Processors

Microprocessors for PCs


Embedded processors or Microcontrollers for embedded
systems
Often with lower clock speeds
Integrated with memory and
I/O devices e.g. A/D D/A PWM CAN
Higher environmental specs

Introduction to Embedded Systems


20

Microcontrollers dominates processor market

Introduction to Embedded Systems


21

There are so many microcontrollers in the world

Introduction to Embedded Systems


22

Types of Embedded Processors


Computational micros (32- or 64-bit datapaths)
CPU of workstations, PCs, or high-end portable devices
(PDAs)
x86, PA-RISC, PowerPC, SPARC, etc.
Embedded general purpose micros (32-bit datapaths)
Designed for a wide range of embedded applications
Often scaled-down version of computational micros
ARM, PowerPC, MIPS, x86, 68K, etc.
Microcontrollers (4-, 8-, or 16-bit datapaths)
Integrate processing unit, memory, I/O buses, and peripherals
Often low-cost, high-volume devices
Domain-specific processors (datapath size varies
greatly)
Designed for a particular application domain
Digital signal processors, multimedia processors, graphics
processors, network processors, security processors, etc.
Slide credit - Mike Schulte

Introduction to Embedded Systems


23

Processor Sales Data

Slide credit - Mike Schulte

Introduction to Embedded Systems


24

Processor Market

Source: UBM Tech report


Introduction to Embedded Systems
25

Trend in Programmable Logic Usage in Embedded Systems


26

Growing Demand
Embedded
processors account
for
Over 97% of total
processors sold
Over 60% of total
sales from processors
Sales expected to
increase by roughly
15% each year
Slide credit - Mike Schulte

Source: Gartner

Introduction to Embedded Systems


27

Some common characteristics of embedded systems

Single-functioned
Executes a single program, repeatedly
Tightly-constrained
Low cost, low power, small, fast, etc.
Reactive and real-time
Continually reacts to changes in the systems
environment
Must compute certain results in real-time without
delay
Slide credit Vahid/Givargis, Embedded Systems Design: A Unified Hardware/Software Introduction, 2000

Introduction to Embedded Systems


28

Characteristics of Embedded Systems


Application-specific functionality specialized for one or one
class of applications
Deadline constrained operation system may have to perform
its function(s) within specific time periods to achieve successful
results
Resource challenged systems typically are configured with a
modest set of resources to meet the performance objectives
Power efficient many systems are battery-powered and must
conserve power to maximize the usable life of the system.
Form factor many systems are light weight and low volume to
be used as components in host systems
Manufacturable usually small and inexpensive to manufacture
based on the size and low complexity of the hardware.
Slide credit Y William, GWU

Introduction to Embedded Systems


29

Design with focus on Application

Slide credit P Koopman, CMU


Introduction to Embedded Systems
30

Design Constraints

Slide credit P Koopman, CMU


Introduction to Embedded Systems
31

Design Challenges

Does it really work?


Is the specification correct?
Does the implementation meet the spec?
How do we test for real-time characteristics?
How do we test on real data?
How do we work on the system?
Observability, controllability?
What is our development platform?
Slide credit P Koopman, CMU

More importantly optimizing design


metrics!!

Introduction to Embedded Systems


32
Design Metrics
Common metrics
Unit cost: the monetary cost of manufacturing each copy
of the system, excluding NRE cost
NRE cost (Non-Recurring Engineering cost):
The one-time monetary cost of designing the system
Size: the physical space required by the system
Performance: the execution time or throughput of the
system
Power: the amount of power consumed by the system
Flexibility: the ability to change the functionality of the
system without incurring heavy NRE cost

Slide credit Vahid/Givargis, Embedded Systems Design: A Unified Hardware/Software


Introduction

Introduction to Embedded Systems


33

Design Metrics
Common metrics (continued)
Time-to-prototype: the time needed to build a working
version of the system
Time-to-market: the time required to develop a system to
the point that it can be released and sold to customers
Maintainability: the ability to modify the system after its
initial release
Correctness, safety, many more

Slide credit Vahid/Givargis, Embedded Systems Design: A Unified Hardware/Software


Introduction

Introduction to Embedded Systems


34

Trade-off in Design Metrics


Expertise with both
Power
software and
hardware is needed to
optimize design metrics
Performance Size Not just a hardware or
software expert, as is
common
A designer must be
NRE cost comfortable with various
technologies in order to
choose the best for a
given application and
constraints
Slide credit Vahid/Givargis, Embedded Systems
Design: A Unified Hardware/Software
Introduction

Introduction to Embedded Systems


35

Time-to-market: a demanding design metric

Time required to
develop a product to
the point it can be
sold to customers
Revenues ($)

Market window
Period during which the
product would have
highest sales
Average time-to-
Time (months) market constraint is
about 8 months
Delays can be costly
Slide credit Vahid/Givargis, Embedded Systems
Design: A Unified Hardware/Software
Introduction

Introduction to Embedded Systems


36

Losses due to delayed market entry

Simplified revenue model


Product life = 2W, peak at W
Peak revenue
Time of market entry defines
Peak revenue from a triangle, representing
Revenues ($)

delayed entry
On-time market penetration
Market rise Market fall Triangle area equals revenue
Delayed Loss
The difference between the
on-time and delayed triangle
D W 2W areas
On-time Delayed Time Slide credit Vahid/Givargis, Embedded Systems
entry entry Design: A Unified Hardware/Software
Introduction

Introduction to Embedded Systems


37

Other Design Considerations


Dependability
Reliability: probability of system working
correctly provided that it worked at time t=0
Maintainability: probability of system working
correctly d time units after error occurred.
[Some systems require no maintenance
throughout their operating lives (e.g. electric
kettles, computer keyboards), while some may
need it such as mobile phones and airplane
flight control (software upgrade)]

Introduction to Embedded Systems


38

Other Design Considerations

Dependability
Availability: probability of system working at time t
Safety
Security
Basically, critical applications have to operate correctly at
all time e.g. airplane flight control computer. This
includes both hardware and software aspects.

Introduction to Embedded Systems


39

Example of System Fault

Slide credit B. Pahami


40

Other Design Considerations

Operating environment
Some engine Electronic Control Units (ECUs) in
cars are located under the bonnets. So they have to
work at high temperature, as well as dusty and wet
environment.
EMI (Electromagnetic Interference)

Introduction to Embedded Systems


41

Real-Time Consideration

Correct operation of real-time systems means:


Working correctly (functionally correct)
Producing outputs in time!
i.e. correct result at the right time

Introduction to Embedded Systems


42

Hard Real-time
System designed to meet all deadlines
A missed deadline is a design flaw
For examples: ABS brake, nuclear reactor monitoring
system
System hardware (over) designed for worst-case
performance
System software rigorously tested
Formal proofs used to guarantee timing correctness
Slide credit T Givargis

Introduction to Embedded Systems


43

Firm Real-time
System designed to meet all deadlines, but occasional
missed deadline is allowed
Sometimes statistically quantified (e.g. 5% misses)
For examples: multimedia systems
System hardware designed for average case
performance
System software tested under average (ideal)
conditions
Slide credit T Givargis

Introduction to Embedded Systems


44

Soft Real-time
System designed to meet as many deadlines as possible
Best effort to complete within specified time, but may
be late
For examples: network switch or router
System hardware designed for average case performance
System software tested under averaged (ideal) conditions
Slide credit T Givargis

Introduction to Embedded Systems


45

Real-time Systems Deadlines


Deadlines

Deadline : maximum time before


task
a task must complete
time
d

The profit associated with execution of a task


after the deadline:
Hard deadline: negative soft

Firm deadline: 0 (either make d


profit
time
it or just dont do it) firm

Soft deadline: decreasing


hard
with time Slide taken from J.J Lukkien

Introduction to Embedded Systems


46

Levels of System Design

requirements

specification

architecture

component
design
system
integration

Introduction to Embedded Systems


47

Traditional Embedded System Design Approach

Decide on the hardware


Give the chip to the software people.
Software programmer must make software fit
on the chip and only use that hardwares
capabilities.

Slide credit - W. McUmber,MSU

Introduction to Embedded Systems


48

Problems with Increased Complexity


Systems are becoming more and more complex.
Harder to think about total design.
Harder to fix bugs.
Harder to maintain systems over time.
Therefore, the traditional development process has to
change,
Slide credit - W. McUmber,MSU

Introduction to Embedded Systems


49

Design with Time Constraint


In embedded electronics, the total design cycle must
decrease.
Historically, design for automotive electronic systems
takes 3-5 years to develop.
Must be reduced to a 1-3 year development cycle.
Must still be reliable and safe.
B. Wilkie, R. Frank and J. Suchyta - Motorola Semiconductor Products Sectors, Silicon or Software: The
Foundation of Automotive Electronics, IEEE Vehicular Tech., August 95.

Introduction to Embedded Systems


50

Possible Ways to Do
Need to keep design process abstract for a longer
period of time.
Decomposable hierarchy (object-oriented).
Reuse previous designs:
When a design changes, reuse similar sections.
Dont throw away last years design and start from scratch!
Automated verification systems.
Slide credit - W. McUmber,MSU

Introduction to Embedded Systems


51

Levels of Embedded System Design

Slide credit Ingo Sander

Introduction to Embedded Systems


52

Design Abstraction

Slide credit Ingo Sander


Introduction to Embedded Systems
53

Abstraction Levels

Slide credit Ingo Sander

Introduction to Embedded Systems


54

Abstraction Levels

Slide credit Ingo Sander

Introduction to Embedded Systems


55

Abstraction Levels

Slide credit Ingo Sander

Introduction to Embedded Systems


56

Abstraction Level

Slide credit Ingo Sander

Introduction to Embedded Systems


57

Hardware vs Software
Many functions can be done by software on a general
purpose microprocessor OR by hardware on an
application specific ICs (ASICs)
For examples: game console graphic, PWM, PID control
Leads to Hardware/Software Co-design concept

Introduction to Embedded Systems


58

Hardware or Software?

Where to place functionality?


ex: A Sort algorithm
Faster in hardware, but more expensive.
More flexible in software but slower.
Other examples?
Must be able to explore these various trade-
offs:
Cost.
Speed.
Reliability.
Form (size, weight, and power constraints.)

Slide credit - W. McUmber, MSU

Introduction to Embedded Systems


59

Hardware vs Software
Workstations
Personal Computers
Power/Performance

Graphics Processors
DSP Processors
Network Processors
FFT Processors General-Purpose
MPEG Processors Processors
FIR Processors Embedded
Domain-Specific
Processors
Embedded
Application-Specific
Processors

Programmability and Flexibility


Slide credit - Mike Schulte
Introduction to Embedded Systems
60

Hardware vs Software

Slide credit Ingo Sander

Introduction to Embedded Systems


61

General-purpose processors
Programmable device used in a variety of
applications Controller Datapath
Also known as microprocessor Control Register
Features logic and file
State register
Program memory
General datapath with large register file and General
IR PC ALU
general ALU
User benefits Program Data
Low time-to-market and NRE costs memory memory
High flexibility Assembly code
for:
Pentium the most well-known, but
there are hundreds of others total = 0
for i =1 to

Slide credit Vahid/Givargis, Embedded Systems Design: A Unified Hardware/Software Introduction, 2000

Introduction to Embedded Systems


62

Single-purpose processors
Digital circuit designed to execute exactly
one program Controller Datapath
a.k.a. coprocessor, accelerator or peripheral Control index
logic
Features total
State
Contains only the components needed to register +
execute a single program
No program memory Data
memory
Benefits
Fast
Low power
Small size

Slide credit Vahid/Givargis, Embedded Systems Design: A Unified Hardware/Software Introduction, 2000

Introduction to Embedded Systems


63

Application-specific processors
Programmable processor optimized for a particular
Controller Datapath
class of applications having common
characteristics Control Registers
logic and
Compromise between general-purpose and single- State register
purpose processors Custom
Features ALU
IR PC
Program memory
Data
Optimized datapath Program memory
Special functional units memory

Benefits Assembly code


for:
Some flexibility, good performance, size and power
total = 0
DSP for i =1 to

Slide credit Vahid/Givargis, Embedded Systems Design: A Unified Hardware/Software Introduction, 2000

Introduction to Embedded Systems


64

FPGA Architecture
IOB IOB IOB IOB
IOB

CLB CLB
IOB

Wiring Channels
IOB

Programmable switch at wiring intersection


CLB CLB (credit: www.wikipedia.com)
IOB

FPGA layout with Configurable Logic Blocks (CLB) and I/O Blocks (IOB) (credit: Katzs Contemporary Logic
Design)

Typical CLB (credit: www.wikipedia.com)

Introduction to Embedded Systems


65

Highly constrained products tend to use


application specific processors
Many mobile phones (power&size constrained)
contain ARM chips
Hi-Fi (high performance&time constrained)
contain DSP chips

Introduction to Embedded Systems


66

Software Costs

Slide credit P Koopman, CMU

Introduction to Embedded Systems


67

Disciplines Used in Embedded System Design

Slide credit R Gupta, UC Irvine


Introduction to Embedded Systems
68

Trends in Embedded Systems

Slide credit R Gupta, UC Irvine

Introduction to Embedded Systems


69

Future Embedded Systems

Slide credit P Koopman, CMU


Introduction to Embedded Systems
70

Future Embedded Systems

Slide credit P Koopman, CMU


Introduction to Embedded Systems
71

Observations on Future Embedded Systems

More complexity (people expect more


functions and higher performance from their
electronic products)
This leads to more complex software
Which requires better design process
More importantly, thorough testing for safety
critical systems (diagnostics codes of engine
ECUs is half of its total software codes)

Introduction to Embedded Systems


72

Research in Embedded Systems


Hardware to improve performance (sensors and
actuators), verification, etc.
Software reusability, testing, verification, OS, etc.
Network higher connectivity between systems (e.g.
smart homes link many systems together,
standardised protocols, etc.
Security protection against attacks
Design improved methodology, more automation,
formal verification

Introduction to Embedded Systems