Contents

Platform services on the MCU-based ECU

These services let a control ECU answer diagnostic requests, remember important data across power cycles, authenticate selected messages and use protected cryptographic operations.

What runs here

On an MCU-based brake, steering or battery-management ECU, platform services provide shared infrastructure around the control application. AUTOSAR Classic supplies the module model; the exact selection and configuration depend on the ECU requirements.

Component Role
Diagnostic Communication Manager (Dcm) Handles diagnostic requests, sessions and configured access checks, and dispatches services to their handlers.
Diagnostic Event Manager (Dem) Collects reported fault events and manages diagnostic trouble code status and associated records.
NVRAM Manager (NvM) Manages configured persistent data blocks, such as learned values, configuration and fault records.
Secure Onboard Communication (SecOC) Generates and verifies authentication information for selected protocol data units, using freshness information to resist replay.
Crypto Service Manager (Csm), Crypto Interface (CryIf), Crypto Driver Provide cryptographic jobs and route them to software or hardware implementations, potentially using a hardware security module (HSM).

Dcm handles the diagnostic conversation; Dem manages the fault information that the conversation can expose. Application monitors still decide whether particular faults exist. See the AUTOSAR specifications for Dcm and Dem.

Why it looks like this

Control deadlines, limited RAM and embedded flash favour explicitly configured services with bounded resource use. Diagnostic requests, flash operations and cryptographic jobs compete with control tasks for processor time, memory and shared hardware. Their scheduling and overload behaviour therefore need deliberate budgets.

Persistent storage also costs flash endurance and shutdown time. NvM separates application data handling from the underlying memory technology and supports asynchronous processing. Accepting a write request does not mean the data is already durable. AUTOSAR NVRAM Manager.

An ECU supporting functions up to ASIL D does not automatically make every platform service ASIL D. Safety requirements determine which services need safety assurance and which need isolation. Recording a DTC is not, by itself, a timely safety reaction.

An HSM can support protected key handling and cryptographic execution, but its capabilities and driver integration are silicon-specific. Keeping the application behind stable interfaces helps manage hardware variants and software updates; persistent-data formats and key references still need compatibility planning.

How it connects

Above these services, application software components use configured RTE service interfaces; basic software modules also interact through defined APIs. Monitors report events to Dem, diagnostic handlers provide data or execute routines for Dcm, and clients request persistent-block operations from NvM.

Below them, NvM reaches memory abstraction and drivers—for example, MemIf and Fee for a flash-emulation configuration. The crypto path runs through Csm, CryIf and Crypto Driver to the selected implementation. HSM access belongs behind that integration rather than arbitrary application calls. AUTOSAR crypto services overview.

Diagnostic traffic reaches Dcm through PduR and the configured transport stack, such as CanTp over CAN. A gateway may forward requests from a remote tester. SecOC integrates with PduR to authenticate selected communication paths; communicating nodes must agree on keys, protected content and freshness handling. SecOC provides authenticity and integrity, not confidentiality or a replacement for safety E2E protection. AUTOSAR SecOC specification.

Compared with other node classes

  • HPC application processor: Platform services emphasise update orchestration, SOVD, host intrusion detection and richer logging; this MCU keeps local control-support services tightly budgeted.
  • HPC safety island: Watchdog supervision, E2E checking and fault memory dominate its narrower safety role; diagnostic access may be mediated by the host.
  • Zone controller: Similar Dcm/Dem services coexist with network management, security-event handling and local power-distribution services.
  • Smart node or LIN slave: Configuration and basic diagnostics may use a much smaller implementation; a full AUTOSAR service stack is not implied.

Best practices

  • Budget diagnostic, NvM and crypto work under simultaneous peak demand, including shared flash and HSM contention.
  • Define Dem event ownership, debounce rules, operation cycles and record retention alongside application monitors.
  • Specify NvM defaults, write frequency, completion handling, power-loss recovery and data migration across updates.
  • Design key provisioning, replacement and SecOC freshness recovery together, including ECU replacement and reset scenarios.
  • Gate diagnostic writes and routines by authorization and operating conditions; verify that service activity cannot violate control deadlines.
  • Test interrupted writes, full queues, authentication failures and reset sequences on representative hardware.

Common pitfalls

  • Treating an accepted asynchronous request as completed storage or completed cryptography.
  • Assuming SecOC authenticates the physical truth of a sensor reading or replaces plausibility checks.
  • Treating ordinary NvM blocks as protected key storage without analysing the implementation.
  • Assuming AUTOSAR conformance alone establishes functional safety or cybersecurity assurance.

What it means for your discipline

  • Base software Core

    Configures and integrates the service modules, their scheduled processing, queues and memory mappings. Verifies startup, shutdown and failure behaviour against ECU resource budgets.

  • Diagnostics & lifecycle Core

    Defines diagnostic services, access conditions, event-to-DTC mappings and fault-record content. Checks that workshop observations match application monitor behaviour.

  • Cybersecurity Partial

    Defines message authentication, diagnostic authorization and key-lifecycle requirements. Reviews freshness recovery and the protection provided by the crypto backend and HSM.

  • Functional safety Partial

    Determines which service failures can affect safety requirements and what isolation or monitoring is needed. Checks that diagnostics, persistence and cryptography cannot disrupt required control timing.

  • Software update & OTA Partial

    Coordinates diagnostic access and programming handover with the ECU's service configuration. Plans persistent-data migration and key compatibility so installation, reset and rollback preserve usable ECU state.

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

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
  • Diagnostics — Dcm handles diagnostic requests and access checks; Dem manages reported fault events, DTC status and associated records.
  • Memory · crypto · WdgM — NvM manages persistent blocks; cryptographic services route jobs to configured backends with bounded resource use.
  • Communication — SecOC authenticates selected PDUs and checks freshness using coordinated keys and recovery rules.