| Message ID | 20250627060416.639661-1-anshuld@ti.com |
|---|---|
| State | Under Review |
| Delegated to: | Ryan Eatmon |
| Headers | show |
| Series | [v1,1/2] conf: machine: k3: update fitImage load address | expand |
On Fri Jun 27, 2025 at 11:34 AM IST, Anshul Dalal wrote: > In yocto, the UBOOT_ENTRYPOINT and UBOOT_*LOADADDRESS variables specify > the entry point and load addresses for the kernel image and the DTB when > creating the fitImage[1]. > > Currently the load address for the kernel is set to 0x81000000 and > 0x83000000 for the DTB for all k3 platforms. > > However the region 0x80080000 to 0x81880000 is reserved for OPTEE on > am62xxsip-evm, leading to boot failure[2] when using the fitImage. > > This patch fixes the issue by changing the addresses to 0x82000000 for > kernel and 0x88000000 for the DTB. This also allows us to load kernel > images > 32MiB in size when not using initrd while also making the > falcon and standard boot addresses consistent. > > [1]: > https://docs.yoctoproject.org/ref-manual/variables.html#term-UBOOT_ENTRYPOINT > [2]: > https://raw.githubusercontent.com/ArchUsr64/ti_boot_logs/HEAD/am62xxsip-evm/failures/fitImage_load_addr_issue.log > > Signed-off-by: Anshul Dalal <anshuld@ti.com> > --- Sorry I forgot to add prefix in the subject, this patch set is meant for scarthgap-next. Regards, Anshul
diff --git a/meta-ti-bsp/conf/machine/include/k3.inc b/meta-ti-bsp/conf/machine/include/k3.inc index 9b85f867..28785173 100644 --- a/meta-ti-bsp/conf/machine/include/k3.inc +++ b/meta-ti-bsp/conf/machine/include/k3.inc @@ -13,12 +13,12 @@ KERNEL_IMAGETYPES = "Image fitImage" KERNEL_CLASSES += "kernel-fitimage" UBOOT_ARCH = "arm" -UBOOT_ENTRYPOINT = "0x81000000" -UBOOT_LOADADDRESS = "0x81000000" +UBOOT_ENTRYPOINT = "0x82000000" +UBOOT_LOADADDRESS = "0x82000000" UBOOT_RD_LOADADDRESS = "0x84000000" UBOOT_RD_ENTRYPOINT = "0x84000000" -UBOOT_DTB_LOADADDRESS = "0x83000000" -UBOOT_DTBO_LOADADDRESS = "0x83080000" +UBOOT_DTB_LOADADDRESS = "0x88000000" +UBOOT_DTBO_LOADADDRESS = "0x88080000" UBOOT_DTBO_OFFSET = "0x00010000" SPL_BINARY = "tispl.bin" diff --git a/meta-ti-bsp/conf/machine/include/ti-falcon.inc b/meta-ti-bsp/conf/machine/include/ti-falcon.inc index 0b938470..84a62b22 100644 --- a/meta-ti-bsp/conf/machine/include/ti-falcon.inc +++ b/meta-ti-bsp/conf/machine/include/ti-falcon.inc @@ -1,6 +1,4 @@ IMAGE_INSTALL:append = " u-boot-ti-staging-falcon" KERNEL_CLASSES:remove = "kernel-fitimage" KERNEL_CLASSES += "kernel-fitimage-legacyhs" -UBOOT_DTB_LOADADDRESS = "0x88000000" -UBOOT_LOADADDRESS = "0x82000000" FIT_KERNEL_COMP_ALG = "none"
In yocto, the UBOOT_ENTRYPOINT and UBOOT_*LOADADDRESS variables specify the entry point and load addresses for the kernel image and the DTB when creating the fitImage[1]. Currently the load address for the kernel is set to 0x81000000 and 0x83000000 for the DTB for all k3 platforms. However the region 0x80080000 to 0x81880000 is reserved for OPTEE on am62xxsip-evm, leading to boot failure[2] when using the fitImage. This patch fixes the issue by changing the addresses to 0x82000000 for kernel and 0x88000000 for the DTB. This also allows us to load kernel images > 32MiB in size when not using initrd while also making the falcon and standard boot addresses consistent. [1]: https://docs.yoctoproject.org/ref-manual/variables.html#term-UBOOT_ENTRYPOINT [2]: https://raw.githubusercontent.com/ArchUsr64/ti_boot_logs/HEAD/am62xxsip-evm/failures/fitImage_load_addr_issue.log Signed-off-by: Anshul Dalal <anshuld@ti.com> --- meta-ti-bsp/conf/machine/include/k3.inc | 8 ++++---- meta-ti-bsp/conf/machine/include/ti-falcon.inc | 2 -- 2 files changed, 4 insertions(+), 6 deletions(-)