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.

TUSB215-Q1: USB2 redriver overheating and failing to work

Part Number: TUSB215-Q1

Hi all.

Hope you can help with an issue.

Designed a circuit following the design example. MID boost while using a thin 1m cable that runs near motors.

When the board was connected to PC (no slave device) it shows up as failed to enumerate USB device in windows device manager.

It was drawing 200mA and the chip got hot. Did not detect any short to ground and measured 0.5V at Vreg output.(should be 1.8V)

Replaced chip, worked for some time (1.8V at vreg) and then developed the same issue again.

My only guess was an ESD event, but would that cause the chip to overheat?

Any advice?

Tks

  • Can you share the schematic?  If you don't want to post you send it to me over direct message.

    Regards,

    JMMN

  • Hi. Here you go.
    Both jumpers were open and zero ohm resistor was installed in Req.
    Usb lines go directly to connectors.

    5V comes from host.

    THank You

  • Hi Marco,

    I don't see anything wrong in the schematic.  Can you confirm how the thermal pad is connected?  If that is not connected with enough solder, there could be issues.

    Regards,

    JMMN

  • If the redriver is connected to the host without any downstream device connected, nothing should show up at the host.  If there is a "device failed to enumerate" error something is incorrect - can you check the ENA_HS and CD outputs?

  • Decent amount of solder. Using stencil. 4 thermal vias connecting to gnd plane.

    No heating when working.

    The only thing I can think off would be ESD event, but find it strange that it would cause heating

  • The device is only "detected" when it fails to work (overheating)

    When working, nothing is detected on the host. Only the slave device is detected after it's connected.

    Will check the voltages and get back to you.

    However, the behaviour has occurred in two different boards so it's unlikely that it is an assembly issue. 

    Tks

  • Ok, if the host is detecting something when nothing is there, that means that there is a voltage on DP or DM that it is interpreting as a pullup.

    If you load a tool like usbview.exe or USB Device Tree Viewer.exe when you see the error - it should tell you if the host thinks it is a full speed device connected or a low speed device connected.  If it is full speed, it thinks there is a DP pullup and low speed = DM pullup.  Of course, scope plots of DP and DM would be good for debug as well.

    Thanks,

    JMMN