|
From: Ian M. <ian...@gm...> - 2017-09-13 14:39:57
|
Tim,
Here is the EndPointDescriptor data:
{bLength = 7 '\a', bDescriptorType = 5 '\005', bEndpointAddress = 130
'\202', bmAttributes = 2 '\002', wMaxPacketSize = 512, bInterval = 0
'\000', bRefresh = 0 '\000', bSynchAddress = 0 '\000', extra = 0x0,
extra_length = 0}
bmAttribute = 2 says this is an endpoint for a bulk transfer.
bEndpointAddress = 130 says this is an... NOOOOOOO... this is an IN
endpoint... well there is the problem! It is always the stupid, simple
things that are the easiest to overlook and take the longest to solve...
Tim, Chris, and David,
Thank you for asking the questions that forced me to walk through my own
silly assumptions! It is greatly appreciated!
Signing Off,
Ian
On Wed, Sep 13, 2017 at 2:21 AM, Tim Roberts <ti...@pr...> wrote:
> On Sep 12, 2017, at 12:36 PM, Ian Murtaugh <ian...@gm...> wrote:
> >
> > I am using libusb on Ubuntu and am attempting to send 4 bytes of data
> via an asynchronous bulk transfer. I am able to successfully perform the
> following steps:
> > ...
> > What does a URB status of -2 mean?
>
> Timeout. Exactly what kind of device is this? Are you absolutely sure
> you're talking to a bulk pipe, and that your bulk pipe is ready to accept
> new data? A device is not required to accept whatever you send it.
>
> Tim
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> libusb-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-devel
>
|