Index: /anr/annexe-reponse.tex =================================================================== --- /anr/annexe-reponse.tex (revision 315) +++ /anr/annexe-reponse.tex (revision 316) @@ -7,10 +7,10 @@ Dans la premiÚre section, nous présentons nos réponses aux suggestions et remarques des experts en suivant l'ordre du dossier d'évaluation qui nous a été -retourné. La seconde section quant à elle, synthétise ces réponses. +retourné. La seconde section, quant à elle, synthétise ces réponses. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \subsection{Réponses séquentielles} % \subsubsection{Pertinence de la proposition au regard de l'appel à projet} -Pas de faiblesses signalées. +Pas de faiblesse signalée. \subsubsection{Qualité scientifique et technique de la proposition} \begin{description} @@ -37,13 +37,14 @@ possibilité. \item[Point 2 (\textit{pas de dimension recherche})]\mbox{} - \\ La dimension recherche se trouve à plusieurs niveaux. + \\ La dimension recherche est présente à différents niveaux de ce projet. \t%\note{R.1} - D'abord, synthétiser la même description de haut niveau soit par HLS + Tour d'abord, le fait de synthétiser la même description de haut niveau soit par HLS soit par ASIP, est à notre connaissance non encore réalisé à ce jour. \t%\note{R.2} - L'utilisation de transformations polyédriques dans des outils de HLS + De plus, l'utilisation de transformations polyédriques dans des outils de HLS opérationnels n'est pas courant. \t%\note{R.3} - Les IPs sont d'abord des composants matériels génériques, COACH permettra + \mustbecompleted{je ne comprends pas cet argument} + Les IPs sont d'abord des composants matériels génériques, COACH permettra de concevoir des IPs trÚs paramétrables (hardware + software), il sera intéressant de voir ce que de tel IP peuvent apporter à la micro @@ -52,13 +53,13 @@ Les outils de conception de SoC actuels ont soit une approche matérielle (sans limite sur les choix architecturaux), soit massivement parallÚle à - gros grain (MPSoC à mémoire cohérente). - Il en résulte des systÚmes trÚs complexes nécessitant des spécialistes en - matériel (approche matérielle) ou en programmation parallÚle.\\ + gros grain (MPSoC à mémoire cohérente). Il en résulte des systÚmes trÚs complexes nécessitant des spécialistes en + matériel (approche matérielle) ou en programmation parallÚle. A l'opposé, dans COACH l'architecture matérielle est simple et quasiment fixée. - Le moyen d'accélération est parallélisme à grain trÚs fin généré au sein + Le moyen d'accélération est le parallélisme à grain trÚs fin généré au sein des coprocesseurs par HLS. Il en résulte que des développeurs de logiciel standard pourront utiliser COACH. \\ La démonstration de la pertinence ou de la non pertinence de ces choix est - notre avis l'axe de recherche principal du projet. + à notre avis l'axe de recherche principal du projet car il impactera les orientations + technologiques liées à l'exploitation des plateformes matérielles de demain. \item[Point 3 (\textit{lien entre HPC et SoC embarqué})]\mbox{} \\ %\note{X.1} Index: /anr/section-1.tex =================================================================== --- /anr/section-1.tex (revision 315) +++ /anr/section-1.tex (revision 316) @@ -5,5 +5,5 @@ complex Multi-Processors System on Chip (MPSoC). \\ -During the last decade, the design of ASICs (Application Specific +During the last decade, the use of ASICs (Application Specific Integrated Circuits) appeared to be more and more reserved to high volume markets, because the design and fabrication costs of such components exploded, due to increasing NRE (Non Index: /anr/section-dissemination.tex =================================================================== --- /anr/section-dissemination.tex (revision 315) +++ /anr/section-dissemination.tex (revision 316) @@ -36,10 +36,15 @@ Following the general policy of the SoCLib platform, the COACH project will be an open infrastructure, and the COACH tools and libraries will be available in the framework -of the SoCLib WEB server. This server will be maintened by the UPMC/LIP6 laboratory. +of the SoCLib WEB server. This server will be maintened by the UPMC/LIP6 laboratory. -\subsection{Exploitation of results} +On the standardization side, some effort will be made for analysing how the work around IP-XACT +could be donated for the evolution of the IEEE 1685 standard. Magillem is board member of +Accellera, TRT, TIMA and LIP6 are members, so we'll try to have some influence and at least +communicate on the fact that our solutions will be compatible with the standard. -The main goal of the COACH project is to help SMEs (Small and Medium Enterprises) -to enter the world of MPSoC technologies. For small companies, the cost is a primary concern. +\subsection{Industrial exploitation of results} + +The main goal of the COACH project is to help SMEs (Small and Medium Enterprises) and even small design team in bigger entities +to enter the world of MPSoC technologies. For small companies or design services, the cost is a primary concern. Moreover, these companies have not always in-home expertise in hardware design and VHDL modelling. As the fabrication costs of an ASIC is generally too high for SMEs, the COACH project focus @@ -69,4 +74,7 @@ that are not involved by the free software policy, but these libraries will be supported by the synthesis tools developed in the COACH project. +\item +\mds will propose a commercial version of COACH, integrated into Magillem tool suite and compatible with a standard IP-XACT flow. +This version will integrate some generic features, already available for production (some of them from standard Magillem pack, some other developped in COACH). Other COACH features will have to be tailored for the specifics of the customer framework and will generate service business. \end{itemize} @@ -92,6 +100,8 @@ - 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) +be to ensure this objective and after the project, we expect a growing contribution for rising the turnover (2015: 2 new customers = 100keuros, +2016: 4 new customers = 250keuros, 2017: 5 new customers = 400Keuros). These numbers are not high but we tried to keep them realistic. +The return on investment is nevertheless important and we can also expect side effects of this project on sales with existing +*customers and prospects interrested in the global magillem solution. Index: /anr/task-dissemination.tex =================================================================== --- /anr/task-dissemination.tex (revision 315) +++ /anr/task-dissemination.tex (revision 316) @@ -6,9 +6,10 @@ \begin{objectif} This task relates to the diffusion of the project results. -The objective is to ensure the COACH dissemination +The classical objective is to ensure the dissemination of the result into the community by writing papers, by presenting COACH in trade shows and by publishing on a public WEB site all the information that a COACH user requires. -Those lasts are: +The main objective is to prepare the further industrial exploitation of the results. +The deliverables to reach these goals will be: \begin{itemize} \item The packaging of COACH milestones and final release and their associated @@ -39,5 +40,5 @@ \begin{livrable} \itemV{6}{12}{d+x}{\Supmc}{Tutorial} - It will illustrate the features the T0+12 milestone provides especially: + It will illustrate the features that the T0+12 milestone provides especially: \begin{description} \item[HPC] This tutorial section shows how an application can be split into @@ -57,5 +58,6 @@ FPGA. \item[Inegration (\Smds)] This section is dedicated to the integration of - COACH generated IP into an IP-XACT based design flow such as SOCKET. + COACH generated IP into an IP-XACT based design flow such as the one define in the SoCket project for critical systems + and which is generic enough to support a wide range of application domains. \end{description} \end{livrable} @@ -88,5 +90,6 @@ This deliverable groups the effort to make to know COACH. It consists mainly in writing/submitting papers and in presenting COACH in to trade - show and workshop and organizing a final white paper. + show and workshop and organizing a final white paper. + This white paper will facilitates the dissemination towards industrial prospects. \end{livrable} \end{workpackage}