Changeset 31 for anr/section-1.tex
- Timestamp:
- Jan 12, 2010, 3:56:03 PM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
anr/section-1.tex
r25 r31 1 1 % les objectifs globaux, 2 During the se last decades, the design of complex digital systems is more and more reserved2 During the last decades, the design of complex digital systems is more and more reserved to the 3 3 high volume market. Indeed, the design and fabrication costs of submicronic technologies reach highs 4 due to increasing NRE (Non Recurring-Engineering) c harges. The market of digital systems is about4 due to increasing NRE (Non Recurring-Engineering) costs. The market of digital systems is about 5 5 4,600 M\$ today and is estimated to 5,600 M\$ in 2012. 6 Digital system design has been investigated since eighties by using Applications7 Specific Integrated Circuits (ASIC), Digital Signal Process ing(DSP) and parallel computing on6 Digital system design has been investigated since the eighties for Application 7 Specific Integrated Circuits (ASIC), Digital Signal Processors (DSP) and parallel computing on 8 8 multiprocessor machines or networks. Other technologies appeared like Very Large 9 9 Instruction Word (VLIW) and Application Specific Instruction Processors (ASIP). 10 10 Unfortunatly, the ever growing applications' complexity involves higher integration of heterogeneous technologies 11 and thus requieres t o designSystem-on-Chip (SoC) and Multi-Processors SoC (MPSoC).12 Nowadays, Field Programmable Gate Arrays (FPGA), such like Virtex5 from Xilinx13 andStratix4 from Altera, can implement a complete SoC with multiple processors and11 and thus requieres the design of System-on-Chip (SoC) and Multi-Processors SoC (MPSoC). 12 Nowadays, Field Programmable Gate Arrays (FPGA), such as the Virtex5 from Xilinx 13 or the Stratix4 from Altera, can implement a complete SoC with multiple processors and 14 14 several coprocessors for less than 10K euros per device. 15 15 In addition, Electronic System Level (ESL) design methodologies (Virtual Prototyping, 16 Co-design, High-Level Synthesis...) become mature and allow to automatethe design of digital17 systems and to drastically decrease their cost in terms of manpower.16 Co-design, High-Level Synthesis...) is now mature and allow the automation of the design of digital 17 systems and drastically decrease their cost in terms of manpower. 18 18 Thus, coupling both FPGA and ESL methodologies will soon allow small and medium 19 19 enterprises (SMEs) and major companies to get into new, low and medium volume markets, … … 23 23 complex digital systems on FPGA devices. A digital system is an application integrated into one or 24 24 several chips. These chips can be embedded in devices such as a personal digital assistant (PDA), 25 a mbiant computing component,wireless sensor network (WSN). They can also be used on a board connected26 to a PC to accelerate an application like in High-Performance Computing (HPC) andin High-Speed Signal25 an ambiant computing component or a wireless sensor network (WSN). They can also be used on a board connected 26 to a PC to accelerate an application as in High-Performance Computing (HPC) or in High-Speed Signal 27 27 Processing (HSSP). 28 28 29 29 COACH will reduce the NRE costs to the design costs (the FPGA device being only a few 30 K\euro) and reduces drastically them. So one can expect that tools targeting FPGA and dedicated to software developpers 30 K\euro) and drastically reduces them. If proper tools, better suited to 31 softaware developers are created, one 32 can expect that FPGA based devices 31 33 will gain market share over Multi-core CPUs and GPUs HPC based solutions. 32 34 Moreover this market can also be boosted by small and even very small new companies … … 37 39 and targeting the area of complex digital systems. This project involves the development of methodologies and 38 40 tools that allows an efficient design space exploration (processors, coprocessors, memories and buses or NoC) 39 of whole systems, bytaking into account different application constraints (power consumption, throughput, latency...).41 of whole systems, while taking into account different application constraints (power consumption, throughput, latency...). 40 42 The project will also optimize an 41 43 important interface, usually not taken into account, between the high-level synthesis and the implementation 42 44 techniques on physical targets and the associated low level tools (logic synthesis and compilation). 43 The flow will allow, from a high-level specification (written inC language), to estimate, analyze, optimize the44 performances and finallyimplement a real architecture. The COACH framework will allow the designer to explore various45 software/hardware partitioning scenario ofthe target application through timing and functional simulations and to45 The design flow will allow, from a high-level specification (written in the C language), to estimate, analyze, optimize the 46 performances and then implement a real architecture. The COACH framework will allow the designer to explore various 47 software/hardware partitioning scenario for the target application through timing and functional simulations and to 46 48 generate automatically both the software and the synthesizable description of the hardware. 47 49 … … 55 57 %the coprocessors, the number and the size of the FIFO communication channels 56 58 Basically, the 3 following architectural templates will be provided: 57 A COACH architectural template based on the MIPS of the TSAR ANR project and a VCI ring bus, 58 An Altera architectural template based on the NIOS and the AVALON bus, 59 \begin{itemize} 60 \item A COACH architectural template based on the MIPS of the TSAR ANR project and a VCI ring bus, 61 \item An Altera architectural template based on the NIOS and the AVALON bus, 59 62 %FIXME 60 63 % The following point has to be confirmed by XILINX 61 64 % Microblaze+OPB => ARM+Amba ??? 62 A Xilinx architectural template based on the MICROBLAZE and the OPB bus. 65 \item A Xilinx architectural template based on the MICROBLAZE and the OPB bus. 66 \end{itemize} 63 67 Moreover, the specification of the application will be independant of both the template 64 68 architecture and the selected technology. 65 \item Design space exploration: The COACH environment will allow t o select and parametrize66 the target architecture, t o define hardware/software partitioning and to profilethe application.67 For each point of design space exploration, metrics such as throughput, latency, power consumption,68 area, memory allocation and data locality will be provided.69 \item Design space exploration: The COACH environment will allow the selection and parametrization of 70 the target architecture, the definition of the hardware/software partitioning and the profiling of the application. 71 For each point in the design space, metrics such as throughput, latency, power consumption, 72 silicon area, memory allocation and data locality will be provided. 69 73 This criteria will be evaluated by using virtual prototyping and high-level estimation methodologies. 70 \item Hardware accelerators synthesis (HAS): COACH will allow t o generate automaticallyhardware accelerators74 \item Hardware accelerators synthesis (HAS): COACH will allow the automatic generation of hardware accelerators 71 75 when required. Hence, High-Level Synthesis (HLS) tools, ASIP design environement and 72 76 source-level transformations (loop transformations and memory optimisation) will be provided. 73 This will allow to further explorethe micro-architectural design space.77 This will allow further exploration of the micro-architectural design space. 74 78 HLS tools are sensitive to the coding style of the input specification and the domain they target (control vs. 75 data dominated). The HLS tools of COACH will support a common language and coding style to avoid engineering 76 work to the designer. 79 data dominated). The HLS tools of COACH will support a common language and coding style to avoid re-engineering by the designer. 77 80 \item Communication interface: Coach will define and implement HW/SW communication management and define APIs 78 81 enabling communication between processors, processor/coprocessors, FPGA and PC. … … 83 86 %FIXME licence a speficier 84 87 85 COACH will be designed to abstract the hardware as much as possible tothe end user.88 The COACH tools will be designed to hide the hardware as much as possible from the end user. 86 89 It will thus be mainly dedicated to system designers. 87 90 … … 109 112 The main steps of this project are: 110 113 1) Definition of the user inputs: application description as set of communicating tasks, each 111 task beeing described in C++ language; architectural template with its parameters; design constraints.114 task beeing described in the C++ language; architectural template with its parameters; design constraints. 112 115 2) Definition of the internal \xcoach format for representing a task. 113 116 3) Development of a GCC pluggin for generating the \xcoach representation of a C++ task. 114 117 4) Adaptation of the existing HLS tools to read and write the \xcoach format. This will allow to 115 swap from one tool to an 116 5) Modification of the Design System eXplorator DSXof the SocLib platform to let the user118 swap from one tool to another one and to chain them. 119 5) Modification of the Design System eXplorator (DSX) of the SocLib platform to let the user 117 120 explore the design space and then to generate the bitstream. 118 121 %FIXME : a completer … … 126 129 127 130 The COACH arhitectural templates will be freely distributed for non commercial use. 128 COACH will be developped under the General Public Licence for the software tools.131 The software tools of COACH will be developped under the General Public Licence. 129 132
Note: See TracChangeset
for help on using the changeset viewer.