What is an Embedded System?

Definition of an embedded computer system:

Embedded Systems is a digital system.
Introduction uses a microprocessor (usually).
runs software for some or all of its functions.
frequently used as a controller.

02-Embedded-intro 1 02-Embedded-intro 2

What an embedded system is Examples of Embedded

NOT. Systems
Not a computer system that is used primarily for
processing.
Not a software system on a PC or Unix box.
Not a traditional business or scientific application. Medical instruments
Automotive systems:
electronic
controls:
dashboards, ABS brakes,
CAT scanners, implanted
transmission controls.
heart
monitors, etc.

Controls for digital equipment: CD players, TV remote,

programmable sprinklers, household appliances, etc.

02-Embedded-intro 3 02-Embedded-intro 4

Why embedded? Special Characteristics

Because the processor is inside some other hardware and software (in one system)
system.
A microprocessor is embedded into your TV, car, concurrency (several
or appliance. processes working at
The consumer does not think about performing same time) timing
processing, (often real sensors and
Considers running a machine or `making time) actuators
something work. synchronization (this process (for inputs
Considered part of the thing rather than the must complete before this and outputs)
process begins)
thing
02-Embedded-intro 5 02-Embedded-intro 6

1
 Timing and Concurrency How are embedded systems different
than traditional software?

Fire Spark

Engine Responding to sensors (Was this button

shaft angle
pushed?)
Fire Injectors Turning on actuators (Turn on power to the
boiler.)
Watch Real-time (Respond to temperature change
Emissions within 3 seconds.)

02-Embedded-intro 7 02-Embedded-intro 8

Differences between ES and traditional

software development
Small and Many!

Not dealing with only sequential code.
Routine can stop at completion or in response to
an external event.
Many parts of system might be running
concurrently.
Safety-critical component of many systems.
Ganssle, J. The Art of Programming Embedded Systems Academic Press, 1992, San Diego, Cal.
Most embedded systems use 4-, 8-, or 16-bit processors.
32-bit used for intensive applications like printer controls.
8-bit processors have about 64K of memory, that limits
amount of code.
By 1990 a total of about 45 million recognizable computers (i.e., PCs,
Macintosh, even CP/M systems) were in place. Yet over 1 billion
microprocessors and microcontrollers were shipped in that year
alone!

02-Embedded-intro 9 02-Embedded-intro 10


 
 hardware/software Codesign or
hardware or ? Codesign

Where to place functionality?

ex: A Sort algorithm
Model the hardware and the software system in a
Faster in hardware, but more expensive.
unified approach.
More flexible in software but slower. Use similar design models.
Other examples? Need for model continuity spanning levels of the
Must be able to explore these various trade-offs: design process.
Cost.
Speed.
Reliability.
Form (size, weight, and power constraints.)

02-Embedded-intro 11 02-Embedded-intro 12

2
 Traditional Embedded System
Increased Complexity
Development Approach

Decide on the hardware Systems are becoming more and more complex.
Give the chip to the software people. Harder to think about total design.
Software programmer must make software fit on Harder to fix bugs.
the chip and only use that hardwares capabilities. Harder to maintain systems over time.
Therefore, the traditional development process
has to change,

02-Embedded-intro 13 02-Embedded-intro 14

Less Time to Develop Solutions to Complexity:

Need to keep design process abstract for a longer

In embedded electronics, the total design cycle must
period of time.
decrease.
Decomposable hierarchy (object-oriented).
Historically, design for automotive electronic systems
Reuse previous designs:
takes 3-5 years to develop. When a design changes, reuse similar sections.
Must become a 1-3 year development cycle. Dont throw away last years design and start from scratch!

Must still be reliable and safe. Automated verification systems.

B. Wilkie, R. Frank and J. Suchyta - Motorola Semiconductor Products Sectors, Silicon or Software: The Foundation of
Automotive Electronics, IEEE Vehicular Tech., August 95.

02-Embedded-intro 15 02-Embedded-intro 16

Fly-by-Wire Airplane
Example: Fly-by-Wire Airplane
Continued
How would you start to think about developing this What would be the sensors and actuators of this
complex/large system? system?
What are potential problems with deciding on the How concerned should developers be about the
hardware right away? safety of the system?
What are possible concurrent systems needs? Would testing be enough?
What type of timing constraints might be needed?

02-Embedded-intro 17 02-Embedded-intro 18