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.
To read the full article, click here
Related Semiconductor IP
- HBM4 PHY IP
- Ultra-Low-Power LPDDR3/LPDDR2/DDR3L Combo Subsystem
- HBM4 Controller IP
- IPSEC AES-256-GCM (Standalone IPsec)
- Parameterizable compact BCH codec
Related Articles
- Fault-robust microcontrollers allow automotive technology convergence: Part 1, the nature of faults
- How to choose an RTOS for your FPGA and ASIC designs
- Comparing IP integration approaches for FPGA implementation
- Evolving passive optical networks (PONs) demand FPGA design flexibility
Latest Articles
- A 14ns-Latency 9Gb/s 0.44mm² 62pJ/b Short-Blocklength LDPC Decoder ASIC in 22FDX
- Pipeline Stage Resolved Timing Characterization of FPGA and ASIC Implementations of a RISC V Processor
- Lyra: A Hardware-Accelerated RISC-V Verification Framework with Generative Model-Based Processor Fuzzing
- Leveraging FPGAs for Homomorphic Matrix-Vector Multiplication in Oblivious Message Retrieval
- Extending and Accelerating Inner Product Masking with Fault Detection via Instruction Set Extension