Following the instructions on http://dev.3dr.com/hardware-accessorybay.html, bridging 3DRBUS to GROUND and connecting a USB cable to USB d+/d-/ground does not bring the co-prossesor into host mode. It does list another USB root hub, when logging into the co-processor but this does not respond to plugging in devices. No output is shown in dmesg.
I have identified the following modules loaded on the 3DR Solo co-processor that may be problematic:
root@3dr_solo:~# lsmod
Module Size Used by
usb_f_acm 4037 1
u_serial 7979 3 usb_f_acm
g_acm_ms 18540 0
libcomposite 26342 2 usb_f_acm,g_acm_ms
Attempting to remove _g_acmms causes rmmod to freeze. It appears as if
the 3DR Solo is hardcoded to work as a USB device only. Are these modules the ones responsible for making the 3DR Solo appear as a composite USB device (storage device + serial port)?
Hi!
Following the instructions on http://dev.3dr.com/hardware-accessorybay.html, bridging 3DRBUS to GROUND and connecting a USB cable to USB d+/d-/ground does not bring the co-prossesor into host mode. It does list another USB root hub, when logging into the co-processor but this does not respond to plugging in devices. No output is shown in dmesg.
I have identified the following modules loaded on the 3DR Solo co-processor that may be problematic:
Attempting to remove _g_acmms causes rmmod to freeze. It appears as if the 3DR Solo is hardcoded to work as a USB device only. Are these modules the ones responsible for making the 3DR Solo appear as a composite USB device (storage device + serial port)?
Hope to hear back from you soon.
In advance thanks Sondre