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 am testing TEE_GetSystemTime in a QEMU environment.
According to the TEE Intercore API Spec 1.3, it should be able to get the value "Filled with the number of seconds and milliseconds since midnight on January 1, 1970, UTC" when using the TEE_GetSystemTime function.
However, When I check the results of the TEE_GetSystemTime function, return the time as long as it has been since the boot.
What should I check to get the time as in the Spec?
The text was updated successfully, but these errors were encountered:
To get an effective real-time origin, you need a platform that has some RTC capabilities and that is provisioned with a reliable time origin, either from non-secure world (protection level 100) or from secure world (protection level 1000).
Thank you for your response.
I have an additional question.
Do I need RTC capabilities to maintain persistence when using TEE_SetTAPersistentTime and TEE_GetTAPersistentTime?
Indeed you would need a RTC to have persistence of TAPersistentTime. But that is not enough. Current OP-TEE does not well manages persistent time, especially the TA ones. We would need to save a time reference per TA in the persistent secure storage area (likely when TEE_SetTAPersistentTime() is called) which is currently not implemented.
Contributions are welcome.
To reach TAPersistentTime level 1000, you need the RTC to be secure.
I am testing TEE_GetSystemTime in a QEMU environment.
According to the TEE Intercore API Spec 1.3, it should be able to get the value "Filled with the number of seconds and milliseconds since midnight on January 1, 1970, UTC" when using the TEE_GetSystemTime function.
However, When I check the results of the TEE_GetSystemTime function, return the time as long as it has been since the boot.
What should I check to get the time as in the Spec?
The text was updated successfully, but these errors were encountered: