[meta-ti] Beaglebone USB Issues
Nick G
exosyst+metaTI at gmail.com
Mon Oct 15 09:42:54 PDT 2012
Hey guys,
I'm using the Beaglebone with the 3.2 kernel ( Linux beaglebone 3.2.14 #1
Mon Oct 15 16:37:10 BST 2012 armv7l GNU/Linux ) and am having a weird issue.
I developed a driver for a USB gadget based on known working code, and
tested it on my desktop just fine but when I try it with the beaglebone I
sometimes get a USB disconnect:
root at beaglebone:/# /launcher_control -l -t 100 //sends a
Duration set to [ 2792.937500] Received command 0x4
100
[ 2793.043304] Received command 0x20
root at beaglebone:/# /launcher_control -f
[ 2848.961364] Received command 0x10
root at beaglebone:/# [ 2866.422424] usb 1-1: USB disconnect, device number 6
[ 2866.428436] udev not attached
[ 2866.711853] usb 1-1: new low-speed USB device number 7 using musb-hdrc
[ 2866.856842] usb 1-1: New USB device found, idVendor=2123, idProduct=1010
[ 2866.864013] usb 1-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 2866.871612] usb 1-1: Product: USB Missile Launcher
[ 2866.876708] usb 1-1: Manufacturer: Syntek
[ 2866.893524] generic-usb 0003:2123:1010.0006: claimed by neither input,
hiddev nor hidraw
This doesn't happen on the desktop, nor on an older board I have with a 3.4
kernel and wondered if there were any known regressions?
The code that matters is:
pr_debug("Sending usb_control_message()\n");
retval = usb_control_msg(dev->udev,
usb_sndctrlpipe(dev->udev, 0),
LAUNCHER_CTRL_REQUEST,
LAUNCHER_CTRL_REQUEST_TYPE,
LAUNCHER_CTRL_VALUE,
LAUNCHER_CTRL_INDEX,
&buf,
sizeof(buf),
HZ*5);
if (retval < 0) {
pr_err("usb_control_msg failed (%d)", retval);
goto unlock_exit;
}
It returns fine on sending the code, but a subsequent request yields a -110
error return value and the device disconnects.
Any ideas would be appreciated as I am hoping to use the Beaglebone for a
training course.
Regards,
Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20121015/40b8ca33/attachment.html>
More information about the meta-ti
mailing list