Changeset 46


Ignore:
Timestamp:
Jan 29, 2010, 12:03:56 AM (14 years ago)
Author:
coach
Message:
 
Location:
anr
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • anr/anr.tex

    r45 r46  
    2121\def\xcoachplus{\texttt{xcoach+}\xspace}
    2222\def\backbone{backbone infrastructure\xspace}
     23\def\Backbone{Backbone infrastructure\xspace}
    2324
    2425%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
  • anr/section-2.tex

    r38 r46  
    5858\begin{itemize}
    5959\item
    60 Design space exploration: It consists in analysing the application runnig
     60\textbf{Design space exploration}: It consists in analysing the application runnig
    6161on FPGA, defining the target technology (SoC, MPSoC, ASIP, ...) and
    6262hardware/software partitioning of tasks depending on technology choice.
     
    6464consumption criteria.
    6565\item
    66 Micro-architectural exploration: When hardware components are required, the
     66\textbf{Micro-architectural exploration}: When hardware components are required, the
    6767HLS tools of the framework generate them automatically. At this stage the
    6868framework provides various HLS tools that allow the micro-architectural space
     
    7575
    7676\item
    77 Performance measurement: For each point in the design space,
     77\textbf{Performance measurement}: For each point in the design space,
    7878figures of merit are available such as throughput, latency, power
    7979consumption, area, memory allocation and data locality. They are evaluated
    8080using virtual prototyping, estimation or analyzing methodologies.
    8181\item
    82 Targeted hardware technology: The COACH description of a system is
     82\textbf{Targeted hardware technology}: The COACH description of a system is
    8383independent of the FPGA family.  Every point of the design
    8484space can be implemented on any FPGA having the required resources.
     
    9393COACH is the result of the will of several laboratories to unify their knowhow
    9494and skills in the following domains: Operating system and hardware
    95 communication (\tima, \citi), SoC and MPSoC (\upmc and \tima), ASIP (\irisa) and
     95communication (\tima, \upmc), SoC and MPSoC (\upmc and \tima), ASIP (\irisa) and
    9696HLS (\upmc, \ubs) and compilation (\irisa, \lip).
    9797The project objective is to integrate these various domains into a unique
  • anr/section-4.1.tex

    r38 r46  
    6969is done through \verb!CSG! (figure~\ref{archi-csg}).
    7070\vspace*{.75ex}\par
     71\mustbecompleted{FIXME == MODIFICATION DE LA FIGURE}
    7172The project is split into 8 tasks numbered from 0 to 7.
    7273The first task (task 0) is the project management, the last one (task 7) is
    7374the dissemination the other task are listed below:
    7475\begin{enumerate}
    75 \item\textbf{\backbone:} This task tackles the fundamental points of the
     76\item\textbf{\Backbone:} This task tackles the fundamental points of the
    7677        project such as the defintion of the COACH inputs and outputs,
    7778    the internal formats (e.g. \xcoach), the architectural templates and
    7879    the design flow.
    79 \item\textbf{system generation:} This task addresses the prototyping and
     80\item\textbf{System generation:} This task addresses the prototyping and
    8081    the generation of digital system. Apart from HAS that belong to the task 3
    8182    and 4, its components are those presented figure~\ref{archi-csg}
Note: See TracChangeset for help on using the changeset viewer.