Fls (Flash) Driver Architecture - MCAL & Driver Development

FLS Architecture: Flash Driver in AUTOSAR

Flash Memory Stack

  NvM (NV Memory Manager) -- logical block management
      |
  MemIf (Memory Abstraction Interface) -- selects FLS or EEP
      |
  Fee (Flash EEPROM Emulation) -- wear levelling, virtual addresses
      |
  Fls (MCAL) -- physical flash read/write/erase
      |
  Hardware: on-chip flash (data flash / DFLASH on Aurix)

  Flash characteristics that FLS must manage:
  - Read: fast (single cycle at any address)
  - Write: slow (10-100 us per word); sector must be erased first
  - Erase: very slow (1-10 ms per sector); min granularity = sector
  - Endurance: 100k-1M erase cycles (Fee handles wear levelling)
  - Read-while-write: data flash supports reading code flash while
    writing data flash; code flash does NOT support this

FLS Configuration and Usage

Cfls_cfg.c

/* FLS MCAL configuration and usage */
#include "Fls.h"

/* Flash sector layout (project-specific, matches MCU datasheet) */
#define FLS_SECTOR_SIZE     0x4000u  /* 16 KB per sector (Aurix DFLASH) */
#define FLS_DATA_BASE_ADDR  0xAF000000u  /* DFLASH start address */
#define FLS_TOTAL_SECTORS   4u

const Fls_ConfigType FlsConfig = {
    .FlsBaseAddress         = FLS_DATA_BASE_ADDR,
    .FlsTotalSize           = FLS_SECTOR_SIZE * FLS_TOTAL_SECTORS,
    .FlsDefaultMode         = MEMIF_MODE_FAST,
    .FlsMaxReadFastMode     = 256u,  /* bytes per Fls_MainFunction call */
    .FlsMaxReadNormalMode   = 32u,
    .FlsMaxWriteFastMode    = 256u,
    .FlsMaxWriteNormalMode  = 32u,
    .FlsJobEndNotification  = Fee_JobEndNotification,
    .FlsJobErrorNotification= Fee_JobErrorNotification,
};

/* Flash write sequence (async -- do NOT call from high-priority task) */
Std_ReturnType Fls_WriteCalibrationData(uint32 addr, const uint8* data, uint16 len)
{
    /* 1. Erase sector (must erase before write if already programmed) */
    if (Fls_Erase(addr, FLS_SECTOR_SIZE) != E_OK) return E_NOT_OK;
    /* Fls_MainFunction() must be called repeatedly until job completes */
    while (Fls_GetStatus() == MEMIF_BUSY) Fls_MainFunction();
    if (Fls_GetJobResult() != MEMIF_JOB_OK) return E_NOT_OK;

    /* 2. Write data */
    if (Fls_Write(addr, data, len) != E_OK) return E_NOT_OK;
    while (Fls_GetStatus() == MEMIF_BUSY) Fls_MainFunction();
    return (Fls_GetJobResult() == MEMIF_JOB_OK) ? E_OK : E_NOT_OK;
}

Summary

Flash write and erase are the most dangerous MCAL operations: an interrupted erase (power loss during Fls_Erase()) leaves the sector in an indeterminate state. This is why Fee (Flash EEPROM Emulation) uses a double-page pattern - it writes to a new page before invalidating the old one, ensuring data survives a power cut during write. Never call Fls_Erase() directly from application code in production; always go through Fee/NvM which handle power-loss safety. The FlsMaxWriteFastMode and FlsMaxWriteNormalMode parameters are critical for real-time performance: they limit how many bytes are written per Fls_MainFunction() call, preventing flash write operations from monopolising the CPU for tens of milliseconds.

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