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.

How to configure external USB PHY via AM3715 USB port 0 (OTG)?

Other Parts Discussed in Thread: AM3715

We are using USB port 0 of AM3715 to communicate a on-board module. An USB3330 from SMSC is used as external PHY. The USB3330 PHY needs to be configured properly before it can function. However AM3715's TRM has no details about how the external PHY could be access via its ULPI interface of USB OTG. The document (section 22.1.6) only lists 7 registers that are used to set up ULPI interface, but nothing about to access to external PHY. It is quite different from those information for USB host controller.

Can some one help to indicate where to find those information? Or those registers listed for USB host also apply to port 0 OTG? Please advise!

Thanks!

 

  • Normally the ULPI PHY is configured by the OTG controller based on the USB OTG driver code.  

     

    What OS are you using?  What PHY function does not seem to be configured properly?

     

    Regards,

    Paul

  • Paul,

    We are using Android. We don't have USB OTG driver for our PHY (USB3330) at this time and we need develop one for it. This question just came out during the development. Can you advise what is the correct approach to development this driver? How can we get more details documents about it?

    thanks

    Jiansheng

  • Jiansheng,

    USB3330 should not need any programming and would get handled by hardware itself. Are you facing any issue with this?

    Ajay

  • We do face problems to send data through OTG, one of the issues is we have to make sure we are able to access to PHY correctly even it doesn't need very much configuration. AM3715's TRM doesn't provide the details about how to push data into into this channel, so we are actually in blind about the situation. We need OTG's data programming details for driver's development and verification. Is any one can provide some details here?

     

    thanks

    Jiansheng

  • Jiansheng,

    Please provide the details of the issue you are facing and what do you plan to access in PHY to fix the issue? musb core document is under NDA restriction and you can contact your local TI person to sign the NDA and get a copy of document.

     

    You can refer below patch in linus's linux tree which add the PHY access functions in linux musb driver.

    http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ffb865b1e4608cf76867f132b9e8df359fdffc91

     

    Regards,

    Ajay

  • Hi, Ajay,

    thanks for the reply. Regarding the MUSB core, are you talking about MentorGraphic? if it is we do have NDA already signed with it to cover it. Please let me know.

    thanks

    Jiansheng

     

  • Yes, I meant MentorGraphics. You can get in touch with your local contact to get a document.

    Ajay