S32K142W internal eeprom access failure, run to DefaultISR

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S32K142W internal eeprom access failure, run to DefaultISR

Jump to solution
654 Views
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 Kudos
1 Solution
602 Views
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

View solution in original post

0 Kudos
4 Replies
603 Views
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 Kudos
632 Views
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 Kudos
620 Views
346500452
Contributor III

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

0 Kudos
624 Views
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 Kudos