topic Kinetis K20 and WINUSB on windows 10 in Kinetis Microcontrollers https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K20-and-WINUSB-on-windows-10/m-p/791390#M48156 <HTML><HEAD></HEAD><BODY><P>I have a K20 based WINUSB device that fails to start automatically in Windows 10. When I plug it in it shows up in device manager under Universal Serial Bus Devices with the proper name and a question mark. When I look at the enumeration process in the USB Beagle debugger I can see that it failed. On the 3rd call to get device descriptor by the host, the device responds with an empty data packet and Windows gives up.</P><P>Whats strange is if I right click the device in device manager and select uninstall the device starts. It goes through a different enumeration process by making some control transfers rather than request the MS extended compatibility ID OS feature descriptor but it works.</P><P>If I unplug the device and plug it back in we are back to the question mark. With or without the question mark the device is using winusb.sys as the driver.</P><P>Any ideas as to what I might be doing wrong? This is only a problem on Windows 10 and only with a very small percentage of our devices.</P></BODY></HTML> Mon, 18 Jun 2018 20:03:32 GMT ryanlush 2018-06-18T20:03:32Z Kinetis K20 and WINUSB on windows 10 https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K20-and-WINUSB-on-windows-10/m-p/791390#M48156 <HTML><HEAD></HEAD><BODY><P>I have a K20 based WINUSB device that fails to start automatically in Windows 10. When I plug it in it shows up in device manager under Universal Serial Bus Devices with the proper name and a question mark. When I look at the enumeration process in the USB Beagle debugger I can see that it failed. On the 3rd call to get device descriptor by the host, the device responds with an empty data packet and Windows gives up.</P><P>Whats strange is if I right click the device in device manager and select uninstall the device starts. It goes through a different enumeration process by making some control transfers rather than request the MS extended compatibility ID OS feature descriptor but it works.</P><P>If I unplug the device and plug it back in we are back to the question mark. With or without the question mark the device is using winusb.sys as the driver.</P><P>Any ideas as to what I might be doing wrong? This is only a problem on Windows 10 and only with a very small percentage of our devices.</P></BODY></HTML> Mon, 18 Jun 2018 20:03:32 GMT https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K20-and-WINUSB-on-windows-10/m-p/791390#M48156 ryanlush 2018-06-18T20:03:32Z