On Freitag, 4. September 2020 14:25:37 CEST Ludwig Nussel wrote:
Fabian Vogt wrote: to get rid of the otg descriptor. That's not the issue though. I found that when setting the hid subclass to 0 the device appears in u-boot. Still doesn't work though. It's not specific to the rpi3 either. Connecting a A10 olinuxino on the other side also gets no keyboard input either. Looking at "usb info" one can see that the gadget has two endpoints. One for input and one for output. Whereas real keyboards and also an Arduino pretending to be a keyboard only has an input endpoint. Could that be relevant? I couldn't find how to disable the second endpoint via configfs though. Any ideas?
Although USB Keyboards all use the HID protocol, grabbing into the stack of Keyboards I used when extending the Rpi1-3 dwc2 implementation: - USB low speed (1.5 MBit/s) and USB full speed (12 MBit/s) - Control + Interupt IN is required, OUT is optional - Devices may have one or multiple interfaces (e.g. Logitech Unifying receivers). As the OTG device appears under some circumstances, physical layer problems are unlikely. Does the OTG device only emulate an USB Keyboard (Class/Subclass/Protocol: 3/1/1), or also a mouse (3/1/2)? U-Boot might be confused when a device has interfaces with both protocols. Other than that, I fear you either have to recompile U-Boot with additional debug output, or connect a logic analyzer in between. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019