Scribd
Upload
89 views14 pages

Embedded Systems: Vinay Chowdary Assistant Professor

Embedded Systems Introduction

Uploaded by

Vinay Chowdary
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
89 views14 pages

Embedded Systems: Vinay Chowdary Assistant Professor

Embedded Systems Introduction

Uploaded by

Vinay Chowdary
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Embedded Systems

Vinay Chowdary
Assistant Professor

© 2014 UPES
Characteristics of Embedded Computing Applications (1.1.2, WW)

embedded computing systems have to provide sophisticated functionality:


i) Complex algorithms: e.g., Processor that controls an automobile engine
ii) User Interface : Best example is Moving map of GPS

embedded computing operations must often be performed to meet deadlines:


i) Real Time : Missed deadline in printers can result in scrambled pages
ii) Multi-rate : Audio and video portions of multimedia stream must be closely synced.

Costs of various sorts are also very important:


i) Manufacturing cost: Total cost
ii) Power and energy : Power consumption directly effects cost of hardware as it requires
larger power supply
Energy consumption effects battery life.

2 © 2014 UPES
Why not use PCs for all embedded computing?

First, real-time performance requirements often drive us to different architectures.


real-time performance is often best achieved by multiprocessors.
Second, low power and low cost also drive us away from PC architectures and
toward multiprocessors.
Challenges in Embedded Computing System Design
1. How much hardware do we need?
(too little hardware and the system fails to meet its deadlines, too much hardware
and it becomes too expensive)
2. How do we meet deadlines?
(speed up the hardware or increasing the CPU clock rate may not make enough
difference to execution time, since the program’s speed may be limited by the
memory system.)
3. How do we minimize power consumption?
(In battery-powered applications, power consumption is extremely important, Even
in non battery applications, excessive power consumption can increase heat
dissipation.)
1. How do we design for upgradability?
2. Does it really work?

© 2014 UPES
© 2014 UPES
ES LIFE CYCLE:
1. Need/opportunity
2. Concept development
3. Manufacturing process design
4. Production
5. Deployment
6. Support/maintenance
7. Upgrades
8. Retirement/Disposals

© 2014 UPES
ES DESIGN PROCESS

© 2014 UPES
Types of ES
 Similar to general computing ex: PDA, Video games, STBs, ATM
 Control Systems ex: feedback control of real time systems, vehicle engines,
Flight control, nuclear reactors.
 Signal Processing ex: Radar, Sonar, DVD Players.
 Communication n Networking ex: Cell phones, Internet applications
Architecture of computer in ES
• It should be Harvard n not van numen (reasons r explained in sample q’s)
As it supports instruction pipelining.

© 2014 UPES
Design Metrics
• Power Dissipation
• Performance
• Process Deadlines
• User Interfaces
• Size
• Engineering cost
• Manufacturing cost
• Flexibility
• Prototype development Time
• Time-to- market System
• User safety Maintenance

8 © 2014 UPES
Software Design Cycle S

9 © 2014 UPES
Hardware/Software Codesign
A definition:

Meeting System level objectives by exploiting


the synergism of hardware and software
through their concurrent design

10
Why codesign?
• Reduce time to market
• Achieve better design
• Explore alternative designs
• Good design can be found by balancing the HW/SW
• To meet strict design constraint
• power, size, timing, and performance trade-offs
• safety and reliability
• system on chip

11
Concurrent design
Traditional design flow Concurrent (codesign)
flow
start

start

HW SW

HW SW
Designed by independent
groups of experts Designed by Same group of
experts with cooperation

12
Typical codesign process

System
Description
Modeling

HW/SW Unified representation


Partitioning

Software Interface Hardware


synthesis synthesis synthesis

System Instruction set level


integration HW/SW evaluation

13
HW/SW Co-design: Main Advantages

• To explore different design alternatives.


• To evaluate cost-performance trade-offs
• To reduce system design time ⇒ Reduction
of product time-to-market and cost
• To improve product quality through design
process optimization
• To support system-level specifications
⇒ To facilitate the reuse of hardware and
software parts.
• To provide an integrated framework for the
synthesis and validation of hardware and
software components.

You might also like