This is a cache of https://discuss.96boards.org/t/build-a-ta-with-prebuild-images/5976. It is a snapshot of the page at 2024-10-23T09:28:30.354+0000.
Build a TA with prebuild images - HiKey 960 - 96Boards Forum

Build a TA with prebuild images

Products Support HiKey 960
#1

Hello !

I am using optee-OS on Hikey960 and would like to build a Trusted Application.
When building a TA, I need to specify the path to the out/ folder of optee-OS (TA_DEV_KIT_DIR). I believe it is to sign the application. However, I am using the prebuilt from:
http://github.com/96boards-hikey/tools-images-hikey960

and don’t have access to the built optee-OS and thus, cannot specify the path to build the TA.

Is there a way to compile my TA? Apart from building the BSP from source and stop using the prebuild?

Thanks.

#2

@poki Are you using prebuilt “fip.bin” image from here [1]? If yes, then you could find OP-TEE OS head commit info in that link [1] only. So you could built standalone OP-TEE OS, your TA and run it using prebuilt images.

[1] http://snapshots.linaro.org/96boards/reference-platform/components/uefi-staging/latest/hikey960/debug/

1 Like
#3

Thanks @sumit.garg I will try this!

Out of curiosity, I found out that the same key is used by default in optee-OS for signing the TA. So I could use any version of optee-OS and this should work ? (https://github.com/OP-TEE/optee_os/issues/1485)
Or is there a version control mechanism that would forbid a TA built with an old version of optee-OS to be loaded in a more recent optee-OS build? (Which would explain why I get an error while trying to open a session with my TA compiled with a different version)

#4

@poki Yes it is due to version skew issue that TA built with an old version of optee-OS fails to run with more recent optee-OS build.

1 Like