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.

EHCI suspend ...again

Other Parts Discussed in Thread: AM3517

Am I correct in assuming there is no reliable workaround for the EHCI suspend/resume issue with a SMSC USB3320 PHY?

I am still seeing issues with the A8_1.00 release.

I see SDOCM00069781 is marked as fixed (but how it can be found and fixed in the same release I don't know) but there are still a lot of suspend/resume issues still open.

I am aware of the PHY not comming out of suspend issue but it is not clear if this is a PHY issue or if the EHCI controller is just not issuing compatable timing. 

My platform uses a USB3320 and i have control over the PHY's RESET and power. I would think this could be made to work if by only doing a brute force reset??

Is this still an active issue?

 

  • What issues are you facing and can you reproduce them on the EVM? If so, what is the frequency? Pl. send us steps to recreate

    thanks

    Atul

  • Hi David,

    Are you using the AM3517 EVM reference board or is this issue seen on a cutsom design?

    On the AM3517 reference board, the RST pin of the USB3320 is controlled by the BSP for an optimal suspend/resume sequence. If the RST pin of the USB3320 on your platform is connected to another GPIO, you need to change the registry from the following file:

    WINCE600\PLATFORM\AM35x_BSP\SRC\DRIVERS\USBHS\omap_usbhs.reg

    You can specify the "PortXRstGpio", "PortXPwrGpio", and "PortXPwrLevel" keys for the particular EHCI controller you use and the driver will take care of toggling the RST and PWR pins when required for a proper reset of the PHY.