source: anr/task-6.tex @ 131

Last change on this file since 131 was 129, checked in by coach, 15 years ago

IA: updated zied

File size: 9.3 KB
Line 
1\begin{taskinfo}
2\let\IRISA\enable
3\let\BULL\enable
4\let\THALES\leader
5\let\NAVTEL\enable
6\let\ZIED\enable
7\end{taskinfo}
8%
9\begin{objectif}
10This task groups the demonstrators of the COACH project.
11The demonstrators cover various domains and application types to drive
12the specification choices and to check most of the COACH features.
13\end{objectif}
14%
15\begin{workpackage}
16  \subtask This \ST relies to the COACH use by \bull.
17    \mustbecompleted{FIXME:BULL ajouter quelques lignes pour donner
18    1) type d'application (HPC ou embedded system, HLS),
19    2) domaine (RADAR, VIDEO, ...)
20    3) et si possible l'interet de BULL dans COACH.}
21    \begin{livrable}
22      \itemV{0}{6}{d}{\Sbull}{\bull demonstrator}
23        The deliverable is a document that describes the application that will be use as
24        demonstrator.
25      \itemV{6}{12}{x}{\Sbull}{\bull demonstrator}
26        The deliverable is the specification of the demonstrator in COACH input format
27        defined in the {\specGenManual} deliverable.
28      \itemL{12}{36}{d}{\Sbull}{\bull demonstrator}{9:5:5}
29        Validation of the demonstrator, the deliverable is a document
30        describing the result of the experimentations.
31    \end{livrable}
32
33  \subtask The objective of this sub-task is to specify the application and to develop the
34    high level code. The application is in the domain of surveillance of critical
35    infrastructures.
36    The objective is to detect and classify the presence of humans in the restricted area.
37    The algorithm is based on the work of Viola and Jones\cite{thales-viola}.
38    It implements in particular a cascade of classifiers operating on Haar like features,
39    where simple weak classifiers at the beginning of the cascade reject a majority of
40    void sub-windows, before more complex classifiers concentrate on potential regions of
41    interest.
42    This application is computation intensive and also makes an intensive use of binary
43    decision trees to cascade the filters, which makes it a good candidate to assess the
44    association of CAL with parallelizing tools.\\
45    Moreover, the higher levels of computing can involve tracking and data fusion between
46    several camera streams and some other informations.
47    The targeted system will be composed of one camera connected to a PC.
48    All the computing part of the application is executed on a FPGA board connected to the
49    PC.
50    \begin{livrable}
51      \itemV{0}{6}{d}{\Sthales}{\thales demonstrator (step 1)}
52        \setMacroInAuxFile{trtAppSpecification}
53        This delivrable is a document that specifies the application.
54      \itemL{6}{12}{x}{\Sthales}{\thales demonstrator (step 1)}{4:0:0}
55        This delivrable is the code of the application spcecified former
56        delivrable (\trtAppSpecification).
57    \end{livrable}
58
59  \subtask \TRT will use its internal software environment tool SPEAR DE to describe the
60    application. The tool is able to partition and to generate the code for the target. \\
61    In this task, we will adapt SPEAR DE to generate the application description input of
62    COACH framework. We will also describe the three templates of architecture in order to
63    be able to partition the application on the architecture.
64    \begin{livrable}
65      \itemL{6}{18}{x}{\Sthales}{SPEAR-DE adaptation}{6:7:0}
66        \setMacroInAuxFile{trtSpearde}
67        Adaptation of SPEAR-DE for COACH framework.
68    \end{livrable}
69
70  \subtask 
71    In this task, \TRT will evaluate the COACH platform. In particular, \TRT will verify
72    its ability to generate a whole VHDL of an embedded system on FPGA for an application
73    mixing control and data flow aspects. \TRT will evaluate the performance of the
74    generated system in terms of GOPS, and the design time from a high level description.
75    \begin{livrable}
76      \itemV{18}{24}{d+x}{\Sthales}{\thales demonstrator (step 2)}
77        This delivrable is a document describing the result got for the application
78        (\trtAppSpecification) with SPEAR-DE (\trtSpearde) using COACH milestone of T0+18.
79        The updated code of the application will be also provide.
80      \itemV{24}{30}{d+x}{\Sthales}{\thales demonstrator (step 2)}
81        This delivrable is a document describing the result got for the application
82        (\trtAppSpecification) with SPEAR-DE (\trtSpearde) using COACH milestone of T0+24.
83        The updated code of the application will be also provide.
84      \itemL{30}{36}{d+x}{\Sthales}{\thales demonstrator (step 2)}{0:5:5}
85        This delivrable is a document that validates and evaluates COACH (final release)
86        for the \thales demonstrators (\trtAppSpecification).
87        The updated code of the application will be also provide.
88    \end{livrable}
89
90  \subtask FLEXRAS proposes a SoC architecture integrating an embedded FPGA (eFPGA).
91    The architecture is composed essentially of a processor, a bus and several RAMs.
92    The embedded FPGA is connected to the bus and communicates with the other components.
93    The (eFPGA) works in 2 modes:
94    \begin{description}
95      \item[Slave mode]
96        As a DMA, the processor will send the configuration bitstream
97        stored on the RAM to the eFPGA. In this mode, the eFPGA is considered as a
98        writeable memory and is configured by the processor.
99      \item[Master mode]
100        Once the FPGA is programmed, it becomes a coprocessor achieving the aimed task.
101    \end{description}
102      The top architecture of this SoC based-platform will be generated using COACH
103      framework. The application that will be run on the SoC corresponds initially to a
104      graph of software tasks. Critical tasks will be identified and transformed
105      automatically to hardware tasks using COACH high level synthesis feature. While
106      software tasks will be run on the processor, hardware ones will be mapped on eFPGA
107      to take advantage of its optimized resources and parallelism. FLEXRAS provides all
108      the flow from RTL synthesis to bitstream generation.
109    \begin{livrable}
110      \itemL{0}{6}{d}{\Szied}{\zied architecture}{2.4:0:0}
111        FLEXRAS will use IPs provided by LIP6 (vhdl models of SoCLIB) and its eFPGA IP to
112        generate the SoC architecture.
113        This delivrable is a document that describes this architecture.
114      \itemL{6}{18}{h}{\Szied}{eFPGA/VCI component}{3.6:3.6:0}
115        FLEXRAS has to adapt the eFPGA interface to connect it to the VCI bus.
116        This delivrable is a VHDL description.
117%      \itemL{12}{18}{x}{\Szied}{bitstream loader port}{0:3.6:0}
118%        Port of the bitstream loader to the MUTEK operating system.
119      \itemL{18}{24}{x}{\Szied}{\zied demonstrators}{0:2.4:0}
120        \zied will propose to test COACH framework and the \zied architecture template
121        throught a basic application.
122        This applicattion will containt 3 communicating tasks under the coach format specified
123        in {\novers{\specGenManual}} delivrable.
124        The first one is a hardware task generated by the HAS tools and transformed into
125        a bit stream by the \zied tools.
126        The second is a bitstream loader that will load the bitstream of the first task on
127        the eFPGA.
128        The third is a software task that communicates with the hw task for testing it.
129      \itemL{24}{30}{x}{\Szied}{eFPGA characterisation}{0:0:2.4}
130        This delivrable is a file under the format defined by the delivrable
131        {\specMacroCell} that characterizes the eFPGA. This will allow the COACH HLS tools
132        to take into account the eFPGA delays.
133      \itemL{30}{36}{d}{\Szied}{\zied evaluation}{0:0:3.6}
134        This delivrable is a document that describes the tests, the validation and the
135        evaluation of COACH with the \zied architecture and tools.
136    \end{livrable}
137
138  \subtask
139The Navtel Embedded Supper Computing(ESC) project is based on simple hardware but tightly coupled module between  ARM processor and FPGA.
140The ARM and FPGA configuration also facilitate the co-simulation which allows to  gain time on the development and integration phase.
141The architecture consists of a wrapper that encapsules computing units depend on the
142application.
143To day Navtel develop these computing units manually.
144Navtel expects to benefit from the COACH project to obtain the computing unit generation
145tools.
146
147The system level cores for FPGA are generated using high level  synthesize tool and scheduled using a real time kernal for task switching and partial reconfiguration on run time environment.
148
149The ESC can function on different topologies: Single, parallel or Grid computing modes for industrial and scientific applications.
150
151    \begin{livrable}
152    \itemL{0}{6}{d}{\Snavtel}{\navtel \ganttlf demonstrator specification}{4:0:0}
153        A document that will be define the requirements for
154                automatic code generation for signal processing unit.
155    \itemL{6}{18}{h}{\Snavtel}{\navtel \ganttlf wrapper adaptation}{2:0:0}
156                The adaptation of our wrapper to support coprocessor generated by COACH.
157    \itemL{18}{36}{d}{\Snavtel}{\navtel evaluation}{0:0:6}
158                \navtel will test the HLS tootls of COACH framework on our market sector such as
159                digital communication, imaging and industrial control.
160                A document will be written that describes the results obtained with the COACH High Level
161                Synthesize for the generation computing units.
162                These results take into account
163            1) performance in terms of space and time
164                        2) Friendlyness of the environment.
165    \end{livrable}
166\end{workpackage}
167        %\CoutHorsD{0}{36}{\Snavtel}{managment}{1:1:1}
Note: See TracBrowser for help on using the repository browser.