1 | \anrdoc{Preciser:\begin{itemize} |
---|
2 | \item positionnement du projet par rapport au contexte developpe precedemment : |
---|
3 | vis- a-vis des projets et recherches concurrents, complementaires ou |
---|
4 | anterieurs, des brevets et standards... |
---|
5 | \item indiquer si le projet s'inscrit dans la continuite de projet(s) anterieurs |
---|
6 | deja finances par l'ANR. Dans ce cas, presenter brievement les resultats acquis, |
---|
7 | \item positionnement du projet par rapport aux axes thematiques de l'appel a projets, |
---|
8 | \item positionnement du projet aux niveaux europeen et international. |
---|
9 | \end{itemize}} |
---|
10 | |
---|
11 | % Relevance of the proposal |
---|
12 | %The COACH proposal addresses directly the \emph{Embedded Systems} item of |
---|
13 | %the ARPEGE program. |
---|
14 | |
---|
15 | %PC => IA et ALain |
---|
16 | %J'aui déplacé le pargraphe ci dessous en conclusion de la section précédente 2.1 |
---|
17 | |
---|
18 | %It aims to propose solutions to the societal/economical challenges by |
---|
19 | %providing SMEs novel design capabilities enabling them to increase their |
---|
20 | %design productivity with design exploration and synthesis methods that are placed on top |
---|
21 | %of the state-of-the-art methods. |
---|
22 | %This project proposes an open-source framework for mapping multi-tasks software applications |
---|
23 | %on Field Programmable Gate Array circuits (FPGA). |
---|
24 | %%% |
---|
25 | \subsubsection*{Positioning in regards with the economical and social context} |
---|
26 | COACH will contribute to build an open design and run-time |
---|
27 | environment, including communication middleware and tools to support |
---|
28 | developers in the production of embedded software, through all phases of the software life cycle, |
---|
29 | from requirements analysis down to deployment and maintenance. |
---|
30 | More specifically, COACH focuses on: |
---|
31 | \begin{itemize} |
---|
32 | \item High level methods and concepts (esp. eequirements and architectural level) for system |
---|
33 | design, development and integration, addressing complexity aspects and modularity. |
---|
34 | \item Open and modular design environments, enabling flexibility and extensibility by |
---|
35 | means of new or sector-specific tools and ensuring consistency and traceability along the |
---|
36 | development life cycle. |
---|
37 | \item Light/agile methodologies and adaptive workflow providing a dynamic and adaptive |
---|
38 | environment, suitable for co-operative and distributed development. |
---|
39 | \item Integration of the solutions and engines being developed into a state of the art SoC and system |
---|
40 | design flow, using the IP-XACT IEEE 1685 specification. |
---|
41 | \end{itemize} |
---|
42 | The COACH results will contribute to strengthen Europe's competitive position by developing |
---|
43 | technologies and methodologies for product design, focusing (in compliance with the |
---|
44 | %scope of the above program) on technologies, engineering methodologies, novel tools, |
---|
45 | %methods which facilitate resource use efficiency. The approaches and tools to be developed |
---|
46 | %in COACH will enable new and emerging information technologies for the development, |
---|
47 | %methods which facilitate resource use efficiency. The COACH approaches and tools |
---|
48 | scope of the above program) on technologies, engineering methodologies, novel tools |
---|
49 | which facilitate resource use efficiency. The COACH approaches and tools |
---|
50 | will enable new and emerging information technologies for the development, |
---|
51 | manufacturing and integration of devices and related software into end-products. |
---|
52 | %%% |
---|
53 | \subsubsection*{Positioning and continuity with other projects} |
---|
54 | The COACH project will benefit from a number of previous recent projects: |
---|
55 | \begin{description} |
---|
56 | \item[SOCLIB] |
---|
57 | The SoCLib ANR platform (2007-2009) is an open infrastructure |
---|
58 | that supports system level virtual prototyping of shared memory, multi-processors |
---|
59 | architectures, and provides tools to map multi-tasks software application on these |
---|
60 | architectures, for reliable performance evaluation. |
---|
61 | The core of this platform is a library of SystemC simulation models for |
---|
62 | general purpose IP cores. |
---|
63 | It provides also embedded operating systems and software/hardware |
---|
64 | communication middleware. |
---|
65 | \item[ROMA] The ROMA ANR project (2007-2010) \cite{roma,RAFFIN:2010:INRIA-00539874:1} |
---|
66 | involving IRISA (CAIRN team), LIRMM, CEA List, THOMSON France R\&D, |
---|
67 | proposes to develop a reconfigurable processor, exhibiting high |
---|
68 | silicon density and power efficiency, able to adapt its computing |
---|
69 | structure to computation patterns that can be faster or more |
---|
70 | power efficient. %The ROMA project study a pipeline of |
---|
71 | %evolved low-power coarse grain reconfigurable operators to avoid |
---|
72 | %traditional overhead, in reconfigurable devices, related to the |
---|
73 | %interconnection network. |
---|
74 | The project will borrow from the ROMA |
---|
75 | ANR project and the ongoing joint INRIA-STMicro |
---|
76 | Nano2012 project to adapt existing pattern extraction algorithms |
---|
77 | and datapath merging techniques to ASIP synthesis. |
---|
78 | % and datapath merging techniques to the synthesis of customized |
---|
79 | % ASIP processors. |
---|
80 | \item[TSAR] |
---|
81 | The TSAR MEDEA+ project (2008-2010) involving BULL, THALES and \upmc targets the design of a |
---|
82 | % The TSAR MEDEA+ project (2008-2010) targets the design of a |
---|
83 | scalable, coherent shared memory, multi-cores processor architecture, and uses the SoCLib |
---|
84 | platform for virtual prototyping. COACH will benefit from the synthesizable VHDL |
---|
85 | models developed in the framework of TSAR (MIPS32 processor core, and RING interconnect). |
---|
86 | \item[BioWic] |
---|
87 | On the HPC application side, we also hope to benefit from the experience in |
---|
88 | hardware acceleration of bioinformatic algorithms/workfows gathered by the |
---|
89 | CAIRN group (ANR BioWic project 2009-2011), so as to |
---|
90 | be able to validate the framework on real-life HPC applications. |
---|
91 | |
---|
92 | \item[SoCket] |
---|
93 | The design flow defined in this project targets the design of critical embedded systems. |
---|
94 | It covers important steps as system architecture exploration, and the definition of virtual |
---|
95 | prototypes at different levels of abstraction to support early embedded software development, |
---|
96 | verification of hardware blocks, and preparation of certification activities. |
---|
97 | COACH solutions and engines will be specified to be integrated into this standard flow. |
---|
98 | MDS, Thales TRT, TIMA are already collaborating in this project. |
---|
99 | |
---|
100 | \item[HOSPI] |
---|
101 | The objective of this project (with TIMA and MDS) was to define innovative methods, and implement the associated tools, to ease |
---|
102 | the mapping of data-streaming applications on heterogeneous platforms. COACH will use the abstracted description |
---|
103 | format based on IP-XACT for hardware platforms and the results concerning the integration of code generators into a standard design flow. |
---|
104 | |
---|
105 | \item[SoftSoC] |
---|
106 | TIMA and MDS are involved in this project which aims at the |
---|
107 | definition and generation of Hardware Dependent Software layers of a |
---|
108 | system. |
---|
109 | Crucial extensions of the IP-XACT standard will be reused from this |
---|
110 | project, as well as code generation techniques based on them. |
---|
111 | |
---|
112 | \end{description} |
---|
113 | %%% |
---|
114 | The partners involved in the COACH project have a well established expertise |
---|
115 | in the following domains: |
---|
116 | \begin{itemize} |
---|
117 | \item |
---|
118 | In the field of High Level Synthesis (HLS), the project |
---|
119 | leverages on know-how acquired over the last 15 years with the GAUT~\cite{gaut08} project |
---|
120 | developed by the \ubs laboratory, and with the UGH~\cite{ugh08} project developed |
---|
121 | by the \upmc and \tima laboratories. |
---|
122 | \item |
---|
123 | Regarding system level architecture, the project is based on the know-how |
---|
124 | acquired by \upmc and \tima in the framework of various projects |
---|
125 | in the field of communication architectures for shared memory multi-processors systems |
---|
126 | (COSY~\cite{cosy}, DISYDENT~\cite{disydent05} or DSPIN~\cite{dspin08} of MEDEA-MESA). |
---|
127 | As an example, the DSPIN project is now used in the TSAR project. |
---|
128 | \item |
---|
129 | Regarding Application Specific Instruction Processor (ASIP) design, the |
---|
130 | CAIRN group at INRIA Rennes -- Bretagne Atlantique benefits from several years of |
---|
131 | expertise in the domain of retargetable compiler |
---|
132 | (Armor/Calife~\cite{CODES99} since 1996, and the Gecos |
---|
133 | compilers~\cite{ASAP05} since 2002). |
---|
134 | \item |
---|
135 | In the field of compilers, the \lip Compsys group was founded in 2002 |
---|
136 | by several senior researchers with experience in |
---|
137 | high performance computing and automatic parallelization. They have been |
---|
138 | among the initiators of the polyhedral model, a theory which serve to |
---|
139 | unify many parallelism detection and exploitation techniques for regular |
---|
140 | programs. It is expected that the techniques developed by \lip for |
---|
141 | parallelism detection, scheduling \cite{Feau:92aa,Feau:92bb}, |
---|
142 | process construction \cite{Feau:96} and memory management \cite{bee} |
---|
143 | will be very useful as a front-end for HLS tools. |
---|
144 | \item |
---|
145 | Regarding industrial flow integration \mds will bring its strong expertise |
---|
146 | in IEEE 1685 (IP-XACT) standard. The \mds team is involved and contributes actively |
---|
147 | to it since 2003 and the Magillem tool suite is used for its validation. Magillem is used in |
---|
148 | industrial production flows of ST, NXP, TI, Qualcomm, and system integrators like Thales, |
---|
149 | Astrium, Thomson, etc. This guarantees a strong alignement on customers needs and enhanced results exploitation. |
---|
150 | |
---|
151 | \end{itemize} |
---|
152 | %%% |
---|
153 | \subsubsection*{Relevance to the call axis} |
---|
154 | This project answer to the global statement of the call "INGENIERIE NUMERIQUE ET SECURITE (INS)" by proposing |
---|
155 | methods and tools for the design of application to be run on platforms of the next generation. |
---|
156 | Improvements can be expected for productivity, |
---|
157 | time-to-market (automation and code generation) and reliability (management of high level specifications down to implementation). |
---|
158 | In this call, the COACH project totally fulfills the objectives of the axis 2 "METHODES, |
---|
159 | OUTILS ET TECHNOLOGIES POUR LES SYSTEMES EMBARQUES". |
---|
160 | COACH will address new embedded systems architectures by allowing the design of |
---|
161 | Multi-Core Systems-on-Chip (possibly heterogeneous) on FPGA according to the design |
---|
162 | constraints and objectives (real-time, low-power). It will permit designing complex SoC |
---|
163 | based on IP cores (memory, peripherals...), |
---|
164 | running Embedded Software, as well as an Operating System with associated middleware and |
---|
165 | API and using automatically generated hardware accelerators. It will also permit to use |
---|
166 | efficiently different dynamic system management techniques and re-configuration mechanisms. |
---|
167 | The results will be tailored in order to be integrated in standard design flow of critical systems. |
---|
168 | \\ |
---|
169 | COACH will address High-Performance Computing (HPC) by helping designers to accelerate an |
---|
170 | application running on a PC. |
---|
171 | By providing tools that translate high level language programs to FPGA |
---|
172 | configurations, COACH will allow to easily migrate critical parts into an FPGA plugged to the |
---|
173 | PC bus (through a communication link like PCI/X). |
---|
174 | \parlf |
---|
175 | The COACH project has been also shaped to answer to the axis 5 "USAGES". |
---|
176 | COACH will address robotic and control applications by |
---|
177 | allowing to design complex systems based on MPSoC architecture. |
---|
178 | Like in the consumer electronics domain, future control applications |
---|
179 | will employ more and more SoC for safety and security applications. |
---|
180 | Application domains for such systems are for example automotive |
---|
181 | or avionics domains (e.g. collision-detection, intelligent navigation...). |
---|
182 | Manufacturing technology will also increasingly need high-end vision analysis and high-speed |
---|
183 | robot control. |
---|
184 | % |
---|
185 | The results of the COACH project will help users to build cryptographic secure systems implemented in |
---|
186 | in a combination of hardware and software in an effective way, substantially enhancing the |
---|
187 | productivity of the field, improving the |
---|
188 | quality and reducing the design time and the cost of synthesised cryptographic devices. |
---|
189 | % |
---|
190 | COACH will contribute to enhance the safety in design of critical system for two main reasons: |
---|
191 | \begin{itemize} |
---|
192 | \item by providing a way to automate the mapping of application onto MPSoC |
---|
193 | architecture; code generators of the tool chain will be subject to |
---|
194 | certification. |
---|
195 | \item by relaying on design flow defined by SoCKET, which is dedicated to |
---|
196 | safety of critical systems, COACH will benefit from features related to |
---|
197 | requirements traceability. |
---|
198 | \end{itemize} |
---|
199 | % |
---|
200 | \subsubsection*{European and international positioning} |
---|
201 | % |
---|
202 | Finally, it is worth noting that this project covers priorities defined by the commission |
---|
203 | experts in the field of Information Technologies Society (IST) for Embedded |
---|
204 | Systems: \textit{ $<<$Concepts, methods and tools for designing systems dealing with systems complexity |
---|
205 | and allowing to apply efficiently applications and various products on embedded platforms, |
---|
206 | considering resources constraints (delays, power, memory, etc.), security and quality |
---|
207 | services$>>$}. |
---|