Fix for issue #8155 (NRF52832: time stops after 35 minutes) #8165
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.
Description
Low power Timer is used as RTC for platforms that don't have HW RTC capabilities (like NRF52832).
_rtc_lpticker_read(void)
function currently usesTimer::read()
function to trace elapsed seconds.Timer::read()
returns seconds represented asfloat
value, but this value is calculated fromint
sinceTimer::read_us()
returnsint
.This limits time tracing to ~35 min.
To fix this problem we will use
timer::read_high_resolution_us()
(which returns unsigned 64 bit value) instead ofTimer::read()
.Pull request type