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.

  • TI Thinks Resolved

AM5728: USB1_DP signal issue

Prodigy 80 points

Replies: 10

Views: 219

Part Number: AM5728

I am evaluating the board for SITARA's USB 2.0 port.
In our USB2.0 circuit configuratio SITARA acts as a host.
We turned on the board without connecting a USB device to the “USB1 port”.
And the waveform from “USB1_DP” to VBUS release was acquired.
Only on the USB1_DP side, a phenomenon of rising about 2.5 [V] occurred.(See waveform below)
    
This phenomenon occurred when power was supplied to the “VDDA33V_USB1” pin of SITARA from the power supply control IC (TPS6590377ZWST).
In addition, SITARA has confirmed that it is in a power-on reset state.
【QUESTION1】
   What is the reason why only USB1_DP is excited about 2.5 [V]?
   Is it affected by HI-Z? Or is the internal pull-up affected?
  Does this always occur when using SITARA on the host? . If there is a way to avoid it, please let me know.
【QUESTION2】
   After canceling the power-on reset of SITARA,The USB_DP signal has changed to about 0 [V].
   Is that because the USB 2.0 standard 15KΩ pull-down has been enabled?
  • Hi,

    Your query has been assigned to a TI engineer. Please note that feedback may be delayed due to holidays in the USA.

    Please post the waveform. It's not visible on your original post.

     

    Best Regards
    Biser
  • In reply to Biser Gatchev-XID:

    Hallo,
    A waveform is attached below.
    >Only on the USB1_DP side, a phenomenon of rising about 2.5 [V] occurred.(See waveform below)
    >This phenomenon occurred when power was supplied to the “VDDA33V_USB1” pin of SITARA from the power supply control >IC (TPS6590377ZWST).
    >In addition, SITARA has confirmed that it is in a power-on reset state.
     A waveform is attached below.
     
  • In reply to user6236094:

    Hi,

    I have not seen this reported previously. Which board did you observe this on?

  • In reply to -DK-:

    HI,
    Thank you for your answer.
    I will answer below.
    This is a self-made board created by our company.
  • In reply to user6236094:

    Hi,

    I've tried to reproduce this issue in the lab using our AM572x IDK EVM, but I am unable to see the issue. My suspicion is that your board has a sequencing issue that is not present on our EVM. I am not a power expert, so I'll need to pull in a coworker for this. Please allow a day or so for them to respond.

  • In reply to -DK-:

    Hello,

    Have you verified that the power sequencing for all rails is correct as per the diagram above? This glitch may be a result of a sequencing issue.

  • In reply to -DK-:

    HI,
    Thank you for your answer.
    I will answer below.

    >Have you verified that the power sequencing for all rails is correct as per the diagram above?

      Yes. We have confirmed that the power-up sequence is correct.
      And the power supply of the SITARA processor uses a dedicated power management Unit(TPS659037)

      However, the input timing of "xi_OSC" was the clock input after "vdda_osc" was supplied.
      It looks like the following figure.

      Will the following contents affect this problem?

  • In reply to user6236094:

    Hi,

    Good news, I was finally able to reproduce this in our lab. Initially I was unable to see the issue because I had a USB device attached and even this tiny load was sufficient to squelch the signal. Once I removed the USB device, the 2.5V glitch was visible.

    After conferring with my Design Engineer counterpart, we are in agreement that this voltage on D+ is the result of an internal leakage path that is present prior to chip reset. I measured this leakage at ~200uA which is well within the specified limits for this interface and I/O cell  (3.3V Analog) design so no resulting issues are expected.

  • In reply to -DK-:

    HI,
    Thank you for your answer.
    Please tell me the following points.

    >I measured this leakage at ~200uA which is well within the specified limits for this interface
    >and I/O cell  (3.3V Analog) design so no resulting issues are expected.

    Regarding the above answer, I couldn't understand why this glitch is not a problem.

    If a glitch occurs when SITARA power is turned on,
    if the connected device does not have the resistance to the non-energized state (when VBUS = “OFF”),
    the connected device may be destroyed.

    Also,Does this glitch have no problem on the SITARA side, but does it mean that there may be a problem with devices connected to USB 2.0?

    Can you tell me in detail why there is no problem?

  • In reply to user6236094:

    Hi,

    Given the sheer number of USB devices in the market, I don't think that anyone can guarantee that this artifact will not present a problem for any of them. However, from a practical standpoint I do not expect this to present a problem for a connected device either given that these pins are 3.3V analog I/O on both sides of the connection and that the voltage potential presented while the SoC is in reset is well within the operational parameters for the interface.

    I did review the USB specification looking for guidance on this topic and did not find it addressed.

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.