QSPI write failed on S32K148EVB-144

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

QSPI write failed on S32K148EVB-144

324 Views
weihouyi
Contributor I

Hello NXP Comminity,

I tried to write content to the external flash (MX25L6433) while using the QSPI routine in the SDK, but when I reread the data, I found that the written data and the read back data were inconsistent, resulting in getting stuck in a dead loop.I also tried to read the device ID, and the ID returned was consistent with the one in the manual

And I also followed the hardware connection shown in the following picture.

weihouyi_0-1705307739184.png

 

Any idea what causes this error?

Development environment:

S32DS for Arm V2.2 、S32K148_SDK V3.0、S32K148EVB-144

0 Kudos
3 Replies

311 Views
VaneB
NXP TechSupport
NXP TechSupport

Hi @weihouyi 

Could you share an image of your signals to analyze their behavior? 

 

B.R.

VaneB

0 Kudos

301 Views
weihouyi
Contributor I

hello VaneB

I tried running this code using S32DS and found that the data returned and written were inconsistent. However, I was able to access the status register and configuration register of the external flash through QSPI.

I suspect there was an issue when reading and writing to the QSPI four line, as both reading and writing to external flash occur in four pin mode, and accessing external flash in one pin mode is normal.

 

The following is a picture of me using the QSPI routine in S32K148EVB

 

 

iwEcAqNwbmcDAQTRB2MF0QP7BrD0D069zkpXJAWXHysMGj4AB9IFHU6ZCAAJomltCgAL0gACl8o.png_720x720q90.jpgiwEcAqNwbmcDAQTRB00F0QOsBrB4uggOXRA3rgWXHysMGj4BB9IFHU6ZCAAJomltCgAL0gACotw.png_720x720q90.jpg

0 Kudos

268 Views
VaneB
NXP TechSupport
NXP TechSupport

Hi @weihouyi 

If possible, could you please share the images with more resolution?

0 Kudos