NXP S32R294 QSPI Flash Memory swap.

[Wernher]

Hello Guys,

I use NXP S32R294 microcontroller with External Flash over Qspi interface.

I want to use Flash memory from another supplier.

Actually I use: Winbond (W25Q32JW) and i want to swap this chip to: ISSI (IS25WP032).

after memory swap to the ISSI(IS25WP032) i have problem with bootup procedure. 

Debugger - T32 seems works and program flash was flashed properly, but every in-target reset i got warning like: 

"Warning: Timeout while waiting for boot ROM execution finished (SOCDATA1=0x00000000)"

I only changed "Flash memory command sequence" in "QuadSPI reconfiguration data" block, to enable Quad-mode (QE=1). in winbound to set QE=1 following command sequence shall be used: "0x06;  0x31 0x2" and in ISSI for QE=1 following command sequence shall be used: 
"0x06 ; 0x01 0x40". Thats only change i made in SW. Orginal SW with windbound chip works well after in-target reset in T32 i can see  Program-Pointer (PC) set on Ram Start Pointer and it works. With ISSI chip after in-target-reset in T32 i only see this warning (SOCDATA1=0x00000000) and it not works. Could somebody help me? Why memory chip swap is so problematic here?

[amy312james]

Swapping QSPI flash chips can be tricky because even if both are 32 Mb devices, their command sets, timing, and status register layouts differ slightly. In your case, the ISSI device may require additional initialization beyond just setting QE (e.g., different dummy cycles, read command codes, or status register bits). The boot ROM on the S32R294 expects exact sequences to match the flash’s JEDEC ID and timing; if these don’t align, it won’t complete the boot process, hence the timeout. You’ll likely need to adjust the QuadSPI reconfiguration data not only for QE but also for read commands, dummy cycles, and possibly the reset/enable sequence to fully match ISSI’s datasheet.

[petervlna]

Hello,

If the BootROM doesn’t recognize the JEDEC ID or the device density bits, it will not configure QSPI and will stall, causing your exact timeout.

Your manual QuadSPI configuration block never gets executed because the BootROM already hangs before reaching it.

On S32R devices:
Boot sequence is:

1. BootROM tries to auto-configure QSPI using JEDEC ID + default assumptions
2. Only after that it loads your QuadSPI Reconfiguration Block
3. Then your application runs

If step (1) fails → nothing else happens → T32 shows:

Warning: Timeout while waiting for boot ROM execution finished
SOCDATA1=0x00000000

Best regards,

Peter