Changeset 81 for anr/section-1.tex
- Timestamp:
- Feb 3, 2010, 2:24:04 PM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
anr/section-1.tex
r68 r81 12 12 Virtex5 family from \xilinx or the Stratix4 family from \altera, can nowadays 13 13 implement a complete MPSoC with multiple processors and several 14 coprocessors for few keuros per device.14 coprocessors for a few keuros per device. 15 15 In addition, Electronic System Level (ESL) design methodologies (Virtual Prototyping, 16 16 Co-design, High-Level Synthesis...) are now mature and allow the automation of … … 24 24 SoCLib infrastructure~\cite{soclib}, and optimized for the design of 25 25 multi-processors digital systems targetting FPGA devices. 26 Such digital system are generally integrated27 into one or several chips, and there istwo types of applications:26 Such digital systems are generally integrated 27 into one or several chips, and there are two types of applications: 28 28 It can be embedded (autonomous) applications 29 29 such as personal digital assistants (PDA), ambiant computing components … … 79 79 Coach will define and implement an homogeneous HW/SW communication infrastructure and 80 80 communication APIs (Application Programming Interface). 81 These laters are on 81 These laters are on-chip communications between processors and coprocessors, 82 82 and external communications between the FPGA and the host PC. 83 83 \end{description} … … 122 122 extension of the SoCLib platform. 123 123 \par 124 The main development of the COACH project stepsare:124 The main development steps of the COACH project are: 125 125 \begin{enumerate} 126 126 \item Definition of the end user inputs: … … 142 142 \end{enumerate} 143 143 \par 144 The two major FPGA companies \altera and \xilinx are participating tothis144 The two major FPGA companies \altera and \xilinx are participating in this 145 145 project to support the partners providing the software technologies, and to 146 146 help to generate efficient bitsream for both FPGA families.
Note: See TracChangeset
for help on using the changeset viewer.