Home Learning Paths ECU Lab Assessments Interview Preparation Arena Pricing Log In Sign Up

Lab Scope: Non-Volatile Memory Access

BlockStorageSizeData
NVM_BLOCK_CALIBFLS via Fee512 bytesEngine calibration map
NVM_BLOCK_ODOMETEREEP4 bytesOdometer value (km)
NVM_BLOCK_DTC_COUNTEREEP16 bytesDTC occurrence counters
NVM_BLOCK_VINEEP17 bytesVehicle Identification Number

Exercise 1: NvM Block Read and Write

Cnvm_access.c
/* NvM block access: read and write via AUTOSAR NvM API */
#include "NvM.h"

/* NvM block IDs (generated by AUTOSAR configurator) */
#define NVM_BLOCK_ODOMETER    ((NvM_BlockIdType)2u)
#define NVM_BLOCK_CALIB       ((NvM_BlockIdType)5u)

/* RAM mirrors: NvM copies NV data here on read; writes from here */
static uint32 g_odometer_km = 0u;   /* RAM mirror for odometer */
static uint8  g_calib[512];          /* RAM mirror for calibration */

/* --- Read at startup (called from EcuM_AL_DriverInitTwo) --- */
void NvM_ReadAll_AndWait(void)
{
    NvM_ReadAll();  /* triggers async read of all NvM blocks */

    /* Wait for all reads to complete (startup phase only) */
    /* In production: use NvM status polling in startup sequence */
    uint16 timeout = 10000u;  /* 10s max */
    while ((NvM_GetErrorStatus(NVM_BLOCK_ODOMETER, ...) == NVM_REQ_PENDING)
           && (timeout-- > 0u)) {
        NvM_MainFunction();
        Fls_MainFunction();
        Eep_MainFunction();
        /* 1ms delay */
    }
}

/* --- Write (triggered by application) --- */
void App_UpdateOdometer(uint32 new_km)
{
    g_odometer_km = new_km;
    /* Request NvM write (async: Fee/EEP will handle at next opportunity) */
    NvM_WriteBlock(NVM_BLOCK_ODOMETER, &g_odometer_km);
    /* NvM_WriteAll() called at shutdown (EcuM GoSleep) to flush pending writes */
}

Exercise 2: Power-Loss Safe Odometer

Codometer_safe.c
/* Power-loss safe odometer: write with CRC protection */
/* NvM handles CRC automatically when NvMBlockUseCrc = TRUE */
/* On read after power loss during write: NvM detects CRC mismatch,
   restores from redundant block (NvM_BlockManagementType = REDUNDANT) */

#define ODOMETER_MAX_KM  999999u

typedef struct {
    uint32 km_total;      /* total odometer */
    uint32 km_trip;       /* trip counter */
    uint16 write_count;   /* NVM write cycle counter (wear monitor) */
    uint8  reserved[2];
} OdometerBlock_t;

static OdometerBlock_t g_odometer;  /* NvM RAM mirror */

void Odometer_Update_1min(uint32 distance_m)
{
    if (g_odometer.km_total >= ODOMETER_MAX_KM) return;

    g_odometer.km_total  += distance_m / 1000u;
    g_odometer.km_trip   += distance_m / 1000u;
    g_odometer.write_count++;

    /* NvM write request: NvM writes at shutdown or on periodic flush */
    NvM_SetDataIndex(NVM_BLOCK_ODOMETER, 0u);  /* select dataset 0 */
    NvM_WriteBlock(NVM_BLOCK_ODOMETER, &g_odometer);
    /* NvM_BlockManagementType = REDUNDANT: two physical copies written */
    /* If power fails during write, second copy is used on next startup */
}

Summary

The NvM/Fee/FLS/EEP stack is one of the most failure-prone parts of an ECU if configured incorrectly. Common failures: NvM RAM mirror not initialised before first write (NvM writes uninitialised RAM to flash), NvM_WriteAll() not called at shutdown (pending writes lost on key-off), CRC mismatch handling not configured (NvM silently uses corrupt data on startup). The AUTOSAR NvM redundant block management feature (writing two physical copies and verifying both on read) is mandatory for data that must survive a single power failure - odometer, VIN, security access counters. Single-copy blocks are acceptable for non-safety data like user preferences.

🔬 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

  1. 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'.
  2. 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.
  3. 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.
  4. 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.

← PreviousDMA Configuration and IntegrationNext →Infineon Aurix TC3xx MCAL