Contents
Software platform

Software Stacks by Node Class

The same software layers — from applications down to silicon — compared across HPC application processors, safety islands, zone controllers, MCU-based ECUs and smart nodes.

Topics in this area

Feature services, HMI, ADAS apps The HPC application processor runs compute-heavy vehicle features, user interfaces, and driver-assistance applications that can evolve through controlled software updates. AUTOSAR Adaptive / SOA (SOME/IP, DDS) This layer starts and manages application processes and lets vehicle software discover services and exchange data locally or across the vehicle network. OTA client · SOVD · host IDS · logging Shared services on the HPC application processor update software, expose diagnostics, detect suspicious activity and collect evidence for troubleshooting. Linux / QNX / Android (per VM) Each virtual machine runs a guest operating system that manages its applications and resources, with Linux, QNX or Android chosen to suit the workload and assurance requirements. Type-1 hypervisor A type-1 hypervisor divides an HPC’s application processor into virtual machines so different operating systems and workloads can share hardware with controlled interference. BSP · Linux drivers · VirtIO Board support and device drivers let HPC operating systems use the physical hardware, while VirtIO provides standard virtual device interfaces for guests. Secure boot chain · TEE Trusted startup firmware checks the software that starts the HPC, while an isolated execution environment protects selected security services during operation. Cortex-A cores · GPU/NPU · LPDDR Application processors combine powerful CPU cores, specialised accelerators and external memory to support large vehicle software workloads. Real-time control & safety monitors The safety island runs predictable control and monitoring software that checks the main processor and coordinates a safe response when something goes wrong. AUTOSAR Classic RTE & COM The safety island uses configured software interfaces and communication paths to exchange control data predictably within the HPC and with other vehicle nodes. Watchdog manager · E2E · fault memory The safety island checks that critical software runs correctly, validates exchanged data and records faults so the system can respond safely. AUTOSAR OS / safety RTOS A small real-time operating system schedules safety control and monitoring tasks on the HPC’s dedicated MCU cores, with predictable execution and controlled fault handling. Physically separate cores The safety island runs its own real-time software on dedicated cores, with hardware boundaries that limit interference from the HPC’s application processor. MCAL MCAL gives the safety island’s real-time software standard interfaces to its hardware peripherals, while keeping device-specific register handling inside drivers. Boot ROM · HSM-verified boot The safety island starts trusted real-time software and, where the chip architecture permits, helps supervise startup of the rest of the HPC. Lockstep Cortex-R/M · ECC SRAM A safety island provides dedicated real-time processing, protected local memory and fault-monitoring hardware inside an HPC chip. Gateway & I/O logic Zone-controller applications turn nearby signals and backbone requests into controlled local actions, with predictable timing and defined fault responses. RTE · COM · PduR gateway The zone controller’s middleware connects local control software to vehicle networks and routes messages between nearby devices and the backbone. NM · Dcm/Dem · IdsM · eFuse management These services coordinate a zone’s network availability, diagnostic records, security events and electrical power outputs. AUTOSAR OS (multi-core) A statically configured real-time operating system schedules zone-controller work across MCU cores and provides protection mechanisms that help contain software faults. MPU-based partitioning The operating system and the MCU’s memory protection hardware separate software workloads so that faults in one have limited effects on others. MCAL · IoHwAb · complex drivers This layer turns the zone controller’s pins, peripherals and external power switches into controlled interfaces for local I/O and vehicle communication. Flash bootloader · secure boot This firmware checks software before starting the zone controller and safely installs authorized updates while keeping local outputs and recovery under control. Multi-core MCU · HSM · smart switches A zone controller combines a real-time microcontroller, protected security hardware and power switches to connect nearby devices and control their electrical supply. Application SWCs (e.g. brake control) Application software components implement an ECU’s vehicle functions, turning sensor inputs and requests into controlled outputs and fault responses. RTE · COM The generated AUTOSAR runtime connects application components to each other and to communication software that exchanges signals with other ECUs. Dcm/Dem · NvM · SecOC · crypto stack These services let a control ECU answer diagnostic requests, remember important data across power cycles, authenticate selected messages and use protected cryptographic operations. AUTOSAR OS / RTOS A real-time operating system schedules control software and provides protection mechanisms that help safety-critical functions share an MCU with other software. MPU-based partitioning Hardware memory protection and operating-system controls help software of different safety criticalities share an MCU without disrupting one another. MCAL · ECU abstraction Microcontroller drivers and board-specific abstraction turn electrical inputs and outputs into interfaces that control software can use predictably. Flash bootloader · secure boot (HSM) This firmware checks that an ECU starts authorized software and installs updates, using hardware-protected keys and a controlled recovery path. Lockstep MCU · HSM · embedded flash An automotive microcontroller combines real-time processing, local memory, safety monitoring and protected cryptography to control functions such as braking, steering or battery management. Fixed function (motor, lamp, sensor) A small smart node performs one local job, such as moving a motor, controlling a lamp or reporting a sensor value, under commands from another controller. LIN / T1S protocol handling A small protocol handler turns network messages into commands and sensor values, using LIN or a separately designed 10BASE-T1S Ethernet interface. Node configuration & basic diagnostics A small LIN node provides identification, configuration and simple health information so its master can integrate and diagnose a local sensor or actuator. Bare metal or tiny scheduler A small sensor or actuator usually coordinates its work with a main loop, interrupts, and simple state machines instead of a full operating system. Peripheral drivers / ASIC logic Small drivers or fixed hardware logic connect a simple sensor or actuator to its pins, local peripherals and communication hardware. ROM or simple bootloader A small sensor or actuator starts through minimal firmware, with protection shared between the device, its controlling ECU and the physical network. Small MCU / LIN SBC / ASIC A smart node uses a small microcontroller or dedicated logic, together with power and communication circuitry, to control a nearby sensor or actuator.

Area overview

Start here

A software-defined vehicle does not run one software stack — it runs several, each shaped by the hardware it sits on. A central computer’s application processor (MPU) runs a hypervisor, Linux or QNX and service middleware. Inside the same chip, an MCU-class safety island runs a real-time OS and AUTOSAR Classic. Zone controllers and MCU-based ECUs run AUTOSAR Classic stacks, and smart nodes often run no operating system at all.

This area slices every node class into the same eight layers, so you can compare them directly: applications, middleware & runtime, platform services, operating system, virtualisation & partitioning, drivers & hardware abstraction, boot & security firmware, and silicon. Each page explains one cell of that grid — use the Atlas view Software stacks to navigate them visually.

Latest Software stacks news

All news →

No news on this topic yet.