TDA4VM: Tiboot3 source code path on Linux-SDK

Hi,

Yes, the code must be inside ti-u-boot-2024.04+git but I can´t find it yet. To give you more context, tiboot3 somewhere must have the address to start loading tispl.bin file, which is 0x80000, but the only definition with that value is related to a config file and a tispl.bin related source code. So my suspect is that the address where tispl is loaded by tiboot3 is defined differently without specifying the exact address value, maybe by performing some calculations with offsets and other addreses. Do you know where it can be?

Thanks in advance for your help.

Mac Alfred Pinnock-Chacon said:

which is 0x80000, but the only definition with that value is related to a config file and a tispl.bin related source code. So my suspect is that the address where tispl is loaded by tiboot3 is defined differently without specifying the exact address value, maybe by performing some calculations with offsets and other addreses. Do you know where it can be?

Are you checking about the OSPI flash address?

https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-jacinto7/10_01_00_04/exports/docs/linux/Foundational_Components/U-Boot/UG-QSPI.html

CONFIG_SYS_SPI_U_BOOT_OFFS=0x80000

in configs/j721e_evm_r5_defconfig.

This is the tispl.bin aka A72 SPL that gets loaded by R5 SPL.

Post this u-boot.img is loaded by A72 SPL at the below address:

CONFIG_SYS_SPI_U_BOOT_OFFS=0x280000

in configs/j721e_evm_a72_defconfig

- Keerthy

So, spl_spi.c is responsible for loading both images, but it determines which CONFIG definition to use based on the boot stage. For instance, during the first execution, spl_spi.c refers to CONFIG_SYS_SPI_U_BOOT_OFFS from j721e_evm_r5_defconfig. Later, when tispl runs and loads uboot.img, it executes spl_spi.c again, this time using CONFIG_SYS_SPI_U_BOOT_OFFS from j721e_evm_a72_defconfig. Is that correct?

That's correct. R5 SPL loads the tispl.bin and A72 SPL loads the U-Boot.img

Best Regards,

Keerthy