Flashed with Android-99 the DragonBoard 410c appears to behave as I would expect with regards to USB Host and peripheral mode. No connection to the microUSB connector and the USB is configured as a Host and the two hub connectors work with mouse and keyboard. When the micro-usb is connected, the 5V from the host (level shifted) is detected on an IO line on the DragonBoard MPU and the usb controller is reconfigured as a peripheral, which can be enumerated by the host.
When the micro-usb is disconnected, the process reverses, and the mouse and keyboard become active again.
When Debian (Buster, 359) is loaded, either using the SD Development image or the SD Install image, the system appears to be fixed in host mode only. Although Gadget support appears to be configured in the kernel, no UDC is shown in /sys/class/udc, so loading libcomposite and setting up a Gadget using configfs has no effect.
I don’t see any activity in the SysLog when I plug and unplug the Micro USB cable either, which I assume means that there is no module akin to dcw2 monitoring OTG_SENSE (or, in this case, the 5V being present, not the actual sense connection on the connector). But it is not clear to me what that driver should be for this build.
I’m sorry if this is a remedial question, but when I searched this forum and others, most people where just confused that there is a single USB controller, so the connectors are mutually exclusive, but were seeing a switch in their syslogs. There is a similar report to mine from Oct 16 here:
But it doesn’t seem answered/resolved. I was hoping someone could point me in the right direction before I bite the bullet and rebuild the kernel and dive into the driver source.
Thanks in advance!