• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 97 subscribers
  • Views 474 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

OMAP3530 latest silicon revision and USB

Jeffs_Fairway
Intellectual 290 points
Other Parts Discussed in Thread: OMAP3530, TPS65920

Have I read the errata correctly, where it implies that silicon revisions 3.1 and later can now have the USB EHCI block connected to one port whilst having the OHCI block connected to another simultaneously?  We've designed with an external HS phy on host port 1 plus a hub to get a couple of HS/FS/LS ports, but it would be nice to interface to the wireless module using host port 2 in tll mode using the OHCI block.  Simply using another port off the hub for this doesn't make sense due to the power consumption.

Regards,

-Jeff

  • 0
    TI__Genius 9460 points

    Jeff,

    Yes, you have correctly read it. This fix is available in OMAP3530 silicon version 3.0 and above.

    Regards,

    Ajay

  • 0 in reply to Ajay
    Intellectual 290 points

    Thanks for that Ajay.  The plan is to use an external phy on host port 1 using the EHCI block (the otg port is using the phy inside the TPS65920), with port 3 using the OHCI block lashed up in serial TLL mode to the GSM radio module.  Does that make sense?  The developer's manual is a bit confusing regarding all this.

    Regards,

    -Jeff

  • 0 in reply to Jeffs_Fairway
    TI__Genius 9460 points

    I don't see any issue with this configuration.

    Regards,
    Ajay

  • 0 in reply to Ajay
    TI__Genius 9460 points

    I have an update on OMAP35x errata which affects this configuration.

    Though the OMAP35x ES3.0 and above made it possible to use one port as EHCI and another port in OHCI mode by introducing two new bits (ULPI BYPASS) in UHH_HOSTCONFIG register to select the either PHY mode or TLL mode for each individual port separately, but when  this configuration was tried on ES3.x, we found another AHB arbiter bug that prevents EHCI and OHCI from being simultaneously operational.

    This newer limitation is getting fixed in OMAP3630/AM37x ES1.1 onward.

    Regards,
    Ajay