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 the power settings (sorry, no cookies) more details: I found a tool for Windows called USBlyzer (http://www.usblyzer.com/) which gave me the right hint. I can see that windows is trying to get the Configuration index 3 Times: first time with a length of 9 Byte, which is handled correctly, second time, immediately after the first call, with a length of 20 Byte which is also handled correctly, and the third time, a few milliseconds later which is not properly handled by my device, answering with a STALL EP0. I don't know right now what is the exact reason, but suddenly while adding extra debug code in my device the error disappeared. I think that I have somewhere some memory leak, pointer stuff etc. Tim was basically right with his assumption Linux is happy with just 2 requests to the Configuration Descriptor, Windows makes 4 requests, thats the reason why one system is working and the other not. As far as I understood libusb_get_config_descriptor gives my just cached values, can I force this function to perform an actual read from the Hardware? regards Arne ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: DESIGN Expert tips on starting your parallel project right. http://goparallel.sourceforge.net/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
