S32K142W internal eeprom access failure, run to DefaultISR

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

S32K142W internal eeprom access failure, run to DefaultISR

ソリューションへジャンプ
697件の閲覧回数
346500452
Contributor III

We use S32K142W, and SDK is 4.0.3.

We want use internal simulation eeprom, referred to example <flash_partitioning_s32k142w>.

It looks like the initialization is fine.

But when access with eeprom addr, like 0x14000001, will jump to DefaultISR.

Debug as follow picture.

eeprom fail.png

 

 

 

Attached is my project file.

 

0 件の賞賛
返信
1 解決策
645件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hi @346500452,

I see now you have the S32K142W part.

There is the FTFM module that supports 32bit aligned writes only.

danielmartynek_0-1700127202289.png

Unlike the FTFC module on other S32K14x parts:

danielmartynek_1-1700127270831.png

 

Regards,

Daniel

元の投稿で解決策を見る

0 件の賞賛
返信
4 返答(返信)
646件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hi @346500452,

I see now you have the S32K142W part.

There is the FTFM module that supports 32bit aligned writes only.

danielmartynek_0-1700127202289.png

Unlike the FTFC module on other S32K14x parts:

danielmartynek_1-1700127270831.png

 

Regards,

Daniel

0 件の賞賛
返信
675件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hi @346500452,

What kind if fault exception do you get there?

Can you implement the HardFault_Handler() and read the CSFR register?

https://community.nxp.com/t5/S32K-Knowledge-Base/Fault-handling-on-S32K14x/ta-p/1114447

 

BR, Daniel

0 件の賞賛
返信
663件の閲覧回数
346500452
Contributor III

Hi, @danielmartynek
I change address to access, like 0x14000000 or 0x14000004 or (0x1400000 + 4*n).
And it works ok.

0 件の賞賛
返信
667件の閲覧回数
346500452
Contributor III
Hi
I implement fault process function in project.
When debug it jump to BusFault_Handler, and CFSR is 0x00008200.
It means : BFAR holds a valid fault address.
S32K142W doesn't have FlexRAM ? Or initialize somewhere is wrong ?
0 件の賞賛
返信