On Tue, Aug 28, 2012 at 12:40 AM, John Chen <john...@gmail.com> wrote: > I believe I did exactly what is expecting, because I did the same thing in > Window's API and it did not timeout, if you please look at the trace file I > attached, there is not difference in turns of parameters I am passing to USB > Device (between window's API vs LibUSB, Only difference is the > TransferBuffer and PipeHandler , which I believe they should be different.). > > any other ideas?
Maybe you want to give more details of what you are doing in both cases, for example, if you are using the WinUSB API for the first cases "Left file: C:\temp\WinUSBBulkRead", then you may want to post your WinUSB program. You may want tell more about the device and what you want to achieve. And from your trace, it seems to me that bulkread failed too for your first case, just like the libusbx case, the differences are only the internal processing differences between the WinUSB API and the libusbx API. URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER Length: 0x80 USBD Status: USBD_STATUS_CANCELED (0xC0010000) EndpointAddress: 0x88 USBD_STATUS_CANCELED So it seems to me that you do not know how the device works. All in all, you need to understand the communication protocol of the USB device in order to use libusb/libusbx. -- Xiaofan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
