[clock] Fix multicore us clock reading on RP2040 #1010
Merged
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
salkinium
force-pushed
the
fix/multicore_clock
branch
from
ea063ae to
6bc6e10
Compare
|
Can you check if this also fixes your Problem, @cocasema? |
Ran the example till |
salkinium
force-pushed
the
fix/multicore_clock
branch
from
6bc6e10 to
389a9c3
Compare
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.
When using the microsecond clock from both Core0 and Core1, the interrupt semaphore was accessed by both, which broke the overflow detection and caused jitters of up to 1ms.
This gives each core its own flag.
Add 64-bit timer as alternativetoo much effort, cannot be botheredFixes #907. cc @cocasema