I was wondering if the Framework 13 supports the USB OTG ethernet over usb capabilities usually utilized by a Raspberry Pi Zero.
I have all of the necessary drivers on the Pi itself, and am able to connect via Ethernet over USB on my full windows 11 tower.
Would I need to buy a USB-c to Ethernet adapter to fit into the framework? My current configuration is a USB-A to USB micro OTG adapter being plugged into my tower/framework with a USB-A to USB-C cord.
I am assuming I will need additional drivers or hardware in addition to the RDNIS drivers nessecary for the USB to be recognized as an ethernet connection.
Sorry, not sure if I follow. So you currently have a USB ethernet adapter? Can you link to the product?
And this USB ethernet adapter is working on your windows 11 PC? How exactly is it connected?
“OTG” USB is found on microUSB devices who’s normal role isn’t as a host, such as mobile phones or devices that use mobile CPUs, such as raspi zero. The OTG signalling pin isn’t even present on USB-A or USB-C. As long as your cable or connector is correct, a normal non-OTG host doesn’t care if the device is “OTG”. The OTG signalling only comes into play when the host (phone, raspi, or other computer) has a microUSB port.
No, I am currently using a raspberry pi 0, with an OTG adapter to bring it’s mode pin low (set it to device mode instead of host mode).
The windows 11 tower works with this alone, but the framework 13 does not.
I am wondering if I need a USB ethernet adapter to be able to read that as an ethernet connection on the framework 13.
Are you connecting the same way on both? Connected to USB-C on the Framework? Perhaps you could link the adapters and cables?
I’m not sure how you’re suggesting using a USB ethernet adapter. Framework > USB ethernet expansion card > ethernet cable > USB ethernet adapter > raspi zero in host mode?
I cannot really link to the cables are they are just generic ones, however this is a similar model from adafruit.
No Ethernet is physically present. I am using a USB-C → USB-A cable to plug the framework into the adapter, which plugs directly into the raspberry pi.
When working, it shows up as an Ethernet connection on the host pc, and allows me to SSH into the raspberry pi.
So the USB-C male side plugged into the Framework?
To be clear, Framework > USB-C male to USB-A male cable > USB-A female to microUSB male adapter > raspi zero. I don’t think that’s an orientation which will work. Particularly Framework > USB-C male to USB-A male cable.
Is this the same cable setup you’re successfully using with your windows 11 pc?
Yes it is the same setup. When used in the windows 11 PC it is:
USB-C Male → USB-A Male → USB-A Female → Micro USB —> Raspberry Pi Zero
|<— —USB C to A Cable— —>| |<— — OTG Adapter — —> |
It works fine on the PC, I think it needs additional drivers for the framework to recognize it as an Ethernet connection and allow connection, but I am unsure of what or how.
Issue solved, I guess the framework is just not compatible with the connection scheme I had set up ending in USB-C.
It works perfectly fine with the normal RDNIS drivers, as long as a USB-A to USB-A adapter is used to connect the Raspberry Pi with OTG adapter to the framework.