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.

TUSB8041: A few clarificiations

Part Number: TUSB8041
Other Parts Discussed in Thread: TPD6E05U06, , TPD4E05U06

Hello

I have been studying your datasheets, reference designs, and development boards  and I have not seen any mention of any data line termination. Am I safe to assume that if I match the impedance  of my traces to 45 ohm single ended or 90 ohm differential no termination is required, other than the AC coupling capacitor on the TX line? I.e. that it is embedded on the chip where appropriate.

I also wanted to ask what your recommendation on ESD protection devices is. As most of them have footprints significantly larger than my traces there will be a significant impedance mismatch which will cause reflections to occur. Do you have any suggestions how to handle this? I have found that using your TPD6E05U06 the reflection coefficient can be kept below 0.2. The same reflection issue will occur on the hub footprint but can be kept at the same level.

I also wanted to ask about the PWRCTLX pins. They all incorporate a Pull Down resistor and as I am using the GANGED mode of the device I understand that I can leave 3 of them unconnected, leaving no battery charging support on those three ports, and use the last one still with a pull down to enable or disable the current for all the downstream ports. Am I correct in my understanding of the PWRCTLX pins?

Lastly I wanted to ask about the EEPROM. I am planning to allow a microcontroller to share the I2C bus with the EEPROM and the hub in order to reprogram the EEPROM easily if needed. Does the hub have an I2C address? As far as I can tell it only requires the EEPROM to have a specific address but doesn't state its own, presumably because it should never be addressed. Am I missing something from the datasheet that would not allow me to configure the device like so?

I hope that these questions are clear enough, if not please let me know and I will clarify them further. I am currently in the process of making a schematic and selecting components for a new design using the TUSB8041.

  • Hello,
    Correct, you only have to populate the series capacitors on the SS_TX lines, all the other passive components are internal in the Hub, this is required by the USB Spec that's why we don't declare it on the datasheet, we may change that though.

    I would recommend the TPD4E05U06 , we have successfully made design using those diodes.

    The PWRCTLx/BATEN pins have dual functionality, they select the BC support with per-port basis during power-up, after Reset they control the power switches in which case they can be configured as ganged or individual. In few words, the BC is selected in a per-port basis.

    The Hub is not a complete I2C slave, it only uses I2C to load the values from an attached EEPROM.
    The Hub does support a SMBUS master, its SMBUS address can be found in Section 8.4.3 of the datasheet.

    Regards
  • Hello,

    Thank you for that, I had seen the mention of it in the USB standard but I was vary as it was not explicitly stated in the datasheet as well.

    As for the PWRCTLx pins, if I leave them all to be PD on reset, i.e. no battery support on any port, and as I am in ganged mode am I correct in assuming I can use any one of them to control the power to all of the ports? Or am I bound to use the PWRCTLx pin corresponding to my ~OVERCURx pin?

    In terms of the I2C, if I populate the I2C bus with more devices than the USB hub and the EEPROM, will the USB hub cause me issues on the I2C bus? The datasheet details the UM10204 I2C specification which I take to mean that it is compliant with the I2C protocol and by populating the bus with more devices I will not run into any issues caused by the hub's lack of address.

    Kind regards,

    Atli

  • Hello,
    You are correct about the PWRCTLx pins, all of them will toggle together when configured in GANGED mode.
    You can share the I2C bus, the Hub is only a I2C Master, it is not a slave. You may have to tune the pull-up values on the I2C devices since all of them will be sharing the same bus.
    Regards