Design Codesign of Embedded Systems Evolution of DigitalDesign

Design & Co-design of Embedded Systems Evolution of Digital-Design: Past, Present, and Future Maziar Goudarzi 2005 Design & Co-design of Embedded Systems

Topics of Discussion Why Digital? Evolution of Digital Design Methods and Tools HDL vs. SDL What’s a System? Hardware/Software Co-design 2005 Design & Co-design of Embedded Systems 2

Why Digital? Analog Digital – Analog – Fully digital IO inputs/outputs – Discrete in time and – Continuous in time value or value – Independent from – Sensitive to environment – Always reproducible – No reproducible – Relatively slow state and result – Fast Digital view of the world is an abstract view of real world. 2005 Design & Co-design of Embedded Systems 3

Evolution of Digital Design Methods Transistor Netlist 1970’s 2005 Design & Co-design of Embedded Systems 4

Evolution of DDM (cont. ) RT level, Schematic 1980’s 2005 RT level: Register Transfer level Design & Co-design of Embedded Systems 5

Evolution of DDM (cont. ) BL, HDL 1990’s 2005 Design & Co-design of Embedded Systems BL: Behavioral Level, HDL: Hardware Description Language 6

HDL vs. SDL: Requirements 2005 HDL’s SDL’s Hardware. C Verilog AHDL VHDL C Pascal ADA Design & Co-design of Embedded Systems 7

HDL vs. SDL: Realization Hardware Program Software Program Compilation Synthesis Operating System 2005 Design & Co-design of Embedded Systems 8

HDL vs. SDL: Features Any SW-realizable algorithm is HW-realizable as well. Hardware Realization Software Realization – Speed – Energy Efficiency – Cost Efficiency (in high volumes) 2005 – Flexibility – Ease of Development – Ease of Test and Debug – Cost = SW + Processor Design & Co-design of Embedded Systems 9

Topics of Discussion Why Digital? Evolution of Digital Design Methods and Tools HDL’s vs. SDL’s What’s a System? Hardware/Software Co-design 2005 Design & Co-design of Embedded Systems 10

What’s a System? Examples System 2005 Design & Co-design of Embedded Systems 11

What’s a System? Customer’s view: System = User/Customer-specified functionality + requirements in terms of: Cost, Speed, Power, Dimensions, Weight, … Designer’s view: System = HW components +SW modules 2005 Design & Co-design of Embedded Systems 12

What’s a System? Examples Arvand’s RCU (Robot Control Unit) – Functionality Motors – Motion motors – Steering motors Sensors – Touch sensors – Infra-Red sensors Arvand Robots Sharif CE Middle-Size Soccer Robots 2005 – Requirements Design & Co-design of Embedded Systems Dimensions Power 13

System Realization: An Example Full SW RCU – – HW/SW Compound RCU Sole HW: Motherboard SW: non-terminating loops for image processing, sensor enabling and readout, and motors + playing strategy – HW: Motherboard + RCU Sensor enabling Micro-controller – SW: Full HW RCU – HW: Motherboard + RCU All sensor/motor handling SW on motherboard: image processing, strategy, downward communication SW on RCU: motor control, sensor readout, upward communication. – SW: Non-terminating loop only for image, strategy, and downward communication 2005 Design & Co-design of Embedded Systems 14

HW-SW Co-design How much SW + how much HW? Objectives: – Power – Speed – Area – Memory space – Time-to-market Implementation platform: – Collection of chips on a board (MCM) – Distributed Multi-processor 2005 Design & Co-design of Embedded Systems 15

Co-design Main Topics Synthesis System H System S OS Specification 2005 Design & Co-design of Embedded Systems Verification 16

System Specification Verification Co-Synthesis Partitioning HW Parameter Estimation SW Parameter Estimation HW Synthesis Verification SW Synthesis Verification ASIC OS EXE Code 2005 System Integration Design & Co-design of Embedded Systems Verification 17 Final Verification

What we learned today Hardware and software functionally equivalent – Non-functional requirements determine HW/SW implementation Next step toward higher abstracions: HWSW Co-design – Examples – Classification of issues – A typical co-design flow 2005 Design & Co-design of Embedded Systems 18