source: anr/section-5.tex @ 289

Last change on this file since 289 was 285, checked in by coach, 14 years ago

Added FIXME.

File size: 7.8 KB
Line 
1\subsection{Dissemination}
2
3The COACH project will bring new scientific results in various fields, such as high level synthesis,
4hardware/software codesign, virtual prototyping, hardware oriented compilation techniques,
5automatic parallelisation, etc. These results will be published in relevant International
6Conferences, namely DATE, DAC, or ICCAD.
7
8More generally, the COACH infrastructure and the design flow supported by the COACH
9tools and libraries will be promoted by proposing tutorials on FPGA oriented system level synthesis
10in various worshops and conferences (DATE, DAC, CODES+ISSS...).
11
12Several COACH partners being members of the HiPEAC European Network of Excellence
13(High Performance and Embedded Architecture and Compilation), courses will be proposed for the
14HiPEAC summer school on Advanced Computer Architecture and Compilation for Embedded Systems.
15
16Following the general policy of the SoCLib platform, the COACH project will be an
17open infrastructure, and the COACH tools and libraries will be available in the framework
18of the SoCLib WEB server. This server will be maintened by the UPMC/LIP6 laboratory.
19
20\subsection{Exploitation of results}
21
22The main goal of the COACH project is to help SMEs (Small and Medium Enterprises)
23to enter the world of MPSoC technologies. For small companies, the cost is a primary concern.
24Moreover, these companies have not always in-home expertise in hardware design and VHDL modelling.
25As the fabrication costs of an ASIC is generally too high for SMEs, the COACH project focus
26on FPGA technologies. Regarding the design tools, the cost of advanced ESL (Electronic System Design)
27tools is an issue, and the COACH project will follow the same general policy as the SoCLib platform :
28
29\begin{itemize}
30\item
31All software tools supporting the COACH design flow will be available as free software.
32All academic partners contributing to the COACH project agreed to distribute the ESL software
33tools under the same GPL license as the SoCLib tools. 
34\item
35The SystemC simulation models for the hardware components
36used by the SoCLib architectural template will be distributed as free software
37under a non-contaminant LGPL license.
38\item
39The synthesizable VHDL models supporting the neutral architectural template
40(corresponding to the SocLib IP cores library), will have two modes of dissemination.
41A typical MPSoC contains not only dedicated, synthesized coprocessors. It contains
42also general purpose, reusable components, such as processor cores, memory controllers
43optimised cache controllers, peripheral controllers, or bus controllers.
44For non commercial use (i.e. research or education in an academic context, 
45or feasibility study in an industrial context), the synthesizable VHDL models will be freely available.
46For commercial use, commercial licenses will be negotiated between the owners and the customers.
47\item
48The proprietary \altera and \xilinx IP core libraries are commercial products
49that are not involved by the free software policy, but these libraries will be supported by the
50synthesis tools developed in the COACH project.
51\end{itemize}
52
53This general approach is supported by a large number (\letterOfInterestNb) of SMEs, as
54demonstrated by the "letters of interest" that have been collected during the preparation
55of the project and presented in annexe~\ref{lettre-soutien}.
56
57\subsection{Indusrial Interest in COACH}
58
59\subsubsection*{Partner: \textit{\mds}}
60
61\mustbecompleted{A COMPLETER: Emmanuel ....}
62
63\subsubsection*{Partner: \textit{\bull}}
64The team of \bull participating to the COACH project is from the Server Development
65Department who is in charge of developing hardware for open servers (e.g. NovaScale) and
66HPC solutions. The main expectation from COACH is to derive a new component (fine-grain
67FPGA parallelism) to add to existing Bull HPC solutions.
68
69%\subsubsection*{Partner: \textit{\xilinx}}
70%Computing power potential of our FPGA architectures
71%growing very quickly on one side, and complexity of designs implemented
72%using our FPGAs dramatically increasing on the other side, it is very
73%interesting for us to get high level design methodologies progressing
74%quickly and targetting our FPGAs in the most possible efficient way.
75%\parlf
76%\xilinx goal is to get COACH to generate bitstream optimized as much as possible for
77%\xilinx FPGAs in order to both, validate the methodology on our FPGA families, and ease
78%future work of our customers.
79
80\subsubsection*{Partner: \textit{\thales}}
81\noindent
82\thales has two main reasons to use the COACH platform:
83\begin{itemize}
84  \item The huge increase of the complexity of the systems in particular by their
85  heterogeneity, raises the issues of design cost and time in the same proportion. The
86  divisions need a design tool which supports the implementation of the applications from
87  algorithm description to the executable code on platforms composed of several general
88  purpose processors and dedicated IPs.
89  \item The applications are more and more complex and adaptable to the environment which
90  leads to a mixture of control aspects and data stream computing aspects. A new approach
91  is necessary to be able to describe this type of application and manage the high level
92  synthesis of system embedding control and data flow aspects.
93\end{itemize}
94\parlf
95TRT (Thales Research and Technology) has the mission to assess and de-risk the emerging
96technologies in its domains of expertise. Specifically in COACH, the studied technology is
97a method and associated tools to make the bridge between application capture at system
98level and the implementation on heterogeneous distributed computing architectures. The
99main stake for Thales behind this is the future design process that will be applied to its
100system teams in the future for the computation-intensive sensor applications. In a context
101of very instable market of tools for parallel programming, it is important to experiment
102and demonstrate the candidate technologies.
103\\
104In its role of internal dissemination, TRT will make the demonstration of the full design
105flow within Thales, and will keep available a platform to later evaluate additional
106applications coming from the Business Units.
107\\
108The COACH platform will be used in the new \thales products in which the algorithms are more
109and more dependent of the environment and have to permanently adapt their behavior in
110varying environments. The target markets are the critical infrastructures security and
111border monitoring.
112
113\subsubsection*{Industrial supports}
114
115\mustbecompleted{NON A JOUR}
116The following SMEs demonstrate interest to the COACH project (see the "letters of
117interest" in annexe~\ref{lettre-soutien}) and will follow the COACH evolution and will
118evaluate it:
119\letterOfInterest{ALTERA Corporation}{lettres/Altera1.pdf},
120\letterOfInterestPlus{lettres/Altera2.pdf}
121\letterOfInterest{ADACSYS}{lettres/Coach_ADACSYS_lettre_interet},
122\letterOfInterest{MAGILLEM Design Services}{lettres/Coach_lettre_interet_MDS},
123\letterOfInterest{INPIXAL}{lettres/inpixal.jpg},
124\letterOfInterest{CAMKA System}{lettres/CAMKA-System.pdf},
125\letterOfInterest{ATEME}{lettres/ATEME.pdf},
126\letterOfInterest{ALSIM Simulateur}{lettres/Alsim.pdf},
127\letterOfInterest{SILICOMP-AQL}{lettres/itlabs.pdf},
128\letterOfInterest{ABOUND Logic}{lettres/abound.pdf},
129\letterOfInterest{EADS-ASTRIUM}{lettres/Astrium1.pdf}.
130\letterOfInterestPlus{lettres/Astrium2.pdf}
131
132\letterOfInterestClose
133
134\subsection{Management of Intellectual Property}
135A global consortium agreement will be defined during the first six monts of the project.
136As already stated, the COACH project has been prepared during one year by a monthly meeting
137involving the five academic partners. The general free software policy described in the
138previous section has been agreed by academic partners  and has been
139approved by all industrial participants. This free software policy will
140simplify the definition of the consortium agreement.
141
Note: See TracBrowser for help on using the repository browser.