Infineon AURIX RC1 Adds RISC-V Compute and Virtual Prototyping for SDVs
- Majeed Ahmad
- 495 reads
AURIX RC1 combines up to 12 RISC-V cores, 40 MB of embedded memory and a virtual development kit for software work before silicon arrives.

Infineon’s AURIX RC1 pairs a high-compute automotive microcontroller with a virtual model intended to let engineering teams begin software development before physical hardware is available. The combination addresses two pressures in software-defined vehicle (SDV) design: consolidating functions that have traditionally run on separate electronic control units (ECUs), and bringing software integration forward in the development schedule.
Unveiled at electronica 2026 in Munich, Germany, RC1 is Infineon’s first RISC-V-based MCU. The company positions it for real-time vehicle control and physical AI applications. Its key design choice is a scalable mix of processing, memory and connectivity that can serve several vehicle domains, with RISC-V allowing different RC1 lineups to be tailored to particular applications.

Compute for functions moving into central and zone controllers
SDV architectures are shifting functions from numerous distributed ECUs toward central vehicle computers and zone controllers. That shift raises the value of compute platforms able to handle workloads across domains while meeting real-time, security and functional safety requirements. RC1 is designed to cover zone, body and chassis control, battery management systems, powertrains, cockpit functions and driver-assistance safety management.
The device integrates up to 12 32-bit processing cores, an advanced parallel processing unit for edge AI, and up to 40 megabytes of embedded memory. Those are maximum configurations, not a guarantee that every RC1 part will contain the same resources. The modular RISC-V architecture gives Infineon room to build variants around the needs of particular applications, while the broader family is intended to scale across vehicle domains.

Figure 1. Infineon positions AURIX RC1 for real-time vehicle control and physical AI applications. Source: Infineon.
Using one scalable device family across multiple domains could simplify platform planning for automakers and Tier 1 suppliers. It may also give software teams a more consistent target as vehicle functions are consolidated. The practical result will depend on the available device variants, how workloads map to their cores and accelerators, and how teams integrate them into their vehicle architectures.

Figure 2. Zone controllers and central computers are changing where vehicle functions run. Source: Infineon.
Vehicle links and security features
RC1 supports CAN-XL, 10BASE-T1S and multi-Gigabit Ethernet for in-vehicle data transfer. Those interfaces address a mix of network needs as vehicle architectures connect distributed zones with higher-capacity computing nodes. Their presence in the MCU’s feature set does not, by itself, specify how a particular vehicle network will be arranged; that remains an application-level design choice.
Infineon also describes hardware mechanisms for physical protection and crypto agility, alongside support for cybersecurity requirements including ISO/SAE 21434 and the Cyber Resilience Act. For engineers, crypto agility matters because vehicle platforms may need to accommodate changes in cryptographic methods over a long service life. The exact protection mechanisms and their implementation in production systems will need to be assessed against each program’s security and safety design.
Virtual development before the MCU is available
The software ecosystem is a major part of the RC1 announcement. Infineon’s DRIVECORE combines its own tools with pre-integrated software from ecosystem partners. It supports AUTOSAR, open-source software, functional safety and cybersecurity workflows. The intended benefit is to give OEMs and Tier 1s a starting point for software work before production hardware arrives, while lowering the effort involved in moving between designs.
Synopsys’ Virtualizer Development Kit (VDK) supplies a virtual prototype of the MCU. Engineers can use it to develop, run, debug, verify and validate production software across application domains before silicon or evaluation boards exist. This can move software integration earlier, when teams have more opportunity to identify interactions between vehicle functions and address them in the virtual environment.

Figure 3. DRIVECORE combines Infineon tools with software bundles from ecosystem partners. Source: Infineon.
Synopsys vice president of product management Marc Serughetti said the VDK is intended to support development before silicon is available and to scale validation from virtual ECUs to complete electronics digital twins. That approach can help teams test software across a vehicle’s electronics architecture earlier. Its usefulness will depend on how well the virtual model represents the hardware and system behavior that the production design must handle.
TASKING is also supporting RC1 across the development lifecycle with a unified toolchain for compiling, debugging and verifying systems based on the MCU. The toolchain includes agentic AI features intended to speed work on complex multicore systems. TASKING says the environment can help teams produce software for ISO 26262 and ISO/SAE 21434 requirements; the final work still rests on the project’s engineering and validation processes.
Infineon plans to provide AURIX RC1 samples in the first half of 2027. Until then, the virtual prototype and software tools offer a way for teams to examine their software architecture ahead of hardware availability. The next practical questions are how the eventual device variants distribute compute and memory, and how closely the virtual environment supports the target system’s development and validation needs.