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
HAL_Timer_Get_Milli_Seconds()
/HAL_Timer_Get_Micro_Seconds()
Eventually reset after ~1 hour of execution. This results inmillis()
rolling over to zero.Solution
It appears that the problem is due to integer promotion (in this case, demotion?) when calculating elapsed micro seconds:
Making
US_PER_OVERFLOW
a uint64_t seems to solve the problem.Steps to Test
Modify
timer_hal.cpp
init()
andstart()
functions to start theoverflowCounter_
at a value close to 65536Run the app and observe the uptime millis incrementing beyond
0004294659
Example App
tinker or any app with timestamp logging
References
Links to the Community, Docs, Other Issues, etc..
Completeness