the map of E-flash and EEE

[lyz]

FlexNVM and FlexRAM together emulate the EEPROM storage. In emulated form, FlexNVM is called

EEPROM-backup and FlexRAM is called EEERAM. The user/application program directly interfaces with EEERAM for emulated

EEPROM operations. For example, if the user wants to write to the emulated-EEPROM, the user writes to the EEERAM and

internally, the flash system locks the interface and writes data back to the EEPROM-backup for non-volatile update. Similarly on

every power-up data is retrieved from EEPROM-backup and copied to the EEERAM for use/application use. In simple language,

EEERAM is the point of contact for user/application to talk to emulated-EEPROM storage.

Problen:the map of e-flash and EEE(How do the datas of EEE write to e-flash, How do addr change?) ,in case of setting FlexNVM is 32k d-flash(Base addr:0x10000000) and 32k e-flash(Base addr:0x10008000), setting FlexRAM is 4k EEE(Base addr:0x14000000)

[danielmartynek]

Hi @lyz,

Your description is correct.

The mapping of EEERAM data to EEPROM-backup data is entirelly managed by the EEPROM state machine - the process / the EEPROM-backup data are not accessible by the user.

Basically. every EEERAM data record is stored in the EEPROM-backup flash along with the EEERAM address of the record. If an EEERAM data record is updated, the updated record is moved to another EEPROM-backup location (again with the EEERAM address) while the old record is invalidated. The oldest sector gets erased when there is no more space for new records / updates, while the still valid static (not updated) records in that sector are moved to new locations (sectors) in EEPROM-backup.

BR, Daniel