Pi Zero multiple USB gadgets minimal example

myusbgadget

#!/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

myusbgadget.service

# /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

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

If you have a working example that provides ACM, ECM, and RNDIS (with ACM/RNDIS working on windows and ACM/ECM working on Mac), it could help me out bigtime.

See this
https://gist.github.com/Leo-PL/1ee48d132bc7a7ccd4657ea1ed7badd8

It includes two alternative configurations (USB term): one with RNDIS+ACM, another with ECM+ACM.

EDIT: nevermind, it doesn't work indeed. Windows stops recognizing ACM as soon as there are two configurations.
Interestingly, this question is about this exact issue has been fixed by using

echo "0xEF" > ${g}/bDeviceClass
echo "0x02" > ${g}/bDeviceSubClass
echo "0x01" > ${g}/bDeviceProtocol

which is already present in the script above. I've tried the snippet from the question with the fix, and it does not work for me.