Hardware/Software Introduction Chapter 1 Introduction

More documents

Recommendations

Info

Design process model • Describes order that design steps are processed – Behavior description step – Behavior to structure conversion step – Mapping structure to physical implementation step • Waterfall model – Proceed to next step only after current step completed • Spiral model – Proceed through 3 steps in order but with less detail – Repeat 3 steps gradually increasing detail – Keep repeating until desired system obtained – Becoming extremely popular (hardware & software development) Waterfall design model Behavioral Structural Physical Spiral design model Structural Behavioral Physical Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 88
Waterfall method • Not very realistic – Bugs often found in later steps that must be fixed in earlier step • E.g., forgot to handle certain input condition – Prototype often needed to know complete desired behavior • E.g, customer adds features after product demo – System specifications commonly change • E.g., to remain competitive by reducing power, size – Certain features dropped • Unexpected iterations back through 3 steps cause missed deadlines – Lost revenues – May never make it to market Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis Waterfall design model Behavioral Structural Physical 89
Page 1 and 2:
Embedded Systems Design: A Unified
Page 3 and 4:
Embedded systems overview • Embed
Page 5 and 6:
Some common characteristics of embe
Page 7 and 8:
Design challenge - optimizing desig
Page 9 and 10:
Design challenge - optimizing desig
Page 11 and 12:
Time-to-market: a demanding design
Page 13 and 14:
Losses due to delayed market entry
Page 15 and 16:
The performance design metric • W
Page 17 and 18:
Processor technology • The archit
Page 19 and 20:
General-purpose processors • Prog
Page 21 and 22:
Application-specific processors •
Page 23 and 24:
Full-custom/VLSI • All layers are
Page 25 and 26:
PLD (Programmable Logic Device) •
Page 27 and 28:
Graphical illustration of Moore’s
Page 29 and 30:
The co-design ladder • In the pas
Page 31 and 32:
Design productivity gap • 1981 le
Page 33 and 34:
Summary • Embedded systems are ev
Page 35 and 36:
Ch3. GPP: Software Summary • Gene
Page 37 and 38: Ch7. Digital Camera Example Summary
Page 39 and 40: Embedded Systems Design: A Unified
Page 41 and 42: Introduction • Design task - Defi
Page 43 and 44: Automation: synthesis • Early des
Page 45 and 46: Increasing abstraction level • Hi
Page 47 and 48: Gajski’s Y-chart • Each axis re
Page 49 and 50: Two-level minimization • Represen
Page 51 and 52: Minimum cover: K-map approach • K
Page 53 and 54: Minimum cover: heuristics • K-map
Page 55 and 56: Example • Minimized 2-level logic
Page 57 and 58: Technology mapping • Library of g
Page 59 and 60: Integrating logic design and physic
Page 61 and 62: Behavioral synthesis • High-level
Page 63 and 64: System synthesis • Tasks (cont.)
Page 65 and 66: Temporal vs. spatial thinking • D
Page 67 and 68: Verification • Ensuring design is
Page 69 and 70: Simulation • Create computer mode
Page 71 and 72: Advantages over physical implementa
Page 73 and 74: Simulation speed • Relative speed
Page 75 and 76: Reducing precision/accuracy • Don
Page 77 and 78: Integrating GPP/SPP simulations •
Page 79 and 80: Emulators • General physical devi
Page 81 and 82: Reuse: intellectual property cores
Page 83 and 84: Advantages/disadvantages of hard co
Page 85 and 86: New challenges to processor provide
Page 87: New challenges to processor users
Page 91 and 92: General-purpose processor design mo
Page 93 and 94: Summary • Design technology seeks
show all

Hardware/Software Introduction Chapter 1 Introduction

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?