I've not done USB gadget stuff on the CM4 but have on other Pi models (including A+ and 3A+ which also have the ID pin pulled low).
I don't think the problem is with the ID pin. I suspect it's a problem with the network configuration on both ends of the link.
All the ID pin does is tell the Pi whether to act as a host or device but you've overridden that in your config.txt (,dr_mode=peripheral). The state of the ID pin is not used by the ethernet gadget and has no effect on dwc2 unless using dr_mode=otg (which is the default if nto specified).
Your PC is seeing the RNDIS device so the dwc2 driver and g_ether have done what they're supposed to.
Is your CM4 running RPiOS Bookworm?
Are you running a DHCP server on the PC or the PI?
Have you configured static IP addresses?
Bookworm uses Network Manager not dhcpcd to configure interfaces. In the default configuratino it does not fall back to self assigned IP addresses in the MDNS/Avahi/Bonjour subnet. That means it probably won't bring it's end of the interface up.
There's advice in Bookworm vs Bullseye - A Guide on how to get the old fallback behaviour working.
You might want to fond a local to you linux networking expert to assist and you'll almost certainly need a way top login to the CM4 while the g_ether link is down.
I don't think the problem is with the ID pin. I suspect it's a problem with the network configuration on both ends of the link.
All the ID pin does is tell the Pi whether to act as a host or device but you've overridden that in your config.txt (,dr_mode=peripheral). The state of the ID pin is not used by the ethernet gadget and has no effect on dwc2 unless using dr_mode=otg (which is the default if nto specified).
Your PC is seeing the RNDIS device so the dwc2 driver and g_ether have done what they're supposed to.
Is your CM4 running RPiOS Bookworm?
Are you running a DHCP server on the PC or the PI?
Have you configured static IP addresses?
Bookworm uses Network Manager not dhcpcd to configure interfaces. In the default configuratino it does not fall back to self assigned IP addresses in the MDNS/Avahi/Bonjour subnet. That means it probably won't bring it's end of the interface up.
There's advice in Bookworm vs Bullseye - A Guide on how to get the old fallback behaviour working.
You might want to fond a local to you linux networking expert to assist and you'll almost certainly need a way top login to the CM4 while the g_ether link is down.
Statistics: Posted by thagrol — Thu Jan 04, 2024 12:56 am