Re: [Libusbx-devel] Bulk transfer queueing order problem

2013-05-29 Thread qse drf
>> That's the problem. The supposedly synchronous function calls each return >> success >> as I call them in order: OUT 1KB, IN 16B, OUT 1KB, IN 16B >> But the bus trace shows: OUT 2KB, IN 16B, IN 16B >> This is the case even if I add a 5 second delay after each call to >> libusb_bulk_transfer. >

Re: [Libusbx-devel] Bulk transfer queueing order problem

2013-05-28 Thread qse drf
>>> WinUsb_GetAssociatedInterface should be the magic you need. >> Thanks, I'll try that. That was what I was missing! The call didn't appear any where in the Microsoft example. Thanks! > I'm also curious with the results you'll get from bypassing libusbx > altogether. I implemented my test wi

Re: [Libusbx-devel] Bulk transfer queueing order problem

2013-05-28 Thread qse drf
>> I checked the inf created by Zadig, and it claims the entire device. I >> assumed this had to be the case, since libusbx is able to acces both >> interfaces. > > You can modify that INF... But it works as-is with libusbx. > >> I'm going to keep trying to figure out how to use WinUSB directly. >

Re: [Libusbx-devel] Bulk transfer queueing order problem

2013-05-28 Thread qse drf
>>> So this seems like a bug in libusbx that it doesn't seem to honor the >>> synchronous API expectations in this case, as evidenced by the >>> concatenating of the >>> buffers from multiple calls. Or am I missing something? >> >> Can you try using the libusb-win32 or libusbK driver instead of Wi

Re: [Libusbx-devel] Bulk transfer queueing order problem

2013-05-27 Thread qse drf
>> So this seems like a bug in libusbx that it doesn't seem to honor the >> synchronous API expectations in this case, as evidenced by the concatenating >> of the >> buffers from multiple calls. Or am I missing something? > > Can you try using the libusb-win32 or libusbK driver instead of WinUSB?

Re: [Libusbx-devel] Bulk transfer queueing order problem

2013-05-24 Thread qse drf
>> I just installed the driver with Zadig. Yes there are two interfaces, >> interface 0 has a single endpoint and interface 1 has the two bulk end >> points. What confused me was that using libusbx I am able to use the >> bulk endpoints, but with the WinUSB API I can't. > > I don't know how Zadig

Re: [Libusbx-devel] Bulk transfer queueing order problem

2013-05-24 Thread qse drf
> Well, wait a minute here. If you are waiting for the "bulk in" in the > middle, how could you possibly get the sequence you just described? > You wouldn't even send the second 1KB until you'd read the first > response. Are you sending the two "bulk out" calls consecutively, > without waiting for

[Libusbx-devel] Bulk transfer queueing order problem

2013-05-24 Thread qse drf
Hello, I am trying to communicate with a device via a simple bulk transfer protocol under 64-bit Win7, it doesn't require high bandwidth. I don't have access to to the device firmware, but I know it is working properly because I have some software that communicates with it correctly under Win