Hardware-SoftwareCodesign软硬体共同设计.pptVIP

State of CodesignTechnology Current use limited by: Lack of a standardized representation Lack of good validation and evaluation methods Possible solutions: Extend existing hardware/software languages to the use of heterogeneous paradigms Extend formal verification techniques to the HW/SW domain Issues and Problems:Integration Errors in hardware and software design become much more costly as more commitments are made “Hardware first” approach often compounds software cost because software must compensate for hardware inadequacies 1 2 3 4 25 50 75 100 Relative Prog. Cost / Instr. % Util. of speed and mem capacity Experience Folklore Software Cost Impact of Inadequate Hardware Resources This slide shows where the Hardware/Software Codesign and Partitioning process fits into the RASSP design flow. The goals of this module are to present what hardware/software codesign and partitioning is, what the benefits of truly integrated codesign are, and how industry and research groups are attempting to automate parts of the codesign process. The common definitions for HW/SW codesign is presented above. The two key concepts involved in codesign are concurrent development of HW and SW, and integrated design. Integrated design allows interaction between the design of HW and SW. Codesign techniques using these two key concepts take advantage of design flexibility to create systems that can meet stringent performance requirements with a shorter design cycle. [DeMicheli97],[Franke91],[Kumar95],[Subrahmanyam93] The major factor driving the need for hardware/software codesign is the fact that most systems today include both dedicated hardware units and software units executing on microcontrollers or general purpose processors. The increasing use of programmable processors being used in systems that formerly may have been all hardware, the availability of cheap microcontrollers for use in embedded systems, the availability of processors cores that can be easily embedded into an