Contents

AUTOSAR Classic Platform

The standard software architecture for MCU-based ECUs: layered base software, a generated runtime environment and statically configured, predictable behaviour.

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:

  1. Microcontroller Abstraction Layer (MCAL) — standard drivers for the MCU’s peripherals (CAN, SPI, ADC, flash), typically from the silicon vendor.
  2. ECU Abstraction Layer — hides board specifics.
  3. Services Layer — OS, communication, memory (NvM), diagnostics (Dcm/Dem), crypto, mode management.
  4. Runtime Environment (RTE) — generated glue between applications and BSW.
  5. Application Software Components (SWCs) — the functions.
  6. Complex Device Drivers — escape hatch for special hardware.
AUTOSAR Classic layered architecture
Application SWCsVehicle functions
RTEGenerated runtime environment
ServicesOS, communication, memory, diagnostics
BSW
ECU abstractionHides board specifics
BSW
MCALMicrocontroller peripheral drivers
BSW
Microcontroller

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.

What it means for your discipline

  • Base software Core

    This is the BSW engineer's home: layers, modules, configuration (ARXML) and integration.

  • Functional safety Partial

    Classic BSW is available with safety qualification up to ASIL D; memory partitioning and timing protection support freedom from interference.

  • Cybersecurity Partial

    Provides the crypto stack (Csm, CryIf), SecOC, secure diagnostics and the intrusion detection manager.

  • Networks & communication Partial

    The communication stack implements CAN, LIN, Ethernet, NM and gateway routing.

  • Diagnostics & lifecycle Partial

    Dcm and Dem implement UDS services and fault memory.

  • Software update & OTA Partial

    Coordinates diagnostic programming entry, memory handling and resets with Classic BSW integration teams so ECU software can be flashed reliably.

No direct stake: E/E architecture · HPC & application software · Hardware & silicon

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • Classic RTE & COM — Provides generated RTE connections and statically configured Classic communication on the safety island.
  • WdgM · E2E · Dem — Provides watchdog supervision, end-to-end communication protection and diagnostic event management.
  • AUTOSAR OS — Schedules statically configured tasks and supports timing protection and memory partitioning where configured.
  • MCAL — Provides standard peripheral drivers beneath the safety island's Classic basic software.
MCU-based ECU · AUTOSAR Classic
  • Runtime environment (RTE) — Connects application software components to each other and to configured basic software services through generated interfaces.
  • OS — Schedules configured tasks and supports timing protection and memory partitioning where configured.
  • ECU abstraction — Hides board-specific devices and connections behind interfaces used by higher software layers.
  • Microcontroller abstraction (MCAL) — Provides standard drivers for microcontroller peripherals such as CAN, ADC, PWM and flash.