| Concept | Description | Purpose |
|---|---|---|
| Partition A (current) | Currently running OS/firmware partition | Active system; vehicle operates from here |
| Partition B (standby) | Inactive copy; OTA writes new version here | Update target; written without interrupting running system |
| Bootloader | Reads boot flag to select A or B; validates signature | Entry point; decides which partition to boot |
| Boot flag | Persistent storage (eMMC reserved, fuse, RTC register) | Survives power cycle; indicates which partition is active |
| Revert flag | Set after switch to B; cleared after health validation | If health check fails, revert to A on next boot |
| Commit | Clear revert flag; make B permanent | After successful health check: B is now trusted |
A/B (Redundant) Partition Concepts
Partition Layout Example
# HPC eMMC partition layout for A/B OTA
storage:
device: /dev/mmcblk0
total_size_gb: 64
partitions:
- name: boot_a
size_mb: 256
content: kernel + device tree (partition A)
mountpoint: /boot_a
- name: system_a
size_mb: 8192
content: root filesystem (OS + middleware) partition A
filesystem: ext4 (read-only when active)
mountpoint: /system
- name: boot_b
size_mb: 256
content: kernel + device tree (partition B)
mountpoint: /boot_b
- name: system_b
size_mb: 8192
content: root filesystem (OS + middleware) partition B
filesystem: ext4
mountpoint: /system_b # mounted only during OTA write
- name: userdata
size_mb: 32768
content: apps, maps, user preferences, logs
filesystem: ext4 (read-write)
note: NOT updated by A/B OTA; persists across updates
- name: factory
size_mb: 4096
content: factory recovery image
note: read-only; used for factory reset only
- name: metadata
size_mb: 64
content: boot flag, update status, anti-rollback counter
filesystem: raw (no filesystem; direct structure write)Bootloader A/B Decision Logic
/* Simplified A/B bootloader partition selection */
#include "partition_metadata.h"
#include "secure_boot.h"
typedef struct {
uint32_t magic; /* 0xAB2024AB */
uint8_t active_slot; /* 0=A, 1=B */
uint8_t boot_attempt; /* retry counter */
uint8_t max_retries; /* 3: after 3 failures, revert */
uint8_t health_ok; /* set by OS after validation */
uint32_t version_a; /* anti-rollback counter */
uint32_t version_b;
uint32_t crc32; /* metadata integrity */
} BootMetadata_t;
uint8_t bootloader_select_partition(BootMetadata_t *meta) {
/* Check if last boot was health-validated */
if (meta->health_ok == 0 && meta->boot_attempt > 0) {
/* Previous boot did not confirm health -- count attempts */
meta->boot_attempt++;
if (meta->boot_attempt > meta->max_retries) {
/* Too many failures: revert to other slot */
meta->active_slot ^= 1; /* toggle A<->B */
meta->boot_attempt = 0;
meta->health_ok = 0;
}
} else {
meta->boot_attempt = 1;
meta->health_ok = 0; /* cleared until OS sets it */
}
/* Verify signature of selected partition before booting */
if (!secure_boot_verify_partition(meta->active_slot)) {
/* Signature invalid: try other slot */
meta->active_slot ^= 1;
if (!secure_boot_verify_partition(meta->active_slot)) {
bootloader_panic("Both partitions failed signature check");
}
}
return meta->active_slot;
}Summary
The A/B partition strategy is the foundation of reliable OTA updates. Without A/B, every firmware update risks bricking the vehicle if power fails mid-flash -- there is no safe copy to fall back to. With A/B, the update is written to the inactive partition while the vehicle continues running from the active one; only the boot flag changes at the moment of switchover. The bootloader retry counter and automatic revert are the hardware-level safety net: even if the OS health check never runs (because the new OS crashes on boot), the bootloader will automatically revert to the previous partition after N failed boot attempts. This mechanism alone has prevented countless field failures in production SDV deployments.
🔬 Deep Dive — Core Concepts Expanded
This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.
Key principles to reinforce:
- Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
- Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
- Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.
🏭 How This Topic Appears in Production Projects
- Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
- Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
- Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.
⚠️ Common Mistakes and How to Avoid Them
- Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
- Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
- Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
- Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.
📊 Industry Note
Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.