Changeset 46 for anr/section-2.tex
- Timestamp:
- Jan 29, 2010, 12:03:56 AM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
anr/section-2.tex
r38 r46 58 58 \begin{itemize} 59 59 \item 60 Design space exploration: It consists in analysing the application runnig60 \textbf{Design space exploration}: It consists in analysing the application runnig 61 61 on FPGA, defining the target technology (SoC, MPSoC, ASIP, ...) and 62 62 hardware/software partitioning of tasks depending on technology choice. … … 64 64 consumption criteria. 65 65 \item 66 Micro-architectural exploration: When hardware components are required, the66 \textbf{Micro-architectural exploration}: When hardware components are required, the 67 67 HLS tools of the framework generate them automatically. At this stage the 68 68 framework provides various HLS tools that allow the micro-architectural space … … 75 75 76 76 \item 77 Performance measurement: For each point in the design space,77 \textbf{Performance measurement}: For each point in the design space, 78 78 figures of merit are available such as throughput, latency, power 79 79 consumption, area, memory allocation and data locality. They are evaluated 80 80 using virtual prototyping, estimation or analyzing methodologies. 81 81 \item 82 Targeted hardware technology: The COACH description of a system is82 \textbf{Targeted hardware technology}: The COACH description of a system is 83 83 independent of the FPGA family. Every point of the design 84 84 space can be implemented on any FPGA having the required resources. … … 93 93 COACH is the result of the will of several laboratories to unify their knowhow 94 94 and skills in the following domains: Operating system and hardware 95 communication (\tima, \ citi), SoC and MPSoC (\upmc and \tima), ASIP (\irisa) and95 communication (\tima, \upmc), SoC and MPSoC (\upmc and \tima), ASIP (\irisa) and 96 96 HLS (\upmc, \ubs) and compilation (\irisa, \lip). 97 97 The project objective is to integrate these various domains into a unique
Note: See TracChangeset
for help on using the changeset viewer.