Changeset 297 for anr/section-1.tex
- Timestamp:
- Dec 16, 2010, 2:13:23 PM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
anr/section-1.tex
r290 r297 27 27 will allow both SMEs (Small and Medium Enterprise) and major companies to design innovative 28 28 devices and to enter new, low and medium volume markets. 29 \begin{ADDEDENV}30 29 Furthermore, today there is an increasing industrial interest to IC 31 30 that integrates both hardwired CPU cores or MPSoC and a configurable area (FPGA) … … 34 33 general purpose CPU cores will contains a configurable area making explode the low and medium volume 35 34 markets of digital systems. 36 \end{ADDEDENV}37 35 \parlf 38 \begin{SUPPRESSEDENV}39 The objective of COACH is to provide an integrated design flow, based on the40 SoCLib infrastructure~\cite{soclib}, and optimized for the design of41 multi-processors digital systems targeting FPGA devices.42 The digital systems are generally integrated into one or several chips, and there are two types of applications:43 They can be embedded (autonomous) applications44 such as personal digital assistants (PDA), ambient computing components,45 or wireless sensor networks (WSN).46 They can also be extension boards connected to a PC to accelerate a specific computation,47 as in High-Performance Computing (HPC) or High-Speed Signal Processing (HSSP).48 \end{SUPPRESSEDENV}\begin{ADDEDENV}49 36 The objective of COACH is to provide an integrated design flow for the design of 50 37 multi-processors digital systems targeting FPGA devices. … … 57 44 it is the domain of High-Performance Computing (HPC) and High-Speed Signal Processing (HSSP); 58 45 3) sub-system application for generating an IP to a larger system. 59 \end{ADDEDENV}60 46 \parlf 61 47 %verrous scientifiques et techniques … … 70 56 For each point in the design space, metrics such as throughput, latency, power 71 57 consumption, silicon area, memory allocation and data locality will be provided. 72 \begin{SUPPRESSEDENV}73 These criteria will be evaluated by using the SoCLib virtual prototyping infrastructure74 and high-level estimation methodologies.75 \end{SUPPRESSEDENV}76 58 \item[Hardware Accelerators Synthesis (HAS):] 77 59 COACH will allow the automatic generation of hardware accelerators when required. … … 106 88 communications between software tasks running on embedded processors and 107 89 dedicated hardware coprocessors. 108 \begin{ADDEDENV} 109 \item[Interaction with the industrial world] 90 \item[Interaction with the industrial world:] 110 91 COACH will not be a closed framework but it will be opened to the industrial 111 92 world by using the IP-XACT format \cite{IP-XACT-08} for describing the components of the … … 113 94 This should facilitate the enhancement of the architectural template with IP and the 114 95 integration of the IP produced by COACH in larger design. 115 \end{ADDEDENV}116 96 \end{description} 117 \begin{SUPPRESSEDENV}118 MOVED ABOVE119 The COACH design flow will be dedicated to system designers, and will as120 much as possible hide the hardware characteristics to the end-user.121 \end{SUPPRESSEDENV}122 97 %From the end user point of view, the specification of the application will be 123 98 %independant from both the architectural template and from the selected FPGA … … 135 110 ASIP architectures (\irisa), 136 111 High Level Synthesis (\tima, \ubs, \upmc), and compilation (\lip), 137 HPC (\bull, \thales), \mustbecompleted{XXX (\mds)}.112 HPC (\bull, \thales), tools integration in IP-XACT flow (\mds). 138 113 \\ 139 114 The COACH project does not start from scratch. 140 \begin{SUPPRESSEDENV}141 It strongly relies on the SoCLib virtual prototyping platform~\cite{soclib} for prototyping,142 (DSX, component library), operating systems (MUTEKH, DNA/OS).143 It also leverages on several existing technologies:144 on the GAUT~\cite{gaut08} and UGH~\cite{ugh08} tools for HLS,145 on the ROMA~\cite{roma} project for ASIP,146 on the SYNTOL~\cite{syntol} and BEE~\cite{bee} tools for source-level analysis and transformations147 and on the \xilinx and \altera IP core libraries.148 \end{SUPPRESSEDENV}\begin{ADDEDENV}149 115 It relies 116 on the Magillem industrial platform for the integration into IP-XACT flows, 150 117 on the SoCLib platform~\cite{soclib} for prototyping and operating systems (DNA/OS), 151 118 on the GAUT~\cite{gaut08} and UGH~\cite{ugh08} tools for HLS, … … 153 120 on the SYNTOL~\cite{syntol} and BEE~\cite{bee} tools for source-level analysis and 154 121 transformations, 155 on the \mustbecompleted{XXXX:magillem} for \mustbecompleted{XXXX:magillem},156 122 and on the \xilinx and \altera IP core libraries. 157 \end{ADDEDENV}158 123 Finally it will use the \xilinx and \altera logic and physical synthesis tools 159 124 to generate the FPGA configuration bitstreams. 160 \parlf161 The COACH proposal has been prepared during one year by a technical working group162 involving the 5 academic partners (one monthly meeting from january 2009 to february163 2010). The objective was to analyse the issues of integrating164 and enhancing the existing tools and technologies into a unique framework.165 Most of the general software architecture of the proposed design flow (including the166 exchange format specification) has been define by this working group.167 \SUPPRESSED{Because the COACH project leanes on the ANR SoCLib platform, it may be168 described as an extension of the SoCLib platform.}169 125 %The main development steps of the COACH project are: 170 126 %\begin{enumerate} … … 187 143 %\end{enumerate} 188 144 \parlf 189 Two major FPGA companies are involved in the project: \xilinx will contribute190 as a contractual partner providing documentation and manpower; \altera will contribute as191 a supporter (see letter page \pageref{supp:1})192 providing documentation and development boards. These two companies are strongly motivated193 to help the COACH project to generate efficient bitstreams for both FPGA families.194 145 The role of the industrial partners \bull, \thales and \mds is to provide 195 146 real use cases to benchmark the COACH design environment and to analyze the designer productivity 196 147 improvements. 197 148 \parlf 198 \begin{SUPPRESSEDENV} 199 Following the general policy of the SoCLib platform, the COACH project will be an open 200 infrastructure, available in the framework of the SoCLib server. 201 The architectural templates, and the COACH software tools will be distributed under the 202 GPL license. The VHDL synthesizable models for the neutral architectural template (SoCLib 203 IP core library) will be freely available for non commercial use. 204 \end{SUPPRESSEDENV}\begin{ADDEDENV} 205 The COACH project will be an open infrastructure and freely distributed. 206 The architectural templates and the COACH software tools will be distributed under the 207 GPL license. The VHDL synthesizable models for the neutral architectural template 149 The COACH project will deliver an open and freely distributed infrastructure. 150 The architectural templates and most of the software tools will be distributed under the 151 GPL-like license. 152 The VHDL synthesizable models for the neutral architectural template 208 153 will also be freely available for non commercial use. 209 \end{ADDEDENV}210 154 For industrial exploitation the technology providers are ready to propose commercial licenses, 211 155 directly to the end user, or through a third party. 212 156 \parlf 213 157 \mustbecompleted{LIST NON A JOUR} 158 The major FPGA companies (\xilinx and \altera) have expressed their interest for 159 this project. 214 160 Finally, the COACH project is already supported by a large number of SMEs, as demonstrated by the 215 161 "letters of interest" (see Annex B), that have collected during the preparation of the project :
Note: See TracChangeset
for help on using the changeset viewer.