You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to setup measured boot on rk3399 but without much success, I expect TF-A to generate event log when MEASUERD_BOOT is enabled, but this does not happen. I suspect this is due to problems with memory mapping between the secure world and the non-secure world:
I/TC: No non-secure external DT
E/TC:0 0 get_tpm_phys_params:84 TPM: No DTB found
D/TC:0 0 tpm_map_log_area:141 TPM Event log PA: 0
D/TC:0 0 tpm_map_log_area:142 TPM Event log size: 0 Bytes
E/TC:0 0 tpm_map_log_area:149 TPM: Failed to map TPM log memory
Looking at get_tpm_phys_params it seems like the non-secure memory address and size for storing TPM Event Log is obtained from the arm,tpm_event_log node in the DTB, but I'm not sure:
How do I find the address I can use for storing TPM log?
Should I include the DTB via CFG_DT for OP-TEE? or there is a better approach?
This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time.
How do I find the address I can use for storing TPM log?
I guess TF-A already is using an address. Perhaps you can find it in some define or config variable?
Should I include the DTB via CFG_DT for OP-TEE? or there is a better approach?
That depends on how TF-A is configured on your platform. If it's configured to pass a DTB to OP-TEE then it should be quite easy to just update the DTB and let OP-TEE take the address from there. If not, then setting it in CFG_TPM_LOG_BASE_ADDR might be an option.
This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time.
I'm trying to setup measured boot on rk3399 but without much success, I expect TF-A to generate event log when MEASUERD_BOOT is enabled, but this does not happen. I suspect this is due to problems with memory mapping between the secure world and the non-secure world:
Looking at
get_tpm_phys_params
it seems like the non-secure memory address and size for storing TPM Event Log is obtained from thearm,tpm_event_log
node in the DTB, but I'm not sure:CFG_DT
for OP-TEE? or there is a better approach?Make env and flags: (full Makefile: https://github.com/ZhanYF/veritymobile/blob/dev-wip/Makefile)
TF-A:
fTPM:
optee with fTPM as early TA:
Version info:
Mainline U-Boot SPL 2023.10
BL31: v2.9(release):v2.9.0-788-ga1377a89a
OP-TEE version: 3.22.0-233-g69a443d05-dev (gcc version 12.2.0 (Debian 12.2.0-14)) #1 Fri Feb 9 12:36:07 UTC 2024 aarch64
ftpm: https://github.com/ZhanYF/MSRSec/commits/master/
Full log:
The text was updated successfully, but these errors were encountered: