What it is
The AUTOSAR Classic Platform is the specification set for software on a microcontroller-based electronic control unit. It defines a layered architecture so application code, the runtime, and basic software can be developed and integrated the same way on every project. The architecture is static: software components, tasks, and communication paths are configured for a known ECU, which fits hard real-time control on small processors.
At design time, software components exchange data over a virtual functional bus without knowing which unit will run them. On the unit, the Runtime Environment (RTE) realizes those connections. Beneath the RTE, basic software provides the operating system, communication, diagnostics, memory, mode management, and microcontroller access. A project picks one Classic release and keeps modules, interfaces, and configuration on that release.
Who it applies to
Classic is the platform for microcontroller ECUs: powertrain, chassis, and body controllers, zone controllers, and the safety island inside a high-performance computer. It scales from a full control unit down to a small network node. Service-oriented computers sit outside it; those use the AUTOSAR Adaptive Platform or a general-purpose operating system.
Application suppliers, basic-software suppliers, and the OEM or integrator who builds the ECU extract all work to the same release. Hardware engineers meet the standard at the driver boundary. Safety and cybersecurity engineers use the diagnostic, communication, and crypto modules, while the safety and cybersecurity cases stay in their own standards.
What it covers
The stack has a fixed order. Application software components sit on top, described by ports, interfaces, runnable entities, and events. The RTE is generated glue between components and between components and basic software. Under that, services hold the operating system and the platform modules, ECU abstraction and I/O hardware abstraction hide the board, and the microcontroller abstraction layer (MCAL) binds drivers to a specific device. Complex drivers carry functions the standard modules do not cover, and they still have to honor the same boundaries.
| Area | Typical modules and responsibility |
|---|---|
| Communication | COM and the PDU Router, then the bus interface and driver; network management beside that path |
| Modes and lifecycle | EcuM, BswM, and ComM |
| Diagnostics | Dcm for protocol and sessions; Dem for event status and event memory |
| Memory and crypto | NvM for non-volatile data; SecOC, Csm, CryIf, and the crypto driver for protected communication and cryptographic jobs |
| Operating system | Tasks, interrupts, and the timing base for runnables |
| Drivers | MCAL for peripherals such as CAN and general-purpose timers; ECU abstraction and complex drivers around them |
Each module specification states behavior, the interfaces other modules may call, and the configuration the integrator must set. The methodology stores that description in a structured ECU model so tools can generate the RTE. The Layered Software Architecture document is the map; module documents are the detail for one service at a time.
How it fits with other documents
Classic is the microcontroller half of AUTOSAR. Adaptive is the service-oriented platform for high-performance computers. A vehicle often uses both.
ISO 26262 remains the safety standard; Classic supplies the operating system, communication, and memory services a safety concept uses. ISO/SAE 21434 and the applicable vehicle cybersecurity regulation remain the security standards; Classic supplies SecOC, the crypto stack, and intrusion-detection services. Bus standards define the controller; Classic defines the software above it, including routing on a zone controller. Diagnostic standards define the services on the wire; Dcm and Dem define how the ECU stores events and answers requests.
In practice
Keep one release for the whole ECU. Mixed releases disagree on interfaces and configuration parameters, and the fault appears at integration. Read the layered architecture, then only the modules this unit includes.
Application teams deliver components whose ports and runnables match the RTE contract. Basic-software teams configure COM, the PDU Router, network management, EcuM, BswM, Dcm, Dem, and NvM together, adding SecOC and the crypto modules only when the design needs them. Driver teams place MCAL, ECU abstraction, and complex drivers on the correct side of the boundary. The specifications are free to read, but signal mapping, parameters, timing, safety, and security remain project work.