S32K146 FlexRam Regional data is abnormal

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

S32K146 FlexRam Regional data is abnormal

跳至解决方案
1,270 次查看
Louis1916
Contributor III

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!

标记 (1)
0 项奖励
回复
1 解答
1,247 次查看
Senlent
NXP TechSupport
NXP TechSupport

 

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

 

Senlent_1-1736406941652.png

 

在原帖中查看解决方案

0 项奖励
回复
1 回复
1,248 次查看
Senlent
NXP TechSupport
NXP TechSupport

 

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

 

Senlent_1-1736406941652.png

 

0 项奖励
回复