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.

TUSB4041I: Can't reactive USB port after short circuit this port

Part Number: TUSB4041I
Other Parts Discussed in Thread: TUSB8041, TPS2561

Hi all,

I am facing a problem with TUSB4041I, when I plugged a shorted cable to a USB port, the BATEN pin of this will be 0, and I couldn't enable charge when I plugged a good cable until I reset HUB. (protect IC is: TPS2561DRCR)

But before when i had used TUSB8041, when plugged a shorted cable the BATEN pin of this will be 1. The USB port could charge right after i unplugged a shorted cable, and plugged good cable + phone.

The difference of this because TUSB4041I behavior or my schematic is wrong? Please give me some advice.

Best Regards,

Phien 

  • Hello,
    Can you provide your schematic?
    Is the TUSB4041 connected to a hub?

    When you say "shorted cable", do you mean a short between VBUS and GND? If so, then PWRCTL#/BATEN going low is the expected behavior because you will be generating an over-current condition.

    Regards
  • Hi Elias Villegas,

    TUSB4041 connected to a "main hub",  and this "main hub" connect to a PC. You're correct about "shorted cable".  When BATEN = 0 after shorted, I couldn't set BATEN = 1 again, although I used SMBUS wrote 0x0F to  Reg06 of  TUSB4041. How can I activate USB port after shorted but needn't reset HUB, or power off and on again?

    I attached a schematic.

    And below schematic i remove EN1, EN2 of TPS2561 from HUB (only control by MCU, EN is always high), because I want USB port can ready right after shorted cable is unplugged. But when I use this some time my USB port is died (only charge device, couldn't recognize device  from PC  ever).

    Best Regards.

  • Hello,
    When you short VBUS to GND on the USB connector the OVRCUR# input on the TUSB4041 is driven low indicating an over-current condition and thus the TUSB4041 will "de-assert" PWRON#/BATEN.
    After this, only the USB Host is able to clear the over-current "flag" on the hub, this is the expected behavior required by the USB spec.
    You need to connect the tUSB4041 to a USB Host and remove the over-current condition so the USB Host send the instruction to the TUSB4041 to "assert" the PWRON#/BATEN signal again.
    Regards
  • Hi Elias Villegas,

    Thank you very much about this, and what about the second circuit, when I only connect pin EN of TPS2561 to MCU, and the port of hub is died, can't detect device any more.

    Best Regards,

    Phien nguyen

  • If the OVRCUR# input is being asserted low, then it will happen the same.
    In order to isolate the power switch from the Hub you will have to disconnect both the PWRON# and OVRCUR# signals.
    If you are going to control the power switches with the MCU, You will have to report to the Host that the Hub does NOT support power management (FULLPWRMGMT#=high) in order to pass USB compliance tests.
  • Hi Elias Villegas,

    Thank you very much. It's very clear.

    Best Regards,

    Phien Nguyen