#26 SynchFrame to Isochronous endpoint throws UsbException

TCK
closed-invalid
5
2004-06-08
2004-05-11
No

When I do a StandardRequest.synchFrame() with a valid
UsbDevice and a valid Isochronous endpoint, instead of
getting a data event, I get a UsbException with the
error number -121 (which should be a
UsbShortPacketException based on a previous defect)
instead.

The endpoint address is 0x88, and the endpoint is on
the active Configuration, Interface & Alternate Setting.

Discussion

  • Dan Streetman

    Dan Streetman - 2004-05-24
    • assigned_to: nobody --> ddstreet
     
  • Dan Streetman

    Dan Streetman - 2004-05-26

    Logged In: YES
    user_id=23654

    The -121 bug is fixed in CVS, so a UsbShortPacketException should be
    generated now instead of a UsbException with error -121. Need to do a
    bus trace to figure out if the device (or Linux USB stack) is actually causing
    the UsbShortPacketException or if there is actually a javax.usb bug.

     
  • Dan Streetman

    Dan Streetman - 2004-06-08
    • status: open --> closed-invalid
     
  • Dan Streetman

    Dan Streetman - 2004-06-08

    Logged In: YES
    user_id=23654

    Bus tracing showed that the device is actually rejecting the request.
    According to the USB spec, "If the specified endpoint does not support
    this request, then the device will respond with a Request Error". So it looks
    like the device has not been programmed to support the request, and there
    is no bug in javax.usb

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks