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.
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 & OTACore
Software logistics: which version goes to which ECU and vehicle variant, flash sequences in production and service, and records for SUMS.
Diagnostics & lifecycleCore
UDS programming services, tester tools and version checks used for flashing in production and the workshop.
Base softwareCore
Flash bootloaders, memory layout and update interfaces in each ECU.
CybersecurityPartial
Authenticated reprogramming, signature verification and SBOM-based vulnerability tracking.
Hardware & siliconPartial
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)