-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USB device stack #3890
USB device stack #3890
Conversation
More good news today! Thanks! |
@jfischer-phytec-iot, nice to see your PR. Currently, a USB stack is a big lacks in RIOT imho. |
@jfischer-phytec-iot
Could you elaborate on this? Perhaps it is possible to improve the autostart system? |
(prepare for usbdev stack), set core clock to 120MHz
sys/usbdev/usbdev_acm.c: add uart driver
If someone wants to test it with the PhyNode Boards version 1426.0 or 1426.1, the following modifications must be performed:
New 1426.2 Boards do not need this modifications. The PhyWave module should be populated with MKW22D. |
I got usb working on samr21-xpro, this PR will be rebased and updated in the next days. |
nice! very looking forward... |
This PR is WIP and I assume we won't make it until the release. Removing the Milstone now. Feel free to reset I was wrong in my assumption. |
WIP -> postponed. And please rebase if possible. |
Postponed due to feature freeze. |
Let's remove the milestone until someone has time to pick it up again. |
@OlegHahm What is the status of this? How close was it to being done? Is anyone familiar with what has been completed already and could walk me through some of it? I can't make any promises but depending on the level of work, I'd be interested in helping finish it. I would like to get a shell working over USB CDC ultimately. |
Total outdated, update will come |
@jfischer-phytec-iot, this PR is very interesting for some SAMD21 based boards (Arduino MKR, Adafruit Feather). In this comment above, you said that you could make it work on Samr21-xpro which kind of samd21 based. Is there any chance that you update your branch soon or give some notes on how you achieved this ? (We might consider reopening this PR I think) |
@aabadie yes, I have tested it with samr21 board. I have to look again and squash so that it looks reasonable. Would you like to work on the usb device stack? I will unfortunately not have much time to help and I do not want that only the samr/d driver will be maintained, as it indicates in your message. |
@jfischer-phytec-iot Your work is really interesting ! It would be great if you can reopen or share your branch. I'd would love to help RIOT to have a full USB support someday :) |
@dylad, if you are interested in working on this, you can fetch the branch reference by the PR:
|
Thanks for the tip @aabadie ! |
@dylad This PR can not be reopen, please pick wip@usbdev branch from my repository |
This PR is still referred in the |
Let's try to summon @bergzand, he might know. |
This PR is no longer relevant regarding USB support for RIOT. I think it was added there as a "TODO" to add USB support later. I think you can remove it. |
I don't think this PR was on my radar while working on the USB stack. |
USB Device stack implementation for RIOT.
Description:
It's all still WIP but it works. As it says in the title, it is a USB Device stack. It means that a RIOT board with this stack can communicate with the USB host.
For now, only the Kinetis Driver (8bef8ab) exists. It would be great if someone would add a different platform. Possibly the interface between driver and stack needs to be expanded.
Hardware Driver and Stack use few macros and need only few changes in Makefile. The Driver uses a "driver_init" macro to register at the stack, similar to module_init in Linux. It (dc8a7c9) still needs a little fine-tuning. And I hope you find it useful (I do not like the RIOTs autostart).
To be continued....
Supported and boards (SoCs):
How to test:
Under test/usbdev (8db566c) is the appropriate Makefile. For testing you can either do
./dist/tools/pyterm/pyterm --port /dev/ttyACM1
Depends on
#4114, #4163 and serves as an example for #4155