usbd-smart-keyboard: feature flag usbd-serial #235
Merged
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
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.
When porting over the onekey example & adapting it to use the
usbd-smart-keyboardcrate (which descends from the keyberon-using code I'd written over at keyboard-labs), I found that the STM32F4 didn't work when using usbd-serial.This likely has something to do with STM32F4xx only having 4 USB endpoints.
I'm not exactly sure where those 4 are coming from. (tinyuf2 + hid device with keyboard and consumer control?). But, using conditional compilation avoids this.