• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 32 subscribers
  • Views 2280 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

some issue about the TUSB1210 USB ULPI phy -- issue

kerr chang
Genius 4075 points
Other Parts Discussed in Thread: TUSB1210

Hi

         We faced some issue when using this USB ULPI phy .  it seems that TUSB1210 doesn't support hot-plug function.
We found that once the down-link(DM DP) of TUSB1210 doesn't have any connection when TUSB1210 has power on completely for a while, then we can't connect any device successfully any more.
Take oue circuit for example, we can't connect the USB hub(U1305) successfully when TUSB1210 has power on completely for a while.
And we also can't connect the USB hub successfully when we reset USB hub IC again.
 
 
Please refer to the attached file as our circuit about USB ULPI phy.
Is there any design error on TUSB1210?

  • 0
    TI__Mastermind 36085 points

    Hello Kerr,

        Could you confirm that the supply voltages are stable during the issue, also please verify that the input clock  is running within the specs (datasheet section 4).

    Best regards,

    Diego.

  • 0 in reply to Diego Cortes
    Genius 4075 points

    HI

    We have checked the clock signals ( REFCLK and ULPI clock) and both clocks are normal when this issue happened. At the same time, the power (1.8V and 3.3V) is OK as well.

    The clock is 19.2Mhz.

  • 0 in reply to kerr chang
    Genius 4075 points

    Hi Sir

                Did you have any idea for this issue?

    We have checked the clock signals ( REFCLK and ULPI clock) and both clocks are normal when this issue happened. At the same time, the power (1.8V and 3.3V) is OK as well.

    The clock is 19.2Mhz.

  • 0 in reply to kerr chang
    TI__Mastermind 36085 points

    Hello Kerr,

        This is the first time I heard about such issue, so as a next step I would like to confirm a few things:

        1) Is the issue present on more than one unit?

        2) What is the failure rate?

        3) Which OS, Host controller and Driver are being used on the system?

        4) Is the issue present with a different Os / Driver? 

    Best regards,

    Diego.

  • 0 in reply to Diego Cortes
    Genius 4075 points

    Here are our reply.
     
        This is the first time I heard about such issue, so as a next step I would like to confirm a few things:
        1) Is the issue present on more than one unit?
    [Ans]: This issue presents on every board.
        2) What is the failure rate?
    [Ans]: It happened 1~2 times around every 20 times power-on cycle.
        3) Which OS, Host controller and Driver are being used on the system?
    [Ans]: Our OS is Android 4.2.2 and the host controller is TI OMAP4460 and we used the driver which is orginal enclosed in kernal 3.4.
        4) Is the issue present with a different Os / Driver?
    [Ans]: We don't have any other sample runing other OS/Driver.