configs: ti_am62{a, p}_sk_defconfig: switch to am62x platform flavor
cover configs: ti_am62{a, p}_sk_defconfig: switch to am62x platform flavor
Hello everyone!
Turns out we never defined the AM62Ax and AM62Px SA2UL base address in optee which causes a build failure. Fortunately the base address is exactly the same as with the AM62x SoCs.
Happy Hacking
~Bryan
---
Bryan Brattlof (2):
configs/ti_am62ax_sk_defconfig: switch to am62x op-tee platform flavor configs/ti_am62px_sk_defconfig: switch to am62x op-tee platform flavor
configs/ti_am62ax_sk_defconfig | 2 +- configs/ti_am62px_sk_defconfig | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
---
base-commit: 11b93ef2081316e37613902944b60e4c799e6314
change-id: 20250412-optee-fixes-c08947e2cddc
Best regards,
Signature · 6 lines
Bryan Brattlof <[email protected]> _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
PATCH 1/2 configs/ti_am62ax_sk_defconfig: switch to am62x op-tee platform flavor
There is unfortunately no SA2UL_BASE defined for the am62ax in op-tee which is causing the op-tee builds to fail however the platform is identical to the am62x platform. So for now let's switch to using the am62x which has the proper configuration for this SoC even if it's mislabeled
--- configs/ti_am62ax_sk_defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
configs/ti_am62ax_sk_defconfig +1 -1
@@ -23,7 +23,7 @@ BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="k3" BR2_TARGET_ARM_TRUSTED_FIRMWARE_TARGET_BOARD="lite" BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL32_OPTEE=y BR2_TARGET_OPTEE_OS=y -BR2_TARGET_OPTEE_OS_PLATFORM="k3-am62ax" +BR2_TARGET_OPTEE_OS_PLATFORM="k3-am62x" BR2_TARGET_TI_K3_R5_LOADER=y BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION=y BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION_VALUE="2024.07"
Signature · 6 lines
2.48.1 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Re: [Buildroot] [PATCH 1/2] configs/ti_am62ax_sk_defconfig: switch to am62x op-tee platform flavor
Hi Bryan,
Quoted 7 lines · Bryan Brattlof via buildroot
There is unfortunately no
SA2UL_BASEdefined for the am62ax in op-tee which is causing the op-tee builds to fail however the platform is identical to the am62x platform. So for now let's switch to using the am62x which has the proper configuration for this SoC even if it's mislabeledSigned-off-by Bryan Brattlof <[email protected]>
I applied this series to master, thanks.
I also added extra info in the commit log. See:
https://gitlab.com/buildroot.org/buildroot/-/commit/b1fac04a6e3d979e8dbcb436b42bbe167db96bab
https://gitlab.com/buildroot.org/buildroot/-/commit/637eead755ebb1b89aafd9345f2c6dee8412fb19
Best regards,
Julien.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
PATCH 2/2 configs/ti_am62px_sk_defconfig: switch to am62x op-tee platform flavor
In reply to Bryan Brattlof via buildrootThere is unfortunately no SA2UL_BASE defined for the am62px in op-tee which is causing the op-tee builds to fail however the platform is identical to the am62x platform. So for now let's switch to using the am62x which has the proper configuration for this SoC even if it's mislabeled
--- configs/ti_am62px_sk_defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
configs/ti_am62px_sk_defconfig +1 -1
@@ -22,7 +22,7 @@ BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="k3" BR2_TARGET_ARM_TRUSTED_FIRMWARE_TARGET_BOARD="lite" BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL32_OPTEE=y BR2_TARGET_OPTEE_OS=y -BR2_TARGET_OPTEE_OS_PLATFORM="k3-am62px" +BR2_TARGET_OPTEE_OS_PLATFORM="k3-am62x" BR2_TARGET_TI_K3_R5_LOADER=y BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION=y BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION_VALUE="2024.07"
Signature · 6 lines
2.48.1 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot