The instruction-set choice for automotive MCUs has moved from paper discussion to product launch for the first time. On November 19 in Shanghai, Infineon unveiled the AURIX RC1, its first MCU platform based on RISC-V, and on the same stage brought together the China EV100 Research Institute and more than 100 industry-chain organizations to establish the RISC-V Club. For those working on boards and high-speed interfaces, what really matters is where the toolchain and IP supply behind this chip are heading.
Infineon released the AURIX RC1 on site in Shanghai, officially positioned as the company's first MCU platform built with RISC-V. According to Infineon, the product can extend from traditional microcontrollers to hybrid MCU/MPU devices, targeting energy-efficient real-time intelligence for software-defined vehicles, software-defined everything, and physical AI scenarios. This means the instruction-set path for automotive main control is no longer a single choice, but the RC1's specific core configuration, compute performance, and power figures were not disclosed at the event, and whether it can enter mass-production projects still depends on subsequent sample and certification progress.
The RISC-V Club is led by Infineon and the China EV100 Research Institute, and jointly initiated with chip industry-chain companies, software ecosystem firms, application companies, and research institutions. The official statement is that it will promote technical collaboration and application-system building for RISC-V automotive chips through joint development, technical seminars, and industry resource linkage. The list of those witnessing the launch and participating in discussions covers OEMs, Tier1s, chip design companies, and basic software vendors, including Tongji University, Chery, FAW, SAIC, Leapmotor, Li Auto, Geely, Changan, Dongfeng, Xiaomi, NIO, XPeng, Bosch, Inovance, Jingwei Hirain, Desay SV, Horizon, Nuclei, Andes, MIPS, Vector, ETAS, HighTec, TASKING, IAR, and Lauterbach. The breadth of the list shows parties are positioning themselves while watching, which does not yet equal joint development projects already in place.
More than ten representatives from OEMs, Tier1s, chip design, and basic software companies shared their exploration and route judgments for RISC-V in automotive scenarios. Infineon said the RC1's flexible and scalable characteristics open new innovation space for automotive chips, and said the RISC-V Club will use this meeting as a starting point to continue joint development and ecosystem building and accelerate solutions toward practical application. The real issue lies in the maturity of the automotive software stack: compilers, debuggers, AUTOSAR adaptation, and functional safety certification need to be filled in item by item, and this work cannot be completed by a single launch event.
For domestic engineers working on boards and high-speed interfaces, there is no direct replacement pressure in the short term: the RC1's interface specifications, packaging, and sample timing have not been announced, and existing AURIX solutions will not change selection because of a launch event. The indirect impact is on the toolchain side: IAR, TASKING, HighTec, Lauterbach, Vector, ETAS, and others appear on the initiator list, indicating that debugging and AUTOSAR adaptation have been put on the table, but each vendor's support pace will depend on subsequent versions. Teams working on domestic alternatives can watch whether joint projects between IP providers such as Nuclei and Andes and OEMs form reusable reference designs, which determines whether RISC-V automotive solutions can move from demonstration to mass production.
Daily Briefing · Weekly Digest · Monthly Deep Dive