No, that is *not* a bus trace. You need a hardware bus trace box to get a bus trace. Sorry.
On Sun, Jun 29, 2008 at 12:07 AM, Gabriel Queiroz <[EMAIL PROTECTED]> wrote: > Hi Dan! > > Ok, I've got the bus trace (god save usbfs_snoop!). > > So, here is the output from when I connect the device to the hub (usbhid > claims the device): > > ... > Jun 29 00:37:40 gilmour kernel: [112648.801378] usb 2-3: new full speed USB > device using ohci_hcd and address 10 > Jun 29 00:37:41 gilmour kernel: [112649.008693] usb 2-3: configuration #1 > chosen from 1 choice > Jun 29 00:37:41 gilmour kernel: [112649.083844] usbcore: registered new > interface driver hiddev > Jun 29 00:37:41 gilmour kernel: [112649.085622] usb usb1: usbdev_ioctl: > IOCTL > ... > Jun 29 00:37:41 gilmour kernel: [112649.086835] usb usb2: usbdev_ioctl: > CONNECTINFO > Jun 29 00:37:41 gilmour kernel: [112649.281557] input: HID ffff:0000 as > /devices/pci0000:00/0000:00:03.1/usb2/2-3/2-3:1.0/input/input18 > Jun 29 00:37:41 gilmour kernel: [112649.308496] input,hidraw0: USB HID v1.00 > Mouse [HID ffff:0000] on usb-0000:00:03.1-3 > Jun 29 00:37:41 gilmour kernel: [112649.389391] usb usb3: usbdev_ioctl: > IOCTLJun 29 00:37:41 gilmour kernel: [112649.390691] usb usb4: usbdev_ioctl: > CONNECTINFO > Jun 29 00:37:41 gilmour kernel: [112649.390916] usb 2-3: usbdev_ioctl: > CONTROL > Jun 29 00:37:41 gilmour kernel: [112649.390925] usb 2-3: control read: > bRequest=08 bRrequestType=80 wValue=0000 wIndex=0000 wLength=0001 > Jun 29 00:37:41 gilmour kernel: [112649.392981] usb 2-3: usbdev_ioctl: > CONTROL > Jun 29 00:37:41 gilmour kernel: [112649.392991] usb 2-3: control read: > bRequest=08 bRrequestType=80 wValue=0000 wIndex=0000 wLength=0001 > Jun 29 00:37:41 gilmour kernel: [112649.393644] usbcore: registered new > interface driver usbhid > ... > Jun 29 00:37:41 gilmour kernel: [112649.393898] > /build/buildd/linux-2.6.24/drivers/hid/usbhid/hid-core.c: v2.6:USB HID core > driver > Jun 29 00:37:41 gilmour kernel: [112649.421261] usb 2-3: control read: data > 01 > Jun 29 00:37:41 gilmour kernel: [112649.467158] usb 2-3: control read: data > 01 > Jun 29 00:37:41 gilmour kernel: [112649.495158] usb usb1: usbdev_ioctl: > IOCTL > ... > > > The device works! =) > > So, I manually rmmod usbhid, and get this output: > > ... > Jun 29 00:39:57 gilmour kernel: [112785.157004] usb usb4: usbdev_ioctl: > CONNECTINFO > Jun 29 00:40:01 gilmour kernel: [112789.230351] usbcore: deregistering > interface driver usbhid > Jun 29 00:40:01 gilmour kernel: [112789.344360] usbcore: deregistering > interface driver hiddev > Jun 29 00:40:02 gilmour kernel: [112790.231698] usb usb1: usbdev_ioctl: > IOCTL > ... > > ...as expected. Then, from inside eclipse (running it as root), I start the > MouseDriver.java example. Here's the output: > > Jun 29 00:51:24 gilmour kernel: [113471.992638] usb usb4: usbdev_ioctl: > IOCTL > Jun 29 00:51:24 gilmour kernel: [113471.992709] usb usb4: usbdev_ioctl: > CONNECTINFO > Jun 29 00:51:24 gilmour kernel: [113471.992925] usb usb3: usbdev_ioctl: > IOCTL > Jun 29 00:51:24 gilmour kernel: [113471.993098] usb usb3: usbdev_ioctl: > CONNECTINFO > Jun 29 00:51:24 gilmour kernel: [113471.993663] usb usb4: usbdev_ioctl: > IOCTL > Jun 29 00:51:24 gilmour kernel: [113471.993942] usb usb4: usbdev_ioctl: > CONNECTINFO > Jun 29 00:51:24 gilmour kernel: [113471.994260] usb usb1: usbdev_ioctl: > CONTROL > Jun 29 00:51:24 gilmour kernel: [113471.994271] usb usb1: control read: > bRequest=08 bRrequestType=80 wValue=0000 wIndex=0000 wLength=0001 > Jun 29 00:51:24 gilmour kernel: [113471.994279] usb usb1: control read: data > 01 > Jun 29 00:51:24 gilmour kernel: [113471.995146] usb usb2: usbdev_ioctl: > CONTROL > Jun 29 00:51:24 gilmour kernel: [113471.995156] usb usb2: control read: > bRequest=08 bRrequestType=80 wValue=0000 wIndex=0000 wLength=0001 > Jun 29 00:51:24 gilmour kernel: [113471.995165] usb usb2: control read: data > 01 > Jun 29 00:51:24 gilmour kernel: [113471.995314] usb 2-3: usbdev_ioctl: > CONTROL > Jun 29 00:51:24 gilmour kernel: [113471.995320] usb 2-3: control read: > bRequest=08 bRrequestType=80 wValue=0000 wIndex=0000 wLength=0001 > Jun 29 00:51:24 gilmour kernel: [113472.040766] usb 2-3: control read: data > 01 > Jun 29 00:51:24 gilmour kernel: [113472.041043] usb usb3: usbdev_ioctl: > CONTROL > Jun 29 00:51:24 gilmour kernel: [113472.041053] usb usb3: control read: > bRequest=08 bRrequestType=80 wValue=0000 wIndex=0000 wLength=0001 > Jun 29 00:51:24 gilmour kernel: [113472.041064] usb usb3: control read: data > 01 > Jun 29 00:51:24 gilmour kernel: [113472.041179] usb usb4: usbdev_ioctl: > CONTROL > Jun 29 00:51:24 gilmour kernel: [113472.041186] usb usb4: control read: > bRequest=08 bRrequestType=80 wValue=0000 wIndex=0000 wLength=0001 > Jun 29 00:51:24 gilmour kernel: [113472.041194] usb usb4: control read: data > 01 > Jun 29 00:51:27 gilmour kernel: [113474.546018] usb 2-3: usbdev_ioctl: > CLAIMINTERFACE > Jun 29 00:51:27 gilmour kernel: [113474.546218] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.547266] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.548653] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.549708] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.550751] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.551864] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.552982] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.554038] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.555072] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.556200] usb 2-3: usbdev_ioctl: > SUBMITURB > Jun 29 00:51:27 gilmour kernel: [113474.556211] usb 2-3: control urb: > bRequest=06 bRrequestType=81 wValue=2200 wIndex=0000 wLength=0100 > Jun 29 00:51:27 gilmour kernel: [113474.556221] usb 2-3: direction=IN > Jun 29 00:51:27 gilmour kernel: [113474.556224] usb 2-3: userurb=08091338 > Jun 29 00:51:27 gilmour kernel: [113474.556227] usb 2-3: > transfer_buffer_length=256 > Jun 29 00:51:27 gilmour kernel: [113474.556230] usb 2-3: actual_length=0 > Jun 29 00:51:27 gilmour kernel: [113474.556234] usb 2-3: data: 00 00 00 00 > 00 00 00 00 00 3e 72 f7 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 d0 14 00 00 67 00 00 00 68 00 00 00 00 00 00 00 98 11 9d f7 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 4f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 10 17 2a c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 58 76 f4 00 00 00 00 00 00 00 00 4f 58 > 76 f4 80 58 76 f4 00 58 76 f4 00 58 76 f4 30 01 00 00 01 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 80 02 00 00 00 c0 a8 00 8f d1 55 85 53 02 00 00 00 c0 > a8 00 8f c0 a8 00 8f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 > Jun 29 00:51:27 gilmour kernel: [113474.556540] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.557576] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.558599] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.559647] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.560530] usb 2-3: urb complete > Jun 29 00:51:27 gilmour kernel: [113474.560538] usb 2-3: direction=IN > Jun 29 00:51:27 gilmour kernel: [113474.560540] usb 2-3: userurb=08091338 > Jun 29 00:51:27 gilmour kernel: [113474.560544] usb 2-3: > transfer_buffer_length=256 > Jun 29 00:51:27 gilmour kernel: [113474.560546] usb 2-3: actual_length=50 > Jun 29 00:51:27 gilmour kernel: [113474.560548] usb 2-3: data: 05 01 09 02 > a1 01 09 01 a1 00 05 09 19 01 29 03 15 00 25 01 95 03 75 01 81 02 95 01 75 > 05 81 01 05 01 09 30 09 31 15 81 25 7f 75 08 95 02 81 06 c0 c0 9d f7 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 4f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 10 17 2a c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 58 76 f4 00 00 00 00 00 00 00 00 4f 58 > 76 f4 80 58 76 f4 00 58 76 f4 00 58 76 f4 30 01 00 00 01 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 80 02 00 00 00 c0 a8 00 8f d1 55 85 53 02 00 00 00 c0 > a8 00 8f c0 a8 00 8f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 > Jun 29 00:51:27 gilmour kernel: [113474.560777] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.563705] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.564743] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.565841] usb 2-3: usbdev_ioctl: > RELEASEINTERFACE > Jun 29 00:51:27 gilmour kernel: [113474.653630] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.654698] usb 2-3: usbdev_ioctl: > CLAIMINTERFACE > Jun 29 00:51:27 gilmour kernel: [113474.654806] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.655843] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.656960] usb 2-3: usbdev_ioctl: > SUBMITURB > Jun 29 00:51:27 gilmour kernel: [113474.656972] usb 2-3: interrupt urb > Jun 29 00:51:27 gilmour kernel: [113474.656979] usb 2-3: direction=IN > Jun 29 00:51:27 gilmour kernel: [113474.656982] usb 2-3: userurb=08091458 > Jun 29 00:51:27 gilmour kernel: [113474.656984] usb 2-3: > transfer_buffer_length=4 > Jun 29 00:51:27 gilmour kernel: [113474.656987] usb 2-3: actual_length=0 > Jun 29 00:51:27 gilmour kernel: [113474.656989] usb 2-3: data: f0 33 87 df > Jun 29 00:51:27 gilmour kernel: [113474.657068] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.659129] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.660323] usb 2-3: usbdev_ioctl: > REAPURBDELAY > ... > Jun 29 00:51:27 gilmour kernel: [113474.676818] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.677845] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.678866] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.679883] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.680414] usb 2-3: urb complete > Jun 29 00:51:27 gilmour kernel: [113474.680418] usb 2-3: direction=IN > Jun 29 00:51:27 gilmour kernel: [113474.680420] usb 2-3: userurb=08091458 > Jun 29 00:51:27 gilmour kernel: [113474.680422] usb 2-3: > transfer_buffer_length=4 > Jun 29 00:51:27 gilmour kernel: [113474.680424] usb 2-3: actual_length=0 > Jun 29 00:51:27 gilmour kernel: [113474.680426] usb 2-3: data: f0 33 87 df > Jun 29 00:51:27 gilmour kernel: [113474.680963] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.684759] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.685794] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.686812] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.687827] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.688841] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.689860] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.690876] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.691891] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.692905] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.693920] usb 2-3: usbdev_ioctl: > REAPURBDELAY > Jun 29 00:51:27 gilmour kernel: [113474.694934] usb 2-3: usbdev_ioctl: > REAPURBDELAY > ... > > Then it goes REAPURBDELAY'ng until I disconnect the device. > > I can imagine by the code that javax.usb is getting timeout for some kind of > command it sent to the device, but i can't really tell what kind of response > it could be expecting. > > One thing that occurs to me: It might be the case that the device is > "thinking" it is already "setted-up", so there would be no need to start the > set up routine again. Makes sense? I'll dig in the firmware code to check, > anyways... > > Dan: Thanks a lot for your patience! > > Best regards, > > -- > Gabriel Queiroz Silva > E-mail: [EMAIL PROTECTED] > Tel: +55 61 9604.1412 > > > On Sat, Jun 28, 2008 at 12:03 PM, Dan Streetman <[EMAIL PROTECTED]> wrote: >> >> Ah, the error is on the interrupt in pipe. You're going to need a usb >> bus trace to see what's going on. >> >> On Fri, Jun 27, 2008 at 7:47 PM, Gabriel Queiroz <[EMAIL PROTECTED]> >> wrote: >> > Hi Dan, >> > >> > Sorry, hadn't get ya. I don't need to send any command. The device is >> > enumerated, and after it waits for the user to push a button... If a >> > button is pressed, then the device sends a command. >> > >> > But nothing is being sent before the error, just the normal setup >> > routine. >> > >> > Cheers, >> > >> > On 6/27/08, Dan Streetman <[EMAIL PROTECTED]> wrote: >> >> Yes, of course it happens after a submit, what I meant was what >> >> command are you sending that causes the error? >> >> >> >> On Fri, Jun 27, 2008 at 6:59 PM, Gabriel Queiroz <[EMAIL PROTECTED]> >> >> wrote: >> >>> Hi Dan, >> >>> >> >>> Inside LinuxPipeOsImp.java, method void asyncSubmit( UsbIrpImp irp ), >> >>> line >> >>> 64: >> >>> >> >>> getLinuxInterfaceOsImp().submit(request); >> >>> >> >>> As far as i got it, this call only adds data to a list (suppose it >> >>> would >> >>> be >> >>> sent afterwards?), so, i didn't really get what went wrong. >> >>> >> >>> Thanks again! >> >>> >> >>> -- >> >>> Gabriel Queiroz Silva >> >>> E-mail: [EMAIL PROTECTED] >> >>> Tel: +55 61 9604.1412 >> >>> >> >>> On Fri, Jun 27, 2008 at 7:16 PM, Dan Streetman <[EMAIL PROTECTED]> >> >>> wrote: >> >>>> >> >>>> No hint unfortunately. You may be able to track down where in the >> >>>> kernel it's generating the error, which might help, but ultimately it >> >>>> may be a device problem. >> >>>> >> >>>> What command are you getting the error for? >> >>>> >> >>>> On Fri, Jun 27, 2008 at 5:27 PM, Gabriel Queiroz >> >>>> <[EMAIL PROTECTED]> >> >>>> wrote: >> >>>> > Hi Dan, >> >>>> > >> >>>> > Thanks for your fast reply! >> >>>> > >> >>>> > Here's the output from /var/log/messages when I connect the new >> >>>> > device... >> >>>> > >> >>>> > Jun 27 18:17:50 gilmour kernel: [ 3537.347832] usb 1-3: new full >> >>>> > speed >> >>>> > USB >> >>>> > device using ohci_hcd and address 3 >> >>>> > Jun 27 18:17:50 gilmour kernel: [ 3537.555531] usb 1-3: >> >>>> > configuration >> >>>> > #1 >> >>>> > chosen from 1 choice >> >>>> > Jun 27 18:17:50 gilmour kernel: [ 3537.629783] usbcore: registered >> >>>> > new >> >>>> > interface driver hiddev >> >>>> > Jun 27 18:17:50 gilmour kernel: [ 3537.709497] input: HID ffff:0000 >> >>>> > as >> >>>> > /devices/pci0000:00/0000:00:03.0/usb1/1-3/1-3:1.0/input/input7 >> >>>> > Jun 27 18:17:51 gilmour kernel: [ 3537.735403] input,hidraw0: USB >> >>>> > HID >> >>>> > v1.00 >> >>>> > Mouse [HID ffff:0000] on usb-0000:00:03.0-3 >> >>>> > Jun 27 18:17:51 gilmour kernel: [ 3537.735695] usbcore: registered >> >>>> > new >> >>>> > interface driver usbhid >> >>>> > Jun 27 18:17:51 gilmour kernel: [ 3537.735866] >> >>>> > /build/buildd/linux-2.6.24/drivers/hid/usbhid/hid-core.c: v2.6:USB >> >>>> > HID >> >>>> > core >> >>>> > driver >> >>>> > >> >>>> > Then I rmmod usbhid, so javax-usb can claim the interface, and this >> >>>> > is >> >>>> > the >> >>>> > message i get: >> >>>> > >> >>>> > Jun 27 18:20:08 gilmour kernel: [ 3674.920172] usbcore: >> >>>> > deregistering >> >>>> > interface driver usbhid >> >>>> > Jun 27 18:20:08 gilmour kernel: [ 3675.027665] usbcore: >> >>>> > deregistering >> >>>> > interface driver hiddev >> >>>> > >> >>>> > From dmesg, i get these messages: >> >>>> > >> >>>> > [ 3537.347832] usb 1-3: new full speed USB device using ohci_hcd >> >>>> > and >> >>>> > address >> >>>> > 3 >> >>>> > [ 3537.555531] usb 1-3: configuration #1 chosen from 1 choice >> >>>> > [ 3537.629783] usbcore: registered new interface driver hiddev >> >>>> > [ 3537.709497] input: HID ffff:0000 as >> >>>> > /devices/pci0000:00/0000:00:03.0/usb1/1-3/1-3:1.0/input/input7 >> >>>> > [ 3537.735403] input,hidraw0: USB HID v1.00 Mouse [HID ffff:0000] >> >>>> > on >> >>>> > usb-0000:00:03.0-3 >> >>>> > [ 3537.735695] usbcore: registered new interface driver usbhid >> >>>> > [ 3537.735866] >> >>>> > /build/buildd/linux-2.6.24/drivers/hid/usbhid/hid-core.c: >> >>>> > v2.6:USB HID core driver >> >>>> > [ 3674.920172] usbcore: deregistering interface driver usbhid >> >>>> > [ 3675.027665] usbcore: deregistering interface driver hiddev >> >>>> > >> >>>> > Seems to be pretty normal, huh? After this, no more messages, not >> >>>> > even >> >>>> > during javax-usb initialization... >> >>>> > >> >>>> > I can see that javax-usb claims the device, it just doesn't control >> >>>> > it. >> >>>> > This >> >>>> > is the complete output from MouseDriver.java: >> >>>> > >> >>>> > Found 1 HID-type interfaces. >> >>>> > Found mouse by SubClass/Protocol >> >>>> > Found mouse by Usage Page/Usage ID >> >>>> > Found HID mouse. >> >>>> > Driving HID mouse, move mouse to see movement events. >> >>>> > Press Enter when done. >> >>>> > Unable to submit data buffer to HID mouse : Error submitting IRP : >> >>>> > Error >> >>>> > 62 >> >>>> > >> >>>> > Hope this can give you a hint of what the problem is... I'll now >> >>>> > take a >> >>>> > look >> >>>> > at the kernel source (ouch)... >> >>>> > >> >>>> > Thanks! >> >>>> > >> >>>> > -- >> >>>> > Gabriel Queiroz Silva >> >>>> > E-mail: [EMAIL PROTECTED] >> >>>> > Tel: +55 61 9604.1412 >> >>>> > >> >>>> > On Fri, Jun 27, 2008 at 11:08 AM, Dan Streetman <[EMAIL PROTECTED]> >> >>>> > wrote: >> >>>> >> >> >>>> >> According to my Linux errno.h file, 62 is "Timer expired". I have >> >>>> >> no >> >>>> >> idea where that would come from, but it's almost certainly coming >> >>>> >> from >> >>>> >> Linux, not javax.usb - all the generic "Error N" errors come from >> >>>> >> failed ioctls into Linux. If you are adventurous you could look >> >>>> >> at >> >>>> >> the Linux kernel USB code to try to find a ETIME error. Or maybe >> >>>> >> check your /var/log/messages file or dmesg output. >> >>>> >> >> >>>> >> On Thu, Jun 26, 2008 at 9:30 PM, Gabriel Queiroz >> >>>> >> <[EMAIL PROTECTED]> >> >>>> >> wrote: >> >>>> >> > Hi all, >> >>>> >> > >> >>>> >> > It's my first post to this list (javax newbie). >> >>>> >> > >> >>>> >> > I'm developing a usb device using an Atmel microcontroller >> >>>> >> > (http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3784). >> >>>> >> > For >> >>>> >> > now, it >> >>>> >> > works like a mouse. The microcontroller has 4 push buttons, and >> >>>> >> > these >> >>>> >> > push >> >>>> >> > buttons make the mouse pointer move around the screen.I >> >>>> >> > >> >>>> >> > I've got this device to work under windows and linux with the >> >>>> >> > default >> >>>> >> > hid >> >>>> >> > drivers, but when i let the MouseDriver example drive it I'm >> >>>> >> > getting >> >>>> >> > the >> >>>> >> > following error: >> >>>> >> > >> >>>> >> > Unable to submit data buffer to HID mouse : Error submitting IRP >> >>>> >> > : >> >>>> >> > Error >> >>>> >> > 62 >> >>>> >> > >> >>>> >> > I've digged through javax-usb code, and the exception is being >> >>>> >> > thrown >> >>>> >> > on >> >>>> >> > the >> >>>> >> > asyncSubmit( UsbIrpImp irp ) method, call on file >> >>>> >> > LinuxPipeOsImp, >> >>>> >> > line >> >>>> >> > 64: >> >>>> >> > >> >>>> >> > getLinuxInterfaceOsImp().submit(request); >> >>>> >> > >> >>>> >> > I understand javax is not being able to send an IRP to the >> >>>> >> > device, >> >>>> >> > but i >> >>>> >> > can't really understand why. Any ideas? >> >>>> >> > >> >>>> >> > Is there somewhere I can understand what does "Error 62" mean?! >> >>>> >> > >> >>>> >> > Many thanks and kind regards. >> >>>> >> > >> >>>> >> > PS: I'm a newbie to USB devices implementation as well, so, big >> >>>> >> > chances >> >>>> >> > of >> >>>> >> > this being something really stupid! =) >> >>>> >> > >> >>>> >> > -- >> >>>> >> > Gabriel Queiroz Silva >> >>>> >> > E-mail: [EMAIL PROTECTED] >> >>>> >> > Tel: +55 61 9604.1412 >> >>>> >> > >> >>>> >> > >> >>>> >> > >> >>>> >> > ------------------------------------------------------------------------- >> >>>> >> > Check out the new SourceForge.net Marketplace. >> >>>> >> > It's the best place to buy or sell services for >> >>>> >> > just about anything Open Source. >> >>>> >> > http://sourceforge.net/services/buy/index.php >> >>>> >> > _______________________________________________ >> >>>> >> > javax-usb-devel mailing list >> >>>> >> > javax-usb-devel@lists.sourceforge.net >> >>>> >> > https://lists.sourceforge.net/lists/listinfo/javax-usb-devel >> >>>> >> > >> >>>> >> > >> >>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> > ------------------------------------------------------------------------- >> >>>> > Check out the new SourceForge.net Marketplace. >> >>>> > It's the best place to buy or sell services for >> >>>> > just about anything Open Source. >> >>>> > http://sourceforge.net/services/buy/index.php >> >>>> > _______________________________________________ >> >>>> > javax-usb-devel mailing list >> >>>> > javax-usb-devel@lists.sourceforge.net >> >>>> > https://lists.sourceforge.net/lists/listinfo/javax-usb-devel >> >>>> > >> >>>> > >> >>> >> >>> >> >> >> > >> > >> > -- >> > -- >> > Gabriel Queiroz Silva >> > E-mail: [EMAIL PROTECTED] >> > Tel: +55 61 9604.1412 >> > > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > javax-usb-devel mailing list > javax-usb-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/javax-usb-devel > > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ javax-usb-devel mailing list javax-usb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
