Changeset 182 for anr


Ignore:
Timestamp:
Feb 15, 2010, 4:03:09 PM (15 years ago)
Author:
coach
Message:

UBS

File:
1 edited

Legend:

Unmodified
Added
Removed
  • anr/section-3.2.tex

    r134 r182  
    66\begin{figure}[hbtp]\leavevmode\center
    77  \includegraphics[width=.8\linewidth]{flow}
    8   \caption{\label{coach-flow} COACH flow}
     8  \caption{\label{coach-flow} COACH design flow}
    99\end{figure}
    1010\begin{description}
    1111\item[HPC setup:] During this step, the user splits the application into 2 parts: the host application
    1212which remains on a PC and the SoC application which is mapped on the FPGA.
    13 The COACH framework provides a SystemC simulation model of the whole system (PC+communication+FPGA-SoC) which allows a performance evaluation of the partitioning.
     13The COACH framework will provide a SystemC simulation model of the whole system (PC+communication+FPGA-SoC) which will allow performance evaluation of the partitioning.
    1414\item[SoC design:] In this phase,
    15 the user can obtain simulators for the SoC at different abstraction levels by giving to the COACH framework a SoC description. 
    16 This description consists of a process network corresponding to the SoC application,
     15the user will be able to obtain simulators for the SoC at different abstraction levels by giving to the COACH framework a SoC description. 
     16This description will consist of a process network corresponding to the SoC application,
    1717an OS, an instance of a generic hardware platform
    1818and a mapping of processes on the platform components. The supported mapping are
     
    2020ASIP (the process runs on a SoC processor enhanced with dedicated instructions),
    2121and hardware (the process runs into a coprocessor that is generated by HLS and plugged on the SoC bus).
    22 \item[Application compilation:] Once the SoC description is validated, COACH generates automatically
     22\item[Application compilation:] Once the SoC description is validated, COACH will generate automatically
    2323an FPGA bitstream containing the hardware platform with the SoC application software and
    24 an executable containing the host application. The user can launch the application by
     24an executable containing the host application. The user will be able to launch the application by
    2525loading the bitstream on an FPGA and running the executable on PC.
    2626\end{description}
     
    2929% ambitieux du projet.
    3030%FIXME == {NON ceci n'est pas une contribution scientifique. A re-ecrire}
    31 The main scientific contribution of the project is to unify various synthesis techniques
    32 (same input and output formats) allowing the user to swap without engineering effort
    33 from one to another and even to chain them. For instance, it will be possible to run loop transformations before synthesis.
    34 Another advantage of this framework is to provide different abstraction levels from
    35 a single description.
    36 Finally, this description is device family independent and its hardware implementation
    37 is automatically generated.
     31
     32%The main scientific contribution of the project is to unify various synthesis techniques
     33%(same input and output formats) allowing the user to swap without engineering effort
     34%from one to another and even to chain them. For instance, it will be possible to run loop transformations before synthesis.
     35%Another advantage of this framework is to provide different abstraction levels from
     36%a single description.
     37%Finally, this description is device family independent and its hardware implementation
     38%is automatically generated.
    3839
    3940% Detailler les verrous scientifiques et techniques a lever par la realisation du projet.
    40 System design is a very complicated task and in this project we try to simplify it
     41System design is a very complicated task and in this project we will try to simplify it
    4142as much as possible. For this purpose we have to deal with the following scientific
    4243and technological barriers.
     
    4445\item HLS tools are sensitive to the style in which the algorithm is written.
    4546In addition, they are are not integrated into an architecture and system
    46 exploration tool.
    47 Consequently, engineering work is required to swap from a tool to another,
     47exploration tool. Consequently, engineering work is required to swap from a tool to another,
    4848to integrate the resulting simulation model to an architectural exploration tool
    4949and to synthesize the generated RTL description.
Note: See TracChangeset for help on using the changeset viewer.