Dual-Bank & A/B Update Strategies - Flash Bootloader Development

Dual-Bank Flash Architecture

Dual-Bank Flash: Banks A and B

  PBL (32 kB, hardware-protected)
  SBL (256 kB, write-protected after factory)
  Boot Flags (4 kB, NvM-persistent)
  ┌──────────────────────────┬──────────────────────────┐
  │  BANK A (7 MB)           │  BANK B (7 MB)           │
  │  App v1.0 — ACTIVE       │  App v1.1 — STAGED       │
  │  (running now)           │  (downloaded via OTA)    │
  └──────────────────────────┴──────────────────────────┘

  OTA Flow:
  1. OTA master downloads v1.1 into Bank B while vehicle running from Bank A
  2. Checksum verified → SWAP_REQUESTED = TRUE
  3. Next ignition: PBL verifies Bank B → sets ACTIVE_BANK = B
  4. App v1.1 boots → confirms health → BOOT_ATTEMPT_COUNT = 0
  5. Update confirmed; Bank A becomes fallback

Bank Swap in PBL

Cbank_swap.c

void PBL_DualBankDecision(void)
{
    BootFlags_t f; BootFlags_Read(&f);

    if (f.swap_requested) {
        uint8_t  nb   = (f.active_bank == BANK_A) ? BANK_B : BANK_A;
        uint32_t base = (nb == BANK_A) ? BANK_A_BASE : BANK_B_BASE;
        if (App_IsValidAt(base)) {
            f.active_bank = nb; f.swap_requested = FALSE;
            f.boot_attempt_count = 1u;
        } else {
            f.swap_requested = FALSE;
            Dem_ReportErrorStatus(DEM_EVENT_BANK_SWAP_FAILED, DEM_EVENT_STATUS_FAILED);
        }
        BootFlags_Write(&f);
    }

    /* 3 consecutive crashes → rollback */
    if (f.boot_attempt_count >= 3u) {
        uint8_t fb   = (f.active_bank == BANK_A) ? BANK_B : BANK_A;
        uint32_t fbb = (fb == BANK_A) ? BANK_A_BASE : BANK_B_BASE;
        if (App_IsValidAt(fbb)) {
            f.active_bank = fb; f.boot_attempt_count = 0u;
            BootFlags_Write(&f);
            Dem_ReportErrorStatus(DEM_EVENT_AUTO_ROLLBACK, DEM_EVENT_STATUS_FAILED);
        }
    }
    f.boot_attempt_count++;
    BootFlags_Write(&f);
    PBL_JumpToAppAt((f.active_bank == BANK_A) ? BANK_A_BASE : BANK_B_BASE);
}

Automatic Rollback Conditions

Condition	Detection	Action
New bank CRC fails	PBL validates Bank B before swap	Cancel swap; stay on Bank A
App crashes 3x	BOOT_ATTEMPT_COUNT >= 3	Rollback to other bank
App healthy	App sets BOOT_ATTEMPT_COUNT=0 within 10s	Update confirmed
Manual rollback	UDS routine 0xFF10	Set ACTIVE_BANK to previous; clear count

Summary

Dual-bank architecture enables zero-downtime OTA: the vehicle continues from Bank A while Bank B receives the new software. The boot attempt counter is the critical safety net — without it a crashing app causes an infinite reset loop. The application must explicitly confirm health by clearing the counter within 10 seconds of normal operation, acting as a software watchdog confirmation for the update cycle.

🔬 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.