Jason Kotzin wrote:
> you can change that to the following:
>
> libusb_control_transfer(handle, 0x42, 0x3, variable1, variable2, buf[1], 1,
> 500);
>
> Maybe that answers my question. I don’t have endpoint 3 on my device, so
> maybe winusb is restricting communication where libusbk is not?
That
Tim -
Thanks for the email, I’m sorry, that was my bad.
you can change that to the following:
libusb_control_transfer(handle, 0x42, 0x3, variable1, variable2, buf[1], 1,
500);
Maybe that answers my question. I don’t have endpoint 3 on my device, so maybe
winusb is restricting communication w
Jason Kotzin 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)
Since we do
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 wrote:
> I
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
