Contents

Real-time operating systems and scheduling

How embedded ECUs guarantee timing: priority-based, statically configured operating systems like the AUTOSAR OS, with timing and memory protection for mixed-criticality software.

1 min read · Discipline stake: BSW Safety Hardware Software

Why it exists

A brake controller must run its control loop every few milliseconds — always. General-purpose operating systems optimise average performance; real-time operating systems guarantee worst-case timing.

What it is

  • Static configuration: all tasks and their priorities are known at build time.
  • Priority-based preemptive scheduling: the highest-priority ready task always runs.
  • Protection: memory protection (via the MPU) and timing protection (budgets for tasks) isolate software partitions.
  • Multi-core support: tasks are assigned to cores; inter-core communication is explicit.

Best practices

  • Perform worst-case execution time and response-time analysis, not only measurements.
  • Keep interrupt load bounded; move heavy work to tasks.
  • Separate ASIL and QM software into different OS applications with memory protection.

Common pitfalls

  • Shared resources without proper locking, causing priority inversion.

What it means for your discipline

  • Base software Core

    Configures tasks, priorities, alarms, schedule tables and protection; analyses worst-case timing.

  • Functional safety Core

    Timing protection and memory partitioning provide freedom from interference between software of different ASILs.

  • Hardware & silicon Partial

    Multi-core MCUs, MPUs and lockstep cores determine what the OS can guarantee.

  • HPC & application software Partial

    On HPCs, real-time partitions (e.g. on a safety island) host control loops beside rich operating systems.

No direct stake: E/E architecture · Cybersecurity · Networks & communication · 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)
  • QNX / RT Linux — Schedules real-time workloads with bounded latency and priority-based execution.
  • AUTOSAR OS — Schedules safety-island tasks and enforces timing and memory protection between OS applications.
MCU-based ECU · AUTOSAR Classic
  • OS — Uses configured tasks, priorities, alarms and schedule tables, with timing and memory protection to limit interference.