Contents

Middleware & runtime on the MCU-based ECU

The generated AUTOSAR runtime connects application components to each other and to communication software that exchanges signals with other ECUs.

3 min read · Discipline stake: BSW Software Safety Networks

What runs here

On an MCU-based ECU, this cell typically contains the AUTOSAR Classic Runtime Environment (RTE) and AUTOSAR COM. Together, they connect application software components (SWCs) to configured communication paths. Architecturally, the RTE sits between applications and basic software; COM belongs to basic software.

Component Role
RTE Provides generated application interfaces, implements configured component connections, and connects runnable activation to operating-system mechanisms.
AUTOSAR COM Packs and unpacks signals and signal groups in interaction-layer protocol data units (I-PDUs), with configured transmission behaviour and reception monitoring.
Configured data transformers Adapt representations or apply mechanisms such as end-to-end protection where the design requires them.

A runnable is an application execution unit activated under configured conditions. The RTE supports sender–receiver data exchange and client–server operations; local connections need not pass through COM or a network. Its implementation depends on component descriptions, ECU mapping and configuration. AUTOSAR Specification of RTE Software

Why it looks like this

Brake, steering and battery-control functions need bounded execution and communication behaviour. Mostly static connections, generated interfaces and explicit scheduling make resource use and dependencies easier to analyse. They do not themselves guarantee deadlines: application execution, task priorities, interrupts and network contention still determine timing.

MCUs commonly have constrained RAM, embedded flash and limited processing capacity. Configuring only the required communication paths helps manage these budgets. Buffer copies, queues and runnable activations still consume resources and must be measured.

For safety-related functions, the implementation needs evidence appropriate to allocated ISO 26262 requirements. Neither using AUTOSAR nor running on a lockstep MCU automatically makes middleware suitable for ASIL D. Communication protection, interference control and fault handling remain system-design responsibilities.

Updates also have integration consequences: changing a port type, signal layout or runnable mapping can require regeneration and coordinated verification across components and ECUs.

How it connects

Above this layer, application SWCs use generated RTE interfaces, such as sender–receiver read/write operations. Below it, the RTE uses operating-system services for execution and COM for configured network signal exchange.

A typical CAN transmission path is:

Application SWC → RTE → COM → PduR → CanIf → Can driver

COM handles signal representation and configured transmission rules; PduR routes PDUs onward. Reception follows the corresponding path back toward the application. Other buses use their applicable lower communication modules. COM transmission requests and reception callbacks must be interpreted according to configuration; an application write does not necessarily mean immediate bus transmission. AUTOSAR Specification of Communication

Safety-related communication may add AUTOSAR End-to-End (E2E) protection. Its checks support detection of communication faults, while the receiving function must decide how to handle rejected or unavailable data. SecOC addresses authenticity and freshness under a security design; it has a different purpose. Protection boundaries must be explicit. AUTOSAR Overview of Functional Safety Measures

Compared with other node classes

  • HPC application processor: Adaptive AUTOSAR or other service middleware commonly supports service-oriented applications; Classic RTE/COM focuses on configured component and signal connections.
  • HPC safety island: The same Classic mechanisms can apply, with additional attention to shared-memory or interprocessor communication boundaries.
  • Zone controller: RTE/COM may coexist with extensive PduR gateway routing. Forwarded traffic need not enter an application SWC.
  • Smart node or LIN slave: A smaller protocol implementation may suffice; a full Classic RTE/COM configuration is not inherent to the node class.

Best practices

  • Define units, scaling, ranges, initial values and invalid-data behaviour for every interface.
  • Budget the complete sensor-to-consumer path, including scheduling, buffering, bus access and receiving-task activation.
  • Keep software descriptions, network definitions, generated code and generator versions reproducible and consistent.
  • Specify signal-group consistency, queue behaviour and data-age expectations before selecting communication settings.
  • Verify startup, sleep/wake transitions, missing messages and recovery, including the application’s response.
  • Establish safety protection boundaries and assess interference through shared buffers, tasks and communication resources.

Common pitfalls

  • Treating successful RTE access as proof that data is fresh, valid or already transmitted.
  • Assuming COM reception monitoring alone establishes end-to-end safety or application-level age limits.
  • Changing signal layouts or timing independently of peer ECUs and expecting interface compatibility.
  • Assuming generated code removes the need to review configuration, concurrency and execution costs.

What it means for your discipline

  • Base software Core

    Configures and integrates RTE, COM and their connections to PduR and the operating system. Daily work includes generation, buffer sizing, scheduling integration and communication fault analysis.

  • HPC & application software Core

    Defines SWC ports, runnable behaviour and data-consumption semantics. Application developers must handle unavailable, invalid and stale inputs consistently with the function's requirements.

  • Functional safety Partial

    Allocates communication safety requirements and reviews protection boundaries, timing assumptions and interference arguments. Checks that detected communication faults trigger the required application response.

  • Networks & communication Partial

    Aligns signal layouts, transmission behaviour and network timing with ECU configuration. Investigates discrepancies between application updates and observed bus traffic.

No direct stake: E/E architecture · Cybersecurity · Hardware & silicon · Diagnostics & lifecycle · Software update & OTA

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)

Not directly involved on this node type.

MCU-based ECU · AUTOSAR Classic
  • Runtime environment (RTE) — Connects SWC ports through generated interfaces and maps runnable activation to configured OS mechanisms.
  • Communication — Packs and unpacks signals, applies configured transmission rules, and monitors reception.