Changeset 356 for anr/section-2.tex
- Timestamp:
- Feb 6, 2011, 2:29:09 PM (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
anr/section-2.tex
r338 r356 1 1 Embedded systems (SoC and MPSoC) have become an inevitable evolution in the microelectronic industry. 2 Due to the exploding fabrication costs, the ASIC technology (Application Specific Integrated Circuits)3 is not an option for SMEs (Small and Medium Enterprises).2 The ASIC technology (Application Specific Integrated Circuits) 3 is not an option for markets with small series of products due to ROI. 4 4 Fortunately, the new FPGA (Field Programmable Gate Array) components, 5 such as the Virtex 5family from \xilinx, or the Stratix4 family from \altera can implement a complete5 such as the Virtex6 family from \xilinx, or the Stratix4 family from \altera can implement a complete 6 6 multi-processor architecture on a single device. 7 7 But the design of embedded system is a long and complex task that requires expertise in software, 8 software/hardware p artionning, operating system, hardware design, VHDL/Verilog modeling.8 software/hardware portioning, operating system, hardware design, VHDL/Verilog modeling. 9 9 Only very few SMEs have these multiple expertises and are present on the embedded system market. 10 The corresponding development cost is high and it is not compliant with 11 specification or standard evolution (problem of flexibility). 10 12 Furthermore, even small design shops in big companies are facing the same issue. 11 13 \begin{center}\begin{minipage}{.8\linewidth}\textit{ … … 74 76 unadapted to the current GPU based solutions. 75 77 \parlf 76 C oachgenerates SoCs which are part of larger systems. Thus it is important to take77 78 COACH generates SoCs which are part of larger systems. Thus it is important to take 79 into account the existing industrial design flow. For this reason COACH will use the 78 80 IP-XACT IEEE 1685 standard for packaging these generated SoCs. 79 81 \begin{center}\begin{minipage}{.8\linewidth}\textit{
Note: See TracChangeset
for help on using the changeset viewer.