Dear all,
thanks for your support,
(and sorry for catching the wrong button and not sending to the list before)
I did some Debugging and now I can certainly say:
- This is definitely no libusbx issue,
- There is something strange on my device, but not a timing issue
- It has nothing to do with t
On 28.11.2012 19:01, Tim Roberts wrote:
> The fact that it shows endpoints says that, at SOME point in time, the
> system was able to read your configuration descriptor. Endpoint
> descriptors do not exist on their own -- they are part of the
> configuration descriptor.
Thanks, I just thought that
> We're not doing anything fancy but sending a basic Windows IOCTL for
> that, so I'd rally with Tim in thinking that Windows may not find your
> descriptors compliant enough. And I'm ready to bet that Microsoft's
> USBView [1] will also fail reading your descriptors.
That is right, also Usbview do
> Each version of Windows has grown more and more strict about USB spec
> compliance. Have you ever run the USB Command Verifier test suite on
> this device? It does a pretty good job of exercising the generic
> behavior of your device:
> http://www.usb.org/developers/tools/
>
> Is your devi
Dear all,
currently I have a proplem getting my embedded selfmade usb device running
together with libusbx under win32 (xp)
I think the major point is that for some reason the configuration descriptor of
my device (16D0:05BE) can not be accesed.
Under Linux I am using this device for yers now wit
