e10570: FMC: Potential flash controller hang with multiple flash access errors

julieliu — Tue, 02 Jun 2020 05:42:02 GMT

Hello This a known issue listed in S32K144_0N47T.pdf , my platform is S32K144.

Now I have a few questions regarding this issue.

1.If I only want to do Pflash or Fflash read write or erase,should I disable the speculation buffer.

2.In what case it's a must to disable speculation buffer.

3.How to understand "multiple flash access error" ?

4.If I have such issue , how to recover from the error.

5.If this known issue fixed now on S32K144.

thanks for your reply .

Br,

Julie

Re: e10570: FMC: Potential flash controller hang with multiple flash access errors

danielmartynek — Mon, 08 Jun 2020 12:53:30 GMT

Hello Julie,

This issue has been fixed, there is no such erratum for the production mask: 0N57U.

It is not a must to disable the buffers when the flash is being reprogrammed, it is on the users’ responsibility.
Because the buffers are not updated by the FTFC commands (program phrase, erase sector, …).
For example, when Data Prefetch is enabled, the single-entry 128 (64 for bank1, Data Flash)-bit buffer stores previously accessed flash memory.
Therefore, if a flash location is read, then re-programmed and read again, it can return the old data from the single-entry buffer not the new data from the flash.

Regards,

Daniel

topic e10570: FMC: Potential flash controller hang with multiple flash access errors in S32K

e10570: FMC: Potential flash controller hang with multiple flash access errors

Re: e10570: FMC: Potential flash controller hang with multiple flash access errors