-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[zephyr] Do not initialize real time clock #20505
Merged
andy31415
merged 1 commit into
sve
from
cherry-pick-8b06e80359d5276c6bf5e819e8084a01608800b3
Jul 9, 2022
Merged
[zephyr] Do not initialize real time clock #20505
andy31415
merged 1 commit into
sve
from
cherry-pick-8b06e80359d5276c6bf5e819e8084a01608800b3
Jul 9, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When there was no support for Last Known UTC Time in the common code we added a similar but incomplete solution to the Zephyr platform code that initializes the real time clock to the firmware build time. That solution is incorrect as it doesn't allow for updating the Last Known UTC Time, so we should rather return an error if no time synchronization is in place. Signed-off-by: Damian Krolik <[email protected]>
tcarmelveilleux
approved these changes
Jul 8, 2022
PR #20505: Size comparison from 46c9dae to d2072a5 Increases (3 builds for esp32, telink)
Decreases (12 builds for mbed, nrfconnect, telink)
Full report (49 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
|
andy31415
deleted the
cherry-pick-8b06e80359d5276c6bf5e819e8084a01608800b3
branch
July 9, 2022 12:36
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When there was no support for Last Known UTC Time in the common code we added a similar but incomplete solution to the Zephyr platform code that initializes the real time clock to the firmware build time.
That solution is incorrect as it doesn't allow for updating the Last Known UTC Time, so we should rather return an error if no time synchronization is in place.
Change overview
By default, do not initialize real time clock and use common Last Known UTC Time mechanism to validate operational certificates.
Testing
Verified that the commissioning passes and logs inform about using Last Known UTC Time during CASE.