Remove tickless assert for tick count #5942
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
Remove the assert that the tick count of the OS matches the tick count of the tickless timer as this occurs frequently when debugging. This is because the function svcRtxKernelResume only increments the OS's tick count until the next wakeup event so if the device was halted by a debugger past the next wakeup event the tick counts will be out of sync.
|
/morph build |
Closed
Build : SUCCESSBuild number : 963 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 648 |
Test : SUCCESSBuild number : 790 |
0xc0170
approved these changes
Jan 26, 2018
AGlass0fMilk
added a commit
to HeadsUpDisplayInc/mbed
that referenced
this pull request
Feb 20, 2018
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.
Remove the assert that the tick count of the OS matches the tick count of the tickless timer as this occurs frequently when debugging. This is because the function svcRtxKernelResumeonly increments the OS's tick count until the next wakeup event so if the device was halted by a debugger past the next wakeup event the tick counts will be out of sync.