The customer's engineer feedback received 2pcs fault board from the market side,After preliminary analysis, it is believed that the data in the FlexRam region is abnormal.
1.Engineers want to know what could cause damage to the FlexRam area? Why Can a Read Operation Be Executed Smoothly but a Write Operation Is Abnormal?
2.Why does a write operation to a FlexRam zone affect the data in a FlexNVM zone?
Thanks!
Solved! Go to Solution.
Hi@Louis1916
Sorry for the later reply.
From the perspective of the EEPROMDE mechanism, reading the internal EEPROM will not access the FlexNVM area, but directly access the FlexRam area.
The write operation is different. When you write FlexRam, it needs to synchronize the FlexRam value to FlexNVM for backup. We need to wait for the backup to complete before writing the new value, otherwise it may cause hardfault.
The above are the differences between the two operations
Regarding the RDCOLERR error, you can refer to the following section of the application note AN11983
Hi@Louis1916
Sorry for the later reply.
From the perspective of the EEPROMDE mechanism, reading the internal EEPROM will not access the FlexNVM area, but directly access the FlexRam area.
The write operation is different. When you write FlexRam, it needs to synchronize the FlexRam value to FlexNVM for backup. We need to wait for the backup to complete before writing the new value, otherwise it may cause hardfault.
The above are the differences between the two operations
Regarding the RDCOLERR error, you can refer to the following section of the application note AN11983