ch11_031102 - Embedded Systems Design: A Unified...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
1 Embedded Systems Design: A Unified Hardware/Software Introduction Chapter 11: Design Technology
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis Outline Automation: synthesis Verification: hardware/software co-simulation Reuse: intellectual property cores Design process models
Background image of page 2
3 Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis Design task Define system functionality Convert functionality to physical implementation while Satisfying constrained metrics Optimizing other design metrics Designing embedded systems is hard Complex functionality Millions of possible environment scenarios Competing, tightly constrained metrics Productivity gap As low as 10 lines of code or 100 transistors produced per day Introduction
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis Improving productivity Design technologies developed to improve productivity We focus on technologies advancing hardware/software unified view Automation Program replaces manual design Synthesis Reuse Predesigned components Cores General-purpose and single-purpose processors on single IC Verification Ensuring correctness/completeness of each design step Hardware/software co-simulation Reuse Specification Implementation Automation Verification
Background image of page 4
5 Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis Automation: synthesis Early design mostly hardware Software complexity increased with advent of general-purpose processor Different techniques for software design and hardware design Caused division of the two fields Design tools evolve for higher levels of abstraction Different rate in each field Hardware/software design fields rejoining Both can start from behavioral description in sequential program model 30 years longer for hardware design to reach this step in the ladder Many more design dimensions Optimization critical Implementation Assembly instructions Machine instructions Logic gates Logic equations / FSM's Register transfers Sequential program code (e.g., C, VHDL) Compilers (1960s,1970s) Assemblers, linkers (1950s, 1960s) Behavioral synthesis (1990s) RT synthesis (1980s, 1990s) Logic synthesis (1970s, 1980s) Microprocessor plus program bits VLSI, ASIC, or PLD implementation The codesign ladder
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis Hardware/software parallel evolution Software design evolution Machine instructions Assemblers convert assembly programs into machine instructions Compilers translate sequential programs into assembly Hardware design evolution Interconnected logic gates Logic synthesis converts logic equations or FSMs into gates Register-transfer (RT) synthesis converts FSMDs into FSMs, logic equations,
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 57

ch11_031102 - Embedded Systems Design: A Unified...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online