Changeset 307 for anr/section-issues.tex
- Timestamp:
- Jan 13, 2011, 7:14:58 PM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
anr/section-issues.tex
r289 r307 6 6 indicateurs de réduction de coûts, perspectives de marchés (champs 7 7 dâapplication, âŠ). Indicateurs des gains environnementaux, cycle de vie.} 8 9 8 % 9 \subsubsection*{Predominance of FPGA in the global electronic market} 10 10 \begin{table}\leavevmode\center 11 11 \begin{small}\begin{tabular}{|l|l|l|l|}\hline … … 38 38 Consequently, it is more and more unaffordable to design and fabricate ASICs for low and medium 39 39 volume markets. 40 \parlf 40 % 41 \subsubsection*{FPGAs and Embedded Systems} 41 42 Today, FPGAs become important actors in the computational domain that was originally dominated 42 43 by microprocessors and ASICs. Just like microprocessors, FPGA based systems can be reprogrammed … … 59 60 %This boosts the developpment of automatic design tools and methodologies. 60 61 % 61 \ parlf62 \subsubsection*{FPGAs and High Performance Computing} 62 63 Today, several companies (Atipa, blue-arc, Bull, Chelsio, Convey, CRAY, DataDirect, DELL, hp, 63 64 Wild Systems, IBM, Intel, Microsoft, Myricom, NEC, nvidia etc) are making systems where demand … … 70 71 This market is dominated by Multi-core CPUs and GPUs based solutions and the expansion 71 72 of FPGA-based solutions is limited by the lack of design automation. 72 \\ 73 \\ 73 % 74 \subsubsection*{Evolution of architectures} 75 Nowadays processors mixing core and programmable matrix are available on the market (eg. Intel ATOM E600C). 76 "Donald Newell, AMD technical manager, envisions that such circuits will be at the heart of most of the electronic 77 products (eg. PDAs and nomad items) and even personal computers. 78 To take benefit of such architecture, developping and deploying application will require innovative codesign methods and tools. 79 80 % 81 \subsubsection*{COACH's contribution to this evolution} 74 82 Nowadays, there are no commercial or academic tools covering the whole design flow 75 83 from the system level specification to the bitstream generation neither for embedded system design 76 84 nor for HPC. 77 78 %PC => IA et Alain79 %Le paragraphe ci dessous n'a rien a faire dans la partie Economic et societal issue80 %Je le mets donc en commentaire81 82 %By using SOPC Builder~\cite{spoc-builder} from \altera, designers can select and83 %parameterize components from an extensive drop-down list of IP cores (I/O core, DSP,84 %processor, bus core, ...) as well as incorporate their own IP.85 %Designers can then generate a synthesized netlist, simulation test bench and custom86 %software library that reflect the hardware configuration.87 %Nevertheless, SOPC Builder does not provide any facilities to synthesize coprocessors and to88 %simulate the platform at a high design level (systemC).89 %In addition, SOPC Builder is proprietary and only works together with \altera's Quartus compilation90 %tool to implement designs on \altera devices (Stratix, Arria, Cyclone).91 %PICO~\cite{pico} and CATAPULT-C~\cite{catapult-c} allow to synthesize92 %coprocessors from a C++ description.93 %Nevertheless, they can only deal with data dominated applications and they do not handle94 %the platform level.95 %Similarly, the System Generator for DSP~\cite{system-generateur-for-dsp} is a plug-in to96 %Simulink that enables designers to develop high-performance DSP systems for \xilinx FPGAs.97 %Designers can design and simulate a system using MATLAB and Simulink. The tool will then98 %automatically generate synthesizable Hardware Description Language (HDL) code mapped to99 %\xilinx pre-optimized macro-cells.100 %However, this tool targets only DSP based algorithms.101 %\\102 %Consequently, a designer developping an embedded system needs to master four different103 %design environments:104 %\begin{enumerate}105 % \item a virtual prototyping environment such as SoCLib for system level exploration,106 % \item an architecture compiler (such as SOPC Builder from \altera, or System generator107 % from \xilinx) to define the hardware architecture,108 % \item one or several HLS tools (such as PICO~\cite{pico} or CATAPULT-C~\cite{catapult-c}) for109 % coprocessor synthesis,110 % \item and finally backend synthesis tools (such as Quartus or Synopsys) for the bit-stream generation.111 %\end{enumerate}112 %Furthermore, mixing these tools requires an important interfacing effort and this makes113 %the design process very complex and achievable only by designers skilled in many domains.114 115 85 \begin{center}\begin{minipage}{.9\linewidth}\textit{ 116 86 The aim of the COACH project is to integrate all these design steps into a single design framework 117 87 and to allow \textbf{pure software} developpers to design embedded systems. 118 88 }\end{minipage}\end{center} 119 120 %PC => IA et Alain 121 % le paragraphe suivant est coupé collé de la section suivante 2.2 122 123 124 \parlf 89 % 125 90 The COACH project proposes an open-source framework for mapping multi-tasks software applications 126 91 on Field Programmable Gate Array circuits (FPGA).
Note: See TracChangeset
for help on using the changeset viewer.