Contents

Safety mechanisms, watchdogs and safe states

What an ECU does when something goes wrong: monitoring with watchdogs and plausibility checks, and the transition to a safe or degraded state.

Why it matters

Faults will happen. Safety is about detecting them in time and reacting so that no hazard results.

What the building blocks are

  • Monitoring: watchdogs (is the software alive and on time?), plausibility checks, voltage and clock monitors, lockstep comparison.
  • Fault tolerance time interval: how long a fault may persist before it could cause harm — the reaction must be faster.
  • Safe state: e.g. motor torque off, valve closed, warning to the driver.
  • Degraded / fail-operational mode: for functions that cannot simply switch off (e.g. steering at speed), a reduced but safe function continues on a redundant path.

Best practices

  • Use an independent shutdown path that does not rely on the faulty software.
  • Test fault reactions with fault injection on real hardware.

Common pitfalls

  • A safe state that is not actually safe in all driving situations.

What it means for your discipline

  • Functional safety Core

    Defines safe states, fault tolerance times and degradation strategies.

  • Base software Core

    Implements watchdog management, monitoring, error handling and mode transitions.

  • Hardware & silicon Core

    External watchdogs, lockstep cores, voltage monitors and independent shutdown paths.

  • E/E architecture Partial

    Fail-operational functions (steer-by-wire, automated driving) need redundant architectures, not just a safe state.

  • Software update & OTA Partial

    Coordinates update preconditions and safe vehicle states during flashing, including watchdog handling and recovery when installation fails.

No direct stake: Cybersecurity · HPC & application software · Networks & communication · Diagnostics & lifecycle

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)
  • Safety monitors — Checks plausibility and commands safe or degraded operation when faults threaten the vehicle function.
  • WdgM · E2E · Dem — Watchdog management detects missed execution deadlines and triggers configured fault reactions.
  • Lockstep cores — Lockstep cores and ECC memory detect hardware faults that require timely safety reactions.
MCU-based ECU · AUTOSAR Classic
  • Application layer — Implements plausibility checks and function-specific transitions to safe or degraded operation.
  • Memory · crypto · WdgM — Watchdog management supervises software execution and initiates configured recovery or shutdown reactions.
  • Microcontroller · HSM — Hardware safety mechanisms detect processor and memory faults and support reset or independent shutdown paths.