Changeset 315

Timestamp:

Jan 18, 2011, 8:33:56 PM (13 years ago)

Author:

coach

Message:

 

Location:

anr

Files:

• annexe-reponse.tex (modified) (1 diff)
• section-consortium-people.tex (modified) (1 diff)
• section-dissemination.tex (modified) (1 diff)
• section-etat-de-art.tex (modified) (2 diffs)
• section-position.tex (modified) (5 diffs)
• section-ressources.tex (modified) (3 diffs)

anr/annexe-reponse.tex

@@ -20 +20 @@
     les environnements industriels QUARTUS \& ISE.
     \t%\note{O.2}
-    Pour la synthÚse de SoC, on pourrait effectivement utilisé des outils
+    Pour la synthÚse de SoC, on pourrait effectivement utiliser des outils
     tels \mustbecompleted{XXX ou XXX}.
     Nous avons choisi DSX/SoCLib, car il est open source, et c'est celui que
-    nous maitrisons le plus et nous savons déjà que sont moteur couvre une
+    nous maitrisons le plus et nous savons déjà que son moteur couvre une
     grande partie des besoins de COACH Ã  ce niveau. 
     \t\note{INT}

anr/section-consortium-people.tex

@@ -35 +35 @@
 coordinator & Vaumorin    & Emannuel    & Strategic Project Manager & ESL      & 20 & Project leader \\\hline
 contributor & Spasevski   & Cyril       & CTO                 & EDA            & 6 & Technical specifications \\\hline
-contributor & Guntz       & St\'ephane  & VP of Engineering   & EDA            & 12 & Demonstrator specification and management \\\hline
-contributor & Lucas       & Ronan       & R\&D Engineer       & HW/SW Codesign & 12 & Tools and demonstrator implementation \\\hline
+contributor & Guntz       & St\'ephane  & VP of Engineering   & EDA            & 6 & Demonstrator specification and management \\\hline
+contributor & Lucas       & Ronan       & R\&D Engineer       & HW/SW Codesign & 9 & Tools and demonstrator implementation \\\hline
+contributor & Olivier     & Garry       & R\&D Engineer       & SW development & 9 & Tools and demonstrator implementation \\\hline
 
 \peopletabularentry{\irisa}

anr/section-dissemination.tex

@@ -75 +75 @@
 of the project and presented in annexe~\ref{lettre-soutien}.
 
-\subsection{Indusrial Interest in COACH}
+\subsection{Industrial Interest in COACH}
 
 \subsubsection*{Partner: \textit{\mds}}
+The interest for \mds in this project is multiple. 
 
-\mustbecompleted{A COMPLETER: Emmanuel ....}
+- We will collaborate in experiments for the integration of High Level Synthesis engines into IP-XACT based flow. 
+This point will be very valuable because more and more system integrators are using or considering to use
+HLS in their flow (e.g. Astrium, Airbus, etc.)
+
+- \mds has already a leading position in the usage of IP-XACT standard for managing innovative SoC design
+methodologies. This project will allow to keep the advance in regards with competition by anticipating 
+the next generation platforms hosting mutli cores and programmable logic for coprocessors.
+
+- HPC is a topic that was not covered yet by \mds with its customers. Thanks to this project, \mds will 
+collaborate with BULL on this point and this will open us doors for new customers market.
+
+- This project has been set up for maximizing the industrial exploitation of results. The role of \mds will
+be to ensure this objective and after the project, we expect a growing contribution for rising the turnover (2015: 3 new customers = 150keuros, 
+2016: 5 new customers = 400keuros, 2017: 10 new customers = 1Meuros)
+
 
 \subsubsection*{Partner: \textit{\bull}}

anr/section-etat-de-art.tex

@@ -229 +229 @@
 % EV: SPIRIT IP-XACT Controlled ESL Design Tool Applied to a Network-on-Chip Platform: \cite{mds2}\\
 % EV: SocKET design flow and Application on industrial use cases: \cite{socketflow}\\
