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

Reply via email to