Hello,
I am using a custom configuration of a board based on the S32G3 RDB3 board as reference with the BSP43. The build runs through but while flashing with the fip.bin-qspi & flashimage.bin file, the bootloader hangs after executing BL2. It is not going into the BL31 function. (See screenshot below).
I have applied a patch to debug. As per the log on the UART console, the entry point address for BL31 is set to 0xFF600000.
As per the BSP43 UM, the base address for the BL31 is mentioned as 0xFF800000.
Could you also share the details of the BL31 & BL33 sizes so that we know if we need to translate addresses.
Require support for debugging this issue.
Hello, @y2jsh
Thanks for your post.
May I know the bootloader version you used? I assume that the board booted from QSPI, may I know where you put the fip.bin? on QSPI or SD?
BR
Chenyin
BR
Chenyin
Hello, @y2jsh
Thanks for your reply.
1. The example bootloader is usually from the GoldVIP package or Integration_Reference_Examples package, may I know where you derived the bootloader from? from which version of the GoldVIP(or Integration_Reference_Examples)?
2. Commonly, when using BSP42 or earlier, the fip.bin would be flashed to the QSPI, but since BSP43, the boot image for A53 side is split into 2 images, then you may need to flash the bl2_w_dtb.bin to the QSPI instead of fip.bin.
BR
Chenyin
Hello, @y2jsh
Thanks for your reply.
I could understand that you boot the board solely via QSPI using BSP43.
By default with BSP43, once finished the Yocto building, there would be several images generated.
1. If you are willing to directly flashing the fsl-image-flash-s32g399ardb3.flashimage, then it includes all images that used to boot from QSPI, you may not need to flash other images that generated.(like fip.bin-qspi mentioned)
2. If you are willing to only flashing the Bootloader part(TFA and uboot), then you may flash the following two images step by step as follows: Chapter 4.2.5 of BSP43UM for S32G3
BR
Chenyin
Hello, @y2jsh
Sorry for the delay due PTO.
1. May I know if you have found the image that generated from Yocto which named fsl-image-flash-s32g399ardb3.flashimage?(or similar name since you used custom board, not sure how you had modified the Yocto source/configuration), it could usually generated via the command bitbake fsl-image-flash.
2. Only flashing the fsl-image-flash-s32g399ardb3.flashimage to your QSPI, and then set your board to boot from QSPI, to check if could boot correctly, kindly share the log if still issues.
Thanks.
BR
Chenyin
Hello, @y2jsh
Thanks for your reply.
I'd like to share with the application I had tested from my side, since it is too big to share in the community, let me send it via mail.
BR
Chenyin
Hello, @y2jsh
You are welcome.
Commonly it is not needed, I will continue supporting your issue via the support system.
BR
Chenyin