where libusbk is not?
Thanks so much Tim.
Very Sincerely,
Jason
On Dec 26, 2013, at 9:58 AM, Tim Roberts wrote:
> 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
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
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
im interface
> 9. Use the device as needed
>
> Step 6 and 7 are vitally important, to ensure you are trying to reference the
> newly enumerated device. If this is what you are doing already, then for
> debugging purposes you may wish to skip step 5 and print out the address of
>
That has no effect. If I remove that line the problem still persists.
Very Sincerely,
Jason
> On Dec 23, 2013, at 12:06 PM, Matthias Bolte
> wrote:
>
> 2013/12/23 Jason Kotzin :
>> I have a USB device which has two separate devices in it, a bootloader, and
>
I have a USB device which has two separate devices in it, a bootloader, and the
actual firmware.
When I upgrade the firmware, I need to:
send a message to the USB device which will jump to bootloader firmware
release the interface
close the usb device
call libusb_exit()
Then I wait for the boot
