Arm and Panasonic Automotive Systems (PAS) want automakers and suppliers to build software against more consistent virtualized interfaces instead of tying each application to a particular hypervisor or chipset. Their November 7, 2024 partnership announcement centers on adopting and extending VirtIO within the SOAFEE ecosystem. It sets out a direction for software portability—not a finished industry standard or proof of production-wide adoption.
What the Arm–PAS partnership is trying to standardize
The partnership targets the boundary between automotive software and the hardware beneath it. As functions move from separate electronic control units (ECUs) into cockpit domain controllers and high-performance computers, vehicles rely more on hypervisors and advanced chipsets. The partners say proprietary interfaces at that boundary can make changing hardware or software solutions costly and slow.
Their proposed alternative is a software-first development model: standardize interfaces between automakers’ and suppliers’ software stacks and the underlying hypervisors and chipsets. VirtIO is the named mechanism they plan to adopt and extend. The goal is to let software depend less on a particular hardware configuration, reducing vendor-specific rework when platforms change.
This is not a new consumer vehicle feature. It is an effort to shape development architecture and interfaces across the automotive software ecosystem. The announcement describes collaboration and intended standardization; it does not establish a completed standard, certification, or broad deployment in production vehicles.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
What VirtIO is meant to do in this plan
In the partnership’s framing, VirtIO provides a device-virtualization interface through which software can work with virtualized devices rather than depend directly on vendor-specific hardware interfaces. The intended benefit is a more portable boundary between applications, virtualization layers, and automotive compute hardware.
That boundary can reduce hardware dependence, but it does not make every application automatically portable. Software still has to be designed, integrated, and validated for its target system. Timing behavior, safety requirements, and platform differences remain important, especially for vehicle functions with real-time or safety-critical needs.
Rank #2
- Dual RS485 & CAN485 interfaces for reliable communication in industrial and automotive setups, even in noisy environments.
- Compact STM32F103C8T6 ARM core board that works great for beginners learning embedded systems or experienced developers prototyping.
- All pins fully exposed, so you can easily connect sensors, displays, or other peripherals for custom projects.
- Built with quality PCB materials for long-lasting use, whether you're testing in the lab or deploying in the field.
- Simple to program and debug — just plug in and start coding. Perfect for learning ARM architecture or building professional applications.
The three announced workstreams
| Workstream | What the partners describe | What it is meant to enable |
|---|---|---|
| Unified HMI and zonal architecture | A proof of concept uses PAS’s open-source remote-GPU technology, Unified HMI, to distribute GPU workloads from a central ECU to zonal ECUs. Applications on the central ECU are intended to remain unchanged. The partners describe partitioned Mali-G78AE GPU resources as supporting deterministic graphics performance. | Moving graphics work across centralized and zonal compute could help reduce heat generation and harness weight, according to the partners. These are stated potential benefits, not published measurements of a production vehicle. |
| Cloud-to-car development | PAS’s vSkipGen operates on Arm Neoverse-based cloud servers. The partners aim to use the same Arm CPU architecture and VirtIO framework across virtual cloud hardware and automotive hardware. | A closer match between cloud and vehicle environments could let teams begin software work before physical vehicle hardware is available and reduce differences between virtual and physical development systems. It is a bridge toward parity, not a guarantee that cloud results will behave identically in every real vehicle. |
| Broader VirtIO scope | The initial focus is cockpit use cases, including Android Automotive and Automotive Grade Linux. The partners say they aim to extend standardized interfaces to additional applications, including real-time operating systems (RTOS). | If the approach is extended and validated for those workloads, it could make ADAS software less dependent on a particular hardware platform. The announcement describes this as an aim, not an established result for deployed ADAS systems. |
How SOAFEE fits in
SOAFEE is an industry-led working group within the CoreCollective Open Collaboration Initiative. Its mission is to bring cloud-native development to automotive and bring automakers, suppliers, and technology companies together around an open architecture for software-defined vehicles (SDVs).
SOAFEE describes its framework as hardware-agnostic: developers can build and test in the cloud, then deploy to vehicles. Its Blueprint program accepts real-world workload and technology contributions. Combined with cloud virtual prototyping, that approach is intended to let engineering teams start before vehicle or electronic hardware is available.
Rank #3
- ESP32-S3 4.3″ LCD Development Board,Integrates RGB Interface LCD
- IPS Display Panel,Excellent Display Performance, 160°Viewing Angle
- Supports Multiple Peripherals,Supports The Expansion Of Multiple Peripherals Via Sensor, CAN, RS485, And I2C Interfaces
- A microcontroller development board with 2.4GHz WiFi and BLE 5 support,
- Equipped with Xtensa 32-bit LX7 dual-core processor, up to 240MHz main frequency.
SOAFEE provides the broader collaboration and blueprint context for the Arm–PAS work; it is not the same thing as the partners’ specific VirtIO workstreams. The practical question is whether common interfaces and development environments can be implemented and validated across different hardware, software, and supplier combinations.
Can teams test SDV software before vehicle hardware exists?
The approach is designed to support earlier cloud-based development. Teams can work with virtual hardware and shared frameworks before a physical vehicle platform is ready. The value is less waiting to begin software work and the possibility of finding integration issues earlier—not the elimination of later testing on target vehicle hardware.
What the DENSO blueprint demonstrates
A May 22, 2025 SOAFEE Blueprint from DENSO offers a concrete example of related cloud-based work. It presents deterministic middleware for mixed-criticality SDV applications, with hardware-agnostic application interfaces, deterministic scheduling, runtime detection of safety violations, and fault handling.
The demonstration runs Autoware Foundation’s open-source Automated Valet Parking application on Open AD Kit. Its workloads run on AWS Graviton instances with SOAFEE’s EWAOL, K3S orchestration, and automated cloud CI/CD. DENSO reports that the vehicle completes a reverse-parking sequence under injected system stress, and that runtime traces can inform redesign and tuning.
Best Value
- ALL-IN-ONE FORMULA (PMWCSPI23430): Cleans, protects, and refreshes every interior surface including dashboards, vinyl, plastic, leather, fabric, and glass for a complete detail in one easy step.
- NEW CAR SCENT EXPERIENCE: Infused with the signature New Car Smell fragrance to restore that just-detailed freshness every time you clean your vehicle’s interior.
- SAFE FOR ALL INTERIORS: Designed for modern automotive materials; use on steering wheels, door panels, consoles, and more without streaks, fading, or residue.
- QUICK AND CONVENIENT: Pre-moistened wipes make touch-ups effortless at home or on the go; perfect for daily maintenance or quick cleanup between full details.
- CLEANS AND PROTECTS: Removes dust, light grime, and smudges while leaving behind a smooth, dry finish that helps maintain a clean look and feel across all surfaces.
This is implementation evidence for a particular blueprint and workload, not proof that all production vehicles use the architecture or that cloud testing alone establishes vehicle readiness. DENSO’s stated aim is for software developed and validated in the cloud to behave identically when deployed to a real vehicle; that is a goal to verify through implementation and validation, not an outcome established for every platform by this demonstration.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Does this make ADAS software portable across chips and hypervisors?
Not yet as an established result. The partnership’s initial focus is cockpit software, with RTOS and ADAS among the areas it hopes to address as standardized interfaces expand. The announcement does not show that ADAS applications already run unchanged across chipsets or hypervisors, nor does it provide evidence of production deployment, functional-safety certification, or cross-platform performance testing.
For ADAS, portability depends on more than a common interface. Teams still need evidence that timing is deterministic, safety and cybersecurity requirements are met, and the software behaves correctly on each target platform. The partnership sets out a possible route to reduce hardware-specific dependence; the degree of portability will depend on implementation and validation.
Quick Recap
What remains open
- Standardization status: The partners say they intend to promote and extend VirtIO; the announcement does not establish that their automotive extensions are a completed, universally adopted standard.
- Production use: The cited proof of concept and SOAFEE blueprint show technical work, but do not establish broad production deployment.
- Safety and interoperability evidence: The announcement does not provide a complete cross-vendor benchmark or establish certification across vehicle platforms.
- Comparisons with other approaches: The available material does not provide a full benchmark against AUTOSAR, Eclipse SDV, COVESA, or proprietary OEM stacks. Meaningful comparison would need to address portability across chips and hypervisors, determinism, safety and cybersecurity evidence, cloud-to-vehicle parity, zonal-compute support, tooling maturity, governance, and production deployment.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
