linux/meta-ti.git/meta-ti-bsp/conf/machine/j721e-hs-evm-k3r5.conf, branch master

conf: machine: Remove remaining K3 HS machines

2025-12-19T15:57:39+00:00

Every MACHINE build deploys a tiboot3.bin file for all three K3 security types (GP, HS-FS, HS-SE). These extra MACHINE configs existed to select a different default. As U-Boot now selects a default for us this logic does not need to exist here. Instead if one wants to use a non-default security type for an EVM then can simply rename the tiboot3.bin file in the boot partition. Testing automation already handles this and Sitara- family devices have dropped the dedicated MACHINE configs, do the same for Jacinto-family devices. Signed-off-by: Andrew Davis Reviewed-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

conf: machine: Do not override SPL_BINARY on AM65x and J721e

2023-06-07T15:10:22+00:00

In U-Boot the names of these files have been updated to match our expected defaults. Remove these fixups. Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon

conf: machine: Switch all the machines over to U-Boot binman

2023-06-07T15:08:55+00:00

Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon

j721e-hs-evm: Merge j721e defconfigs

2023-05-17T14:46:34+00:00

uboot will now use a merged defconfig build so keep the defconfig same for hs here Signed-off-by: Manorit Chawdhry Signed-off-by: Ryan Eatmon

conf: machine: Rework do_image_wic dependencies

2023-01-24T18:51:24+00:00

The WIC image for K3 depends on the TI-SCI firmware, on AM65x and J721e also the bootloader. Make this clear by only depending on firmware in the base k3.inc file, then adding the bootloader dependency in AM65x and J721e specific includes. Remove unneeded overrides from the evm level files. Remove do_image_tar dependencies as the tar files do not include the bootloader nor TI-SCI firmware, only the boot partition of the WIC file needs these. Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

conf: machine: Move K3 TI_SECURE_DEV_PKG definition to common include

2022-11-23T22:08:24+00:00

The K3 TI_SECURE_DEV_PKG is the same for all devices, move this out of each machine file and into the common K3 includes. This doesn't have any effect on the GP machines as they make no use of it. Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

machine: k3r5: Make combined R5 boot the default

2022-11-23T22:08:24+00:00

Going forward, the combined tiboot3.bin is going to be the standard. Only AM65x and J721e will still use the split boot. Set the output of U-Boot to be u-boot-spl.bin by default and override only for the two split boot platforms. This makes it easier to add new platforms and simplifies deployment logic. Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

j721e-hs-evm-k3r5: do not create generic sysfw.itb symlink

2022-09-22T16:23:07+00:00

Commit bdceaa05aca9d3685ebfefbe7b7b60e2fd33789f added SR1.1 support for J721e HS with the idea that the default sysfw.itb will point to SR1.1. For that to work, the config for SR1 has to explicitly disable creating such symlink. Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

meta-ti: rename j7-evm to j721e-evm

2022-03-29T12:33:57+00:00

In many places we use "j7" the family when we should be using a specific SoC or EVM and vice-versa. For instance when including graphics drivers we add for all "j7" family, but what we really want is only for some specific j7 SoC. First step in untangling this is to make it clear that there is no SoC called j7. There is a SoC called j721e with a j721e-evm. Fix up this naming here. Signed-off-by: Andrew Davis Tested-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon