Yeah, changing usb dongle selection in coreboot menuconfig to NET20DC or compatible worked. :)
Which, will lead me onto my next mailing list submission once I have perused the output.
Brace yourselves!
On 17/10/2013 16:47, John Lewis wrote:
On 17/10/2013 16:35, Kyösti Mälkki wrote:
On 17.10.2013 17:45, John Lewis wrote:
Hey Guys, I'm trying to setup a Beaglebone Black as the subject. I've followed the instructions and I get lots of this when I try to make it do it's thang: [ 3142.831914] CAUTION: musb: Babble Interrupt Occurred [ 3143.107609] gadget: setup: failure req 9 v 1 [ 3143.289034] CAUTION: musb: Babble Interrupt Occurred [ 3143.289088] gadget: disconnected [ 3143.564615] gadget: setup: failure req 9 v 1 [ 3143.746013] CAUTION: musb: Babble Interrupt Occurred [ 3143.746058] gadget: disconnected [ 3144.021599] gadget: setup: failure req 9 v 1 [ 3144.264994] CAUTION: musb: Babble Interrupt Occurred [ 3144.265038] gadget: disconnected [ 3144.540802] gadget: setup: failure req 9 v 1 [ 3144.722247] CAUTION: musb: Babble Interrupt Occurred [ 3144.722304] gadget: disconnected [ 3144.997944] gadget: setup: failure req 9 v 1 [ 3145.179357] CAUTION: musb: Babble Interrupt Occurred [ 3145.179415] gadget: disconnected Any pointers? Web search comes up fruitless except for references to the kernel source code which I don't understand. ;) Thanks, John.
Hi John Apply the patches and follow the instructions here for BeagleBone Black kernel: http://www.coreboot.org/EHCI_Gadget_Debug [1] In coreboot menuconfig, the selection of usbdebug dongle 'BeagleBone' is only for 'BeagleBone', not 'BeagleBone Black'. I better add option for 'BeagleBone Black' to avoid the confusion. Select 'Net20DC compatible' for now. Also in coreboot menuconfig, under 'Debugging', enable verbose usbdebug messaging. Of course you will need another working console to receive those messages, CBMEM console will do if your target system is able to reach OS. Regards, Kyösti
Hi Kyösti,
Man, you are quick. :)
Yeah, I followed those instructions. The BBB's kernel and modules have been compiled with the patches.
Ah, that explains part of it then, because I had selected Beaglebone as opposed to NET20DC or compatible.
It isn't able to reach OS, but if changing the coreboot menuconfig doesn't fix it I shall try it on a Chromebook which is working with coreboot, and revert.
Thank you!
John.