S32KのトピックNVM Corruption mentioned as below

NVM Corruption mentioned as below

abdul_rahiman_csg — Fri, 04 Jul 2025 10:07:34 GMT

We are observing NVM corruption in one of the Hardware parts during vehicle operation. Could you please help us understand why this is occurring

Re: NVM Corruption mentioned as below

lukaszadrapa — Tue, 08 Jul 2025 11:32:57 GMT

Hi @abdul_rahiman_csg

0x1000_0000 - 0x1001_FFFF is data flash memory. Most likely, your application programs double words (i.e. 64bit word) which is not in fully erased state. But this is not allowed:

If you need to update a double word which is not fully erased, it's necessary to erase whole sector and then program previous data back to that sector.

Regards,

Lukas

Re: NVM Corruption mentioned as below

abdul_rahiman_csg — Wed, 09 Jul 2025 10:00:53 GMT

Thank you for your response.
Based on our understanding, what you mentioned is correct in the case of direct access to Data Flash memory. However, in our case, we are using Data Flash as NVM, and the FEE module handles erase and write operations using a wear-leveling technique.

We are trying to understand the cause of the memory corruption issue mentioned earlier. To reproduce the problem, we have been continuously writing data into NVM, but so far we have not been able to reproduce the issue.
May be you can correct me if i'm wrong

Re: NVM Corruption mentioned as below

lukaszadrapa — Thu, 10 Jul 2025 06:38:47 GMT

If Fee is used, Fee and underneath modules are supposed to recover from brownout. It's described in "Managing Cluster and Block Consistency" section in Fee user manual. What response do you get from FeeInit function? What is the NumberOfSwap (you can get that using Fee_GetRunTimeInfo)? Isn't that caused by wear-out?