Open
Conversation
|
Memory usage change @ e1fdc36
Click for full report table
|
|
Memory usage change @ af72992
Click for full report table
|
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
1 participant
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.
The ability to use a different USB implementation, like TinyUSB, would be a useful addition. I understand that the core contains a USB implementation but I have found TinyUSB to be more feature rich and easier to use. Additionally, it supports many different cores and would allow for better project interoperability between cores.
Compatibility can be achieved simply by giving the user the ability to disable the built in USB core in a menu option. As much of the USB functionality is already wrapped with USBCON I used that trigger enabling and disabling of the USB core. The changes are not specific to TinyUSB.