Contents

ECU reprogramming and software logistics

How software actually gets into each ECU — in the factory, in the workshop and over the air — and how versions, dependencies and SBOMs are kept under control.

Why it matters

A vehicle contains dozens of software components from many suppliers. Each must be the right version, compatible with the others, and traceable for regulation and vulnerability management.

What the process covers

  • Production: end-of-line flashing and configuration (coding, keys).
  • Service: workshop flashing via diagnostic tools.
  • Over the air: remote updates orchestrated by the HPC.
  • Logistics: which software set belongs to which vehicle configuration; SBOMs list every component.
Typical UDS reprogramming sequence
Programming sessionDiagnosticSessionControl selects the required session
Security accessObtain reprogramming authorization as required
Erase memoryTypically an ECU-specific RoutineControl routine
Download and transferRequestDownload → TransferData → RequestTransferExit
Check softwareVerify integrity, authenticity and dependencies as required
Reset ECUECUReset restarts the ECU

Example sequence: authorization, erase and verification procedures, prerequisites and exact ordering depend on the ECU and manufacturer.

Best practices

  • Manage software sets (compatible combinations), not individual files.
  • Keep SBOMs for every released software set and monitor them for new vulnerabilities.

Common pitfalls

  • Variant explosion: too many software combinations to test and manage.

What it means for your discipline

  • Software update & OTA Core

    Software logistics: which version goes to which ECU and vehicle variant, flash sequences in production and service, and records for SUMS.

  • Diagnostics & lifecycle Core

    UDS programming services, tester tools and version checks used for flashing in production and the workshop.

  • Base software Core

    Flash bootloaders, memory layout and update interfaces in each ECU.

  • Cybersecurity Partial

    Authenticated reprogramming, signature verification and SBOM-based vulnerability tracking.

  • Hardware & silicon Partial

    Flash size, write endurance and dual-bank memory determine what is possible.

No direct stake: E/E architecture · Functional safety · HPC & application software · 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)
  • OTA client · UCM — Selects compatible software packages for the vehicle configuration and orchestrates their installation across target controllers.
  • Diagnostics — Exposes software identification and diagnostic operations used by production and workshop tooling.
  • Security services — Provides authorization and cryptographic verification for reprogramming operations and software packages.
MCU-based ECU · AUTOSAR Classic
  • Flash bootloader · secure boot — Executes the programming sequence, verifies downloaded software and restarts the controller into the installed image.
  • Diagnostics — Provides diagnostic programming entry and software identification; programming services may execute in the bootloader.
  • Microcontroller abstraction (MCAL) — Flash drivers perform the erase and write operations required to program the replacement software.
  • Microcontroller · HSM — Flash capacity, write endurance and bank organization constrain image layout and programming strategy.