+% IA: http://www.design-reuse.com/articles/19895/ip-xact-xml.html \cite{dandr}\\
 IP-XACT is an XML based open standard defined by the Accellera consortium. 
 This non-profit organisation provides a unified set of high quality IP-XACT 
@@ -239 +240 @@
 systems from concept to production. The last IEEE 1685 release of IP-XACT incorporates 
 both RTL and TLM (transaction level modelling) capabilities. Thus it can be used to
-package IP portfolios and describe their assembly in complex hardware architectures. 
+package IP portfolios~\cite{dandr} and describe their assembly in complex hardware architectures.~\cite{mds1}~\cite{mds2} 
 These description files are the basis for tool interoperability and data exchange 
-through a common structured data management. Today more than two hundred companies 
+through a common structured data management\cite{socketflow}. Today more than two hundred companies 
 are members of the consortium and the board is incorporating top actors 
 (STM, NXP, TI, ARM, FREESCALE, LSI, Mentor, Synopsys and Cadence), ensuring the 

anr/section-position.tex

@@ -38 +38 @@
 environment, suitable for co-operative and distributed development.
 \item Integration of the solutions and engines being developped into a state of the art SoC and system
-design flow, using the IP-XACT IEEE 1685 standard.
+design flow, using the IP-XACT IEEE 1685 standard
 \end{itemize}
 COACH outcome will contribute to strengthen Europe's competitive position by developing
@@ -151 +151 @@
 %%%
 \subsubsection*{Relevance to the call axis}
-The COACH project totally fulfills the objectives of the axis 2 "METHODES,
+This project answer to the global statement of the call "INGENIERIE NUMERIQUE ET SECURITE (INS)" by proposing 
+methods and tools for the design of application to be ran on platforms of the next generation. Results will be gained in term of productivity, 
+time-to-market (automation and code generation) and safety (management of high level sepcifications down to implementation).
+In this call, the COACH project totally fulfills the objectives of the axis 2 "METHODES,
 OUTILS ET TECHNOLOGIES POUR LES SYSTEMES EMBARQUES".
-\mustbecompleted{BEGIN-FIXME}
 COACH will address new embedded systems architectures by allowing the design of 
 Multi-Core Systems-on-Chip (possibly heterogeneous) on FPGA according to the design 
@@ -161 +163 @@
 API and using hardware accelerator automatically generated. It will also permit to use 
 efficiently different dynamic system management techniques and re-configuration mechanisms.
+The results will be tailored in order to be integrated in standard design flow of critical systems.
 \\
 COACH will address High-Performance Computing (HPC) by helping designers to accelerate an 
@@ -167 +170 @@
 configurations, COACH will allow to easily migrate critical parts into an FPGA plugged to the 
 PC bus (through a communication link like PCI/X). 
-\mustbecompleted{END-FIXME}
 \parlf
-The COACH project well fits also the axis 5 "USAGES".
-\mustbecompleted{BEGIN-FIXME}
+The COACH project has been also shaped to answer to the axis 5 "USAGES".
 COACH will address robotic and control applications by 
 allowing to design complex systems based on MPSoC architecture.
@@ -184 +185 @@
 process productivity of the cryptographic algorithms hardware synthesis, improving the
 quality and reducing the design time and the cost of synthesised cryptographic devices.
-\mustbecompleted{END-FIXME}
 %
 \subsubsection*{European and international positionning}

anr/section-ressources.tex

@@ -205 +205 @@
 \subsection{Partner 6: \mdslong}
 
-\mustbecompleted{A COMPLETER: Emmanuel ....}
 \begin{ADDEDENV}
 \begin{description}
@@ -211 +210 @@
   No specific equipment acquisition is required for this project. 
 \item[Personnel costs]
-  \xilinx employees involved in the project are permanent Software Engineers.
+  \mds employees involved in the project are permanent managers, engineers and doctors.
   The man power detail in \hommemois by deliverables is given in
   figure~\ref{table-livrables-1} and a sumary by task in the following table.
@@ -223 +222 @@
 \item[Other working costs] none
 \end{description}
-\end{ADDEDENV}
+
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%