Linux Embedded OTG gadgets conflict(?) with QDB
I'm working on a custom board based on iMX6 Sabresd board.
I have the following problem:
When I use generic Yocto images like "fsl-image-multimedia-full" I can load USB modules such as g_mass_storage in order to connect my board to a Windows PC and see my SD card content.
When I use "b2qt-embedded-qt5-image" and try to execute:
#modprobe g_mass_storage file=/dev/mmcblk1
I get the following output:
udc-core: couldn't find an available UDC - added [g_mass_storage] to list of pending drivers
Being that I'm using the same kernel and device tree the problem must be some difference in the Root File System.
In particular I think that this problem is related to the fact that in "b2qt-embedded-qt5-image" other USB OTG devices are presented when connecting to a PC: "QDB interface" and "remote NDIS". I know they are useful to debug applications on the target, but could you help me to load my g_mass_storage, with or without them, when I need it?