Anti-Rollback Protection

/* NvM-based monotonic counter: only increments; never decrements */
#include "NvM.h"
#define NVM_MIN_VERSION  0x0010u

uint32_t AntiRollback_GetMin(void) {
    uint32_t v = NvM_Read(NVM_MIN_VERSION);
    return (v == 0xFFFFFFFFu) ? 0u : v;
}

void AntiRollback_UpdateMin(uint32_t new_ver) {
    if (new_ver > AntiRollback_GetMin())
        NvM_Write(NVM_MIN_VERSION, new_ver);
}

Std_ReturnType AntiRollback_Check(uint32_t image_ver) {
    if (image_ver < AntiRollback_GetMin()) {
        Dem_ReportErrorStatus(DEM_EVENT_PROG_ROLLBACK_BLOCK, DEM_EVENT_STATUS_FAILED);
        return E_NOT_OK;   /* NRC 0x22 in UDS session */
    }
    return E_OK;
}
/* Update order: verify sig → verify CRC → anti-rollback check →
   install → verify → update counter → reset (atomic with boot flags) */

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