topic Re: EEPROM Emulation on MPC5xx/S32K3 in S32K

EEPROM Emulation on MPC5xx/S32K3

wuxianlong — Mon, 29 Aug 2022 02:10:55 GMT

Hi,

I have read AN4868(EEPROM Emulation with Qorivva MPC55xx, MPC56xx, and MPC57xx Microcontrollers). The principle of S32K3xx is the same. I'm meeting a little confused and hoping for help.

1. If i want to update the first data of record1,and do i need to rewrite the whole record1 ?
2. Is Block similar to record in FEE of S32K3?

Re: EEPROM Emulation on MPC5xx/S32K3

davidtosenovjan — Mon, 29 Aug 2022 15:00:13 GMT

1) Records are not being rewritten. It is just the principle of EEPROM emulation that records are only sequentially added (i.e. updated) and so the data are spread over the whole flash range what's minimize a need of erase operation (i.e. prolong device's flash lifetime.

2) Blocks and records are two different terms:
Record is basically entry with a data that is written to active block.
Block is smallest unit on which EEPROM emulation operation may perform erase operation. You may understand it well from section (3.6 Swapping blocks) of mentioned AN4868.

Re: EEPROM Emulation on MPC5xx/S32K3

wuxianlong — Wed, 31 Aug 2022 10:59:49 GMT

Hi,@davidtosenovjan,sorry for late response

I get your message. Maybe there's something wrong with my expression.

1. If i want to update the first data of record1,and do i need to rewrite the whole record1 ?

What I want to know is whether record is the smallest operation unit. If I only change the data in the red box,and other data unchanged, I also have to update the whole record1?

2. Is Block similar to record in FEE of S32K3?
I see an API in S32K344_FEE example , Block is like the smallest unit.

Regards,

Re: EEPROM Emulation on MPC5xx/S32K3

davidtosenovjan — Thu, 01 Sep 2022 08:29:56 GMT

1) Yes, the whole record is needed to be written.

2) Yes, you are correct. Now it is called somehow differently. Instead of block FEE driver uses term 'Cluster'. Instead of record FEE driver it use term 'Block'.

I am sorry for confusions.