Hello,
I’m currently testing the Qspi_Ip_Example_S32K344 on the MRCANHUBK344 developer board. The example project uses an MX25L6433FM2R-08G flash device, whereas the CANHUB board is equipped with an MX25L6433FM2I-08G. I believe there isn’t any major difference in configuration between these two flash models, and the QSPI pin definitions in the example also seem to match the MRCANHUBK344 QSPI interface.
However, I’m running into an issue where Qspi_Ip_Init returns STATUS_QSPI_IP_BUSY. Everything appears normal until Qspi_Ip_InitProtection is called inside Qspi_Ip_Init, at which point Qspi_Ip_WaitCommandComplete also returns STATUS_QSPI_IP_BUSY (as shown in the attached image).
I’ve come across a similar issue in this forum post: initial QSPI will be timeout on S32K344 EVB
I’m using S32 Design Studio 3.6 and RTD R21-11 Version 5.0.0. Could anyone advise me on the steps to resolve or further diagnose this issue?
Thank you in advance for your help
Hi,
I tried the configurations you mentioned and successfully ran the example. Thank you.
Hi,
I was able to pass init and run code when lowering QSPI_SFCK
Also slowing down signal edges helps with example default SFCK (80MHz)
Most probably there is some issue with HW design or similar.
BR, Petr
Hi,
devices are the same, there is just temp range difference.
Pins setting looks correct and matches with schematic, as you wrote. You can check in debugger if respective SIUL registers are written that way.
Let me check this RTD demo in MRCANHUBK344 as well.
BR, Petr