English
FPGA-to-ASIC integration provides flexibility in automotive microcontrollers
By Axel Zimmermann, Altera Europe
The primary benefit of using MCUs has been high level system integration combined with relatively low cost. However, there are hidden costs associated with these devices well beyond the unit price.
The widely applied microcontroller in automotive electronics is heading full-speed at a wall of time and cost. The primary benefit of using microcontrollers (MCUs) has been high level system integration combined with relatively low cost. However, there are hidden costs associated with these devices well beyond the unit price. For example, if the chosen part does not have just the right mix of features, it must be augmented with external logic, software, or other integrated devices.
Further, with rapidly changing end-market requirements far more common in today's automotive sector, MCUs often become quickly unavailable. Many MCUs equipped with specialized features and a fixed number of dedicated interfaces do not fulfill market requirements after a short evaluation period. Consequently, system suppliers are being forced to redesign their hardware and re-write associated software, in some cases even having to change the processor core.
The primary benefit of using MCUs has been high level system integration combined with relatively low cost. However, there are hidden costs associated with these devices well beyond the unit price.
The widely applied microcontroller in automotive electronics is heading full-speed at a wall of time and cost. The primary benefit of using microcontrollers (MCUs) has been high level system integration combined with relatively low cost. However, there are hidden costs associated with these devices well beyond the unit price. For example, if the chosen part does not have just the right mix of features, it must be augmented with external logic, software, or other integrated devices.
Further, with rapidly changing end-market requirements far more common in today's automotive sector, MCUs often become quickly unavailable. Many MCUs equipped with specialized features and a fixed number of dedicated interfaces do not fulfill market requirements after a short evaluation period. Consequently, system suppliers are being forced to redesign their hardware and re-write associated software, in some cases even having to change the processor core.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
|
||||||
Intel FPGA Hot IP
Related Articles
- How to get the best cost savings when implementing an FPGA-to-ASIC conversion
- FPGA-to-ASIC conversion a crucial concern
- Asynchronous reset synchronization and distribution - ASICs and FPGAs
- Resets in FPGA & ASIC control and data paths
- General Partitioning Guidelines for Validation of Large ASIC Designs On FPGA
New Articles
- Safeguarding the Arm Ecosystem with PSA Certified PUF-based Crypto Coprocessor
- Mastering Key Technologies to Realize the Dream - M31 IP Integration Services
- Create high-performance SoCs using network-on-chip IP
- IoT Security: Exploring Risks and Countermeasures Across Industries
- How Efinix is Conquering the Hurdle of Hardware Acceleration for Devices at the Edge
Most Popular
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- Dynamic Memory Allocation and Fragmentation in C and C++
- System Verilog Assertions Simplified
- Safeguarding the Arm Ecosystem with PSA Certified PUF-based Crypto Coprocessor
- Design Rule Checks (DRC) - A Practical View for 28nm Technology