upgrade arm-trusted-firmare to v2.7 Signed-off-by: Praneeth Bajjuri <praneeth@...> Tested-by: Judith Mendez <jm@...> --- *Changes from v1: removed linux-fw recipe update, that was a mistake. recipes-b

upgrade arm-trusted-firmare to v2.7 Signed-off-by: Praneeth Bajjuri <praneeth@...> Tested-by: Judith Mendez <jm@...> --- recipes-bsp/ti-linux-fw/ti-linux-fw.inc | 2 +- recipes-bsp/trusted-firmware-a/t

The HS-SE AM64xx machine can now be run on GP devices and built without needing the TI_SECURE_DEV_PKG for the same. AM64xx will only be available in the HS-FS type going forward. Make the HS-SE the de

If we do not have TI_SECURE_DEV_PKG set then SYSFW generation will fail if we are building for the HS platform. When TI_SECURE_DEV_PKG is not set we assume the builder is only interested in the GP boa

This machine was missed when making combined R5 boot the default. Add this machine to fix build failure. Reported-by: Ryan Eatmon <reatmon@...> Signed-off-by: Andrew Davis <afd@...> --- recipes-bsp/ti

FIT Image based kernels are valid for all K3 devices, not just HS, deploy this kernel image type by default so it doesn't have to be appended on a per-device-type basis. Signed-off-by: Andrew Davis <a

Use multiconfig to generate a GP SYSFW image. This allows the HS SDK to be used on GP boards by simply switching out the SYSFW image: $ cd /mnt/sd-card/boot $ mv tiboot3-am64x-gp-evm.bin tiboot3.bin S

Update to the latest commit of ti-u-boot-2021.01. As part of this U-Boot update the non-HS AM64x-evm defconfig was removed. This is okay as building this defconfig without defining TI_SECURE_DEV_PKG w

This recipe deploys the raw SYSFW unconditionally which causes issues when doing multiconfig builds. What should happen is only one deploys these, select that the same way we select which one deploys

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. Sig

Add SYSFW_TIBOOT3_SYMLINK and use it the same way we use SYSFW_SYMLINK for the non-combined boot flow, to allow not setting the default for some machine types. Signed-off-by: Andrew Davis <afd@...> --

We already cd into DEPLOYDIR so this is not needed. This now matches the keystone version below. Also fixes build in some odd situations. Signed-off-by: Andrew Davis <afd@...> --- recipes-bsp/u-boot/u

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

Going forward, the combined tiboot3.bin is going to be the standard. Only AM65x and J721e will still use the split boot. Set DEPENDS and EXTRA_OEMAKE for combined boot and override only for the two sp

This makes sense but looks like was done wrong to match AM65xx which needed the exact EVM specified due to this only working on SR2. Signed-off-by: Andrew Davis <afd@...> --- recipes-bsp/prueth-fw/pru

Signed-off-by: Andrew Davis <afd@...> --- .../trusted-firmware-a_%.bbappend | 38 ++++++++----------- 1 file changed, 16 insertions(+), 22 deletions(-) diff --git a/recipes-bsp/trusted-firmware-a/trust

Signed-off-by: Andrew Davis <afd@...> --- recipes-security/optee/optee-os_%.bbappend | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/recipes-security/optee/optee-os_%.bbappend

Update linux, linux rt and ti-linux-fw to 08.04.01.001 tag Ryan Eatmon (3): linux-ti-staging: Bump to 08.04.01.001 release linux-ti-staging-rt: Bump to 08.04.01.001 release ti-linux-fw: Bump to 08.04.

Updated the linux version for 08.04.01.001 Signed-off-by: Ryan Eatmon <reatmon@...> --- recipes-kernel/linux/linux-ti-staging_5.10.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/

Updated the ti-linux-fw version for 08.04.01.001 Signed-off-by: Ryan Eatmon <reatmon@...> --- recipes-bsp/ti-linux-fw/ti-linux-fw.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/