English
Fault-robust microcontrollers allow automotive technology convergence: Part 1, the nature of faults
In automotive, semiconductor technologies and electronic systems are converging into a "car-on-a-chip." However, this convergence results in a new population of faults and failure modes, so how to make such systems more robust?
Life is hard for today's automotive electronics MCUs (Microcontroller Units). On one side, you could have 50 or more of them are involved in airbags, brakes, chassis control, engine control, and X-by-wire applications. Deeper (and often immature) silicon technologies are used to reduce costs. New functionalities are implemented in software, so the memory and performance requirements have increased. Standardization efforts and new software architectures such AUTOSAR are driving automotive electronics towards more and more powerful CPUs. Internal buses are crowded by demanding peripherals.Modeling uncertainty Functional verification holes Specification misunderstanding EMC (electromagnetic compatibility) Crosstalk Unforeseen interactions and misuse Soft-errors Malicious accesses
Life is hard for today's automotive electronics MCUs (Microcontroller Units). On one side, you could have 50 or more of them are involved in airbags, brakes, chassis control, engine control, and X-by-wire applications. Deeper (and often immature) silicon technologies are used to reduce costs. New functionalities are implemented in software, so the memory and performance requirements have increased. Standardization efforts and new software architectures such AUTOSAR are driving automotive electronics towards more and more powerful CPUs. Internal buses are crowded by demanding peripherals.
On the other side, as a consequence of such increased complexity, the population of faults is increasing as well. These include:
In particular, hardware faults (systematic or random) are worsened by: The increased soft-error failure rates (i.e. cosmic rays); coupling effects and disturbances are more and more important; and intrinsic uncertainty due to model inaccuracy is a problem of new technologies.
Moreover, system complexity and use of third-party IP increase the verification gaps and software faults. If we define "robustness" as the ability to continue mission reliably despite the existence of systematic, random or malicious faults, how do you design fault-robust MCUs ?
|
||||||
Related Articles
- A Platform-Based Technology for Fault-Robust SoC Design
- A Platform-Based Technology for Fault-Robust SoC Design
- Dealing with automotive software complexity with virtual prototyping - Part 1: Virtual HIL development basics
- Automotive System & Software Development Challenges - Part 1
- FPGAs tackle microcontroller tasks: Part 1 - Application growth strains architecture and ASICs
New Articles
- Why RISC-V is a viable option for safety-critical applications
- Dimensioning in 3D space: Object Volumetric Measurement by Leveraging Depth Camera-based Reconstruction on NVIDIA Edge devices
- What is JESD204B? Quick summary of the standard
- Post-Quantum Cryptography - Securing Semiconductors in a Post-Quantum World
- Analysis and Summary on Clock Generator Circuits and PLL Design
Most Popular
- System Verilog Assertions Simplified
- Enhancing VLSI Design Efficiency: Tackling Congestion and Shorts with Practical Approaches and PnR Tool (ICC2)
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- Method for Booting ARM Based Multi-Core SoCs
- An Outline of the Semiconductor Chip Design Flow
|
E-mail This Article | 
|
|
Printer-Friendly Page |