Eep (EEPROM) Driver Configuration - MCAL & Driver Development

EEP Architecture: Internal vs External EEPROM

EEP Driver Variants

  Variant 1: Internal EEPROM (e.g., TC3xx DFLASH emulated EEP)
  EEP (MCAL) -- wraps on-chip EEPROM peripheral or emulated EEPROM
      |
  On-chip EEPROM / DFLASH sector with EEP emulation

  Variant 2: External EEPROM via SPI (e.g., M95256 on SPI bus)
  EEP (MCAL) -- communicates with external IC via Spi driver
      |
  Spi_AsyncTransmit() -- reads/writes EEPROM IC registers
      |
  External M95256 (256 Kbit SPI EEPROM)

  Both variants expose identical AUTOSAR EEP API:
  Eep_Read(), Eep_Write(), Eep_Erase(), Eep_Compare()
  Callers do not know if EEP is internal or external

EEP vs FLS: When to Use Each

Property	FLS (Data Flash)	EEP (EEPROM or emulated)
Write granularity	Sector (16 KB minimum erase)	Byte or word (no erase needed)
Endurance	100k-1M erase cycles per sector	100k-1M write cycles per byte
Speed	Erase: 1-10 ms; Write: 10-100 us/word	Write: 1-5 ms typical (SPI EEP)
AUTOSAR module above	Fee -> NvM	Eep -> NvM directly
Typical use	Large calibration datasets, SW images	Odometer, VIN, DTC non-volatile counters
Wear levelling	Fee provides wear levelling across sectors	EEP provides byte-level wear levelling internally

External SPI EEPROM Configuration (M95256)

Ceep_spi_cfg.c

/* EEP over SPI: external M95256 (256 Kbit, 512 pages x 64 bytes) */
#include "Eep.h"
#include "Spi.h"

#define EEP_M95256_SIZE_BYTES  32768u    /* 256 Kbit = 32 KB */
#define EEP_M95256_PAGE_SIZE   64u       /* 64 bytes per page */

/* M95256 SPI commands */
#define EEP_CMD_WREN  0x06u   /* Write Enable */
#define EEP_CMD_RDSR  0x05u   /* Read Status Register */
#define EEP_CMD_READ  0x03u   /* Read data */
#define EEP_CMD_WRITE 0x02u   /* Write data */

const Eep_ConfigType EepConfig = {
    .EepBaseAddress    = 0x0000u,
    .EepSize           = EEP_M95256_SIZE_BYTES,
    .EepPageSize       = EEP_M95256_PAGE_SIZE,
    .EepDefaultMode    = MEMIF_MODE_NORMAL,
    .EepMaxReadFastMode  = 256u,
    .EepMaxWriteFastMode = 64u,   /* max 1 page per MainFunction call */
    /* SPI sequence used by EEP driver */
    .EepSpiSequenceId  = SPI_SEQ_EEPROM_ACCESS,
    .EepJobEndNotification   = NvM_JobEndNotification,
    .EepJobErrorNotification = NvM_JobErrorNotification,
};

/* NvM block: odometer value (4 bytes) */
/* In NvM ARXML config: */
/* NvMBlockDescriptor: NVM_BLOCK_ODOMETER */
/*   NvMNvBlockLength = 4 (bytes) */
/*   NvMNvBlockNum = 1 (no redundancy) */
/*   NvMDeviceId = 0 (EEP device 0) */
/*   NvMBlockManagementType = NVM_BLOCK_NATIVE */

Summary

The EEP driver abstraction means NvM does not care whether EEPROM is a dedicated IC on SPI, an internal peripheral, or emulated in data flash - the Eep_Write() API is identical in all cases. This becomes important when the hardware team decides mid-project to replace the SPI EEPROM with an emulated internal solution to reduce BOM cost: only the EEP driver implementation changes, not NvM or application code. The maximum bytes per MainFunction call (EepMaxWriteFastMode) is the most important performance tuning parameter - set it too low and a 256-byte NvM block write takes 50+ MainFunction calls; set it too high and the CPU is blocked for several milliseconds per call.

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