S32KのトピックRe: EEPROM LOST OR FAIL

EEPROM LOST OR FAIL

PINKMAN — Tue, 05 Nov 2024 07:09:17 GMT

hello,experts:

We are updating the APP via UDS protocol and recording the number of updates in the EEPROM, we have executed it more than 3000 times in total with one failure in between. The last read count is only about 800 times, we suspect that the EEprom has failed to write due to some factor resulting in data loss, what are the factors that may cause the EEPROM to lose or fail?

Re: EEPROM LOST OR FAIL

PINKMAN — Tue, 05 Nov 2024 07:29:37 GMT

when failed ,we found the eeprom data is 0

Re: EEPROM LOST OR FAIL

davidtosenovjan — Wed, 06 Nov 2024 07:56:03 GMT

Could you specify used product?

Re: EEPROM LOST OR FAIL

PINKMAN — Thu, 07 Nov 2024 00:31:41 GMT

S32K116

Re: EEPROM LOST OR FAIL

davidtosenovjan — Fri, 08 Nov 2024 15:55:03 GMT

In general ECC error in FLASH may have following reason:
- Unexpected reset during flash erase or flash program operation
- Wear out of particular flash sector = number of program/erase cycles that device’s flash is capable to withstand is exceeded (in practice, real endurance is greater than specified minimum).
- Over-programming of particular flash area that is programming without erasing. It is basically software fault.
- Soft error (radiation, electro-magnetic interference, or electrical noise) during reading or executing from flash memory

As EEEPROM state machine is autonomous, over-programming does not happen.
Unexpected reset is typical reason of loosing data, EEEPROM is capable to restore previous data.