Dear @edelh ,
I would like to clarify if the product you are using is the S32G-RDB3. If so, please refer to the following image for the switch setting of boot from SD card.
It is possible that the issue you are experiencing is related to incorrect switch settings. Please double-check these settings and ensure they are in accordance with the requirements for serial boot.
If the problem persists after verifying the settings, please provide more detailed information about the steps you have taken and any error messages or unusual behavior observed during the boot process. This will help us further diagnose and resolve the issue.
Best regards,
Celeste
this is the current switch configuration that I am referencing for serial boot
Dear @edelh ,
In general, the device usually boots from external flash memory, including eMMC, QSPI Flash, etc. Booting from Serial Boot mode is a configuration step before flashing the binary. By setting the S32G - RDB3 to this mode, you can use tools such as S32 Flash Tool to write the binary image to the external flash memory.
After the flashing is completed, the device will boot from the corresponding external flash memory (such as eMMC, QSPI Flash, etc.) according to the configuration, rather than from the Serial Boot mode. The Serial Boot mode is just a configuration mode during the flashing process, which supports writing the binary through the serial port. For more details, please refer to the document AN13456.
Regarding Serial Boot, you can refer to the document "AN14136 Enabling Serial Boot in S32G".
The mentioned documents are available under the "Search" of the NXP official website (link: Search | NXP Semiconductors), as shown below.
Best Regards,
Celeste
Dear @edelh ,
Thank you for your reply. As you mentioned, enabling serial boot is crucial for you. Have you referred to the document AN14136? This document provides detailed descriptions of serial boot and is highly recommended.
I have examined your screenshots. Currently, the issue I can identify is that in screenshot 1, there are 48 Bytes Reserved with "0xFF", but in your binary file, it's all "0x00". As of now, this is the only problem I can see based on your screenshots.
Once again, I recommend referring to AN14136. It contains detailed explanations on how to generate a serial boot image and how to enable it with the board. It also provides a python script to enable non-secure serial boot from UART and FlexCAN interfaces. You can open it using PDF readers like Adobe Acrobat to access the document's attachments as shown in the figure.
The attached prebuilt serial boot image - 's32g3_non_secure_serial_boot_image.bin' is an application demo that lights up the RGB LED (U128) of S32G-VNP-RDB3. You can try this demo binary to see if it works successfully on your board.
I hope the above information is helpful to you.
Best regards,
Celeste
Hey @Celeste_Liu
Probing on this more, I am loading the test image provided for the RDB3 with the S32 Flash Tool and am seeing that the reserved fields being transmitted are actually random, not 0xFF. I have logic analyzer probes hooked up to the RX pin on the RDB3 UART and am doing multiple runs.
The image successfully loads and I can see the output.
See the two images below. Both are captures after the Code Length Word field is sent. The sparse transactions are the Reserved fields and the compressed area is the actual binary, which matches a hex dump of the binary.
From this I must conclude that the Reserved fields are either random or I'm missing something, can you confirm please?
