S32KのトピックRe: initial QSPI will be timeout on S32K344 EVB

initial QSPI will be timeout on S32K344 EVB

Jireh — Fri, 05 Jul 2024 09:54:37 GMT

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?

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.

thanks.

Jireh

, @danielmartynek

Re: initial QSPI will be timeout on S32K344 EVB

VaneB — Fri, 05 Jul 2024 20:42:32 GMT

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

Re: initial QSPI will be timeout on S32K344 EVB

Jireh — Tue, 09 Jul 2024 14:40:53 GMT

Hi @VaneB

We changed the sample code to ExFls as below.

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

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.

the attachment is our code.

thanks,

Jireh

Re: initial QSPI will be timeout on S32K344 EVB

VaneB — Thu, 11 Jul 2024 18:01:09 GMT

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.

Re: initial QSPI will be timeout on S32K344 EVB

Jireh — Mon, 15 Jul 2024 08:58:01 GMT

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?

thanks,

Jireh

Re: initial QSPI will be timeout on S32K344 EVB

VaneB — Mon, 15 Jul 2024 23:05:27 GMT

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.

Re: initial QSPI will be timeout on S32K344 EVB

Jireh — Thu, 22 Aug 2024 08:17:55 GMT

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
Test result:
- Status is Busy & timeout in Qspi_Ip_InitProtection()
- Status is Busy & timeout in Qspi_Ip_WaitCommandComplete()
- Status is Busy in Qspi_Ip_CheckMemoryStatus()
- Status is Error in Qspi_Ip_ErrorCheck()