ADAS/AD: Why An External Safety MCU Remains A Cornerstone For Safety Alongside SoC Safety Islands

A dedicated safety MCU provides robust hardware and software separation, real-time performance, and scalability.

popularity

Advanced driver-assistance systems (ADAS) and autonomous driving (AD) technologies are revolutionizing mobility, making vehicles smarter, safer, and increasingly autonomous. At the heart of these advancements are sophisticated computing architectures built on system-on-chips (SoCs) that manage complex tasks like perception, decision-making, and control. Many SoCs integrate a “Safety Island”—a specialized section designed to support functional safety (FuSa) through capabilities such as lockstep cores and safety peripherals.

Yet, even with advancements in SoC technology, the need for an external safety microcontroller unit (MCU) remains critical. Why? Because a Safety Island alone cannot fully meet the demands of automotive safety in higher levels of automation, such as L2+ and beyond. A dedicated safety MCU, such as Infineon’s AURIX family, provides robust hardware and software separation, real-time performance, and scalability that SoCs can’t achieve on their own. Let us explore why this dual approach is the key to secure, reliable ADAS/AD systems.

Architecting safety beyond redundancy

Ensuring safety in  ADAS/AD systems is a complex endeavor. An external safety MCU does much more than act as a backup—it becomes the backbone of an advanced safety architecture. Infineon’s AURIX family of automotive-grade safety MCUs embodies decades of expertise in safety-critical applications, setting the benchmark for reliability and performance.

One of the core advantages of an external safety MCU is physical isolation. Unlike Safety Islands embedded in SoCs, external MCUs eliminate risks tied to shared memory and processing resources. This ensures consistent functional safety, even in scenarios where the SoC might fail. For instance, AURIX™ integrates safety-optimized memory, interfaces, and software, going far beyond the basic lockstep core functionality commonly found in SoCs.

The use of a trusted safety MCU also streamlines the implementation of functional safety concepts, simplifying system design while meeting the industry’s stringent ASIL-D requirements. By combining SoCs with AURIX, engineers gain a proven, scalable platform that enhances system reliability without compromising on performance.

Addressing critical design challenges: Flexibility, scalability, and real-time performance

1. Platform scalability that evolves with your needs
SoCs tend to evolve rapidly, often leaving developers with fragmented architectures. Safety MCUs, however, offer a stable and scalable foundation for long-term development. The AURIX family provides scalability across multiple performance ranges (low, medium, high) and ensures seamless hardware compatibility with pin-to-pin and software reusability.

This flexibility empowers automakers to standardize their electronic/electrical (E/E) architecture across different vehicle models, even when integrating various SoCs. The result? Reduced development costs, accelerated time-to-market, and a consistent safety backbone amid the ever-changing automotive landscape.

2. Robust isolation and functional safety that stands apart
Integrated Safety Islands often face limitations when it comes to isolating safety-critical functions due to shared resources. AURIX mitigates these challenges by offering true hardware and software isolation. Its advanced virtualization technologies, such as the hypervisor capabilities in the TC4x series, allow for multiple secure virtual machines (VMs) to run independently on a single core, ensuring “Freedom-from-Interference.”

This robust isolation is particularly crucial when consolidating different applications (Fusion) or separating them (Fission) to meet safety or security requirements. With AURIX, safety-critical tasks remain unaffected—even in adverse scenarios such as compromised applications or hardware failures.

3. Deterministic real-time performance for critical functions
Integrated Safety Islands may encounter limitations in hard real-time performance due to memory bottlenecks (no embedded Flash, limited SRAM) or long boot times. External safety MCUs provide proven and high-level real-time performance. This level of performance is vital for critical functions like the firewall to critical actuators (monitoring and blocking unsafe or malicious commands), ECU monitoring (health, safe state management, including shutdown), or managing gateway functions (reliable network communication, fast startup of critical functions). These tasks demand deterministic execution and the ability to react quickly, even in the event of an SoC failure.

The indispensable companion for safe mobility

Although integrated SoC Safety Islands provide a baseline level of safety, they fall short when it comes to delivering the structural and functional advantages of a dedicated external safety MCU. With Infineon’s AURIX family, automakers can achieve unparalleled scalability, robust isolation, and deterministic real-time performance—qualities essential for the next generation of ADAS/AD innovation.

As mobility evolves toward higher levels of autonomy, combining SoCs with external safety MCUs ensures safety remains central to innovation. For automotive engineers seeking a seamless balance of flexibility, reliability, and safety, the dual approach of integrating AURIX into ADAS/AD systems is the key to unlocking a safer, smarter, and autonomous driving future.

Do you want more details? See our Safety MCU as SoC Companion in ADAS/AD webinar.



Leave a Reply


(Note: This name will be displayed publicly)