2. 1

3.  Staunstrup and Wolf Ed. “Hardware Software codesign: principles and practice”, Kluwer Publication, 1997  Gajski, Vahid, Narayan and Gong, “Specification, Design of Embedded Systems”, Prentice Hall, 1994  Suggested papers in the class web 2

4. Digital systems designs consists of hardware components and software programs that execute on the hardware platforms Hardware-Software Co design ? 3

5.  Better device technology  reduced in device sizes  more on chip devices > higher density  higher performances 4

6.  Higher degree of integration  increased device reliability  inclusion of complex designs 5

7. Judged by its objectives in application domain  Performance  Design and Manufacturing cost  Ease of Programmability 6

8. Judged by its objectives in application domain  Performance  Design and Manufacturing cost  Ease of Programmability It depends on both the hardware and software components 7

9.  Key concepts  Concurrent: hardware and software developed at the same time on parallel paths  Integrated: interaction between hardware and software developments to produce designs that meet performance criteria and functional specifications 8 The meeting of system-level objectives by exploiting the trade-offs between hardware and software in a system through their concurrent design

10. Traditional design flowConcurrent (codesign) flow 9 HW SW start HWSW Designed by independent groups of experts Designed by Same group of experts with cooperation

11. Trend toward smaller mask-level geometries leads to:  Higher integration and cost of fabrication. Suggestion: Use software as a means of differentiating products based on the same hardware platform. 10

12. Traditionally  Hardware used to be configured at the time of manufacturing  Software is variant at run time 11 The Field Programmable Gate Arrays (FPGA) has blurred this distinction.

13.  FPGA circuits can be configured on-the-fly to implement a specific software function with better performance than on microprocessor. 12

14.  FPGA circuits can be configured on-the-fly to implement a specific software function with better performance than on microprocessor.  FPGA can be reprogrammed to perform another specific function without changing the underlying hardware. 13

15.  FPGA circuits can be configured on-the-fly to implement a specific software function with better performance than on microprocessor.  FPGA can be reprogrammed to perform another specific function without changing the underlying hardware. This flexibility opens new applications of digital circuits. 14

16.  Reduce time to market 15

17.  Reduce time to market  Achieve better design ▪ Explore alternative designs ▪ Good design can be found by balancing the HW/SW 16

18.  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 17

19.  Interrelated criteria for a system design 18 Hardware Technology Level of Integration Degree of Programmability Application Domain

20.  General purpose computing system ▪ usually self contained and with peripherals ▪ Information processing systems 19

21.  General purpose computing system ▪ usually self contained and with peripherals ▪ Information processing systems  Dedicated control system ▪ part of the whole system, Ex: digital controller in a manufacturing plant ▪ also, known as embedded systems 20

22.  Uses as small computer to perform certain function  Conceived with specific application in mind ▪ examples: dash controller in autombiles, remote controller for robots, answering machines, etc.  User has limited access to system programming ▪ system is provided with system software during manufacturing ▪ not used as a computer 21 Application-specific systems which contain hardware and software tailored for a particular task and are generally part of a larger system (e.g., industrial controllers)

23.  Banking and transaction processing applications  Automobile engine control units  Signal processing applications  Home appliances (microwave ovens)  Industrial controllers in factories  Cellular communications

24. Most digital systems are programmed by some software programs for functionality. Two important issues related to programming:  who has the access to programming?  Level at which programming is performed. 23

25. Understand the role of: End users, application developers, system integrator and component manufacturers. 24

26. Understand the role of: End users, application developers, system integrator and component manufacturers. Application Developer: System to be retarget able. 25

27. Understand the role of: End users, application developers, system integrator and component manufacturers. Application Developer: System to be retargetable. System Integrator: Ensure compatibility of system components 26

28. Understand the role of: End users, application developers, system integrator and component manufacturers. Application Developer: System to be retargetable. System Integrator: Ensure compatibility of system components Component Manufactures: Concerned with maximizing product reuse 27

29. Example 1: Personal computer End User: Limited to application level Application Dev.: Language tools, Operating System, high-level programming environment (off the self components) Component Manf.: Drive by bus standards, protocols etc. 28 Observe that: coalescing the system components due to higher chip density Result: Few but more versatile system hardware components

30. Embedded Systems  End user: Limited access to programming  Most software is already provided by system integrator who could be application developer too! 29

31.  Systems can be programmed at application, instruction and hardware levels  Application Level: Allows users to specify “option of functionality” using special language.  Example: Programming VCR or automated steering control of a ship 30

32.  Hardware level programmability  Example: Microprogramming (determine the behavior of control unit by microprogram) 31 configuring the hardware (after manufacturing) in the desired way.

33. Microprogramming Vrs. Reconfigurability 32 Microprogram allows to reconfigure the control unit whereas Reconfigurable system can modify both Data path and controller.

34. Microprogramming Vrs. Reconfigurability 33 Microprogram allows reconfigure the control unit versus Reconfigurable system can modify both datapath and controller. Reconfigurability increases usability but not the performance of a system.

35. System Concepts Sys/HW Require. Analysis Sys/SW Require. Analysis Operation. Testing and Eval. Software Require. Analysis Prelim. Design Detailed Design Coding, Unit test., Integ. test SW Development HWCI Testing CSCI Testing System Integ. and test [Franke91] Hardware Require. Analysis Prelim. Design Detailed Design Fabric. HW Development DOD-STD-2167A © IEEE 1991

36. System Concepts Sys/HW Require. Analysis Sys/SW Require. Analysis Hardware Require. Analysis Software Require. Analysis Operation. Testing and Evaluation SW Development HW Development System Integ. and test HWCI Testing CSCI Testing [Franke91] Integrated Modeling Substrate Prelim. Design Prelim. Design Detailed Design Detailed Design Fabric. Coding, Unit test., Integ. test © IEEE 1991

37. 36 System Description HW/SW Partitioning Software synthesis Interface synthesis Hardware synthesis System integration Modeling Unified representation Instruction set level HW/SW evaluation

38. HW-SW system involves  specification  modeling  design space exploration and partitioning  synthesis and optimization  validation  implementation 37

39. Specification ▪ List the functions of a system that describe the behavior of an abstraction clearly with out ambiguity. Modeling: ▪ Process of conceptualizing and refining the specifications, and producing a hardware and software model. 38

40.  Homogeneous: a modeling language or a graphical formalism for presentation ▪ partitioning problem used by the designer  Heterogeneous: multiple presentations ▪ partitioning is specified by the models 39

41. Validation: Process of achieving a reasonable level of confidence that the system will work as designed. 40

42. Implementation: Physical realization of the hardware (through synthesis) and of executable software (through compilation). 41

43.  A hardware/software partitioning represents a physical partition of system functionality into application-specific hardware and software.  Scheduling is to assign an execution start time to each task in a set, where tasks are linked by some relations. 42