linux/meta-ti.git/meta-ti-bsp/conf/machine/include/k3.inc, branch 12.00.00.05

conf: Change weak assignment of IMAGE_BOOT_FILES

2026-02-17T22:05:14+00:00

Rather than using ?= to default the value of IMAGE_BOOT_FILES, instead use += to add the files we want to the probably empty value. We ran into an issue where the recent ti-core-initramfs changes used += and overrode the ?= in k3.inc, resulting in no boot files being packaged in the wic boot partition. This addresses the issue by ensuring that we never have a situation where the required files are not in the final list. Signed-off-by: Ryan Eatmon

k3: Move from UBOOT_SIGN_ENABLE to KERNEL_FITIMAGE_SIGN_ENABLE

2025-10-28T16:48:43+00:00

A recent change in oe-core [1] allowed for signing the fitImage without signing the uboot files. Since we use binman to sign all of the uboot files, we do not want oe-core to re-sign themm, but we do want the fitImage signed. [1] https://git.openembedded.org/openembedded-core/commit/?id=313ff06fdfec36a09328dbd60471bd53127fabe3 Signed-off-by: Ryan Eatmon

meta-ti-bsp: Add all tiboot3.bin and sysfw.itb variants by wildcard

2025-08-19T14:00:28+00:00

U-Boot generates all the valid versions of tiboot3.bin and sysfw.itb based on the given defconfig. The defaults are also picked based on the board's binman files. No need to duplicate this logic here, simply deploy what U-Boot generates. Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon

ti-pka-fw: Add a recipe to package prebuilt PKA firmware

2025-08-06T12:22:50+00:00

Add a recipe to install the PKA firmware in root filesystem needed by sa2_ul driver for PKA operations across all K3 platforms. Signed-off-by: Beleswar Padhi Signed-off-by: Ryan Eatmon

wic: sdimage-2part-efi: Add variable for adding bootloader options

2025-07-25T20:45:19+00:00

We have a need for some platforms to add kernel options to the bootloader during wic creation time. Create a new variable and add that to the sdimage-2part-efi.wks.in file so that a machine can override it if needed. Add an override for am64 to point the kernel at console=ttyS2. Signed-off-by: Ryan Eatmon

Revert "conf: machine: k3: disable all fit signing for uboot"

2025-07-16T19:15:14+00:00

FIT signing was disabled in the past as it was interfering with multi DTB usecase in binman, and it was thought that the binman signing being done is equivalent to UBOOT_SIGN_ENABLE. Though looking at the sources, UBOOT_SIGN_ENABLE is actually used to sign the kernel FIT Image instead and the name UBOOT actually specifies that it's used in tandom with U-boot. During the signing process, mkimage from U-boot is used to pack the kernel FIT Image and along with that, one DTB from U-boot is also passed to the mkimage command. The DTB that gets passed gets the key embedded in it that is used to verify the kernel FIT image at runtime. Now this signed DTB is packed in U-boot by triggering a rebuild with EXT_DTB argument in the U-boot build process. However, this failed as there was a U-boot bug which was not looking at the packed sources properly with the multi DTB usecase. Now that a U-boot fix is available [0], revert that commit which disabled the FIT signing. This reverts commit 9656b79cb557a46d2611b67e7e51702f6da05594. [0]: https://lore.kernel.org/all/20250626-b4-upstream-fix-icssg-fit-v1-1-95eff1c853a4@ti.com/ Signed-off-by: Manorit Chawdhry Signed-off-by: Ryan Eatmon

meta-ti-bsp, meta-beagle: switch to the new FIT image wrapper

2025-07-12T15:15:31+00:00

Switch all kernel recipes and K3 based platforms to use the new FIT image wrapper functionality. Update FIT default DTB entry to not contain vendor dubdir, as it is now handled through a conf prefix. Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

conf: machine: move UBOOT_*ADDRESS to top level ti-soc

2025-06-27T15:05:00+00:00

Since all k3 and legacy platforms share common load addresses for kernel and initrd in the fitImage, move them to top level ti-soc.inc. No functional change is intended from this patch. Signed-off-by: Anshul Dalal Signed-off-by: Ryan Eatmon

conf: machine: k3: update fitImage load address

2025-06-27T15:02:14+00:00

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 Signed-off-by: Ryan Eatmon

linux: Temporarily backport previous fitimage classes

2025-06-10T12:44:55+00:00

A recent set of changes on oe-core has dramatically revamped the fitimage generation code. It is initially unclear how to fold those change into our flow, so in the short term we will copy the previous versions of the kernel bbclass files from a commit before [1] any changes to the class files. As soon as we figure it out, these files will be removed. This just help unblock anyone trying to build on master including meta-ti-bsp. [1] https://git.openembedded.org/openembedded-core/commit/?id=fdb0a51598156f99aa91f7495d7eada92a459e97 Signed-off-by: Ryan Eatmon