Merged
Conversation
|
How will the USB software be used? (just curious) |
Contributor
For boards where we add hardware support we are aiming to support USB mass storage devices (e.g. USB memory sticks) but this is not guaranteed. |
rechrtb
force-pushed
the
tinyusb_support
branch
2 times, most recently
from
3750772 to
08492db
Compare
rechrtb
force-pushed
the
tinyusb_support
branch
from
0acf68a to
9875793
Compare
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
4 participants
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.
Replaces the ASF-based USB device stack on SAME5x and SAME70 builds with TinyUSB. Old implementation is actually still there, but turned off using define
CORE_USES_TINYUSB. In this PR, this define is set to1.Related PRs:
Duet3D/CoreN2G#3
Duet3D/LibTinyusb#1