switch to private timer for system time and Tasking System #1
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
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.
Switch the Kernel (and consequently the tasking system) to use the CPU's private timer rather than the global timer, since the global timer is shared between Linux and deep in an AMP context.
Note that Linux currently configures the Zynq to run at 333MHz rather than the previous 667MHz, hence the change to
clockFrequency.Unlike the global timer, which is a 64Bit incrementing timer, the private timer is only 32Bit and decrementing.
This means that it currently overflows every ~12s, creating the needs to store a 64Bit timestamp in a dedicated variable that needs to be updated periodically.