Implement high-frequency PWM functionality #15
Conversation
This file contains hidden or 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
To prevent concurrency when sending event messages, we store sampled analog data and corresponding timestamp in a queue accessed only during the main update loop.
Avoid sending ADC events in timer callback
…-tech/device.hobgoblin into feat-add-high-frequency-pwm
|
|
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.
Introduce PWM capabilities to Hobgoblin. The current implementation relies on a single static pin implementing PWM. The functionality is triggered by configuring a frequency and duty cycle. The parameters can be updated on-the-fly. A second register was added to stop all ongoing PWMs.
Finally, when the board disconnects, the PWM is disabled.