Skip to the stories
Electronics & Semiconductors

Infineon AURIX RC1 Combines RISC-V Compute With Virtual ECU Development

  • Majeed Ahmad
  • 590 reads

The AURIX RC1 targets zonal and cross-domain vehicle control, while a virtual prototype lets teams develop software before silicon is available.

Infineon AURIX RC1 Combines RISC-V Compute With Virtual ECU Development

Infineon’s AURIX RC1 pairs a higher-capacity automotive microcontroller with a virtual development path intended to let software work begin before physical hardware arrives. Unveiled at electronica 2026 in Munich, the RISC-V-based device targets software-defined vehicles (SDVs), where functions once spread among many electronic control units (ECUs) are moving toward central computers and zone controllers. Its practical proposition is a scalable controller family and a digital twin that can run unmodified production software ahead of silicon availability.

Figure 1. Infineon positions AURIX RC1 for real-time vehicle control and physical AI applications. Source: Infineon

One controller family across vehicle domains

The RC1 is Infineon’s first RISC-V-based MCU. The company’s aim is to support computing and control workloads that are being consolidated from distributed ECUs into fewer, more capable vehicle computers and zone controllers. Rather than assigning a separate point solution to each function, the family is intended to scale across several vehicle domains.

Infineon lists zone, body and chassis control, battery management systems (BMS), powertrains, cockpit functions and driver-assistance safety management among the target applications. RISC-V’s modular architecture allows individual RC1 lineups to be configured for particular uses, according to the company. That flexibility matters in a vehicle architecture where a controller’s workload can vary widely: one design may prioritize control tasks, while another may need more compute for a broader mix of functions.

Figure 2. Zonal architectures shift vehicle functions toward zone controllers and central computing. Source: Infineon

The stated maximum configuration includes up to 12 32-bit processing cores, an advanced parallel processing unit for edge AI, and up to 40 megabytes of embedded memory. Those resources are intended to address increased computing demand alongside functional safety, cybersecurity and in-vehicle communications. The figures describe the upper end of the family; the announcement does not specify configurations for particular vehicle applications.

For data movement, Infineon names CAN-XL, 10BASE-T1S and multi-Gigabit Ethernet. Those interfaces reflect the need to connect distributed vehicle equipment with higher-capacity compute nodes. The device also includes hardware mechanisms for physical protection and crypto agility. Infineon says the MCU is designed to comply with ISO/SAE 21434 and the Cyber Resilience Act. The available details do not identify specific certification status, performance figures or implementation requirements for individual designs.

Software work can start before boards arrive

For vehicle programs, software integration often spans multiple teams and domains, so waiting for production hardware can constrain development and validation schedules. Infineon’s DRIVECORE ecosystem is intended to provide tools and pre-integrated software bundles from partners for AURIX RC1. It covers AUTOSAR, open-source software, functional safety and cybersecurity, and includes support for virtual prototyping.

The Synopsys Virtualizer Development Kit (VDK) provides a virtual prototype of the RC1. Engineers can use it to develop, run, debug, verify and validate software before chips or evaluation boards are available. Because the prototype is intended to run unmodified production software, teams can work against a representation of the target MCU earlier in the design process, then use it to exercise software across vehicle domains.

That early access can expose integration issues while changes are still being made in software and system design. Synopsys says the VDK can support validation from virtual ECUs through to complete electronics digital twins. Marc Serughetti, Synopsys vice president of product management, said the approach lets automakers and Tier 1 suppliers begin software development before silicon is available and validate software across the vehicle electronics architecture. The stated benefits—lower integration costs, faster time to market and improved software quality—are company claims, not published test results.

Figure 3. DRIVECORE combines Infineon tools with software bundles from ecosystem partners. Source: Infineon

TASKING is also supporting the RC1 development lifecycle with a unified toolchain for compiling, debugging and verifying systems based on the MCU. The toolchain includes built-in agentic AI, which TASKING says is intended to accelerate work on complex multicore automotive systems. Infineon and TASKING describe the environment as supporting development for ISO 26262 and ISO/SAE 21434 requirements; they do not provide comparative productivity figures.

What engineers will need to assess

The combination of scalable compute and virtual prototyping addresses two linked design pressures: consolidating vehicle functions while starting software integration earlier. For engineering teams, the virtual model’s usefulness will depend on how well it represents the target hardware and how it fits existing toolchains and software workflows. The announcement describes the intended development path, but does not provide benchmark results, model fidelity measurements or detailed compatibility information.

Infineon targets AURIX RC1 sample availability for the first half of 2027. Until samples and further implementation details are available, the key evaluation points are the specific MCU configurations, the fit of the VDK model to each project’s validation needs, and the integration effort required to move between virtual and physical targets.

Source: Majeed Ahmad · www.edn.com

From the same set