Why it exists
Before AUTOSAR, every supplier built its own software platform. Car makers could not reuse software across suppliers, and integrating components was slow and error-prone. AUTOSAR, founded in 2003, standardised the software architecture so that application components and basic software modules can be combined across suppliers.
What it is
Layers, bottom to top:
- Microcontroller Abstraction Layer (MCAL) — standard drivers for the MCU’s peripherals (CAN, SPI, ADC, flash), typically from the silicon vendor.
- ECU Abstraction Layer — hides board specifics.
- Services Layer — OS, communication, memory (NvM), diagnostics (Dcm/Dem), crypto, mode management.
- Runtime Environment (RTE) — generated glue between applications and BSW.
- Application Software Components (SWCs) — the functions.
- Complex Device Drivers — escape hatch for special hardware.
Simplified architecture; Complex Device Drivers can span BSW layers and are omitted here.
How it works
Everything is statically configured in ARXML: which messages exist, which tasks run when, which memory blocks are stored. Tools generate C code. Nothing is created at runtime, which makes behaviour predictable and certifiable.
When to use it
For deeply embedded, real-time and safety-relevant ECUs on microcontrollers — brakes, steering, zone controllers, BMS. For HPCs with dynamic software, the Adaptive Platform or other POSIX-based stacks are used.
Best practices
- Treat configuration as code: version it, review it, generate in CI.
- Keep application SWCs hardware-independent; push hardware specifics into the BSW.
- Plan the OS task and memory partitioning together with the safety team.
Common pitfalls
- Configuration drift between ECUs on the same network (message definitions out of sync).
- Underestimating integration effort for vendor BSW and MCAL releases.