S32KのトピックRe: initial QSPI will be timeout on S32K314 EVB (used NXP example code: AutoSAR R21-11, D2403)

initial QSPI will be timeout on S32K314 EVB (used NXP example code: AutoSAR R21-11, D2403)

Jireh — Fri, 30 Aug 2024 07:02:55 GMT

Hi @VaneB,

please help us, thanks.

the QSPI example code will be timeout after called the "Initial Protection".

Trouble:
- if we used the AutoSAR R21-11 on S32K344 & S32K314 EVB, it still has the TIMEOUT ERROR.
- But AutoSAR 4.4 was OK at version P24, D2405.
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()
- RBDR reg. = 0xc1c1, it will let the status Busy.

thanks.

Jireh

Re: initial QSPI will be timeout on S32K314 EVB (used NXP example code: AutoSAR R21-11, D2403)

VaneB — Tue, 03 Sep 2024 16:56:13 GMT

Hi @Jireh

As we already know, the EVB incorporates a MX25L6433F, which is connected to the QSPI-A Module of the S32K344. If we refer to the schematic of the board we can see that most of the pins are not connected (the resistors are DNP), so hardware changes are required. I want to confirm if you placed the required resistors?

BR, VaneB

Re: initial QSPI will be timeout on S32K314 EVB (used NXP example code: AutoSAR R21-11, D2403)

Jireh — Wed, 04 Sep 2024 01:09:20 GMT

Hi @VaneB

we had reworked the EVB, so it was not a question.

and we can run the erase, write, and read functions on EVB used the AutoSar 4.4, D2405.

please help us to check why AutoSar R21-11 can't initial,

thanks.

Jireh

Re: initial QSPI will be timeout on S32K314 EVB (used NXP example code: AutoSAR R21-11, D2403)

VaneB — Wed, 04 Sep 2024 22:30:31 GMT

Hi @Jireh

I have tested both examples from my side and also the RTD 3.0.0 P07 ones. As you mentioned, the AUTOSAR R21-11 examples always return TIMEOUT.

Let me verify this situation internally. In the meantime I suggest you to use the AUTOSAR 4.4 examples as they work as expected.

Re: initial QSPI will be timeout on S32K314 EVB (used NXP example code: AutoSAR R21-11, D2403)

Jireh — Mon, 09 Sep 2024 09:31:57 GMT

Hi @VaneB

thanks,

did you have any updated?

Jireh

Re: initial QSPI will be timeout on S32K314 EVB (used NXP example code: AutoSAR R21-11, D2403)

VaneB — Fri, 20 Sep 2024 21:18:49 GMT

Hi @Jireh

Sorry for the delay. I was waiting for the response from the internal team.

Please test the following methods:

Do not read AHB during erase and write
Increase the waiting time according to the chapter "ERASE AND PROGRAMMING PERFORMANCE" in the datasheet of the external flash
Check clock for QSPI

Re: initial QSPI will be timeout on S32K314 EVB (used NXP example code: AutoSAR R21-11, D2403)

Jireh — Tue, 10 Sep 2024 08:07:31 GMT

Hi @VaneB,

I was disable the AHB.

and attachment the S32K314 sample code that is modified from S32K344.

thanks,

Jireh

Re: initial QSPI will be timeout on S32K314 EVB (used NXP example code: AutoSAR R21-11, D2403)

Jireh — Tue, 10 Sep 2024 08:20:12 GMT

Hi @VaneB

We can work on AutoSAR 4.4 D2405 such as sector erase, page program, and 4Read.

thanks,

Jireh

Re: initial QSPI will be timeout on S32K314 EVB (used NXP example code: AutoSAR R21-11, D2403)

Jireh — Thu, 19 Sep 2024 08:18:32 GMT

Hi @VaneB ,

Do you have any updates?

thanks.

Re: initial QSPI will be timeout on S32K314 EVB (used NXP example code: AutoSAR R21-11, D2403)

VaneB — Mon, 23 Sep 2024 22:29:33 GMT

Hi @Jireh

Sorry for the delay, due to the workload this situation will take longer than expected, I will be back as soon as possible. The recommendation for now is to continue using the AUTOSAR 4.4 examples since they work as expected.