-
-
Save geekman/5bdb5abdc9ec6ac91d5646de0c0c60c4 to your computer and use it in GitHub Desktop.
| #!/bin/bash -e | |
| modprobe libcomposite | |
| cd /sys/kernel/config/usb_gadget/ | |
| mkdir g && cd g | |
| echo 0x1d6b > idVendor # Linux Foundation | |
| echo 0x0104 > idProduct # Multifunction Composite Gadget | |
| echo 0x0100 > bcdDevice # v1.0.0 | |
| echo 0x0200 > bcdUSB # USB 2.0 | |
| echo 0xEF > bDeviceClass | |
| echo 0x02 > bDeviceSubClass | |
| echo 0x01 > bDeviceProtocol | |
| mkdir -p strings/0x409 | |
| echo "deadbeef00115599" > strings/0x409/serialnumber | |
| echo "irq5 labs" > strings/0x409/manufacturer | |
| echo "Pi Zero Gadget" > strings/0x409/product | |
| mkdir -p functions/acm.usb0 # serial | |
| mkdir -p functions/rndis.usb0 # network | |
| mkdir -p configs/c.1 | |
| echo 250 > configs/c.1/MaxPower | |
| ln -s functions/rndis.usb0 configs/c.1/ | |
| ln -s functions/acm.usb0 configs/c.1/ | |
| # OS descriptors | |
| echo 1 > os_desc/use | |
| echo 0xcd > os_desc/b_vendor_code | |
| echo MSFT100 > os_desc/qw_sign | |
| echo RNDIS > functions/rndis.usb0/os_desc/interface.rndis/compatible_id | |
| echo 5162001 > functions/rndis.usb0/os_desc/interface.rndis/sub_compatible_id | |
| ln -s configs/c.1 os_desc | |
| udevadm settle -t 5 || : | |
| ls /sys/class/udc/ > UDC |
| # /usr/lib/systemd/system/myusbgadget.service | |
| [Unit] | |
| Description=My USB gadget | |
| After=systemd-modules-load.service | |
| [Service] | |
| Type=oneshot | |
| RemainAfterExit=yes | |
| ExecStart=/usr/bin/myusbgadget | |
| [Install] | |
| WantedBy=sysinit.target |
I can confirm the sequence described in the original article http://irq5.io/2016/12/22/raspberry-pi-zero-as-multiple-usb-gadgets/ does not work with the current Raspberry PI os, or an even later one linux-rpi-5.4.y I grabbed yesterday (I'm writing this Sept 3 2020).
Individual usb gadget devices work fine, but as soon as I try to have 2, neither one works. I also tried eem instead of th rndis, no improvement.
I'm wondering which version of the pi linux kernel did work, I'll be happy to rollback to that. This is all on a pi zero, btw.
Regarding my previous post, I have a new datapoint. I grabbed an older release
linux-raspberrypi-kernel_1.20170215-1.tar.gz
and ran through the steps and everything works as promised. So... something was broken between that release and 5.4.51+:
Linux version 5.4.51+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1333 Mon Aug 10 16:38:02 BST 2020
which was the kernel included in the Raspberry Pi OS (32-bit) Lite image I grabbed yesterday... released 2020-08-20 and presumably with sha-256
24342f3668f590d368ce9d57322c401cf2e57f3ca969c88cf9f4df238aaec41f
Ok more progress. I've isolated the failure to between two releases:
linux-raspberrypi-kernel_1.20180313-1 GOOD
linux-raspberrypi-kernel_1.20180328-1 BAD
Unfortunately it seems to be a massive overhaul, just doing diff -Nur on the drivers/usb/gadget directories yields a 544kbyte file with 19,253 lines. My contribution is done now.
I have an open issue against the Raspberry Pi Kernel (raspberrypi/linux#3862) to track this
For the network part, try this:
https://github.com/rundekugel/USBGadgetNetwork
It combines CDC/ECM and RNDIS
It works for Windows10 / Linux and MACos
I didn't try to add additional cdc/acm, but I think, it should work on most OS.
@nrclark I couldn't make Windows recognize RNDIS device in a composite device setup. The only thing I could do was either skip the second device (Mass Storage in my case) on Windows or make it recognize as a composite device but not install appropriate drivers for the RNDIS (a composite device with 2 subdevices is detected, but the required drivers are not installed and devices are not recognized properly).
The first (working) configuration (just RNDIS for Windows and a composite device for other systems) I made available here in my project Ethsploiter.
Since Windows requires a particular pair of IdVendor/idProduct to determine the driver for RNDIS, the configuration of placing RNDIS inside a composite setup might not work without providing a custom INF file stating the information about the devices in the composite setup. However, I haven't confirmed that so If anyone makes it work without the INF file or confirms that it is not possible, I'd be grateful for such information!