Follow-up. I just tried libusbk, and that worked like a charm. The below failure is with winusb.
These are both using libusbx, sha: 7b62a0a171ac0141a3d12237ab496c49cccd79df Let me know if I can provide anything else. Very Sincerely, Jason On Dec 24, 2013, at 9:55 PM, Jason Kotzin <jasonkot...@gmail.com> wrote: > In windows, 8.1, I’m sending a vendor specific control request that looks > like the following: > > Broken down, this is what an example looks like where variable1 and variable2 > can be 0-255 > > rq = fl_send_msg(0x42, 0x3, variable1, variable2, buf[1], 1, 500) > > The result is that the transfer fails with error code 87, “the parameter is > incorrect”. > > usb log at the bottom of this mail. I’m not quite sure what I’m doing wrong, > I don’t seem to have a problem on mac or linux. It’s only windows, and only > seems to be 8.1. > > Anyone know what this could be? > > Thanks so much in advance. > > Very Sincerely, > Jason > > [ 0.109373] [00000aec] libusbx: debug [composite_submit_control_transfer] > using interface 1 > [ 0.109373] [00000aec] libusbx: debug [winusbx_submit_control_transfer] will > use interface 1 > [ 0.109373] [00000aec] libusbx: debug [usbi_add_pollfd] add fd 2 events 1 > [ 0.109373] [00000aec] libusbx: debug [libusb_get_next_timeout] next timeout > in 4.999635s > [ 0.109373] [00000aec] libusbx: debug > [libusb_handle_events_timeout_completed] doing our own event handling > [ 0.109373] [00000aec] libusbx: debug [handle_events] poll() 3 fds with > timeout in 5000ms > [ 0.109373] [00000aec] libusbx: debug [handle_events] poll() returned 1 > [ 0.109373] [00000aec] libusbx: debug [windows_handle_events] checking fd 0 > with revents = 0000 > [ 0.109373] [00000aec] libusbx: debug [windows_handle_events] checking fd 1 > with revents = 0000 > [ 0.109373] [00000aec] libusbx: debug [windows_handle_events] checking fd 2 > with revents = 0001 > [ 0.109373] [00000aec] libusbx: debug [usbi_remove_pollfd] remove fd 2 > [ 0.109373] [00000aec] libusbx: debug [windows_transfer_callback] handling > I/O completion with errcode 87, size 0 > [ 0.109373] [00000aec] libusbx: error [windows_transfer_callback] detected > I/O error 87: [87] The parameter is incorrect. > [ 0.109373] [00000aec] libusbx: debug [usbi_handle_transfer_completion] > transfer 005526f0 has callback 0040d5d0 > [ 0.109373] [00000aec] libusbx: debug [sync_transfer_cb] actual_length=0 ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
