On Thu, Apr 18, 2013 at 8:52 PM, NicoBats wrote:
>> No libusbx will use libusbK.dll by default if it is present. If it is
>> not present, libusbx will then fall back to WinUSB only mode
>> where libusb0.sys/libusbk.sys will not be supported.
>>
>> You can ask your friend to upgrade libusbK to its
I plugged the device into a linux box and got some better error messages.
"bConfigurationValue" above should be 1 instead of 0, and I was not
respected wLength from the GET_DESCRIPTOR setup packet. And I had a struct
padding problem. After fixing all those things I can now libusb_open()
under cy
Thanks Tim. Descriptors below. I have no endpoints; I want to fool with
control transactions first(little steps). Total length is 18.
Dan.
static const configuration_descriptor_t static_config = {
sizeof(configuration_descriptor_t), // bLength
0x02, // bDescriptorType
0, // wTotalLength (calcu
Daniel Goertzen wrote:
> I have libusbx compiling under cygwin now and can look at the device
> descriptors for all attached devices, but I cannot libusb_open() my
> device. The error given is -12 (LIBUSB_ERROR_NOT_SUPPORTED).
>
> I ran zadig and bound my device to WinUSB, but still no luck (I hav
I have libusbx compiling under cygwin now and can look at the device
descriptors for all attached devices, but I cannot libusb_open() my device.
The error given is -12 (LIBUSB_ERROR_NOT_SUPPORTED).
I ran zadig and bound my device to WinUSB, but still no luck (I have to
admit, I don't exactly unde
Xiaofan,
thanks for your inuput...
Le 18/04/13 07:28, Xiaofan Chen a écrit :
> On Tue, Apr 16, 2013 at 8:00 PM, nico wrote:
>> sorry to be late on that...
>> according to the first line of the user's log, libusbx try to use libusbK
>> drivers instead of WINUSB ones:
>>
>> [ 0.00] [1450] l
