TF-A/Hafnium v2.15.0 release updates (FVP)#862
Conversation
As per [1], mbedTLS is hosted as a TF-A project submodule and it is no longer required to provide the path to the library through MBEDTLS_DIR. [1] https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/38136 Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
Latest FVP models renamed has_branch_target_exception to bti_support_level and former is now a deprecated option. Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
odeprez
changed the title
| -C cluster0.has_generic_authentication=1 \ | ||
| -C cluster0.has_pointer_authentication=2 \ | ||
| -C cluster0.has_branch_target_exception=1 \ | ||
| -C cluster0.bti_support_level=1 \ |
There was a problem hiding this comment.
This might require bumping the model version if it exists in a CI.
There was a problem hiding this comment.
It seems the OP-TEE CI runs validation only in QEMU and the CI concern is not valid.
I think running tests on the AEM base FVP in the CI could be enabled now as it has became freely available from here. But this is out of scope for this change.
There was a problem hiding this comment.
It seems the OP-TEE CI runs validation only in QEMU and the CI concern is not valid.
Correct.
I think running tests on the AEM base FVP in the CI could be enabled now as it has became freely available from here. But this is out of scope for this change.
+1. That's interesting.
|
About measured boot: MEASURED_BOOT=y requires cmake needed to build libeventlog hosted as a TF-A submodule. It may require a docker file update if built in a CI. MEASURED_BOOT=y MEASURED_BOOT_FTPM=y breaks linux build with MEASURED_BOOT=y MEASURED_BOOT_FTPM=n crashes at boot time Command lines above assume SPMC_AT_EL=2 |
|
I observe this while booting linux [ 6.056193] optee: probing for conduit method. This happens already with upstream without this change. |
|
Does this break upstream, or is upstream already broken? |
Hi, I retried current v2.14 based integration and it already exhibits both the issues from above. I fixed MEASURED_BOOT=y MEASURED_BOOT_FTPM=n with an additional change adding a tpm event log node to the SPMC manifest. |
When SPD=spmd SPMD_SPM_AT_SEL2=1, TOS_FW_CONFIG is the S-EL2 SPMC manifest. When used along with MEASURED_BOOT=1 the event log logic within BL2 treats the SPMC manifest DTB as TOS_FW_CONFIG and tries to write measured-boot event log fields into it. That write path works if the DTB contains an arm,tpm_event_log node with the expected properties. Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
4 participants
No description provided.