initial QSPI will be timeout on S32K344 EVB

[Jireh]

Hi Sir,

the QSPI sample code was timeout after called the "Initial Protection" as below.

please help us to check, thanks. 

can we disable this protection function?

Jireh_1-1720170317600.png

we had read this timeout issue.

https://community.nxp.com/t5/S32K/QSPI-FLASH-Init-time-out/m-p/1228072

• SDK: S32DS 3.5 (Build id: 240529 (Update 12)), SDK 4.0.0
• HW: S32K344 EVB, it was reworked all pins from ENET to QSPI.
• FW: We used the example code as below.
• Jireh_0-1720167354576.png

thanks.

Jireh

S32K3, @danielmartynek 

[Jireh]

Hi @VaneB , 

please help,

thanks~

• Trouble:
  • if I used the AutoSAR R21-11 on 344EVB, it still has the TIMEOUT ERROR.
  • But AutoSAR 4.4 was OK as above description P24, D2405.
  • we tested QSPI on S32K344 EVB and complete rework.

• SDK version:
  • AutoSAR: R21-11, P14, D2403.
  • SDK: 3.5.13
  • Jireh_0-1724289879065.png
• Test result: 
  • Status is Busy & timeout in Qspi_Ip_InitProtection()
    • Jireh_1-1724314299056.png
  • Status is Busy & timeout in Qspi_Ip_WaitCommandComplete()
    • Jireh_4-1724314498806.png
    • Jireh_0-1724314277258.png
  • Status is Busy in Qspi_Ip_CheckMemoryStatus()
    • Jireh_2-1724314330415.png
  • Status is Error in Qspi_Ip_ErrorCheck()
    • Jireh_3-1724314360773.png

[VaneB]

Hi @Jireh 

First of all, hotfix builds are not fully qualified and are not designed for production; replace them with the next qualified standard version. Please test it with the updated SW version.

Did you make any modifications to the example code? With the SW update does it have the same behavior?

BR, VaneB

[Jireh]

Hi @VaneB 

We changed the sample code to ExFls as below.

Jireh_0-1720535382835.png

but it also had the same timeout problem when initial the protection.

Jireh_1-1720535501667.png

BTW, it always Busy if get the memory status in protection initial.

and then it will be timeout after end of while loop.

why? I didn't change any config.

Jireh_2-1720535877787.png

Jireh_3-1720535915507.png

the attachment is our code.

thanks,

Jireh

[VaneB]

Hi @Jireh 

As previously mentioned the hotfix sw versions are not fully qualified, you can download the software versions RTM qualified from S32K3 Standard Software > Automotive SW - S32K3/S32M27x - Real-Time Drivers for Cortex-M.

[Jireh]

Hi @VaneB ,

thanks,

we changed to this version and used D2405 sample code, it was working.

But We have a question.

Does the generated codes (in board & generate folder) keep the same between the diff. RTD Dxxxx?

Jireh_0-1721032356906.png

Jireh_1-1721033292742.png

thanks,

Jireh

[VaneB]

Hi @Jireh 

Yes, they could be different depending on the RTD version and whether it is compliant with AUTOSAR 4.4 or AUTOSAR R21-11.