What runs here
On a microcontroller-based ECU, application software components (SWCs) implement functions such as brake control, steering assistance or battery management. They interpret inputs, maintain operating states, calculate commands and decide how the function should respond to faults. Suppliers, vehicle manufacturers or both may develop them.
In AUTOSAR Classic Platform, application components communicate through defined ports using the Runtime Environment (RTE). Their executable units are called runnable entities; configured events determine when they execute. A runnable is not itself an operating-system task. AUTOSAR Software Component Template
| Component | Role |
|---|---|
| Input processing and estimation | Check measurements, apply conversions and estimate quantities needed by the controller. |
| Control algorithms | Calculate actuator requests from targets, measurements and internal state. |
| Mode and command management | Coordinate startup, normal operation, shutdown and competing requests. |
| Application safety monitoring | Check plausibility and control results, and request defined fault responses. |
| Diagnostic and adaptation logic | Supply function-specific test results, diagnostic data and learned values. |
These are design responsibilities, not mandatory AUTOSAR component names. Their allocation to SWCs depends on the function and safety architecture.
Why it looks like this
Local control needs predictable execution and bounded input-to-output latency. Keeping control near sensors and actuators reduces dependence on network availability and lets the ECU respond when a remote coordinator is unavailable. Engineers must budget the complete chain: sampling, communication, scheduling, computation and output actuation.
MCUs have finite processing capacity, RAM and embedded flash. Statically configured execution and bounded resource use help fit the function onto cost-constrained silicon and make timing analysis practical. Lockstep execution and hardware protection can support the safety architecture, but do not establish algorithm correctness.
An ECU described as supporting “up to ASIL D” does not make every SWC ASIL D. Software safety requirements and their ASIL follow the safety allocation. Development and verification must address the applicable requirements; using AUTOSAR alone does not demonstrate compliance. ISO 26262-6:2018
Control software updates require reassessing timing, calibration, interfaces and safety evidence. Even a small algorithm change can affect closed-loop behaviour. Update frequency therefore follows the function’s validation needs and vehicle release process.
How it connects
Applications occupy the top of this ECU’s software stack. Above them conceptually are vehicle-level requirements and coordination functions, which may execute on another node. A remote request becomes an input to local control, with explicit validity checks, limits and fallback behaviour.
Below the application, the RTE connects SWCs to each other and to configured services. Sender-receiver interfaces exchange data; client-server interfaces invoke operations. Hardware access normally passes through the configured abstraction layers. AUTOSAR separates applications, RTE and basic software to support this separation of responsibilities. AUTOSAR Classic Platform
For remote signals, the configured communication path can include AUTOSAR COM, PduR, bus interfaces and drivers. Application contracts must define units, ranges, data age and invalid-data handling. Service interfaces connect function logic to facilities such as Diagnostic Event Manager (Dem) event reporting and Nonvolatile RAM Manager (NvM) storage. These services belong below this layer; applications provide function-specific meaning and reactions.
Compared with other node classes
- HPC application processor: Feature services, HMI and ADAS applications often need richer operating-system facilities and larger datasets; MCU applications emphasise bounded local control.
- HPC safety island: Control and monitoring may use similar techniques, but must also address dependencies on the main processor and shared SoC resources.
- Zone controller: Application logic concentrates on local I/O, routing decisions and coordination, although allocated control functions can also run there.
- Smart node or LIN slave: A narrow fixed function may use a much smaller software structure without a full AUTOSAR Classic deployment.
Best practices
- Define port contracts covering units, scaling, validity, startup values and maximum acceptable data age.
- Budget runnable execution, activation rates, ordering and end-to-end latency with the integration team.
- Specify fault responses for missing inputs, implausible measurements, actuator faults and lost coordination.
- Trace safety requirements through implementation and verification; test boundaries, mode transitions and fault recovery.
- Control calibration and persistent-data compatibility alongside software versions; validate changes on representative hardware.
Common pitfalls
- Assuming RTE generation guarantees deadlines or a safe execution order.
- Treating a received value as usable without checking freshness, validity and operating mode.
- Assuming every fault should immediately switch an actuator off; the safe or degraded response depends on the function.
- Bypassing interfaces through shared globals or direct hardware access without analysing coupling and interference.