This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP-L132: Device Cannot be detected in Windows10 when using USB3.0 port

Part Number: OMAP-L132

Hi,

regarding this question https://e2e.ti.com/support/processors/f/791/p/801262/2986630#2986630, sorry for the late reply, been busying with other project.

To reply to lding:

We are using SBL. Do you have any sample driver code for USB3.0 that works in Windows10?

Thanks.

  • Hi Elvin,

    Seems there is some incompatibility with Window 10 USB driver.
    Do you have some log on OMAP-L132 side? 
    What happens when connect the device to Widows 10 USB 2?

    Regards,
    Tsvetolin Shulev

  • Hi Tsvetolin,

    I didn't have any log on OMAP-L132 side. So far I have capture the communication using USB sniffer. Based on the findings, it seems like there is no acknowledgement replied from the device on the second descriptor request from the host. The acknowledgement is triggered by the hardware controller or our code should triggered it? From our usb driver side, I didn't see any handling for this acknowledgement. 

    By the way, what OMAP-L132 log did you expected?

    Another finding is that if the Windows7 have both EHCI and xHCI driver then the device can be recognized by the host. However, Windows10 only support xHCI so device cannot be recognized. We are looking for Windows10 that can support both driver to have further test.

    Regards,

    Elvin Soon 

  • Elvin,

    Unfortunately OMAP-L132 is an old device and it does not support xHCI but only EHCI. As Windows 10 USB driver supports xHCI only seems it is incompatible with OMAP-L132.  Probably if you find an Windows 10 USB EHCI supporting driver you will have a solution but we can not suggest you such solution.

    Regards,
    Tsvetolin Shulev