bugfix: manually trigger cvTimer on cv change #183
Merged
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.
What does this PR do?
Changes what appears to be a typo manually triggering
adcTimer
instead ofcvTimer
intele_cv
, which was causing DACs not to update until the CV timer expires when usingCV
ops.Provide links to any related discussion on lines.
https://llllllll.co/t/teletype-timing-issues-cv-edition/24193/9?u=csboling
How should this be manually tested?
Report from testing with an oscilloscope on Lines: "CV state changes have c. 200us of latency + c. 500us of jitter after this update" (down from as much as 6ms)
Any background context you want to provide?
If the related Github issues aren't referenced in your commits, please link to them here.
I have,
CHANGELOG.md
make format
on each commit - N/A