Changeset 134
- Timestamp:
- Feb 13, 2010, 3:24:29 PM (15 years ago)
- Location:
- anr
- Files:
-
- 15 edited
Legend:
- Unmodified
- Added
- Removed
-
anr/section-1.tex
r100 r134 71 71 architectural template and the target FPGA device. 72 72 \item[Hardware/Software communication middleware:] 73 C oachwill implement an homogeneous HW/SW communication infrastructure and73 COACH will implement an homogeneous HW/SW communication infrastructure and 74 74 communication APIs (Application Programming Interface), that will be used for 75 75 communications between software tasks running on embedded processors and … … 97 97 It stronly relies on SoCLib virtual prototyping platform~\cite{soclib} for prototyping, 98 98 99 \mustbecompleted{FIXME == SUPPRIMER LE H de Mutek ???} 100 (DSX, component library), operating systems (MutekH, DNA/OS). 99 (DSX, component library), operating systems (MUTEKH, DNA/OS). 101 100 It also leverages on several existing technologies: 102 101 on the GAUT~\cite{gaut08} and UGH~\cite{ugh08} tools for HLS, -
anr/section-2.1.tex
r99 r134 38 38 choice for low-to-medium volume applications. 39 39 Since their introduction in the mid eighties, FPGAs evolved from a simple, 40 low-capacity gate array to devices (\altera STRATIX III, Xilinx Virtex V) that40 low-capacity gate array to devices (\altera STRATIX III, \xilinx Virtex V) that 41 41 provide a mix of coarse-grained data path units, memory blocks, microprocessor cores, 42 42 on chip A/D conversion, and gate counts by millions. This high logic capacity allows to implement … … 74 74 software library that reflect the hardware configuration. 75 75 %% Steven disagree : the C2H compiler bundled with SOPCBuilder does a pretty good job at this. 76 %% IA: ces lignes ont ete verifiees et corrigée pa altera. De plus C2H est plutot limite.76 %% IA: ces lignes ont ete verifiees et corrigée pa \altera. De plus C2H est plutot limite. 77 77 Nevertheless, SOPC Builder does not provide any facilities to synthesize coprocessors and to 78 78 simulate the platform at a high design level (systemC). … … 96 96 \begin{enumerate} 97 97 \item a virtual prototyping environment such as SoCLib for system level exploration, 98 \item an architecture compiler (such as SOPC Builder from \altera, or System generator from Xilinx)99 98 \item an architecture compiler (such as SOPC Builder from \altera, or System generator 99 from \xilinx) to define the hardware architecture, 100 100 \item one or several HLS tools (such as PICO~\cite{pico} or CATAPULT-C~\cite{catapult-c}) for 101 101 coprocessor synthesis, -
anr/section-2.2.tex
r120 r134 7 7 The COACH project answers to several of the challenges found in different axis of the call for proposals. Keywords of the call are indicated below in italic writing. 8 8 9 Axis 1 "Architectures des syst emes embarque" :9 Axis 1 "Architectures des syst\`{e}mes embarqu\'{e}s" : 10 10 11 11 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 constraints and objectives (real-time, low-power). It will permit to design complex SoC based on IP cores ((memory, peripherals, network controllers, communication processors), running Embedded Software, as well as an Operating System with associated middleware and API and using hardware accelerator automatically generated. It will also permit to use efficiently different dynamic system management techniques and re-configuration mechanisms. -
anr/section-2.tex
r99 r134 50 50 in a plat-form based design flow supporting virtual prototyping and design space exploration. 51 51 Most building blocks already exist (resulting from previous projects): the GAUT 52 or UGH synthesis tools, the M utekH or DNA embedded operating systems, the ASIP technology,52 or UGH synthesis tools, the MUTEKH or DNA embedded operating systems, the ASIP technology, 53 53 the DSX exploration tool, the MWMR hardware/software communication middleware, the BEE parallelisation tool, 54 54 as well as the SoCLib library of systemC simulation models. They must now be integrated in … … 88 88 %\textbf{High Level Synthesis}: When dedicated hardware coprocessors have been 89 89 %identified as mandatory, they will be generated by the high level synthesis (HLS) tools. 90 %The C oachframework will integrate various HLS tools, supporting the micro-architectural space90 %The COACH framework will integrate various HLS tools, supporting the micro-architectural space 91 91 %design exploration. Here again, the exploration criteria are cost, throughput, latency 92 92 %and power consumption. -
anr/section-3.1.tex
r120 r134 54 54 cover the whole system synthesis process in a full automatic way. Moreover, 55 55 they are bound to a particular device family and to IPs library. 56 The most commonly used are provided by Altera and Xilinx to promote their56 The most commonly used are provided by \altera and \xilinx to promote their 57 57 FPGA devices. These two representative tools used to synthesize SoC on FPGA 58 58 are introduced below. 59 59 \\ 60 The Xilinx System Generator for DSP~\cite{system-generateur-for-dsp} is a60 The \xilinx System Generator for DSP~\cite{system-generateur-for-dsp} is a 61 61 plug-in to Simulink that enables designers to develop high-performance DSP 62 systems for Xilinx FPGAs.62 systems for \xilinx FPGAs. 63 63 Designers can design and simulate a system using MATLAB and Simulink. The 64 64 tool will then automatically generate synthesizable Hardware Description 65 Language (HDL) code mapped to Xilinx pre-optimized algorithms.66 However, this tool targets only DSP based algorithms, Xilinx FPGAs and65 Language (HDL) code mapped to \xilinx pre-optimized algorithms. 66 However, this tool targets only DSP based algorithms, \xilinx FPGAs and 67 67 cannot handle a complete SoC. Thus, it is not really a system synthesis tool. 68 68 \\ … … 70 70 system, to synthesis it, to programm it into a target FPGA and to upload a 71 71 software application. 72 % FIXME(C2H from Altera, marche vite mais ressource monstrueuse)72 % FIXME(C2H from \altera, marche vite mais ressource monstrueuse) 73 73 Nevertheless, SOPC Builder does not provide any facilities to synthesize 74 74 coprocessors. System Designer must provide the synthesizable description … … 77 77 accurate level. 78 78 \\ 79 In addition, Xilinx System Generator and SOPC Builder are closed world79 In addition, \xilinx System Generator and SOPC Builder are closed world 80 80 since each one imposes their own IPs which are not interchangeable. 81 81 … … 98 98 Moreover, low power consumption constraint is mandatory for embedded systems. 99 99 However, it is not yet well handled or not handle at all by the synthesis tools already available. 100 \item The parallelism is extracted from initial algorithmic specification. To get more parallelism or to reduce 101 the amount of required memory in the SoC, the user must re-write the algorithmic specification while there is 102 techniques as polyedric transformations to increase the intrinsic parallelism. 103 \item While they support limited loop transformations like loop unrolling and loop pipelining, current HLS tools 104 do not provide support for design space exploration neither through automatic loop transformations nor through 105 memory mapping. 100 \item The parallelism is extracted from initial algorithmic specification. 101 To get more parallelism or to reduce the amount of required memory in the SoC, the user 102 must re-write the algorithmic specification while there is techniques as polyedric 103 transformations to increase the intrinsic parallelism. 104 \item While they support limited loop transformations like loop unrolling and loop 105 pipelining, current HLS tools do not provide support for design space exploration neither 106 through automatic loop transformations nor through memory mapping. 106 107 \item Despite they have the same input language (C/C++), they are sensitive to the style in 107 108 which the algorithm is written. Consequently, engineering work is required to swap from -
anr/section-3.2.tex
r104 r134 83 83 3 architectural templates that are synthesizable and that can be prototyped, 84 84 one design space exploration tool, 85 2 operating systems (DNA/OS and MUTEK .85 2 operating systems (DNA/OS and MUTEKH. 86 86 \\ 87 87 The framework fonctionality will be demonstrated with the demonstrators -
anr/section-4.1.tex
r132 r134 32 32 hardware) either as a SystemC simulator to prototype and explore quickly the 33 33 design space or as a bitstream\footnote{COACH generates synthesizable VHDL, and 34 launch the Xilinx or Altera RTL synthesis tools.} directly downloadable on the34 launch the \xilinx or \altera RTL synthesis tools.} directly downloadable on the 35 35 FPGA device\footnote{Additional partial bitstreams are generated in case of 36 36 dynamic partial reconfiguration}. 37 %To proove CSG that COACH is open and CSG is really configurable, COACH will38 %basically support 3 architecture template (the COACH template based on a39 %MIPS processors and a VCI token ring, the Altera template based on the NIOS40 %and AVALON bus, the Xilinx template based on the MICROBLAZE and PLB bus)41 %and 2 operating systems (DNA/OS and MUTEK). Furthermore, thus is enforced42 %by the \mustbecompleted{FIXME:zied} contribution that consists in43 %implementing an other hardware target.44 %\\45 %Finally, it is important to notice that this work is a strong46 %enhancement of the SocLib software.47 37 \parlf 48 38 The software architecture for HAS is presented in figure~\ref{archi-hls}. -
anr/section-4.4.tex
r132 r134 36 36 written in the COACH input format. This COACH release allows to prototype and to generate the FPGA-SoC. 37 37 The main restrictions are: 38 1) only the COACHarchitectural template is supported,38 1) only the neutral architectural template is supported, 39 39 2) HAS is not available (but prototyping with virtual coprocessors is available), 40 40 3) Enhanced communication schemes are not available. 41 41 \item[Milestone 3 ($T0+18$)] The second COACH release. At this step most of the COACH 42 42 features are availables. 43 The main restriction is that COACH can not yet generate FPGA-SoC for ALTERA and XILINX44 architectural templates.43 The main restriction is that COACH can not yet generate FPGA-SoC for \altera and 44 \xilinx architectural templates. 45 45 The others restriction is that the HAS tools are not yet fully operational. 46 46 \item[Milestone 4 ($T0+24$)] The pre-release of the COACH project. The full design flow is … … 73 73 % Our experience with UGH and GAUT give us confidence in the succes of this 74 74 % task. 75 \item[Virtual prototyping of ALTERA \& XILINXarchitectural templates ({\csgAlteraSystemC},75 \item[Virtual prototyping of \altera \& \xilinx architectural templates ({\csgAlteraSystemC}, 76 76 {\csgXilinxSystemC})] 77 77 The SocLib component library contains several SystemC models used for the virtual 78 prototyping of the ALTERA and XILINXarchitectural templates (NIOS and Microblaze processor cores).78 prototyping of the \altera and \xilinx architectural templates (NIOS and Microblaze processor cores). 79 79 Nevertheless, at this time we do not know how many IP cores SystemC simulation models have to be developped. 80 80 If the workload of this simulation model development is too important, virtual prototyping … … 85 85 If one of these tasks is impossible or too important or leads to inefficiency, 86 86 it will be abandoned. 87 In this case, the COACHarchitectural template will not be available for HPC and87 In this case, the neutral architectural template will not be available for HPC and 88 88 a SystemC VCI model corresponding to the PCI/X IP will be developped to allow 89 89 virtual prototyping. -
anr/section-5.tex
r126 r134 1 1 \subsection{Dissemination} 2 2 3 The C oachproject will bring new scientific results in various fields, such as high level synthesis,3 The COACH project will bring new scientific results in various fields, such as high level synthesis, 4 4 hardware/software codesign, virtual prototyping, harware oriented compilation techniques, 5 5 automatic parallelisation, etc. These results will be presented in the relevant International 6 6 Conferences, namely DATE, DAC, or ICCAD. 7 7 8 More generally, the C oach infrastructure and the design flow supported by the Coach8 More generally, the COACH infrastructure and the design flow supported by the COACH 9 9 tools and libraries will be promoted by proposing tutorials on FPGA oriented system level synthesis 10 10 in various worshops and conferences. 11 11 12 12 Following the general policy of the SoCLib platform, the COACH project will be an 13 open infrastructure, and the C oachtools and libraries will available in the framework13 open infrastructure, and the COACH tools and libraries will available in the framework 14 14 of the SoCLib WEB server. This server will be maintened by the UPMC/LIP6 laboratory. 15 15 16 16 \subsection{Exploitation of results} 17 17 18 The main goal of the C oachproject is to help SMEs (Small and Medium Enterprises)18 The main goal of the COACH project is to help SMEs (Small and Medium Enterprises) 19 19 to enter the world of MPSoC technologies. For small companies, the cost is a primary concern. 20 20 Moreover, these companies have not always in-home expertise in hardware design and VHDL modelling. 21 As the fabrication costs of an ASIC is generally too high for SMEs, the C oachproject focus21 As the fabrication costs of an ASIC is generally too high for SMEs, the COACH project focus 22 22 on FPGA technologies. Regarding the design tools, the cost of advanced ESL (Electronic System Design) 23 tools is an issue, and the C oachproject will follow the same general policy as the SoCLib platform :23 tools is an issue, and the COACH project will follow the same general policy as the SoCLib platform : 24 24 25 25 \begin{itemize} 26 26 \item 27 All software tools supporting the C oachdesign flow will be available as free software.28 All academic partners contributing to the C oachproject agreed to distribute the ESL software27 All software tools supporting the COACH design flow will be available as free software. 28 All academic partners contributing to the COACH project agreed to distribute the ESL software 29 29 tools under the same GPL license as the SoCLib tools. 30 30 \item … … 42 42 For commercial use, commercial licenses will be negociated between the owners and the customers. 43 43 \item 44 The proprietary ALTERA, XILINX and FLEXRASIP core libraries are commercial products44 The proprietary \altera, \xilinx and \zied IP core libraries are commercial products 45 45 that are not involved by the free software policy, but these libraries will be supported by the 46 synthesis tools developped in the C oachproject.46 synthesis tools developped in the COACH project. 47 47 \end{itemize} 48 48 … … 59 59 60 60 A global consortium agreement will be defined during the first six monts of the project. 61 As already stated, the C oachproject has been prepared during one year by a monthly meeting61 As already stated, the COACH project has been prepared during one year by a monthly meeting 62 62 involving the five academic partners. The general free software policy described in the 63 63 previous section has been agreed by academic partners and has been -
anr/section-6.1.tex
r132 r134 150 150 Moreover, the LIP6 developped during the last 10 years the UGH tool for high level synthesis 151 151 of control-dominated coprocessors. 152 This tool will be modified to be integrated in the C oachdesign flow.153 \parlf 154 Even if the preferred dissemination policy for the C oachdesign flow will be the free software policy,152 This tool will be modified to be integrated in the COACH design flow. 153 \parlf 154 Even if the preferred dissemination policy for the COACH design flow will be the free software policy, 155 155 (following the SoCLib model), the SoC department is ready to support start-ups : Six startup companies 156 156 (including \zied) have been created by former researchers from the SoC department of LIP6 between 1997 and 2002. -
anr/section-6.2.tex
r132 r134 1 The C oachproject will be coordinated by professor Alain Greiner from1 The COACH project will be coordinated by professor Alain Greiner from 2 2 Université Pierre et Marie Curie. 3 3 Alain Greiner is the initiator and the main architect of the SoCLib project. 4 4 This ANR platform for virtual prototyping of MPSoCs involved 6 industrial companies 5 5 (including ST Microelectronics and Thales) and ten academic laboratories 6 (5 of them are involved in the C oachproject).6 (5 of them are involved in the COACH project). 7 7 The SoCLib project was managed by Thales, but the technical coordination has been done 8 8 by Alain Greiner, who has a good experience in coordinating large technical projects -
anr/task-2.tex
r126 r134 24 24 to allow the demonstrators to start working. 25 25 This release will include the standard communication schemes (base on SocLib MWMR component) 26 and support the COACHarchitectural template for prototyping and hardware generation.26 and support the neutral architectural template for prototyping and hardware generation. 27 27 \end{objectif} 28 28 % 29 29 \begin{workpackage} 30 \subtask This \ST corresponds to the C oachSystem Generator (CSG) software.30 \subtask This \ST corresponds to the COACH System Generator (CSG) software. 31 31 \begin{livrable} 32 32 \itemV{0}{12}{x}{\Supmc}{CSG} \setMacroInAuxFile{csgCoachArch} 33 The first software release of the CSG tool that will allow demonstrators to start working by using the COACH34 hardware architecturetemplate.33 The first software release of the CSG tool that will allow demonstrators to start 34 working by using the neutral architectural template. 35 35 \itemV{12}{18}{x}{\Supmc}{CSG} \setMacroInAuxFile{csgPrototypingOnly} 36 The second release of CSG supports the XILINX and ALTERAarchitectural36 The second release of CSG supports the \xilinx and \altera architectural 37 37 templates and the enhanced communication system, but only for SystemC prototyping. 38 38 This release integrates a first integration of HLS tools. 39 39 \itemV{18}{24}{x}{\Supmc}{CSG} \setMacroInAuxFile{csgAllArch} 40 40 This milestone extends CSG (\csgPrototypingOnly) to 41 FPGA-SoC generation for the XILINX and ALTERAarchitectural template.41 FPGA-SoC generation for the \xilinx and \altera architectural template. 42 42 \itemL{24}{36}{x}{\Supmc}{CSG}{6:6:6} 43 43 Final release of CSG. … … 45 45 \subtask This \ST deals with the components of the architectural templates. 46 46 \\ 47 For the COACHarchitectural template, it consists of the development of the VHDL47 For the neutral architectural template, it consists of the development of the VHDL 48 48 synthesizable description of the missing communication components (MWMR) 49 49 in order to support the process network communication model. … … 52 52 ANR project. 53 53 \\ 54 For the XILINX and ALTERA architectural templates, we use the XILINX and ALTERAIPs (NIOS, Microblaze, memories, busses...).54 For the \xilinx and \altera architectural templates, we use the \xilinx and \altera IPs (NIOS, Microblaze, memories, busses...). 55 55 \begin{livrable} 56 \itemL{0}{12}{h}{\Supmc}{ COACHarchitecture}{1:0:0}56 \itemL{0}{12}{h}{\Supmc}{neutral architecture}{1:0:0} 57 57 \setMacroInAuxFile{csgCoachArchTempl} 58 58 The VHDL synthesizable descriptions of the SocLib MWMR, TokenRing components. 59 59 \itemL{12}{15}{d}{\Sxilinx}{\xilinx RTL optimisation (2)}{0:2:0} 60 60 This deliverable consists in optimizing the VHDL descriptions of the components of 61 the COACHarchitectural template (deliverable \novers{\csgCoachArchTempl}) to the61 the neutral architectural template (deliverable \novers{\csgCoachArchTempl}) to the 62 62 \xilinx RTL synthesis tools. 63 63 \upmc will provide the VHDL descriptions, \xilinx will provide back a documentation 64 64 listing that proposes VHDL generation enhancements. 65 \itemV{6}{18}{x}{\Stima}{ XILINXarchitecture}65 \itemV{6}{18}{x}{\Stima}{\xilinx architecture} 66 66 \setMacroInAuxFile{csgXilinxSystemC} 67 67 The SystemC simulation module of the MWMR component with a PLB bus interface plus 68 the SystemC modules of the components of the XILINXarchitectural template68 the SystemC modules of the components of the \xilinx architectural template 69 69 currently not available in the SocLib component library. 70 \itemL{18}{24}{h}{\Stima}{ XILINXarchitecture}{9:9:0}70 \itemL{18}{24}{h}{\Stima}{\xilinx architecture}{9:9:0} 71 71 The synthesizable VHDL description of the MWMR component corresponding to the 72 72 SystemC module of the former delivrable (\csgXilinxSystemC). … … 76 76 \tima will provide MWMR VHDL description, \xilinx will provide back a documentation 77 77 listing that proposes VHDL generation enhancements. 78 \itemV{6}{18}{x}{\Sirisa}{ ALTERAarchitecture}78 \itemV{6}{18}{x}{\Sirisa}{\altera architecture} 79 79 \setMacroInAuxFile{csgAlteraSystemC} 80 80 The SystemC simulation module of the MWMR component with an AVALON bus interface plus 81 the SystemC modules of the components of the ALTERAarchitectural template81 the SystemC modules of the components of the \altera architectural template 82 82 currently not available in the SocLib component library. 83 \itemL{18}{24}{h}{\Sirisa}{ ALTERAarchitecture}{6:6:0}83 \itemL{18}{24}{h}{\Sirisa}{\altera architecture}{6:6:0} 84 84 The synthesizable VHDL description of the MWMR component corresponding to the 85 85 SystemC module of the former delivrable (\csgAlteraSystemC); … … 100 100 listing that proposes VHDL generation enhancements. 101 101 \end{livrable} 102 \subtask This \ST consists of the configuration of the SocLib MUTEK and DNA operating102 \subtask This \ST consists of the configuration of the SocLib MUTEKH and DNA operating 103 103 system and the development of drivers for the hardware architectural templates 104 104 and enhanced communication schemes defined in \novers{\specCsgManual} delivrable. 105 For the ALTERA and XILINXarchitectural templates, the OSs must also be ported on105 For the \altera and \xilinx architectural templates, the OSs must also be ported on 106 106 the NIOS2 and MICROBLAZE processors. 107 107 \begin{livrable} 108 \itemV{6}{8}{x}{\Supmc}{MUTEK OS}108 \itemV{6}{8}{x}{\Supmc}{MUTEKH OS} 109 109 The drivers required for the first CSG milestone (delivrable \csgCoachArch). 110 \itemV{8}{18}{x}{\Supmc}{MUTEK 0S}110 \itemV{8}{18}{x}{\Supmc}{MUTEKH 0S} 111 111 The drivers required for the second CSG milestone ({\csgPrototypingOnly}). 112 \itemL{18}{33}{x}{\Supmc}{MUTEK OS}{1:1:2}112 \itemL{18}{33}{x}{\Supmc}{MUTEKH OS}{1:1:2} 113 113 Maintenance work. 114 \itemL{6}{18}{x}{\Supmc}{Port of MUTEK OS}{1.0:1:0}115 Porting of MUTEK OS on the NIOS2 and MICROBLAZE processors.114 \itemL{6}{18}{x}{\Supmc}{Port of MUTEKH OS}{1.0:1:0} 115 Porting of MUTEKH OS on the NIOS2 and MICROBLAZE processors. 116 116 \itemV{6}{8}{x}{\Stima}{DNA OS} 117 117 The drivers required for the first CSG milestone (delivrable \csgCoachArch). -
anr/task-3.tex
r126 r134 49 49 \itemL{0}{12}{X}{\Sirisa}{SystemC for NIOS processor}{2:0:0} 50 50 { A SystemC simulation model for an extensible NIOS processor template, the VHDL model being 51 already available from Altera}51 already available from \altera} 52 52 \itemV{12}{18}{H}{\Sirisa}{VHDL for an extensible MIPS} 53 53 {A synthesizable VHDL model for a simple extensible MIPS architectural template} -
anr/task-5.tex
r130 r134 25 25 26 26 The low level hardware transmission support will be the PCI/X bus which allows high bit-rate 27 transfers. The reasons of this choices are that both ALTERA and Xilinx provide PCI/X IP for27 transfers. The reasons of this choices are that both \altera and \xilinx provide PCI/X IP for 28 28 their FPGA and that GPU HPC softwares use also it. 29 29 %This will allow us at least to be inspired by GPU communication schemes and may be to reuse … … 58 58 The PC part of the HPC communication API that comminicates with the FPGA-SOC, a 59 59 library and probably a LINUX module. 60 \itemL{12}{21}{x}{\Supmc}{HPC API for MUTEK OS}{0:3:0}60 \itemL{12}{21}{x}{\Supmc}{HPC API for MUTEKH OS}{0:3:0} 61 61 \setMacroInAuxFile{hpcMutekDriver} 62 62 The FPGA-SoC part of the communication API, a driver. … … 64 64 Port of the {\hpcMutekDriver} driver on the DNA OS. 65 65 \itemL{24}{33}{x}{\Supmc}{HPC API}{0:0:1} 66 Maintenance work of HPC API for both Linux PC and MUTEK OS.66 Maintenance work of HPC API for both Linux PC and MUTEKH OS. 67 67 \end{livrable} 68 68 \subtask This \ST deals with the implementation of hardware and SystemC modules 69 required by the COACHarchitectural template for using the PCI/X IP of \altera and \xilinx.69 required by the neutral architectural template for using the PCI/X IP of \altera and \xilinx. 70 70 \begin{livrable} 71 71 \itemL{9}{18}{h}{\Stima}{HPC hardware \xilinx}{3:9:0} … … 94 94 The drivers required by the DNA OS in order to manage dynamic partial 95 95 reconfiguration inside the SoC-FPGA. 96 \itemL{30}{36}{x}{\Supmc}{dynamic reconfiguration \ganttlf MUTEK drivers}{0:0:1}97 Port of the {\hpcDynconfDriver} drivers on the MUTEK OS.96 \itemL{30}{36}{x}{\Supmc}{dynamic reconfiguration \ganttlf MUTEKH drivers}{0:0:1} 97 Port of the {\hpcDynconfDriver} drivers on the MUTEKH OS. 98 98 \itemL{24}{36}{x}{\Stima}{Profiler for \ganttlf dynamic reconfiguration}{0:0:6} 99 99 Extension of the HPC partionning helper in order to integrate dynamic partial -
anr/task-6.tex
r129 r134 116 116 This delivrable is a VHDL description. 117 117 % \itemL{12}{18}{x}{\Szied}{bitstream loader port}{0:3.6:0} 118 % Port of the bitstream loader to the MUTEK operating system.118 % Port of the bitstream loader to the MUTEKH operating system. 119 119 \itemL{18}{24}{x}{\Szied}{\zied demonstrators}{0:2.4:0} 120 120 \zied will propose to test COACH framework and the \zied architecture template 121 121 throught a basic application. 122 This applicattion will containt 3 communicating tasks under the coachformat specified122 This applicattion will containt 3 communicating tasks under the COACH format specified 123 123 in {\novers{\specGenManual}} delivrable. 124 124 The first one is a hardware task generated by the HAS tools and transformed into
Note: See TracChangeset
for help on using the changeset viewer.