Contents
Software platform

Base Software & AUTOSAR

How AUTOSAR Classic and Adaptive structure ECU and HPC software — layers, configuration, communication stacks — and where open-source platforms like Eclipse S-CORE fit in.

Topics in this area

Area overview

Start here

Basic Software (BSW) is everything an ECU needs beneath the application: communication stacks, memory handling, diagnostics, mode management, the OS and hardware abstraction. In the AUTOSAR Classic Platform (CP) it is arranged in layers:

  • Services layer — OS, communication (COM, PduR, bus interfaces), diagnostics (Dcm/Dem), memory (NvM), crypto (Csm, CryIf), ECU state and mode management (EcuM, BswM).
  • ECU abstraction layer — hides board wiring: which pin, which transceiver.
  • Microcontroller Abstraction Layer (MCAL) — standard drivers for MCU peripherals, usually delivered by the silicon vendor.
  • Complex Device Drivers — the escape hatch for timing-critical or non-standard hardware.

Application Software Components (SWCs) talk to BSW only through the generated Runtime Environment (RTE). Everything is configured in ARXML and generated at build time — CP is deliberately static, which makes it predictable and certifiable up to ASIL D.

The Adaptive Platform

The AUTOSAR Adaptive Platform (AP) targets HPCs: a POSIX OS, C++ applications, dynamic deployment and service-oriented communication through ara::com (bound to SOME/IP, DDS or IPC). Key functional clusters include Execution Management, State Management, Update & Configuration Management (UCM), Diagnostics and Identity & Access Management.

A typical SDV mixes both: dozens of CP ECUs at the edge and in zone controllers, plus AP — or a non-AUTOSAR stack — on central computers.

State of play (late 2026)

  • AUTOSAR R25-11 (December 2025) incorporated roughly 1,900 changes; examples include Suspend-to-RAM in Adaptive state management and a reworked ara::com C++ API. The next release is expected at the end of 2026.
  • Open source is moving into series projects. Eclipse S-CORE (Safe Open Vehicle Core) reached v0.9 in September 2026, with 1.0 planned for December 2026; the VDA–Eclipse collaboration grew to 32 participants.
  • Toolchains are shifting from GUI configurators to code-first, CI-friendly workflows and virtual ECUs for earlier testing.

Commercial-vehicle angle

Truck ECUs carry long-lived J1939 communication, high variant counts and decades of legacy BSW. Migration happens incrementally: new zone controllers and central compute adopt new platforms, while proven CP ECUs stay in place for years.

Key sources & further reading

  • AUTOSAR standards (R25-11) — free specifications; start with the Layered Software Architecture (CP) and Explanation of Adaptive Platform Software Architecture (AP) documents.
  • Eclipse S-CORE — open-source safe vehicle core: architecture, roadmap and release notes.
  • Broy, Challenges in Automotive Software Engineering, ICSE 2006 — still the clearest statement of why automotive software is different.
  • Deterministic and Reliable Software-Defined Vehicles, arXiv 2024 — building blocks for SOA, virtualisation and orchestration.

Latest BSW / AUTOSAR news

All news →