Error Recovery & Redundant Blocks - AUTOSAR Classic BSW

REDUNDANT Block Read Sequence

REDUNDANT Block Failover Logic

  NvM_ReadBlock(REDUNDANT_BLOCK_ID)
       │
       ├──► Read Primary copy → CRC OK → return NVM_REQ_OK
       │    CRC FAIL ──►
       │         Read Redundant copy → CRC OK → restore primary, return NVM_REQ_OK
       │         CRC FAIL ──►
       │              Both copies corrupt!
       │              → Copy ROM default to RAM block
       │              → Return NVM_REQ_INTEGRITY_FAILED
       │              → NvMInitBlockCallback() called
       ▼
  SWC RAM block now contains valid data (primary, redundant, or default)

NvM RequestResult Codes

Result Code	Value	Meaning
NVM_REQ_OK	0x00	Job completed; data valid
NVM_REQ_NOT_OK	0x01	Job failed; unspecified error
NVM_REQ_PENDING	0x04	Job queued or in progress
NVM_REQ_NV_INVALIDATED	0x05	Block explicitly invalidated; ROM default used
NVM_REQ_INTEGRITY_FAILED	0x08	CRC check failed; ROM default used
NVM_REQ_RESTORED_FROM_ROM	0x0D	Block did not exist in NvM; ROM default restored

Flash Driver ECC Fault Handling

CFls_ECC_Recovery.c

/* Fee detects MEMIF_JOB_FAILED → attempts re-erase of affected block */
if (Fee_GetJobResult() == MEMIF_JOB_FAILED) {
    if (IsEccError()) {
        Fee_EraseImmediateBlock(FEE_BLOCK_ID_FAULTED);
        /* NvM will restore from redundant copy or ROM default */
    }
}

Emergency Erase Procedure (EOL Only)

CEmergencyErase.c

/* UDS RoutineControl $31 — EOL tooling only */
void EmergencyErase_Execute(void)
{
    uint16 blockId;
    for (blockId = 1; blockId <= FEE_MAX_BLOCK_ID; blockId++) {
        (void)Fee_InvalidateBlock(blockId);
        while (Fee_GetJobResult() == MEMIF_JOB_PENDING) { Fee_MainFunction(); }
    }
    (void)Fee_ForceSwapActive(); /* erase old sector */
}

⚠️ Never in Field Use

Emergency erase destroys all persistent data: odometer, fault history, calibration. Only safe at EOL in production with a fresh NvM WriteAll following immediately. Gate via SecurityAccess to prevent field use.

Summary

The REDUNDANT block failover sequence, NvM result codes, and Fee ECC recovery paths form the memory stack's fault tolerance model. Every safety-critical NvM block must be tested for: primary-corrupt-secondary-OK, both-corrupt, and ECC-error-during-read scenarios.

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