Thanks for all the details, this is helpful.
Just to keep you posted, I get to boot TF-A/Hafnium/OP-TEE/linux down to console with ffa and optee drivers initializing properly. For now my attempts with xtest fail early for some reason (perhaps an issue with userspace), so I'm not (yet) facing the same issue with cache maintenance as you reported. I'll let know later when I'm there.
Meanwhile, I noted a number of fixes I had to do, and I wonder if you did the same e.g.: 1/ create an OP-TEE partition manifest with appropriate load address/entry point, declare the qemu secure uart address. I notice the UART console may trigger secure interrupts so that might require declaring as well in the manifest. 2/ In OP-TEE strip out any GIC related initialization as a SP doesn't have direct access to the physical GIC. 3/ enabled managed exit to handle the case where a NS interrupt triggers while OP-TEE/or TA runs.
For TF-A (BL1/BL2/BL31) do you actually use your own changes, or the earlier experimental changes of mine?
________________________________ From: shiju.jose--- via Hafnium email@example.com Sent: 27 October 2022 16:47 To: firstname.lastname@example.org email@example.com Subject: [Hafnium] Re: Trapped access to system register and excpetion
I tested with the op-tee build generated rootfs, however this issue (Trapped access to system register and exception) still exists.
Thanks, Shiju -- Hafnium mailing list -- firstname.lastname@example.org To unsubscribe send an email to email@example.com