creating a USB gadget
I want to create a USB gadget with a raspberry pi zero 2W. I'm starting with imitating a webcam I already have to see how much of this I can figure out. I've used the online documentation and a couple AI bots to get this far quickly, but I'm hung up on a ln command. It's telling me "ln: failed to create symbolic link 'configs/c.1/uvc.usb0': No such file or directory" when trying to create the link. This makes no sense to me though. I'm trying to create the link, of course it doesn't exist yet. That's what that command is supposed to do.
I've confirmed this problem in alpine linux and raspbian lite.
Below is the little script I have so far just to create the device:
\#!/bin/bash
modprobe libcomposite
cd /sys/kernel/config/usb_gadget/
mkdir -p fauxcam
cd fauxcam
echo 0x046d > idVendor # Logitech Vendor ID
echo 0x094b > idProduct # Brio 105 Product ID
echo 0x0200 > bcdUSB
echo 0x9914 > bcdDevice
mkdir -p strings/0x409
echo "111111111111" > strings/0x409/serialnumber
echo "Brio 105" > strings/0x409/product
mkdir -p configs/c.1/strings/0x409
echo "UVC Configuration" > configs/c.1/strings/0x409/configuration
echo 250 > configs/c.1/MaxPower
mkdir -p functions/uvc.usb0
ln -s functions/uvc.usb0 configs/c.1/
echo "usb0" > UDC
dafta
in reply to muusemuuse • • •modprobe usb_f_uvc
at the beggining, right aftermodprobe libcomposite
muusemuuse
in reply to dafta • • •dafta
in reply to muusemuuse • • •Hmm, not sure then. It seems correct to me. Check out this repo, it has systemd services for all the USB gadgets, you can run uvc very easily with this: github.com/BigfootACA/systemd-…
I can write specific instructions how to get this working later today, if you'll need them.
GitHub - BigfootACA/systemd-gadget: USB gadget setup scripts for systemd
GitHubmuusemuuse
in reply to dafta • • •Looking at those units I noticed something...
ExecStart=/usr/bin/ln -s ${GADGET}/functions/uvc.0 ${GADGET}/configs/a.1/
It's an a.1 instead of a c.1. Surely it couldn't be as simple as just using a different letter, could it?
dafta
in reply to muusemuuse • • •No, unfortunately not :/
That's just the "name" of the configuration, for instance in my USB ethernet gadget I use both c.1 and c.2 as config names, and not a.1.
Steam Deck USB Ethernet
Gistmuusemuuse
in reply to dafta • • •dafta
in reply to muusemuuse • • •muusemuuse
in reply to dafta • • •dafta
in reply to muusemuuse • • •You should definitely try with the systemd-gadgets I linked earlier. It makes all the configuration really easy, you just need to enable the relevant services, so in your case
usbgadget-func-uvc.service
andgadget-start.service
. You also need to copy them beforehand to/etc/systemd/system
, includinggadget-init.service
, and you need to copygadget
to/etc/default/gadget
, and the scriptsgadget-start.sh
andgadget-init.sh
to/etc/systemd/scripts
. Edit/etc/default/gadget
to edit the configs and names of the gadget, and then startgadget-start.service
. No need to enablegadget-init.service
, it's called as a dependency from other services.There's an install script in the repo that you can use as well.
gnuhaut
in reply to muusemuuse • • •IDK how all that works but I will say that the result of this would (in a normal filesystem) create a link named
configs/c.1/uvc.usb0
yes, but that link would point tofunctions/uvc.usb0
relative to its own dir. This doesn't exist and your symlink would be broken, presumably the special file system there doesn't like that.Edit: Apparently that's not the problem and you're totally supposed to run an ln command that should logically result in a broken symlink, thanks to kernel driver sysfs abuse.
dafta
in reply to gnuhaut • • •gnuhaut
in reply to dafta • • •dafta
in reply to gnuhaut • • •Linux USB gadget configured through configfs — The Linux Kernel documentation
www.kernel.orggnuhaut
in reply to dafta • • •Edit: OK, I looked at the docs, and they sure do make a broken symlink there. I still think it's worth a try to create a non-broken link, maybe the docs are wrong. I would expect they would put a little note there, that yes, you really do want to create a broken symlink (if so, why not a regular file?), but then again its kernel docs and those aren't the most friendly.
I also thought you were OP for some reason, sorry.
Edit2: If you look at the file listing later in the docs, you can see this:
Which does look like a real non-broken symlink, so I maintain the docs are wrong and you're not supposed to make a broken symlink.
Original comment, silightly edited:
You misunderstand. I suspect OP cannot create the symlink, because it would be a broken symlink, not because the symlink is relative. Maybe you cannot create broken symlinks in the sysfs for some reason.
I was just trying to explain that a relative symlink is relative to the directory in which it resides. The target to the symlink should point to
../../functions/uvc.usb0
if you want it to point to something that exists. The ln command in OP's listing would result in a broken symlink, since the specified path is not relative to the c.1 directory. It is relative to the working directory, but that's wrong, that's not what ln expects you to put there.Maybe it needs to be a correct symlink, maybe that will solve the problem.