Introduction to Embedded Systems

Sistemas Embebidos
Oscar Acevedo, PhD
Introduction

• About the information processing technology:

• 80´s, large mainframe computers and tape drives

• 90´s, personal computers

• 2000+, small portable computers, many of which will be integrated into larger products
Introduction

• Information Technology is characterized by terms such as:

• Disappearing computer

• Ubiquitous computing
• Information anytime, anywhere

• Pervasive computing
• Practical aspects and the exploitation of already available
Introduction

• Information Technology is characterized by terms such as:

• Ambient intelligence

• Post-PC era

• Cyber-physical systems

• Networked systems of embedded computers

What is an Embedded System?

• An embedded system is an information processing system with a dedicated function

within a larger mechanical or electrical system, often with real-time computing constraints
Embedded Systems Characteristics

• Embedded systems are designed to do some specific tasks, rather than be a general-
purpose computer for multiple tasks

• They may have real-time performance constraints that must be met, for reasons such as
safety and usability
Embedded System Characteristics

• The program instructions written for embedded systems are referred to as firmware, and
are stored in read-only memory or flash memory chips
• These programs run endlessly

• They run with limited computer hardware resources: little memory, small or non-existent
keyboard or screen
Example - Automotive electronics

• ABS: Anti-lock braking systems

• Cruise control
• Airbags
• Efficient automatic gearboxes
• Theft prevention with smart keys
• Blind-angle alert systems
• Autonomous driving
Example - Avionics

• Flight control systems

• Anti-collision systems
• Pilot information systems
• Power supply system
• Flap control system
• Entertainment system
More Embedded Systems Examples
Embedded Systems must be dependable

• Reliability R(t) = probability of system working correctly provided that is was working at
t=0
• Maintainability M(d) = probability of system working correctly d time units after error
occurred
• Availability A(t): probability of system working at time t
• Safety: no harm to be caused
• Security: confidential and authentic communication

• It must be considered from the very beginning

Embedded Systems must be efficient

• Code-size efficient
• Run-time efficient
• Weight efficient
• Cost efficient
• Energy efficient
Energy Efficiency

The number of
operations per Joule is
increasing as
technology
advances to smaller
feature sizes of
integrated circuits.

Efficient software
design needed,
otherwise, the price for
software flexibility
cannot be paid
Embedded Systems must meet Real-Time Constraints

• A real-time system must react to stimuli from the controlled object (or the operator) within
the time interval dictated by the environment

• For real-time systems, right answers arriving too late are wrong

• A real-time constraint is called hard, if not meeting that constraint could result in a
catastrophe. All other time-constraints are called soft

• A guaranteed system response has to be explained without statistical arguments

V Methodology

Assembly &
Genesis Simulation Deployment

Design Verification

Build Validation
Waterfall Methodology

Genesis

Simulation
Design

Build

Assembly &
Validation Deployment

Verification
Successive Refinement Methodology

Genesi
s

Genesi
Do it
s Simulation
Design

Simulation
Design Build
Assembly &
Deployment
Build Validation

Assembly &
Deployment
Validation Verification

Verification

Do it right
Fin de la presentación