S32K146 FlexRam Regional data is abnormal

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

S32K146 FlexRam Regional data is abnormal

ソリューションへジャンプ
1,275件の閲覧回数
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,252件の閲覧回数
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,253件の閲覧回数
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 件の賞賛
返信