Shouldn't 3 be 0x03? because of uint16_t?
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/161#issuecomment-30138164--
Sponsored by Intel(R) XDK
Develop, test and display we
Thanks!
It works now perfectly.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/160#issuecomment-29510111--
Rapidly troubleshoot problems before they affect your business.
Right to say, the bug is in windows_transfer_callback, just easy if (io_size >
0) will help.
case ERROR_OPERATION_ABORTED:
- istatus = priv->apib->copy_transfer_data(SUB_API_NOTSET, itransfer,
io_size);
- if (istatus != LIBUSB_TRANSFER_COMPLETED) {
- usbi_dbg("Failed to copy par
I have set a timeout 500ms in libusb_interrupt_transfer().
>From the debug log:
libusbx: debug [hid_submit_bulk_transfer] matched endpoint 81 with interface 0
libusbx: debug [hid_submit_bulk_transfer] reading 26 bytes (report ID: 0x00)
libusbx: debug [usbi_add_pollfd] add fd 2 events 1
libusbx: de
I have a problem with libusb_interrupt_transfer under cygwin. When I want to
read data from a USB device and there is nothing to receive, I get a
Segmentation fault. I managed to backtrace the fault to
hid_copy_transfer_data() in windows_usb.c, line:
memcpy(transfer_priv->hid_dest, transfer_pri
