- Timestamp:
- Nov 24, 2010, 12:14:38 AM (14 years ago)
- Location:
- anr
- Files:
-
- 15 edited
Legend:
- Unmodified
- Added
- Removed
-
anr/Makefile
r193 r278 1 1 # set here all the sources files 2 2 # required to build anr.pdf 3 SOURCES= anr.tex anr.bib section-1.tex \3 SOURCES= anr.tex anr.bib anr.sty section-1.tex \ 4 4 section-2.tex section-2.1.tex section-2.2.tex \ 5 5 flow.pdf section-3.1.tex section-3.2.tex \ … … 12 12 section-6.1.tex section-6.2.tex section-7.tex 13 13 14 TABLES= table_upmc_full.tex table_upmc_short.tex \ 15 table_tima_full.tex table_tima_short.tex \ 14 TABLES= \ 16 15 table_inria_cairn_full.tex table_inria_cairn_short.tex \ 17 16 table_inria_compsys_full.tex table_inria_compsys_short.tex \ 17 table_tima_full.tex table_tima_short.tex \ 18 18 table_ubs_full.tex table_ubs_short.tex \ 19 table_ xilinx_full.tex table_xilinx_short.tex \19 table_upmc_full.tex table_upmc_short.tex \ 20 20 table_bull_full.tex table_bull_short.tex \ 21 21 table_thales_full.tex table_thales_short.tex \ 22 table_zied_full.tex table_zied_short.tex \ 23 table_navtel_full.tex table_navtel_short.tex \ 24 table_livrable_01.tex table_livrable_02.tex 22 table_mds_full.tex table_mds_short.tex 25 23 26 24 # PROGRAMS … … 31 29 @$(FIG2DEV) -L pdf -p aaa $< $@ 32 30 33 anr.pdf: $(SOURCES) gantt1.tex gantt2.tex gantt $(TABLES) 31 anr.pdf: $(SOURCES) gantt 32 touch gantt1.tex gantt2.tex $(TABLES) 34 33 @echo "Generating pdf file" 35 34 @pdflatex anr.tex || true … … 40 39 @grep ndefine anr.log 41 40 42 anr.bbl:anr.aux anr.bib43 bibtex anr || true44 45 anr.aux gantt1.tex gantt2.tex $(TABLES):46 touch $@47 41 48 42 gantt: gantt.l -
anr/anr.sty
r263 r278 85 85 \let\UBS\disable% 86 86 \let\UPMC\disable% 87 \let\XILINX\disable%88 87 \let\BULL\disable% 89 88 \let\THALES\disable% 90 \let\NAVTEL\disable% 91 \let\ZIED\disable% 89 \let\MDS\disable% 92 90 }{% 93 91 \ifx\ALL\enable% … … 97 95 \ifx\TIMA\disable\let\TIMA\enable\fi% 98 96 \ifx\UBS\disable\let\UBS\enable\fi% 99 \ifx\XILINX\disable\let\XILINX\enable\fi%100 97 \ifx\BULL\disable\let\BULL\enable\fi% 101 98 \ifx\THALES\disable\let\THALES\enable\fi% 102 \ifx\NAVTEL\disable\let\NAVTEL\enable\fi% 103 \ifx\ZIED\disable\let\ZIED\enable\fi% 99 \ifx\MDS\disable\let\MDS\enable\fi% 104 100 \fi% 105 101 \def\@leader{\begin{small}\textcolor{red}{lead.}\end{small}} … … 110 106 \def\@TIMA{\ifx\TIMA\disable{}\else\ifx\TIMA\enable{\@partner}\else{\@leader}\fi\fi}% 111 107 \def\@UBS{\ifx\UBS\disable{}\else\ifx\UBS\enable{\@partner}\else{\@leader}\fi\fi}% 112 \def\@XILINX{\ifx\XILINX\disable{}\else\ifx\XILINX\enable{\@partner}\else{\@leader}\fi\fi}%113 108 \def\@BULL{\ifx\BULL\disable{}\else\ifx\BULL\enable{\@partner}\else{\@leader}\fi\fi}% 114 109 \def\@THALES{\ifx\THALES\disable{}\else\ifx\THALES\enable{\@partner}\else{\@leader}\fi\fi}% 115 \def\@NAVTEL{\ifx\NAVTEL\disable{}\else\ifx\NAVTEL\enable{\@partner}\else{\@leader}\fi\fi}% 116 \def\@ZIED{\ifx\ZIED\disable{}\else\ifx\ZIED\enable{\@partner}\else{\@leader}\fi\fi}% 117 \begin{tabular}{|c|c|c|c|c|c|c|c|c|c|}\hline 118 \Sirisa & \Slip & \Stima & \Subs & \Supmc & \Sxilinx & \Sbull & \Sthales & \Snavtel & \Szied \\\hline 119 \@IRISA & \@LIP & \@TIMA & \@UBS & \@UPMC & \@XILINX & \@BULL & \@THALES & \@NAVTEL & \@ZIED \\\hline 110 \def\@MDS{\ifx\MDS\disable{}\else\ifx\MDS\enable{\@partner}\else{\@leader}\fi\fi}% 111 \begin{tabular}{|c|c|c|c|c|c|c|c|}\hline 112 \Sirisa & \Slip & \Stima & \Subs & \Supmc & \Smds & \Sbull & \Sthales \\\hline 113 \@IRISA & \@LIP & \@TIMA & \@UBS & \@UPMC & \@MDS & \@BULL & \@THALES \\\hline 120 114 \end{tabular}\par 121 115 } … … 136 130 \begin{description}% 137 131 %\let\itemsave\item% 138 \def\subtask {%132 \def\subtask##1{% 139 133 \global\advance\subtaskcnt1 140 134 \def\subtaskname{S\taskname-\the\subtaskcnt}% 141 \item[\subtaskname ]}}135 \item[\subtaskname: ##1]\mbox{}\\}} 142 136 {\end{description}} 143 137 … … 152 146 \let\upmc\relax \let\Supmc\relax 153 147 \let\altera\relax \let\Saltera\relax 154 \let\xilinx\relax \let\Sxilinx\relax155 148 \let\bull\relax \let\Sbull\relax 156 149 \let\thales\relax \let\Sthales\relax 157 \let\ zied\relax \let\Szied\relax158 \let\ navtel\relax \let\Snavtel\relax150 \let\mds\relax \let\Smds\relax 151 \let\xilinx\relax 159 152 \immediate\write\ganttdata{% 160 153 T=\the\taskcnt\space S=\the\subtaskcnt\space% … … 240 233 \let\upmc\relax \let\Supmc\relax 241 234 \let\altera\relax \let\Saltera\relax 242 \let\xilinx\relax \let\Sxilinx\relax243 235 \let\bull\relax \let\Sbull\relax 244 236 \let\thales\relax \let\Sthales\relax 245 \let\zied\relax \let\Szied\relax 246 \let\navtel\relax \let\Snavtel\relax 237 \let\mds\relax \let\Smds\relax 247 238 \immediate\write\ganttdata{% 248 239 T=\the\taskcnt\space S=\the\subtaskcnt\space% -
anr/anr.tex
r276 r278 65 65 \def\zied{FLEXRAS\xspace} \def\Szied{\Sformat{FLEX}\xspace} 66 66 \def\navtel{NAVTEL-SYSTEM\xspace} \def\Snavtel{\Sformat{NAV}\xspace} 67 \def\mds{MAGILLEM DESIGN SERVICES\xspace} \def\Smds{\Sformat{MDS}\xspace} 67 68 68 69 \def\alllabs{\irisa \citi \lip \tima \ubs \upmc} … … 407 408 \bibliography{anr} 408 409 410 \end{document} 411 409 412 \newpage 410 413 \section{Letters of interest} -
anr/flow.fig
r275 r278 20 20 6 10800 2400 11272 3999 21 21 6 10879 2545 11194 3417 22 4 1 0 50 -1 2 17 0.0000 4 205 17311036 2763 P\00123 4 1 0 50 -1 2 17 0.0000 4 205 20511036 2981 R\00124 4 1 0 50 -1 2 17 0.0000 4 205 23611036 3199 O\00125 4 1 0 50 -1 2 17 0.0000 4 205 20511035 3418 C\00122 4 1 0 50 -1 2 17 0.0000 4 195 180 11036 2763 P\001 23 4 1 0 50 -1 2 17 0.0000 4 195 210 11036 2981 R\001 24 4 1 0 50 -1 2 17 0.0000 4 195 225 11036 3199 O\001 25 4 1 0 50 -1 2 17 0.0000 4 195 210 11035 3418 C\001 26 26 -6 27 27 2 2 0 2 0 7 50 -1 -1 0.000 0 0 -1 0 0 5 … … 30 30 6 11272 2400 11745 3999 31 31 6 11351 2545 11666 3199 32 4 1 0 50 -1 2 17 0.0000 4 205 20511509 2763 R\00133 4 1 0 50 -1 2 17 0.0000 4 205 20511509 2981 A\00134 4 1 0 50 -1 2 17 0.0000 4 205 26811509 3199 M\00132 4 1 0 50 -1 2 17 0.0000 4 195 210 11509 2763 R\001 33 4 1 0 50 -1 2 17 0.0000 4 195 210 11509 2981 A\001 34 4 1 0 50 -1 2 17 0.0000 4 195 270 11509 3199 M\001 35 35 -6 36 36 2 2 0 2 0 7 50 -1 -1 0.000 0 0 -1 0 0 5 … … 40 40 2 2 0 2 0 7 50 -1 -1 0.000 0 0 -1 0 0 5 41 41 11824 2473 12139 2473 12139 3926 11824 3926 11824 2473 42 4 1 0 50 -1 2 17 0.0000 4 205 11011981 2763 I\00143 4 1 0 50 -1 2 17 0.0000 4 205 23611981 2981 O\00142 4 1 0 50 -1 2 17 0.0000 4 195 105 11981 2763 I\001 43 4 1 0 50 -1 2 17 0.0000 4 195 225 11981 2981 O\001 44 44 -6 45 45 6 12217 2400 12690 3999 46 46 6 12296 2473 12611 3781 47 4 1 0 50 -1 2 17 0.0000 4 205 17312454 3127 P\00148 4 1 0 50 -1 2 17 0.0000 4 205 20512454 3345 R\00149 4 1 0 50 -1 2 17 0.0000 4 205 23612454 3563 O\00150 4 1 0 50 -1 2 17 0.0000 4 205 20512453 3781 C\00151 4 1 0 50 -1 2 17 0.0000 4 205 23612454 2909 O\00152 4 1 0 50 -1 2 17 0.0000 4 205 20512454 2691 C\00147 4 1 0 50 -1 2 17 0.0000 4 195 180 12454 3127 P\001 48 4 1 0 50 -1 2 17 0.0000 4 195 210 12454 3345 R\001 49 4 1 0 50 -1 2 17 0.0000 4 195 225 12454 3563 O\001 50 4 1 0 50 -1 2 17 0.0000 4 195 210 12453 3781 C\001 51 4 1 0 50 -1 2 17 0.0000 4 195 225 12454 2909 O\001 52 4 1 0 50 -1 2 17 0.0000 4 195 210 12454 2691 C\001 53 53 -6 54 54 2 2 0 2 0 7 50 -1 -1 0.000 0 0 -1 0 0 5 … … 58 58 2 2 0 2 0 7 50 -1 -1 0.000 0 0 7 0 0 5 59 59 10879 4072 12611 4072 12611 4362 10879 4362 10879 4072 60 4 1 0 50 -1 2 17 0.0000 4 205 56711745 4290 BUS\00160 4 1 0 50 -1 2 17 0.0000 4 195 570 11745 4290 BUS\001 61 61 -6 62 62 -6 … … 67 67 4 1 0 50 -1 0 12 0.0000 4 195 2085 11790 5040 (bitstream or IP-XACT)\001 68 68 4 1 0 50 -1 2 16 0.0000 4 195 495 11820 4815 SoC\001 69 -670 6 1665 3300 3315 610771 6 1665 3300 3315 427572 2 4 0 2 0 7 50 -1 -1 0.000 0 0 7 0 0 573 3240 4200 1740 4200 1740 3375 3240 3375 3240 420074 4 0 0 50 -1 2 16 0.0000 4 195 585 2265 3750 HPC\00175 4 0 0 50 -1 2 16 0.0000 4 255 1335 1890 4050 application\00176 -677 6 1725 5552 3255 610778 2 4 0 2 0 7 50 -1 -1 0.000 0 0 7 0 0 579 3240 6092 1740 6092 1740 5567 3240 5567 3240 609280 4 1 0 50 -1 2 16 0.0000 4 195 1095 2490 5927 Function\00181 -682 6 1665 4387 3315 536283 2 4 0 2 0 7 50 -1 -1 0.000 0 0 7 0 0 584 3240 5287 1740 5287 1740 4462 3240 4462 3240 528785 4 0 0 50 -1 2 16 0.0000 4 195 1245 1965 4837 Embedded\00186 4 0 0 50 -1 2 16 0.0000 4 255 1335 1890 5137 application\00187 -688 69 -6 89 70 6 4275 2307 6675 4782 … … 163 144 4 1 0 50 -1 2 16 0.0000 4 255 1140 8625 3630 Template\001 164 145 -6 146 6 1650 3268 3300 4243 147 2 4 0 2 0 7 50 -1 -1 0.000 0 0 7 0 0 5 148 3225 4168 1725 4168 1725 3343 3225 3343 3225 4168 149 4 0 0 50 -1 2 16 0.0000 4 195 585 2250 3718 HPC\001 150 4 0 0 50 -1 2 16 0.0000 4 255 1335 1875 4018 application\001 151 -6 152 6 1650 4355 3300 5330 153 2 4 0 2 0 7 50 -1 -1 0.000 0 0 7 0 0 5 154 3225 5255 1725 5255 1725 4430 3225 4430 3225 5255 155 4 0 0 50 -1 2 16 0.0000 4 195 1245 1950 4805 Embedded\001 156 4 0 0 50 -1 2 16 0.0000 4 255 1335 1875 5105 application\001 157 -6 165 158 2 1 0 2 0 7 50 -1 -1 0.000 0 0 -1 1 0 2 166 159 1 1 2.00 60.00 120.00 … … 182 175 2 4 0 2 0 7 50 -1 -1 0.000 0 0 7 0 0 5 183 176 12855 1960 10650 1960 10650 1275 12855 1275 12855 1960 177 2 4 0 2 0 7 50 -1 -1 0.000 0 0 7 0 0 5 178 3225 6300 1725 6300 1725 5535 3225 5535 3225 6300 184 179 4 0 0 50 -1 2 16 0.0000 4 195 1305 11100 1650 Executable\001 185 180 4 0 0 50 -1 2 16 0.0000 4 255 690 2250 675 Input\001 … … 189 184 4 0 0 50 -1 2 16 0.0000 4 255 2535 4275 6300 Performance analysis\001 190 185 4 0 0 50 -1 2 16 0.0000 4 255 2805 10350 6300 Running or Integration\001 186 4 1 0 50 -1 2 16 0.0000 4 255 1305 2475 5850 sub-system\001 187 4 1 0 50 -1 2 16 0.0000 4 255 1335 2475 6150 application\001 -
anr/gantt.l
r251 r278 47 47 { "ubs" ,"ubs" ,"table_ubs_full.tex" ,"table_ubs_short.tex" }, 48 48 { "upmc" ,"upmc" ,"table_upmc_full.tex" ,"table_upmc_short.tex" }, 49 { "altera" ,"altera" ,"table_altera_full.tex" ,"table_altera_short.tex" },50 { "xilinx" ,"xilinx" ,"table_xilinx_full.tex" ,"table_xilinx_short.tex" },51 49 { "bull" ,"bull" ,"table_bull_full.tex" ,"table_bull_short.tex" }, 52 50 { "thales" ,"thales" ,"table_thales_full.tex" ,"table_thales_short.tex" }, 53 { "zied" ,"zied" ,"table_zied_full.tex" ,"table_zied_short.tex" }, 54 { "navtel" ,"navtel" ,"table_navtel_full.tex" ,"table_navtel_short.tex" }, 51 { "mds" ,"mds" ,"table_mds_full.tex" ,"table_mds_short.tex" }, 55 52 { 0 ,0 ,0 ,0 }, 56 53 }; … … 862 859 int main() 863 860 { 864 int tnplus[10] = { 1, 2, 3, 4, 8, -1 };865 int tnmoins[10] = { 1, 2, 3, 4, 8, -1 };861 int tnplus[10] = { 1, 2, 3, 4, 5, 6, -1 }; 862 int tnmoins[10] = { 1, 2, 3, 4, 5, 6, -1 }; 866 863 867 864 yylex(); … … 876 873 prepare3(curr); 877 874 do_partner_table_full(1); do_partner_table_short(1); 878 do_partner_table_full(2); do_partner_table_short( 3);875 do_partner_table_full(2); do_partner_table_short(2); 879 876 do_partner_table_full(3); do_partner_table_short(3); 880 877 do_partner_table_full(4); do_partner_table_short(4); 881 878 do_partner_table_full(5); do_partner_table_short(5); 879 do_partner_table_full(6); do_partner_table_short(6); 882 880 do_partner_table_full(7); do_partner_table_short(7); 883 881 do_partner_table_full(8); do_partner_table_short(8); 884 do_partner_table_full(9); do_partner_table_short(9);885 do_partner_table_full(10); do_partner_table_short(10);886 do_partner_table_full(11); do_partner_table_short(10);887 882 888 883 curr = data_new(0,0); … … 891 886 prepare2(curr); 892 887 prepare3(curr); 893 do_livrable_tables( 70);888 do_livrable_tables(40); 894 889 return 0; 895 890 } -
anr/section-4.4.tex
r266 r278 17 17 \hspace*{-.4cm}%\vspace{-1.5cm} 18 18 \input{gantt1.tex} 19 \caption{\label{gantt1}Gantt diagram of deliverables (task-1 to task- 4 and task-8)}19 \caption{\label{gantt1}Gantt diagram of deliverables (task-1 to task-6)} 20 20 \end{figure} 21 21 … … 23 23 \hspace*{-.4cm}%\vspace{-1.5cm} 24 24 \input{gantt2.tex} 25 \caption{\label{gantt2}Gantt diagram of deliverables (task- 5, task-6 and task-7)}25 \caption{\label{gantt2}Gantt diagram of deliverables (task-7 and task-8)} 26 26 \end{figure} 27 27 … … 74 74 % Our experience with UGH and GAUT give us confidence in the succes of this 75 75 % task. 76 \item[Virtual prototyping of \altera \& \xilinx architectural templates ({\csgAlteraSystemC}, 77 {\csgXilinxSystemC})] 76 \item[Virtual prototyping of \altera \& \xilinx architectural templates (\novers{\csgImplementation})] 78 77 The SoCLib component library contains several SystemC models used for the virtual 79 78 prototyping of the \altera and \xilinx architectural templates (NIOS and Microblaze processor cores). -
anr/section-7.tex
r268 r278 169 169 170 170 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 171 \subsection{Partner 6: \xilinx} 172 171 \subsection{Partner 6: \mds} 172 173 \begin{ADDEDENV} 173 174 \begin{description} 174 175 \item[Equipment] … … 178 179 The man power detail in \hommemois by deliverables is given in 179 180 figure~\ref{table-livrables-1} and a sumary by task in the following table. 180 \begin{center}\input{table_ xilinx_short.tex}\end{center}181 \begin{center}\input{table_mds_short.tex}\end{center} 181 182 \item[Subcontracting] 182 183 No subcontracting costs. … … 187 188 \item[Other working costs] none 188 189 \end{description} 190 \end{ADDEDENV} 189 191 190 192 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% … … 234 236 235 237 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 236 \subsection{Partner 9: \zied}237 238 \begin{description}239 \item[Equipment]240 No equipement costs.241 \item[Personnel costs]242 The effort to define SoC architecture and adapt eFPGA interface to generate is243 estimated to 9.6 \hommemois.244 The effort to develop demonstrator and to extract eFPGA timining characteristics is245 estimated to 4.8 \hommemois.246 Finally we need one 3.6 man.month for the evaluation of the FLEXRAS solution.247 The table below summarizes the these manpower costs in \hommemois for the deliverables248 and by tasks.249 \begin{center}\input{table_zied_full.tex}\end{center}250 \item[Subcontracting]251 No subcontracting costs.252 \item[Travel]253 No travel costs.254 \item[Expenses for inward billing] none255 \item[Other working costs] none256 \end{description}257 258 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%259 \subsection{Partner 10: \navtel}260 261 \begin{description}262 \item[Equipment]263 Navtel will use FPGA board with ARM processors for the validation.264 The costs for depreciation of the board and the instrument of test265 are evaluated to 7\% of the total requested ANR funding.266 \item[Personnel costs]267 A permanent engineer will be assigned on average 1/3 time for268 all the duration of the project.269 The table below shows the estimated manpower cost in \hommemois for the deliverables270 and by tasks.271 \begin{center}\input{table_navtel_full.tex}\end{center}272 \item[Subcontracting]273 No subcontracting costs.274 \item[Travel]275 The travel costs are associated to meeting, plenaries as well as participation to276 conferences. The travel costs are estimated to 3 k\euro.277 \item[Expenses for inward billing] none278 \item[Other working costs] none279 \end{description}280 238 % 281 239 \begin{landscape} … … 286 244 \begin{minipage}[b]{.47\linewidth}\center 287 245 \input{table_inria_cairn_full.tex}\vspace{.5ex}\\ \irisa \vspace{2.5ex}\\ 288 \input{table_ xilinx_full.tex}\vspace{.5ex}\\ \xilinx\\246 \input{table_mds_full.tex}\vspace{.5ex}\\ \mds \\ 289 247 \end{minipage}\hfill\begin{minipage}[b]{.47\linewidth}\center 290 248 \input{table_tima_full.tex}\vspace{.5ex} \\ \tima -
anr/task-0.tex
r267 r278 1 1 \begin{taskinfo} 2 \let\ UPMC\leader2 \let\MDS\leader 3 3 \let\ALL\enable 4 4 \end{taskinfo} … … 20 20 % 21 21 \begin{workpackage} 22 \subtask This \ST consists in writing and ratifying the consortium agreement.22 \subtask{Consortium agreement} This \ST consists in writing and ratifying the consortium agreement. 23 23 \begin{livrable} 24 24 \CoutHorsD{0}{36}{\Subs}{project management}{1:1:1} 25 \itemL{0}{6}{d}{\S upmc}{Consortium agreement}{1:0:0}25 \itemL{0}{6}{d}{\Smds}{Consortium agreement}{1:0:0} 26 26 A document describing the consortium agreement, signed by all the partners. 27 27 \end{livrable} 28 \subtask This \ST concerns the global management of the deliverables and of the global28 \subtask{Global management} This \ST concerns the global management of the deliverables and of the global 29 29 organization of the project at all the levels. 30 30 \begin{livrable} 31 \itemL{0}{36}{d}{\S upmc}{Global management}{1:1:1}31 \itemL{0}{36}{d}{\Smds}{Global management}{1:1:1} 32 32 Global management of the project at all the 33 33 levels: progress monitoring, record keeping, meeting organization, review 34 34 organization, the writing of the review reports. 35 35 \end{livrable} 36 \subtask This \ST consists in managing the project at the partner level.36 \subtask{Partner level management} This \ST consists in managing the project at the partner level. 37 37 It includes mainly the progress monitoring, the record keeping the participation to the 38 38 project meetings and the communication with the project leader and the other partners. … … 41 41 \CoutHorsD{0}{36}{\Stima}{project management}{1:1:1} 42 42 \end{livrable} 43 \subtask This \ST consists firstly in the building, and next in the administration and the 44 maintenance of the development and dissemination infrastructure. It is also in charge of 43 \subtask{Setup of dissemination infrastructure} 44 This \ST consists firstly in the building, and next in the administration and the 45 maintenance of the development and dissemination infrastructure. It is also in charge of 45 46 the COACH releases distribution. 46 47 \begin{livrable} -
anr/task-1.tex
r244 r278 12 12 % 13 13 \begin{workpackage} 14 \subtask This \ST specifies the COACH environment for the system designer. At this 15 level the COACH framework is a black box. The deliverables are documents 16 specifying: how to feed COACH (the inputs), how to use COACH (the design flow), 14 \subtask{Specification of the COACH environment} 15 This \ST specifies the COACH environment for the system designer. In this 16 \ST the COACH framework is a black box. The deliverables are documents 17 specifying: how to feed COACH (the inputs), how to use COACH (use model), 17 18 what is generated (the outputs). 18 19 %(definition of the generic architecture of the … … 22 23 \itemV{0}{6}{d}{\Supmc}{COACH specification} \setMacroInAuxFile{specGenManualI} 23 24 The first version of the COACH specification. 24 This document contains the general description of the framework, the design flowand the25 This document contains the general description of the framework, the use model and the 25 26 description of the architectural templates. 26 27 It refers to the HAS specification (deliverable {\specHasManual}) and … … 50 51 feed-backs of the demonstrator \STs. 51 52 \end{livrable} 52 \subtask This \ST specifies the software COACH structure. The deliverable is a 53 \subtask{Internal software structure} 54 This \ST specifies the COACH software structure. The deliverable is a 53 55 document listing all the COACH software components and how they cooperate. 54 56 \begin{livrable} … … 57 59 Description of the software list and the data flow among the tools. 58 60 \end{livrable} 59 \subtask This \ST specifies the \xcoach and the \xcoachplus formats. 61 \subtask{\xcoach format} 62 This \ST specifies the \xcoach and the \xcoachplus formats. 60 63 \begin{livrable} 61 64 \itemV{0}{6}{d+x}{\Slip}{\xcoach format specification} … … 74 77 \itemV{6}{12}{x}{\Subs}{First release of C2X} 75 78 \setMacroInAuxFile{specXcoachToCAI} 76 A GCC plugin C2X that generates a \xcoach description 79 This delivrable groups 2 tools. 80 The first one C2X is a GCC plugin that generates a \xcoach description 77 81 (defined in {\specXcoachDocI} deliverable) from a C/C++ task description 78 82 (defined in {\specHasManual} deliverable). 79 \itemL{12}{18}{x}{\Subs}{C2X tool}{2:1:0} 83 The second one X2C regenerates a C description from a \xcoach 84 description. 85 % TACHE INCLUSE mais non decrite; Specification of the GCC driver tool. 86 \itemL{12}{18}{x}{\Subs}{C2X tool}{4:2:0} 80 87 \setMacroInAuxFile{specXcoachToCA} 81 An updated version of C2X (\specXcoachToCAI) which supports the \xcoach format defined88 An updated version of C2X and X2C (\specXcoachToCAI) which supports the \xcoach format defined 82 89 in the {\specXcoachDoc} deliverable and the HAS input format defined in the {\specHasManual} 83 90 deliverable. 84 \itemV{7}{12}{x}{\Subs}{First release of X2C}85 \setMacroInAuxFile{specXcoachToCBI}86 This second tool X2C regenerates a C description from a \xcoach87 description.88 \itemL{12}{18}{x}{\Subs}{X2C tool}{2:1:0}89 \setMacroInAuxFile{specXcoachToCB}90 The same software as the former (\specXcoachToCBI) but for the \xcoach format as defined91 in the {\specXcoachDoc} deliverable and HAS input as defined in the {\specHasManual}92 deliverable.91 % \itemV{7}{12}{x}{\Subs}{First release of X2C} 92 % \setMacroInAuxFile{specXcoachToCBI} 93 % This second tool X2C regenerates a C description from a \xcoach 94 % description. 95 % \itemL{12}{18}{x}{\Subs}{X2C tool}{2:1:0} 96 % \setMacroInAuxFile{specXcoachToCB} 97 % The same software as the former (\specXcoachToCBI) but for the \xcoach format as defined 98 % in the {\specXcoachDoc} deliverable and HAS input as defined in the {\specHasManual} 99 % deliverable. 93 100 \itemV{12}{18}{x}{\Supmc}{First release of X2SC} 94 101 \setMacroInAuxFile{specXcoachToSystemCI} … … 106 113 Final release of the former software (\specXcoachToVhdlI) and integration 107 114 of enhancements proposed in \novers{\specXilinxOptimization} deliverable. 108 \itemL{18}{21}{d}{\Sxilinx}{\xilinx RTL optimisation (1)}{0:3:0}109 \setMacroInAuxFile{specXilinxOptimization}110 This deliverable consists in optimizing the VHDL generated from \xcoachplus format111 (deliverable \novers{\specXcoachToVhdl}) for the \xilinx RTL synthesis tools.112 \ubs will provide several examples of VHDL source files generated from \xcoachplus,113 with explanations about generation process of main data structures used in VHDL sources,114 \xilinx will provide back a documentation listing that proposes VHDL generation enhancements.115 115 \end{livrable} 116 116 117 \subtask This \ST aims to define a tool in order to pilot the GCC/xcoach compiler. 118 \begin{livrable} 119 \itemL{0}{3}{d}{\Subs}{GCC driver specification}{1:0:0} 120 Specification of the GCC driver tool. 121 \itemV{3}{9}{x}{\Subs}{GCC driver} 122 First release of the GCC driver tool. 123 %en T0+18 car va peut etre evoluer en fonction du DSE µ-archi 124 \itemL{9}{12}{x}{\Subs}{GCC driver}{3:0:0} 125 Final release of the GCC driver tool. 126 \end{livrable} 117 % TACHE INCLUSE SANS X2C & C2X 118 %\subtask This \ST aims to define a tool in order to pilot the GCC/xcoach compiler. 119 % \begin{livrable} 120 % \itemL{0}{3}{d}{\Subs}{GCC driver specification}{1:0:0} 121 % Specification of the GCC driver tool. 122 % \itemV{3}{9}{x}{\Subs}{GCC driver} 123 % First release of the GCC driver tool. 124 % %en T0+18 car va peut etre evoluer en fonction du DSE µ-archi 125 % \itemL{9}{12}{x}{\Subs}{GCC driver}{3:0:0} 126 % Final release of the GCC driver tool. 127 % \end{livrable} 127 128 128 \subtask Backend HLS tools use a characterized macro-cell library to build the 129 \subtask{Tool for cell library creation} 130 Backend HLS tools use a characterized macro-cell library to build the 129 131 micro-architecture of a coprocessor. The characterisation of a cell depends 130 132 on the target device. The role of this \ST is to define the macro-cells and -
anr/task-2.tex
r253 r278 12 12 Its objective is to allow the system designer to explore the design space by 13 13 quickly prototyping and then to automatically generate the FPGA-SoC systems. 14 This task consists of 14 This task consists of: 15 15 \begin{itemize} 16 \item The development of all the missing components (SytemC models and/or synthesizable VHDL models17 of the IP-cores), 16 \item The development of the synthesizable models required for the connection of 17 the coprocessors on the platform bus (2 bridges). 18 18 \item The configuration and the development of drivers of the operating systems (Board Support Package, HAL), 19 19 \item The CSG software that generates the SystemC simulators for prototyping and the FPGA-SoC system 20 20 including its bitstream and software executable code, 21 \item The specification of enhanced communication schemes and their sofware and hardware implementations.22 21 \end{itemize} 23 This task being based on the SoCLib platform, a first release will be delivered at $T0+12$ 24 to allow the demonstrators to start working. 25 This release will include the standard communication schemes (based on SoCLib MWMR component) 22 A first release will be delivered at $T0+12$ to allow the demonstrators to start working. 23 This release will include the standard communication schemes based on SoCLib MWMR component 26 24 and support the neutral architectural template for prototyping and hardware generation. 27 25 \end{objectif} 28 26 % 29 27 \begin{workpackage} 30 \subtask This \ST corresponds to the COACH System Generator (CSG) software. 28 \subtask{Bridge implementation} 29 This \ST deals with the development of the synthesizable models required for the connection of 30 the coprocessors on the platform bus). 31 31 \begin{livrable} 32 \itemV{0}{12}{x}{\Supmc}{CSG tool} \setMacroInAuxFile{csgCoachArch} 33 The first software release of the CSG tool that will allow demonstrators to start 34 working by using the neutral architectural template. 35 \itemV{12}{18}{x}{\Supmc}{CSG} \setMacroInAuxFile{csgPrototypingOnly} 36 The second release of CSG supports the \xilinx and \altera architectural 37 templates and the enhanced communication system, but only for SystemC prototyping. 38 This release integrates a first integration of HLS tools. 39 \itemV{18}{24}{x}{\Supmc}{CSG} \setMacroInAuxFile{csgAllArch} 40 This milestone extends CSG (\csgPrototypingOnly) to 41 FPGA-SoC generation for the \xilinx and \altera architectural template. 42 \itemL{24}{36}{x}{\Supmc}{CSG tool}{6:5.5:5.5} 43 Final release of CSG. 32 \itemL{9}{18}{h}{\Stima}{HPC hardware \xilinx}{3:9:0} 33 \setMacroInAuxFile{hpcPlbBridge} 34 The synthesizable VHDL description of a PLB/VCI bridge. 35 \itemL{9}{18}{h}{\Supmc}{HPC hardware \altera}{1:2:0} 36 \setMacroInAuxFile{hpcAvalonBridge} 37 The synthesizable VHDL description of an AVALON/VCI bridge. 44 38 \end{livrable} 45 \subtask This \ST deals with the components of the architectural templates. 46 \\ 47 For the neutral architectural template, it consists of the development of the VHDL 48 synthesizable description of the missing communication components (MWMR) 49 in order to support the process network communication model. 50 Notice that the SystemC models 51 comes from the SocLib ANR project, the processor with its cache comes from the TSAR 52 ANR project. 53 \\ 54 For the \xilinx and \altera architectural templates, we use the \xilinx and \altera IPs (NIOS, Microblaze, memories, busses...). 55 \begin{livrable} 56 \itemL{0}{12}{h}{\Supmc}{Neutral architecture}{1:0:0} 57 \setMacroInAuxFile{csgCoachArchTempl} 58 The VHDL synthesizable descriptions of the SocLib MWMR, TokenRing components. 59 \itemL{12}{15}{d}{\Sxilinx}{\xilinx RTL optimisation (2)}{0:2:0} 60 This deliverable consists in optimizing the VHDL descriptions of the components of 61 the neutral architectural template (deliverable \novers{\csgCoachArchTempl}) to the 62 \xilinx RTL synthesis tools. 63 \upmc will provide the VHDL descriptions, \xilinx will provide back a documentation 64 listing that proposes VHDL generation enhancements. 65 \itemV{6}{18}{x}{\Stima}{\xilinx architecture} 66 \setMacroInAuxFile{csgXilinxSystemC} 67 The SystemC simulation module of the MWMR component with a PLB bus interface plus 68 the SystemC modules of the components of the \xilinx architectural template 69 currently not available in the SocLib component library. 70 \itemL{18}{24}{h}{\Stima}{\xilinx architecture}{9:9:0} 71 The synthesizable VHDL description of the MWMR component corresponding to the 72 SystemC module of the former deliverable (\csgXilinxSystemC). 73 \itemL{24}{27}{d}{\Sxilinx}{\xilinx RTL optimisation (3)}{0:0:1.5} 74 This deliverable consists in optimizing the MWMR VHDL description (deliverable 75 \novers{\csgXilinxSystemC}) of the \xilinx architectural template. 76 \tima will provide MWMR VHDL description, \xilinx will provide back a documentation 77 listing that proposes VHDL generation enhancements. 78 \itemV{6}{18}{x}{\Sirisa}{\altera architecture} 79 \setMacroInAuxFile{csgAlteraSystemC} 80 The SystemC simulation module of the MWMR component with an AVALON bus interface plus 81 the SystemC modules of the components of the \altera architectural template 82 currently not available in the SocLib component library. 83 \itemL{18}{24}{h}{\Sirisa}{\altera architecture}{6:6:0} 84 The synthesizable VHDL description of the MWMR component corresponding to the 85 SystemC module of the former deliverable (\csgAlteraSystemC); 86 \itemL{6}{12}{d}{\Subs}{Communication adapter spec.}{1:0:0} 87 \setMacroInAuxFile{gautCOMMoptimization} 88 Specification of an optimized communication adapter (space and time) component to handle data interleaving. 89 This evolution aims to solve out of order communication weakness of the classical MWMR. 90 \itemV{12}{24}{x}{\Subs}{Communication adapter}{0:6:0} 91 First release of the tool that generates the VHDL description of the optimized communication adapter 92 and its corresponding SystemC module. 93 \itemL{24}{30}{x}{\Subs}{Comm. adapter generator}{0:6:3} 94 Final release of the tool that generates the VHDL description of the optimized 95 communication adapter and its corresponding SystemC module (\gautCOMMoptimization). 96 \itemL{24}{27}{d}{\Sxilinx}{\xilinx RTL optimisation (4)}{0:0:1.5} 97 This deliverable consists in optimizing the communication adapter VHDL description (deliverable 98 \novers{\gautCOMMoptimization}). 99 \ubs will provide communication adapter VHDL description, \xilinx will provide back a documentation 100 listing that proposes VHDL generation enhancements. 101 \end{livrable} 102 \subtask This \ST consists of the configuration of the SocLib MUTEKH and DNA operating 103 system and the development of drivers for the hardware architectural templates 104 and enhanced communication schemes defined in \novers{\specCsgManual} deliverable. 39 \subtask{OS setup} This \ST consists of the configuration of the SocLib DNA operating 40 system and the development of drivers for the hardware architectural templates. 105 41 For the \altera and \xilinx architectural templates, the OSs must also be ported on 106 42 the NIOS2 and MICROBLAZE processors. 107 43 \begin{livrable} 108 \itemV{6}{8}{x}{\Supmc}{MUTEKH OS}109 The drivers required for the first CSG milestone (deliverable \csgCoachArch).110 \itemV{8}{18}{x}{\Supmc}{MUTEKH 0S drivers}111 The drivers required for the second CSG milestone ({\csgPrototypingOnly}).112 \itemL{18}{33}{x}{\Supmc}{MUTEKH OS drivers}{1:1:2}113 Final release of the MUTEKH OS drivers.114 \itemL{6}{18}{x}{\Supmc}{Porting of MUTEKH OS}{1.0:1:0}115 Porting of MUTEKH OS on the NIOS2 and MICROBLAZE processors.44 %IVG \itemV{6}{8}{x}{\Supmc}{MUTEKH OS} 45 %IVG The drivers required for the first CSG milestone (deliverable \csgCoachArch). 46 %IVG \itemV{8}{18}{x}{\Supmc}{MUTEKH 0S drivers} 47 %IVG The drivers required for the second CSG milestone ({\csgPrototypingOnly}). 48 %IVG \itemL{18}{33}{x}{\Supmc}{MUTEKH OS drivers}{1:1:2} 49 %IVG Final release of the MUTEKH OS drivers. 50 %IVG \itemL{6}{18}{x}{\Supmc}{Porting of MUTEKH OS}{1.0:1:0} 51 %IVG Porting of MUTEKH OS on the NIOS2 and MICROBLAZE processors. 116 52 \itemV{6}{8}{x}{\Stima}{DNA OS} 117 The drivers required for the first CSG milestone (deliverable \csgCoachArch).53 The drivers required for the first CSG milestone. 118 54 \itemV{8}{18}{x}{\Stima}{DNA 0S} 119 The drivers required for the second CSG milestone ({\csgPrototypingOnly}).55 The drivers required for the second CSG milestone. 120 56 \itemL{18}{33}{x}{\Stima}{DNA OS drivers}{6:3:2} 121 57 Final release of the DNA OS drivers. … … 123 59 Porting of DNA OS on the NIOS2 and MICROBLAZE processors. 124 60 \end{livrable} 61 % 62 \subtask{Implementation of CSG} This \ST corresponds to the COACH System Generator (CSG) software. 63 \begin{livrable} 64 \itemV{0}{12}{x}{\Supmc}{CSG tool} 65 The first software release of the CSG tool that will allow demonstrators to start 66 working by using the neutral architectural template only for SystemC. 67 \itemV{12}{18}{x}{\Supmc}{CSG} 68 The second release of CSG integrates the VHDL driver for the neutral 69 architectural template, and an integration of an HLS tools 70 but only for SystemC prototyping. 71 \itemV{18}{24}{x}{\Supmc}{CSG} 72 This release extends CSG to FPGA-SoC generation for the \xilinx and \altera architectural template. 73 \itemL{24}{36}{x}{\Supmc}{CSG tool}{6:5.5:5.5} \setMacroInAuxFile{csgImplementation} 74 Final release of CSG enhanced by the demonstrator's feedback. 75 \end{livrable} 125 76 \end{workpackage} -
anr/task-3.tex
r267 r278 21 21 % 22 22 \begin{workpackage} 23 \subtask This sub-task aims at providing compiler support for custom instructions 23 \subtask{ASIP compiler} 24 This sub-task aims at providing compiler support for custom instructions 24 25 within the HAS front-end. It will take as input the COACH intermediate 25 26 representation, and will output an annotated COACH IR containing the custom … … 36 37 \end{livrable} 37 38 38 \subtask In this sub-task, we provide micro-architectural template models for the two target 39 \subtask{Micro-architectural template models for ASIP} 40 In this sub-task, we provide micro-architectural template models for the two target 39 41 processor architectures (NIOS-II and MIPS) supported within the COACH-ASIP design flow. 40 42 For each processor, we provide a simulation model (System-C) and a synthesizable model (VHDL) … … 46 48 {A SystemC simulation model for an extensible MIPS with a tight architectural integration of 47 49 its instruction set extensions} 48 \itemL{0}{12}{x}{\Sirisa}{SystemC for NIOS processor}{2:0:0}49 { A SystemC simulation model for an extensible NIOS processor template, the VHDL model being50 already available from \altera}51 50 \itemV{3}{18}{h}{\Sirisa}{VHDL for an extensible MIPS} 52 51 {A synthesizable VHDL model for a simple extensible MIPS architectural template} … … 59 58 \end{livrable} 60 59 61 \subtask Extraction of parallelism in polyhedral loops and conversion into a process network.62 60 \subtask{Parallelism optimization} 61 Extraction of parallelism in polyhedral loops and conversion into a process network. 63 62 \begin{livrable} 64 63 \itemV{0}{6}{d}{\Slip}{Method, Preliminary Definition} -
anr/task-4.tex
r267 r278 9 9 The objectives of this task are to provide the two HAS back-ends of the COACH project and 10 10 a tool that adapt the coprocessor frequency to the FPGA-SoC frequency as required 11 by the processors and the system BUS. 12 %pourquoi en majuscule? 11 by the processors and the system bus. 13 12 \\ 14 13 The HAS back-ends as shown in figure~\ref{archi-hls} reads an \xcoach description and provides an … … 22 21 UGH. These tools are complementary and not in competition because they cover respectively 23 22 data and control dominated designs. 24 The organization of the task is firstly to quickly integrate the existing HLS to the COACH25 framework. Secondly these tools will be improved to allows to treat data dominated application26 with a few control for GAUT and control dominated application with a few data processing27 for UGH. This will enlarge the domain the HLS can cover which is a strong limitation of the28 tools currently avilable \cite{HLSBOOK} \cite{IEEEDT} \cite{CATRENE}.29 23 \end{objectif} 30 24 31 %FIXMA == {il faudrait fusionner les taches ST5-1 et ST5-2, non ???}32 25 \begin{workpackage} 33 \subtask The goal of this \ST is to integrate the UGH HLS tool to the COACH framework. It34 consists of suppressing the C compiler and the SystemC and VHDL drivers and replacing35 them by \xcoach and \xcoachplus drivers i.e. C2X, X2SC and X2VHDL.26 \subtask{Making HAS back-end to read \xcoach format} 27 The goal of this \ST is to integrate the UGH and GAUT HLS tool to the COACH framework. 28 by implementing the mechanism to read \xcoach format. 36 29 \begin{livrable} 37 30 \itemL{6}{12}{x}{\Stima}{UGH integration}{12:0:0} 38 31 Release of the UGH software that reads \xcoach format. 39 \itemV{12}{18}{x}{\Supmc}{UGH integration}40 Release of the UGH software that writes \xcoachplus format.41 \itemL{18}{33}{x}{\Supmc}{UGH integration}{0:2:4.0}42 Final release of the UGH software.43 \end{livrable}44 \subtask The goal of this \ST is to integrate the GAUT HLS tool to the COACH framework. It45 consists of suppressing the C compiler and the SystemC and VHDL drivers and replacing46 them by \xcoach and \xcoachplus drivers.47 \begin{livrable}48 32 \itemL{6}{12}{x}{\Subs}{GAUT release reading \xcoach}{6:0:0} 49 33 Release of the GAUT software that is able to read \xcoach format. 34 \end{livrable} 35 % 36 \subtask{Making HAS back-end to write \xcoachplus format} 37 The goal of this \ST is to integrate the UGH and GAUT HLS tool to the COACH framework. 38 by implementing the mechanism to write \xcoachplus format. 39 \begin{livrable} 40 \itemL{12}{18}{x}{\Supmc}{UGH integration}{0:2:4.0} 41 Release of the UGH software that writes \xcoachplus format. 50 42 \itemL{12}{18}{x}{\Subs}{GAUT release writing \xcoachplus}{0:6:0} 51 43 Release of the GAUT software that is able to read \xcoach format and to write \xcoachplus format. 52 %\itemL{18}{33}{x}{\Subs}{Final release of GAUT}{0:1:6}53 % Final release of the GAUT software.54 44 \end{livrable} 55 \subtask The goal of this \ST is to improve the UGH and GAUT HLS tools. 56 UGH and GAUT experimentations have shown respectively usefull enhancements. 57 \begin{livrable} 58 \itemL{18}{24}{x}{\Stima}{UGH enhancement 1}{0:9:0} 59 Release of the UGH software with support for treating automatically data dominated sections 60 included into a control dominated application. 61 \itemL{21}{27}{x}{\Stima}{UGH enhancement 2}{0:3:6} 62 Release of the UGH software able to generate a micro-architecture without the 63 variable binding currently done by the designer. 64 \itemL{12}{24}{x}{\Subs}{Release of GAUT with \ganttlf enhanced synthesis steps}{0:9:0} 65 Release of the GAUT software that supports the \xcoach model during the binding and the scheduling steps. 66 \itemL{24}{33}{x}{\Subs}{Release of GAUT supporting \ganttlf new const./obj.}{0:0:7} 67 Release of the GAUT software that supports the \xcoach model during the binding and the scheduling steps 68 and also supports new constraints and objectives. 69 \itemV{18}{24}{d}{\Subs}{Micro-architecture Exploration}\setMacroInAuxFile{MAE} 70 Specification of a Design Space Exploration framework for the HAS Back-end: 71 The high level specification tools, such as GAUT, have to be able to use synthesis feed-back 72 informations in order to explore the design space and to generate optimized architectures. 73 \itemL{24}{36}{x}{\Subs}{Micro-architecture Exploration}{0:4:4} 74 Release of the GAUT software that supports the features defined in \MAE 75 \end{livrable} 76 \subtask In FPGA-SoC, the frequency is given by the processor(s) and the system BUS. The coprocessors 45 46 \subtask{Coprocessor frequency adaptation} 47 In FPGA-SoC, the frequency is given by the processor(s) and the system BUS. The coprocessors 77 48 generated by HLS synthesis must respect this frequency. However, the HLS tools can not 78 49 guarantee that the micro-architectures they generate accurately respect this … … 84 55 \begin{livrable} 85 56 \itemV{0}{12}{d}{\Supmc}{Frequency calibration} 86 A document describing the set up of the coprocessor frequency calibration. :57 A document describing the set up of the coprocessor frequency calibration. 87 58 \itemV{12}{24}{x}{\Supmc}{Frequency calibration} 88 59 \setMacroInAuxFile{freqCalibrationVhdl} … … 91 62 The frequency calibration software consists of a driver in the FPGA-SoC operating 92 63 system and of a control software. 93 \itemL{24}{27}{d}{\Sxilinx}{\xilinx RTL optimisation (5)}{0:0:1.5}94 This deliverable consists in optimizing the VHDL description provided in95 \novers{\freqCalibrationVhdl}.96 \upmc will provide the VHDL description, \xilinx will provide back a documentation97 listing that proposes VHDL generation enhancements.98 64 \end{livrable} 99 65 \end{workpackage} -
anr/task-5.tex
r237 r278 20 20 \item Implementing the communication scheme at all levels: partition help, software 21 21 implementation both on the PC and in the operating system of the FPGA-SoC, hardware. 22 \item Providing support for dynamic partial reconfiguration of \xilinx FPGA in order23 to optimize FPGA ressource usage.22 %\item Providing support for dynamic partial reconfiguration of \xilinx FPGA in order 23 %to optimize FPGA ressource usage. 24 24 \end{itemize} 25 25 … … 33 33 % 34 34 \begin{workpackage} 35 \subtask 35 \subtask{Implementation of API between PC and FPGA-SoC} 36 36 This \ST deals with the COACH HPC feature that consists in accelerating an existing 37 ap llication running on a PC by migrating critical parts into a SoC implemented on an37 application running on a PC by migrating critical parts into a SoC implemented on an 38 38 FPGA plugged to the PC PCI/X bus. 39 39 The main steps and components of this \ST are: … … 54 54 \setMacroInAuxFile{hpcCommHelper} 55 55 A library implementing the communication API defined in the {\hpcCommApi} deliverable. 56 This library is dedicated to help the end-user to partition an applicattion for 57 HPC. 56 This library is dedicated to help the end-user to partition an application for HPC. 58 57 \itemL{12}{21}{x}{\Supmc}{HPC API for Linux PC}{0:2.5:0} 59 58 \setMacroInAuxFile{hpcCommLinux} 60 The PC part of the HPC communication API that comm inicates with the FPGA-SOC, a61 library and probablya LINUX module.62 \itemL{12}{21}{x}{\Supmc}{HPC API for MUTEKH OS}{0:2.5:0}63 \setMacroInAuxFile{hpcMutekDriver}64 The FPGA-SoC part of the communication API, a driver.59 The PC part of the HPC communication API that communicates with the FPGA-SOC, a 60 library and a LINUX module. 61 % \itemL{12}{21}{x}{\Supmc}{HPC API for MUTEKH OS}{0:2.5:0} 62 % \setMacroInAuxFile{hpcMutekDriver} 63 % The FPGA-SoC part of the communication API, a driver. 65 64 \itemL{21}{24}{x}{\Stima}{HPC API for DNA OS}{0:3:0} 66 65 \setMacroInAuxFile{hpcDnaDriver} 67 Port of the {\hpcMutekDriver} driver on the DNA OS. 68 \itemL{24}{33}{x}{\Supmc}{HPC API}{0:0:1} 69 Bug corrections and enhancements of communication middleware 70 (\novers{\hpcCommApi}, \novers{\hpcCommHelper}, \novers{\hpcCommLinux}, 71 \novers{\hpcMutekDriver}, \novers{\hpcDnaDriver}). 66 The FPGA-SoC part of the communication API. 67 % Port of the {\hpcMutekDriver} driver on the DNA OS. 68 % \itemL{24}{33}{x}{\Supmc}{HPC API}{0:0:1} 69 % Bug corrections and enhancements of communication middleware 70 % (\novers{\hpcCommApi}, \novers{\hpcCommHelper}, \novers{\hpcCommLinux}, 71 % \novers{\hpcMutekDriver}, \novers{\hpcDnaDriver}). 72 72 \end{livrable} 73 73 74 \subtask This \ST deals with the implementation of hardware and SystemC modules 74 \subtask{SystemC model of the PCI/X} 75 This \ST deals with the implementation of hardware and SystemC modules 75 76 required by the neutral architectural template for using the PCI/X IP of \altera and \xilinx. 76 77 \begin{livrable} 77 \itemL{9}{18}{h}{\Stima}{HPC hardware \xilinx}{3:9:0} 78 \setMacroInAuxFile{hpcPlbBridge} 79 The synthesizable VHDL description of a PLB/VCI bridge and its corresponding SystemC model. 80 \itemL{9}{18}{h}{\Supmc}{HPC hardware \altera}{1:2:0} 81 \setMacroInAuxFile{hpcAvalonBridge} 82 The synthesizable VHDL description of an AVALON/VCI bridge and its corresponding SystemC model. 78 % FIXME: moved to task 3 (CSG) 79 % \itemL{9}{18}{h}{\Stima}{HPC hardware \xilinx}{3:9:0} 80 % \setMacroInAuxFile{hpcPlbBridge} 81 % The synthesizable VHDL description of a PLB/VCI bridge and its corresponding SystemC model. 82 % \itemL{9}{18}{h}{\Supmc}{HPC hardware \altera}{1:2:0} 83 % \setMacroInAuxFile{hpcAvalonBridge} 84 % The synthesizable VHDL description of an AVALON/VCI bridge and its corresponding SystemC model. 83 85 \itemL{9}{24}{h}{\Supmc}{PCI/X traffic generator}{1:1:0} 84 86 The SystemC description of a component that generates PCI/X traffic. It is … … 86 88 \end{livrable} 87 89 88 \subtask This \ST consists in integrating dynamic partial reconfiguration of \xilinx FPGA in the CSG design flow.89 It also includes appropriate SoC-FPGA OS drivers and a modification of the profiling library.90 \begin{livrable}91 \itemL{24}{36}{x}{\Supmc}{CSG support for \ganttlf reconfiguration}{0:0:2}92 Modification of the CSG software to support statically reconfigurable tasks.93 \itemL{18}{36}{x}{\Stima}{CSG module for \ganttlf dynamic reconfiguration}{0:4:12}94 This livrable is a CSG module allowing to partition the task graph along95 the dynamic partial reconfiguration regions. The resulting task-region assignement96 is directly used for generation of bitstreams. The module also produces reconfiguration97 management software to be run on the SoC-FPGA.98 \itemL{18}{30}{x}{\Stima}{Dynamic reconfiguration \ganttlf for DNA drivers}{0:3:3}99 \setMacroInAuxFile{hpcDynconfDriver}100 The drivers required by the DNA OS in order to manage dynamic partial101 reconfiguration inside the SoC-FPGA.102 \itemL{30}{36}{x}{\Supmc}{Dynamic reconfiguration \ganttlf for MUTEKH drivers}{0:0:1}103 Port of the {\hpcDynconfDriver} drivers on the MUTEKH OS.104 \itemL{24}{36}{x}{\Stima}{Profiler for \ganttlf dynamic reconfiguration}{0:0:6}105 Extension of the HPC partionning helper in order to integrate dynamic partial106 reconfiguration dedicated features (reconfiguration time of regions, variable107 number of coprocessors).108 \itemL{24}{36}{d}{\Sxilinx}{Optimisation for \xilinx \ganttlf dynamic reconfiguration}{0:0:2}109 \xilinx will work with \tima in order to better take into account during110 partitioning decisions specific constraints due to partial reconfiguration process.111 The deliverable is a document describing the \xilinx specific constraints.112 \end{livrable}113 % \item This \ST is the delivery of 2 PCI/X \mustbecompleted{FIXME: Stratix4} FPGA board114 % with its PCI/X IP. These boards are dedicated to the COACH HPC development.115 % They are based on \mustbecompleted{FIXME:stratix4} FPGA device of 400,000 LUT.116 % \begin{livrable}117 % \itemL{0}{6}{m}{\Saltera}{HPC development boards}{0:0:0} Two PCI/X FPGA boards.118 % \end{livrable}90 % \subtask This \ST consists in integrating dynamic partial reconfiguration of \xilinx FPGA in the CSG design flow. 91 % It also includes appropriate SoC-FPGA OS drivers and a modification of the profiling library. 92 % \begin{livrable} 93 % \itemL{24}{36}{x}{\Supmc}{CSG support for \ganttlf reconfiguration}{0:0:2} 94 % Modification of the CSG software to support statically reconfigurable tasks. 95 % \itemL{18}{36}{x}{\Stima}{CSG module for \ganttlf dynamic reconfiguration}{0:4:12} 96 % This livrable is a CSG module allowing to partition the task graph along 97 % the dynamic partial reconfiguration regions. The resulting task-region assignement 98 % is directly used for generation of bitstreams. The module also produces reconfiguration 99 % management software to be run on the SoC-FPGA. 100 % \itemL{18}{30}{x}{\Stima}{Dynamic reconfiguration \ganttlf for DNA drivers}{0:3:3} 101 % \setMacroInAuxFile{hpcDynconfDriver} 102 % The drivers required by the DNA OS in order to manage dynamic partial 103 % reconfiguration inside the SoC-FPGA. 104 % \itemL{30}{36}{x}{\Supmc}{Dynamic reconfiguration \ganttlf for MUTEKH drivers}{0:0:1} 105 % Port of the {\hpcDynconfDriver} drivers on the MUTEKH OS. 106 % \itemL{24}{36}{x}{\Stima}{Profiler for \ganttlf dynamic reconfiguration}{0:0:6} 107 % Extension of the HPC partionning helper in order to integrate dynamic partial 108 % reconfiguration dedicated features (reconfiguration time of regions, variable 109 % number of coprocessors). 110 % \itemL{24}{36}{d}{\Sxilinx}{Optimisation for \xilinx \ganttlf dynamic reconfiguration}{0:0:2} 111 % \xilinx will work with \tima in order to better take into account during 112 % partitioning decisions specific constraints due to partial reconfiguration process. 113 % The deliverable is a document describing the \xilinx specific constraints. 114 % \end{livrable} 115 % %\item This \ST is the delivery of 2 PCI/X \mustbecompleted{FIXME: Stratix4} FPGA board 116 % % with its PCI/X IP. These boards are dedicated to the COACH HPC development. 117 % % They are based on \mustbecompleted{FIXME:stratix4} FPGA device of 400,000 LUT. 118 % % \begin{livrable} 119 % % \itemL{0}{6}{m}{\Saltera}{HPC development boards}{0:0:0} Two PCI/X FPGA boards. 120 % % \end{livrable} 119 121 \end{workpackage} -
anr/task-6.tex
r268 r278 13 13 % 14 14 \begin{workpackage} 15 \subtask 15 \subtask{\bull HPC demonstrator} 16 16 The application that \bull proposes is HPC oriented. 17 17 The domain of the application is the treatment of medical images (image noise … … 31 31 \end{livrable} 32 32 33 \subtask 34 The objective of this sub-task is to specify the THALESapplication and to develop the33 \subtask{\TRT Embedded SoC demonstrator} 34 The objective of this sub-task is to specify the \TRT application and to develop the 35 35 high level code. This application is in the domain of surveillance of critical 36 36 infrastructures. The objective is to detect and classify the presence of humans in the … … 53 53 This deliverable is a document that specifies the application. 54 54 \itemL{6}{12}{x}{\Sthales}{\thales demonstrator (step 1)}{4:0:0} 55 This deliverable is the code of the application sp cecified former55 This deliverable is the code of the application specified former 56 56 deliverable (\trtAppSpecification). 57 57 \end{livrable} 58 58 59 \subtask \TRT will use its internal software environment tool SPEAR DE to describe the 59 \subtask{SPEAR-DE adaptation for COACH} 60 \TRT will use its internal software environment tool SPEAR DE to describe the 60 61 application. The tool is able to partition and to generate the code for the target. \\ 61 62 In this task, we will adapt SPEAR DE to generate the application description input of … … 68 69 \end{livrable} 69 70 70 \subtask 71 \subtask{\mds use case} 72 \mds will use ................. 73 \begin{livrable} 74 \itemL{6}{18}{x}{\Smds}{Use case}{6:7:0} 75 \setMacroInAuxFile{trtSpearde} 76 Adaptation of SPEAR-DE for COACH framework. 77 \end{livrable} 78 79 \subtask{Evaluation report} 80 % FIXME: AJOUTER une evaluation de BULL ET MDS 71 81 In this sub-task, \TRT will evaluate the COACH platform. In particular, \TRT will verify 72 82 its ability to generate a whole VHDL of an embedded system on FPGA for an application … … 88 98 \end{livrable} 89 99 90 \subtask FLEXRAS will design an application based on M-JPEG video standard.91 FLEXRAS will propose a SoC architecture integrating an embedded FPGA (eFPGA).92 The architecture is composed essentially of a processor, a bus and several RAMs.93 The embedded FPGA is connected to the bus and communicates with the other components.94 The (eFPGA) works in 2 modes:95 \begin{description}96 \item[Slave mode]97 As a DMA, the processor will send the configuration bitstream98 stored on the RAM to the eFPGA. In this mode, the eFPGA is considered as a99 writeable memory and is configured by the processor.100 \item[Master mode]101 Once the FPGA is programmed, it becomes a coprocessor achieving the aimed task.102 \end{description}103 The top architecture of this SoC based-platform will be generated using COACH104 framework. The application that will be run on the SoC corresponds initially to a105 graph of software tasks. Critical tasks will be identified and transformed106 automatically to hardware tasks using COACH high level synthesis feature. While107 software tasks will be run on the processor, hardware ones will be mapped on eFPGA108 to take advantage of its optimized resources and parallelism. FLEXRAS provides all109 the flow from RTL synthesis to bitstream generation.110 \begin{livrable}111 \itemL{0}{6}{d}{\Szied}{\zied architecture}{2.4:0:0}112 FLEXRAS will use IPs provided by LIP6 (vhdl models of SoCLIB) and its eFPGA IP to113 generate the SoC architecture.114 This deliverable is a document that describes this architecture.115 \itemL{6}{18}{h}{\Szied}{eFPGA/VCI component}{3.6:3.6:0}116 FLEXRAS has to adapt the eFPGA interface to connect it to the VCI bus.117 This deliverable is a VHDL description.118 % \itemL{12}{18}{x}{\Szied}{bitstream loader port}{0:3.6:0}119 % Port of the bitstream loader to the MUTEKH operating system.120 \itemL{18}{24}{x}{\Szied}{\zied demonstrators}{0:2.4:0}121 \zied will propose to test COACH framework and the \zied architecture template122 throught an application based on M-JPEG video standard.123 This applicattion will containt 3 communicating tasks under the COACH format specified124 in {\novers{\specGenManual}} deliverable.125 The first one is a hardware task generated by the HAS tools and transformed into126 a bit stream by the \zied tools.127 The second is a bitstream loader that will load the bitstream of the first task on128 the eFPGA.129 The third is a software task that communicates with the hw task for testing it.130 \itemL{24}{30}{x}{\Szied}{eFPGA characterisation}{0:0:2.4}131 This deliverable is a file under the format defined by the deliverable132 {\specMacroCell} that characterizes the eFPGA. This will allow the COACH HLS tools133 to take into account the eFPGA delays.134 \itemL{30}{36}{d}{\Szied}{\zied evaluation}{0:0:3.6}135 This deliverable is a document that describes the tests, the validation and the136 evaluation of COACH with the \zied architecture and tools.137 \end{livrable}138 139 \subtask140 The \navtel Embedded Supper Computing (ESC) project is based on simple hardware but tightly141 coupled module between %ARM142 a embedded processor and an FPGA both on a board.143 By using the COACH environment, \navtel will automatically synthetize two cores: one for software radio144 through a polyphase resampler and one for an industrial control application through an embedded145 PID controller.146 The objective is to sequence the cores in realtime in FPGA using partial configuration methods147 proposed in the COACH project.148 This will allow us to gain experience on automatic multi core sequencing at system level. The149 specification for our first work package will concern this aspect.150 151 The ESC can function on different topologies: Single, parallel or Grid computing modes for152 industrial and scientific applications.153 %The ARM154 The processor and FPGA configuration also facilitate the co-simulation which allows to gain155 time on the development and integration phase.156 The architecture consists of a wrapper that encapsules computing units depending on the157 application and a real time kernal for task switching and partial reconfiguration of FPGA158 on run time environment.159 \parlf160 To day \navtel develops these computing units manually.161 \navtel expects to benefit from the COACH project especially the HLS tools for162 generating the computing unit.163 \begin{livrable}164 \itemL{0}{6}{d}{\Snavtel}{\navtel \ganttlf demonstrator specification}{4:0:0}165 \setMacroInAuxFile{navtelSpecification}166 A document that will define the requirements for automatic RTL generation for167 signal processing units of our market sector such as digital communication,168 imaging and industrial control.169 This document will include the description of some already handmade processing units.170 \itemL{6}{18}{h}{\Snavtel}{\navtel \ganttlf wrapper adaptation}{1:1:0}171 The adaptation of our wrapper to support coprocessor generated by COACH.172 \itemL{18}{36}{d}{\Snavtel}{\navtel evaluation}{0:2:4}173 \navtel will test the COACH HLS tools on the processing units that are described174 in the {\navtelSpecification} deliverable.175 A document will be written that describes the results obtained taking into176 account: 1) the performance in terms of space, 2) the performance in terms of177 time, 3) the friendlyness of the environment.178 \end{livrable}179 100 \end{workpackage} -
anr/task-7.tex
r267 r278 1 1 \begin{taskinfo} 2 \let\ UPMC\leader2 \let\MDS\leader 3 3 \let\ALL\enable 4 4 \end{taskinfo} … … 20 20 % 21 21 \begin{workpackage} 22 \subtask This \ST relates to the management of the WEB site and to the distribution of22 \subtask{\mustbecompleted{TITLE}} This \ST relates to the management of the WEB site and to the distribution of 23 23 the COACH releases. 24 24 \begin{livrable} … … 38 38 \CoutHorsD{12}{36}{\Stima}{dissemination}{0:2:1} 39 39 \end{livrable} 40 \subtask 40 \subtask{\mustbecompleted{TITLE}} 41 41 \label{subtask-tutorial} 42 42 This \ST consists of making a COACH tutorial and to publish it on the public WEB … … 59 59 \itemL{30}{36}{d}{\Supmc}{Tutorial}{2:1:1} 60 60 The final release of the tutorial. 61 \itemL{30}{33}{d}{\Sxilinx}{\xilinx feedback}{0:0:0.5}62 \xilinx will check that the developped tutorial works well with \xilinx tools,63 and will propose corrections or enhancements if needed into a document.64 61 \end{livrable} 65 \subtask 62 \subtask{\mustbecompleted{TITLE}} 66 63 This \ST consists of making the COACH user reference manuals. 67 64 They will be published on the public WEB site.
Note: See TracChangeset
for help on using the changeset viewer.