What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Arm and Panasonic Automotive Systems (PAS) want to make software for software-defined vehicles (SDVs) less dependent on a particular chip, hypervisor or vehicle computer. Their November 7, 2024 partnership focuses on adopting and extending VirtIO, a device-virtualization framework, within the SOAFEE ecosystem. It sets out a direction for more portable automotive software—not a finished industry standard or proof of production-wide adoption.
What the partnership is trying to standardize
The goal is to create more consistent interfaces between automotive software and the hardware and virtualization layers beneath it. As vehicles consolidate electronic control units (ECUs) into cockpit domain controllers and high-performance computers, software increasingly depends on hypervisors and advanced chipsets. Arm and PAS say proprietary interfaces can make changing a hardware or virtualization solution costly and slow.
As an Amazon Associate I earn from qualifying purchases.
Their proposed remedy is a software-first development model in which automaker and Tier-1 software stacks can interact with underlying hypervisors and chipsets through standardized interfaces. VirtIO is the mechanism they identify for that work. The announcement does not specify a completed interface specification, certification program, or timetable for broad adoption, so the partnership should be understood as collaborative standardization work rather than a standard already deployed across the industry.
Recommended Free Tools
How VirtIO could make automotive software more portable
Virtualization lets multiple software environments share vehicle computing resources. VirtIO provides a common way for software to interact with virtualized devices. In the partners’ intended model, software can rely less on a particular hardware vendor’s proprietary interface. That could reduce the amount of adaptation needed when moving applications between compatible compute platforms.
#1 Best Overall
Portability is not automatic: applications still need to be designed, integrated, and validated for their target systems. Nor does a common device interface by itself establish that two platforms have identical performance, real-time behavior, safety characteristics, or cybersecurity. The announcement describes the intended decoupling, but does not publish comparative benchmarks or establish those broader equivalences.
The three workstreams in the announcement
Unified HMI and zonal computing
The first workstream is a proof of concept combining PAS’s open-source remote-GPU technology, Unified HMI, with a VirtIO-based zonal architecture. In the described setup, GPU workloads are distributed from a central ECU to zonal ECUs while applications on the central ECU remain unchanged. The partners say the approach could reduce heat generation and harness weight. They also describe partitioned Mali-G78AE GPU resources as supporting deterministic graphics performance; the announcement does not provide quantified test results for those claimed benefits.
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.
Cloud-to-car development parity
PAS’s vSkipGen runs on Arm Neoverse-based cloud servers. The partners aim to use the same Arm CPU architecture and VirtIO framework in virtual cloud hardware and automotive hardware, narrowing the gap between development in the cloud and deployment in a vehicle. The practical idea is to let teams begin software work and testing before the target physical vehicle hardware is available.
Matching architecture and interfaces can make cloud testing more representative, but it does not by itself prove identical behavior on a real vehicle. Hardware differences, system integration, and vehicle-level validation remain relevant.
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.
From cockpit software toward RTOS and ADAS
The initial focus is cockpit software, including Android Automotive and Automotive Grade Linux. Arm and PAS say they want to extend standardized interfaces to more applications, including real-time operating systems (RTOS), with the aim of making advanced driver-assistance system (ADAS) software less hardware-dependent. This is an intended expansion, not evidence that ADAS applications are already portable across chips and hypervisors under a completed VirtIO standard.
What SOAFEE contributes
SOAFEE is an industry-led working group in the CoreCollective Open Collaboration Initiative. Its purpose is to bring cloud-native development into automotive software and provide an open architecture for SDVs. SOAFEE describes its framework as hardware-agnostic: developers can build and test in the cloud, then deploy software to vehicles.
Its Blueprint program accepts real-world workload and technology contributions. Combined with cloud virtual prototyping, that model is intended to let teams start development before vehicle or electronic hardware is available. SOAFEE provides a collaboration and architecture context for the Arm–PAS effort; it is not itself evidence that every participating technology is interoperable or ready for production.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →What a separate SOAFEE blueprint demonstrates
A May 22, 2025 SOAFEE Blueprint from DENSO offers a concrete example of cloud-based SDV development. It describes deterministic middleware for mixed-criticality applications, using hardware-agnostic application interfaces, deterministic scheduling, runtime detection of safety violations, and fault handling.
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.
The demonstration runs the Autoware Foundation’s open-source Automated Valet Parking application on Open AD Kit. Its workloads use AWS Graviton instances, 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.
This is implementation evidence for that blueprint and workload—not proof that all production vehicles use SOAFEE, that the Arm–PAS workstreams have been completed, or that cloud and vehicle behavior is identical in every application.
What automakers and developers should take away
- The target is the software–hardware boundary. The partnership concerns virtualization and interfaces, not a new consumer vehicle or a new chip.
- VirtIO is the named path, not a guarantee of universal compatibility. The announcement describes adopting and extending it; it does not establish that every hypervisor, chipset, or application will work together without adaptation.
- Cloud-first development can bring work forward. Virtual prototyping can help teams start before vehicle hardware exists, while final behavior still needs validation in the relevant vehicle environment.
- ADAS portability remains an ambition. The stated expansion to RTOS and ADAS is a future direction, with no production-wide deployment or certification evidence established in the announcement.
The available material also does not provide a complete benchmark against AUTOSAR, Eclipse SDV, COVESA, or proprietary OEM stacks. A meaningful comparison would need evidence on interface portability, real-time determinism, safety and cybersecurity, cloud-to-vehicle parity, zonal computing, tooling, governance, and production deployment.
Quick Recap
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.
