Changeset 275 for anr/section-3.2.tex
- Timestamp:
- Nov 22, 2010, 10:17:21 PM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
anr/section-3.2.tex
r272 r275 1 1 % les objectifs scientifiques/techniques du projet. 2 2 The design steps are presented figure~\ref{coach-flow}. 3 \ADDED{ 4 The end-user input is 5 either a HPC application (an application running on a PC that must be accelarate), 6 or an embedded application (a standalone application), 7 or a function of a larger design.} 3 8 \begin{figure}[hbtp]\leavevmode\center 4 9 \includegraphics[width=.8\linewidth]{flow} … … 13 18 COACH will allow the user to obtain virtual prototypes for the SoC at different abstraction levels. 14 19 The user input will consist of a process network describing the coarse grain parallelism 15 of the application, an instance of a generic hardware platform16 and a mapping of processes on the platformcomponents.20 of the application, an instance of an architectural template 21 and a mapping of processes on the architectural template components. 17 22 COACH will offer different targets to map the processes: 18 23 software (the process runs as a software task on a SoC processor), 19 24 ASIP (the process runs as a software task on a SoC processor enhanced with dedicated instructions), 20 25 and hardware (the process is implemented as a synthesized hardware coprocessor). 21 \item[Application compilation:] Once the SoC architecture is validated through performances 22 analysis, COACH will generate automatically an executable containing the host application and 26 \item[Application compilation:] 27 \begin{SUPPRESSEDENV} 28 Once the SoC architecture is validated through performances analysis, 29 COACH will generate automatically an executable containing the host application and 23 30 the FPGA bitstream. This bitstream contains 24 31 both the hardware architecture and the SoC application software. 25 32 The user will be able to launch the application by 26 33 loading the bitstream on an FPGA and running the executable on PC. 34 \end{SUPPRESSEDENV}\begin{ADDEDENV} 35 Once the SoC architecture is validated through performances analysis, 36 COACH generates its bitstream in the case of HPC or embedded application, 37 or its IP-XACT description for its integration in the case of a function. 38 Both descriptions contain the hardware architecture and the application software. 39 Furthermore in the HPC case, an executable containing the host application is 40 also generated and the user will be able to launch the application by loading 41 the bitstream on an FPGA and running the executable on PC. 42 \end{ADDEDENV} 27 43 \end{description} 28 44
Note: See TracChangeset
for help on using the changeset viewer.