S32G3 RDB3 boot from QSPI issue

[XD]

Hi,

I am using bsp41 to generate QSPI images (fip.s32-qspi and fsl-image-flash-s32g399ardb3.flashimage). However, none of them are able to boot after I used S32flashtool to flash them into QSPI via UART. The command I used is:

S32G3xxx.bin -a MX25UW51245G.bin -fwrite -f fip.s32-qspi -addr 0

I am confused about the RDB3 dip switch settings. I followed the bsp41 user manual (section 4.3.3), changing SW4[3:4] and SW7[6], but it seems that the ON position is opposite from what I expected (top-side down). Another document mentioned setting all switches SW4-7 to OFF, but neither approach has resulted in a successful boot from QSPI. Can you clarify the correct dip switch settings or suggest other possible solutions?

Thanks,

XD

[chenyin_h · Accepted solution]

Hello, @XD 

Thanks for the post.

I have tested it from my side with pre-built images for QSPI boot, it seems working correct, below please find the switch settings for your reference.

BR

Chenyin

[XD]

Hi Chenyin,

Please disregard this issue. It turns out that the S32flashtool has a problem on Linux. While it works well for eMMC flashing, it doesn't seem to function properly with QSPI flashing. I have already matched the flash parameters to those used in the Windows version, and the same file successfully booted when flashed using the Windows tool. Thank you for your support.

Thanks,

XD

[XD]

Hi Chenyin,

Thank you for the dip switch setting.

I tried using the bsp41 pre-built fip.s32-qspi image, and you are correct—it successfully boots. However, the fip.s32-qspi image generated from the fsl-image-auto build(bsp41) does not boot. Do you know if I should be using a different command to generate the correct fip.s32-qspi QSPI image?

Thanks,

XD