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

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

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

2,712 Views
Jireh
Contributor III

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
    • Jireh_0-1724998808240.png

       

  • Test result
    • Status is Busy & timeout in Qspi_Ip_InitProtection()
    • Jireh_1-1724998859325.png
    • Status is Busy & timeout in Qspi_Ip_WaitCommandComplete()
    • Jireh_2-1724998885984.pngJireh_3-1724998898322.png

       

    • Status is Busy in Qspi_Ip_CheckMemoryStatus()
    • Jireh_4-1724998951350.png

       

    • RBDR reg. = 0xc1c1, it will let the status Busy.
    • Jireh_6-1725000259526.pngJireh_7-1725001279885.png

       

thanks.

Jireh

0 Kudos
Reply
9 Replies

2,441 Views
Jireh
Contributor III

Hi @VaneB ,

Do you have any updates?

thanks.

0 Kudos
Reply

2,371 Views
VaneB
NXP TechSupport
NXP TechSupport

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.

0 Kudos
Reply

2,569 Views
Jireh
Contributor III

Hi @VaneB 

 

thanks,

did you have any updated?

 

Jireh

 

0 Kudos
Reply

2,557 Views
VaneB
NXP TechSupport
NXP TechSupport

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 

2,539 Views
Jireh
Contributor III

Hi @VaneB,

I was disable the AHB.

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

Jireh_1-1725955477189.png

thanks,

Jireh

0 Kudos
Reply

2,662 Views
VaneB
NXP TechSupport
NXP TechSupport

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

0 Kudos
Reply

2,537 Views
Jireh
Contributor III

Hi @VaneB 

Jireh_1-1725956109854.png

Jireh_0-1725956065235.png

Jireh_2-1725956160444.png

Jireh_3-1725956199995.png

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

 

thanks,

Jireh

0 Kudos
Reply

2,652 Views
Jireh
Contributor III

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

0 Kudos
Reply

2,633 Views
VaneB
NXP TechSupport
NXP TechSupport

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.