@@ -45,6 +45,10 @@ do_install:append() {
install -m 644 ${B}/*.optee ${D}${nonarch_base_libdir}/firmware/ || true
install -m 644 ${B}/bl32.bin ${D}${nonarch_base_libdir}/firmware/ || true
install -m 644 ${B}/bl32.elf ${D}${nonarch_base_libdir}/firmware/ || true
+
+ # Install embedded TAs
+ mkdir -p ${D}${nonarch_base_libdir}/optee_armtz/
+ install -D -p -m0444 ${B}/ta/*/*.ta ${D}${nonarch_base_libdir}/optee_armtz/
}
optee_deploy_legacyhs() {
@@ -67,5 +71,7 @@ do_deploy:append:k3() {
ln -sf optee/bl32.elf ${DEPLOYDIR}/
}
+FILES:${PN} += "${nonarch_base_libdir}/optee_armtz/"
+
# This is needed for bl32.elf
INSANE_SKIP:${PN}:append:k3 = " textrel"
OP-TEE OS provides a handful of TAs itself. While these are often meant to be built-in, when they are not we should deploy them as part of the OP-TEE OS package so they can be loaded at runtime. Signed-off-by: Andrew Davis <afd@ti.com> --- meta-ti-bsp/recipes-security/optee/optee-os-ti.inc | 6 ++++++ 1 file changed, 6 insertions(+)