AURIX RC1’s First Test Is the Software Window

A common foundation, with a long runway

Infineon announced AURIX RC1 on November 4 as its first automotive microcontroller platform based on the open-standard RISC-V instruction set. The planned family spans conventional MCUs and hybrid MCU/microprocessor devices, targeting jobs from zone and chassis control to battery management and cockpit systems. Infineon says family configurations can scale to 12 32-bit cores, 40 megabytes of embedded memory and a parallel processing unit for edge AI. These are platform-level ceilings, not specifications for one available part: the company targets samples in the first half of 2027. S1

The strategic bet is consolidation: a common foundation across domains could reduce the number of distinct software stacks teams must maintain. But RISC-V standardizes an instruction set, not every peripheral, memory map, safety mechanism or driver. Code reuse will depend on the details of each device and the qualification work around it.

Software work starts before silicon

On November 10, Synopsys announced a Virtualizer Development Kit for RC1, offered through Infineon’s DRIVECORE software portfolio. The virtual prototype is intended to let automotive teams evaluate the MCU and develop and validate software before physical silicon is available. Synopsys says teams can achieve “up to 90% software validation” before physical-system availability. That is a vendor-stated ceiling, not a measured result for a named vehicle program or a guarantee that every test can move into simulation. S2

That early-access layer may matter as much as the core architecture. Virtual targets can bring forward porting, integration and automated tests; they cannot settle real-device timing, electrical behavior or safety responses. The value therefore depends on model fidelity, partner-tool support and how closely the virtual interface tracks the eventual parts.

The questions for firmware teams

Before planning a migration, ask which RC1 variants the early-access model covers, which compiler, debugger and AUTOSAR components are available, and what the model omits. Separate portable application logic from device-specific drivers and low-level safety code, then identify which timing and safety tests must wait for silicon.

The sample target in 2027 gives teams a practical checkpoint: compare virtual results with hardware, find gaps in the model, and measure how much software genuinely carries across configurations. An open ISA can widen the ecosystem; only that comparison will show whether RC1 also makes automotive firmware more reusable in practice.