>> 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. > > WinUsb_GetAssociatedInterface should be the magic you need. Thanks, I'll try that. > >> 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? > > It's still hard for me to figure out understand how this could happen. > If you don't SEND the second buffer until you have RECEIVED the first > result, how could you even get the first result unless the first buffer > was already gone?
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. ~QSE ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
