Changeset 275 for anr/section-3.2.tex


Ignore:
Timestamp:
Nov 22, 2010, 10:17:21 PM (14 years ago)
Author:
coach
Message:

Introduced IP-XACT in the coach.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • anr/section-3.2.tex

    r272 r275  
    11% les objectifs scientifiques/techniques du projet.
    22The design steps are presented figure~\ref{coach-flow}.
     3\ADDED{
     4The end-user input is
     5either a HPC application (an application running on a PC that must be accelarate),
     6or an embedded application (a standalone application),
     7or a function of a larger design.}
    38\begin{figure}[hbtp]\leavevmode\center
    49  \includegraphics[width=.8\linewidth]{flow}
     
    1318COACH will allow the user to obtain virtual prototypes for the SoC at different abstraction levels.
    1419The user input will consist of a process network describing the coarse grain parallelism
    15 of the application, an instance of a generic hardware platform
    16 and a mapping of processes on the platform components.
     20of the application, an instance of an architectural template
     21and a mapping of processes on the architectural template components.
    1722COACH will offer different targets to map the processes: 
    1823software (the process runs as a software task on a SoC processor),
    1924ASIP (the process runs as a software task on a SoC processor enhanced with dedicated instructions),
    2025and 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}
     28Once the SoC architecture is validated through performances analysis,
     29COACH will generate automatically an executable containing the host application and
    2330the FPGA bitstream. This bitstream contains
    2431both the hardware architecture and the SoC application software.
    2532The user will be able to launch the application by
    2633loading the bitstream on an FPGA and running the executable on PC.
     34\end{SUPPRESSEDENV}\begin{ADDEDENV}
     35Once the SoC architecture is validated through performances analysis,
     36COACH generates its bitstream in the case of HPC or embedded application,
     37or its IP-XACT description for its integration in the case of a function.
     38Both descriptions contain the hardware architecture and the application software.
     39Furthermore in the HPC case, an executable containing the host application is
     40also generated and the user will be able to launch the application by loading
     41the bitstream on an FPGA and running the executable on PC.
     42\end{ADDEDENV}
    2743\end{description}
    2844 
Note: See TracChangeset for help on using the changeset viewer.