Why it matters
Every ECU starts from a bootloader. It decides whether the application is valid and allows new software to be written. If an attacker can bypass it, they can run any software on the ECU.
What it is
- Boot ROM (in silicon) starts first and loads the first software stage.
- Bootloader checks the application, starts it, or stays active to receive new software.
- Flash bootloader implements reprogramming via diagnostics.
- On HPCs, a multi-stage chain (boot ROM → firmware → hypervisor → OS) verifies each stage.
How reprogramming works
A tester or update client switches the ECU into a programming session, authenticates, erases memory, transfers the new software in blocks, verifies a signature and checksum, and resets into the new application.
This simplified sequence follows the article; authentication and verification details depend on the ECU.
Best practices
- Verify signatures, not just checksums, before running or accepting software.
- Use A/B banks where memory allows, so a failed update can roll back.
- Keep the bootloader small, rarely changed and itself protected.
Common pitfalls
- Debug or “engineering” unlock paths left active in production.