On 02/06/2022 13:43, Jens Wiklander wrote: > On Thu, Jun 2, 2022 at 9:50 AM Jerome Forissier > <jerome.foriss...@linaro.org> wrote: >> On 5/29/22 18:08, Alper Nebi Yasak wrote: >>> Why I am asking these is that I'm hypothesizing we can put the >>> unmodified 'tee.bin' (including header) and 'bl31.elf' (normally split >>> into raw binary pieces) into the FIT, and then interpret them at runtime >>> on the C side. Trying to figure out if it's a good idea. >> >> Definitely sounds doable. It could help having more common code perhaps, and >> also >> simplify the content of the FIT and therefore the verification of hash and >> signatures. >> >> [...] > > It could be worth checking how TF-A loads OP-TEE. The relevant code is > in > https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tree/lib/optee/optee_utils.c
I think I'll eventually try to implement what I mentioned above, and the linked TF-A code looks like it would help a lot, thank you both! > Cheers, > Jens
