imxrt dshot timing fix #23365
Merged
imxrt dshot timing fix #23365
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
davids5
approved these changes
Jul 5, 2024
vertiq-jordan
pushed a commit
to iq-motion-control/PX4-Autopilot
that referenced
this pull request
Aug 21, 2024
* imxrt: Change PLL settings for more accurate dshot timing * Update NuttX submodule
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.
Use a FLEXIO base clock of 108Mhz which allows TCMP without fractions and thus gives us exact 150KHz, 300KHz, 600KHz, 1200KHz dshot timings.
Also this improves sampling of BDSHOT telemetry.
FYI @jwwaite this pretty much eliminates the CRC errors for me, could you test as well?