-
Notifications
You must be signed in to change notification settings - Fork 218
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
Virtual ethernet port #94
Comments
I suppose the "correct" way to do this would be to implement one of the This would either mean losing the serial port (CDC/ACM) functionality, or An alternative approach would be to implement a custom device driver that If you want to actually have the stm32 talk to ethernet, you will need a I know ST made a few chips with ethernet MAC hardware peripherals, so it is I have to say, the chances of LeafLabs writing this sort of thing is pretty Thanks for the suggestion! AJ On Wed, Sep 24, 2014 at 4:10 PM, Grégoire Passault <notifications@github.com
|
I think leaving the COM port should be ok, with an appropriated bootloader Unfortunately I won't help on this, USB devices are like sorcery to me :-) But, once we'd have the interface working, writing MAC/IP/TCP/UDP stack and
|
The netv device did this: http://kosagi.com/w/index.php?title=NeTV_Main_Page#USB_Ethernet_support That ran linux though. I vaguely remember hearing about other microcontroller projects doing this recently, but don't have a reference off hand. It would be a pretty great feature! |
Yes! |
(Building a minimal http server would also seems reasonable) |
There might be some cruft HTTP server demo in the project repository On Sun, Sep 28, 2014 at 10:18 AM, Grégoire Passault <
|
Hello
I know this would be really hard to do, but what about writing an adapter to emulate an ethernet over the usb?
Actually, that sounds more powerful and flexible than virtual com port
We could ping the board, netcat to it (with a basic tcp stack) and why not accessing to network
Again, I know it's not easy, and what I've read about that (usb device creating) seems insanely complicated. How feasible would be that?
The text was updated successfully, but these errors were encountered: