• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 557 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.

OMAP4430 USB Padconf

jon pry
Intellectual 370 points

Hi,

   To facilitate debugging, I am trying to temporarily reconfigure the OTG controllers ULPI pins after musb_hdrc has become active. However, the muxmode of the padconf registers appears to have no effect. I can change all configurations to safe mode and USB continues to operate as if nothing has happened. The CONTROL_USB register seems to suggest that the OTG controller does in fact have some control over the muxmode of these pads. Is there someway I can make these settings take effect?

Thanks,

Jon Pry

  • 0
    TI__Expert 8055 points

    Jon,

    I will look into this issue.  Can you please tell me which board you are using (ie, Blaze, Blaze Tablet, or custom), which OMAP device you are using (ie, OMAP4460 ES1.1), and which software release you are using (ie, 4AI.1.5)?

    Thanks,

    Gina

  • 0 in reply to Gina Glaser
    Intellectual 370 points

    Gina,

       This is a custom board using an OMAP4430 ES2.2 device running L27.INC1.GB-ENG-1.

    Thanks,

    Jon

  • 0 in reply to jon pry
    TI__Expert 8055 points

    Jon,

    I will take a look at the mux mode issue you mentioned, but I wanted to note that L27.INC1.GB-Eng-1 is a very old release.  It was intended as an intermediate engineering release only, and you may run into a lot of bugs.  For Gingerbread, I suggest you move to L27.G.5: http://www.omappedia.com/wiki/L27.G.5_OMAP4_GingerBread_Release_Notes  There are also many more recent releases on ICS, such as 4AI.1.5.

    Regards,

    Gina

  • 0 in reply to Gina Glaser
    Intellectual 370 points

    Gina,

        I will look into this other release. However I believe this is a hardware issue. What I want to do here is activate the UART3 which maybe can be facilitated through CONTROL_USB and the OTG's supposed carkit support. But there is no way to get an external interrupt to trigger carkit.What else can be used to turn it on?

    Thanks,,

    Jon

  • 0 in reply to jon pry
    TI__Prodigy 460 points

    Hello, Jon;  My name is Mike, I am a HW OMAP Apps Engineer.

    A block diagram and/or schematic would be good here to be visualize what you needing to do here.

    Are you trying to use a carkit, or just trying to use the OTG pins for UART3 tx/rx debug purposes?

    To recieve a UART3 interrupt, you will need a connection to Ball B7 (dpm_emu_9/ usba0_dat3/ UART3 CTS/ GPIO20), detecting either a CTS edge, or an edge detection on GPIO_20.

    If you are just needing a debug port, are pins AC24, 21, 25, 22 (UART3 tx, rx, rts, cts) available?

    Kind regards, Mike Oehrlein

  • 0 in reply to Michael Oehrlein
    Intellectual 370 points

    Mike,

        Thanks for you help but I have fixed the problem. Setting USBPHY_PD in CONTROL_DEV_CONF causes things to start working as expected. This isn't a real carkit, just want to use that same kind of method for debugging.

    Thanks,

    Jon