This is a cache of https://discuss.96boards.org/t/boot-analysis-of-op-tee/10599. It is a snapshot of the page at 2024-10-31T13:35:50.673+0000.
Boot analysis of OP-TEE - HiKey 960 - 96Boards Forum

Boot analysis of OP-TEE

Products Support HiKey 960
#1

Hi all,
I am doing some research in the OP-TEE security and its implementation.I have started with implementing it in hikey960,and i was able to run a hello world sample app in hikey.
On the analysis is i came across the following questions
1.Is the ATF that loads trusted OS?,If yes to which memory the trusted os is loaded?
2.By default does the REE and TEE runs in same core?If it is running in same core will there be any performance impact on the Rich OS during context switching?

#2

  1. Yes, the ATF (now known as TF-A), specifically BL2, loads the trusted OS (BL32). Each platform has a different memory layout. Dram or sram can be used. Dram seems more common. E.g. platform_def.h « include « hikey960 « hisilicon « plat - trusted-firmware-a.git - Trusted Firmware for A profile Arm CPUs.

  2. Yes. The process in the Rich OS will look like it has ben interrupted/rescheduled. For more details see Frequently Asked Questions — OP-TEE documentation documentation.

Best to ask OP-TEE related questions @ https://github.com/OP-TEE/optee_os/issues/new since the maintainers are there and can give you better answers with more details.

1 Like