I am building the goldvip image for s32g via below command:
bitbake fsl-image-goldvip and figured out the image will be created as below:
dd if=/dev/zero of=/home/junha/work/s32g_bsp/nxp-yocto-goldvip/build_s32g274ardb2goldvip/tmp/work/s32g274ardb2-fsl-linux/fsl-image-goldvip/1.0-r0/deploy-fsl-image-goldvip-image-complete/fsl-image-goldvip-s32g274ardb2-20240327010305.rootfs.sdcard bs=1 count=0 seek=4538236928
dd if=/home/junha/work/s32g_bsp/nxp-yocto-goldvip/build_s32g274ardb2goldvip/tmp/deploy/images/s32g274ardb2/fip.s32-sdcard of=/home/junha/work/s32g_bsp/nxp-yocto-goldvip/build_s32g274ardb2goldvip/tmp/work/s32g274ardb2-fsl-linux/fsl-image-goldvip/1.0-r0/deploy-fsl-image-goldvip-image-complete/fsl-image-goldvip-s32g274ardb2-20240327010305.rootfs.sdcard conv=notrunc bs=512 seek=1 skip=1
dd if=/home/junha/work/s32g_bsp/nxp-yocto-goldvip/build_s32g274ardb2goldvip/tmp/deploy/images/s32g274ardb2/u-boot-flashenv-sd-s32g274ardb2.bin of=/home/junha/work/s32g_bsp/nxp-yocto-goldvip/build_s32g274ardb2goldvip/tmp/work/s32g274ardb2-fsl-linux/fsl-image-goldvip/1.0-r0/deploy-fsl-image-goldvip-image-complete/fsl-image-goldvip-s32g274ardb2-20240327010305.rootfs.sdcard conv=notrunc seek=1966080 bs=1
dd if=/home/junha/work/s32g_bsp/nxp-yocto-goldvip/build_s32g274ardb2goldvip/tmp/work/s32g274ardb2-fsl-linux/fsl-image-goldvip/1.0-r0/boot.img of=/home/junha/work/s32g_bsp/nxp-yocto-goldvip/build_s32g274ardb2goldvip/tmp/work/s32g274ardb2-fsl-linux/fsl-image-goldvip/1.0-r0/deploy-fsl-image-goldvip-image-complete/fsl-image-goldvip-s32g274ardb2-20240327010305.rootfs.sdcard conv=notrunc,fsync seek=1 bs=4194304
dd if=/home/junha/work/s32g_bsp/nxp-yocto-goldvip/build_s32g274ardb2goldvip/tmp/work/s32g274ardb2-fsl-linux/fsl-image-goldvip/1.0-r0/deploy-fsl-image-goldvip-image-complete/fsl-image-goldvip-s32g274ardb2-20240327002837.rootfs.ext4 of=/home/junha/work/s32g_bsp/nxp-yocto-goldvip/build_s32g274ardb2goldvip/tmp/work/s32g274ardb2-fsl-linux/fsl-image-goldvip/1.0-r0/deploy-fsl-image-goldvip-image-complete/fsl-image-goldvip-s32g274ardb2-20240327010305.rootfs.sdcard conv=notrunc,fsync seek=1 bs=71303168
dd if=/home/junha/work/s32g_bsp/nxp-yocto-goldvip/build_s32g274ardb2goldvip/tmp/deploy/images/s32g274ardb2/fsl-image-goldvip-domu-s32g274ardb2.ext4 of=/home/junha/work/s32g_bsp/nxp-yocto-goldvip/build_s32g274ardb2goldvip/tmp/work/s32g274ardb2-fsl-linux/fsl-image-goldvip/1.0-r0/deploy-fsl-image-goldvip-image-complete/fsl-image-goldvip-s32g274ardb2-20240327010305.rootfs.sdcard conv=notrunc,fsync seek=1 bs=2759852032
I am wondering where the u-boot image for A core is located? I am trying to replace it with a binary I built separately. Thanks
Hi, Debing
the u-boot binary file has the flag "AB8", you can search it in your SD image binary file, to find the u-boot location.
For example the u-boot at SD image offset 0xcb040.
U-boot bin file header:
By the way, simple replace u-boot.bin may not work, because the ATF compile will calculated the u-boot binary file length, if your compiled u-boot-nodtb.bin file is bigger than original one, the ATF still load the length with original u-boot.bin file, then u-boot may boot up failed.
You may compile the whole fip.s32 with your compiled u-boot, program to SD card (by pass page 0~7, which is SD card partition table) from 8th page. Of course, you need remove the first 0x1000 byte from fip.s32 image file manually.