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: Schematic review of TUSB8041

Part Number: TUSB8041

Hi Team,

Could you help review schematic of TUSB8041 which my customer applies in their robot. Besides, I have some confusion about this device.

The schematic can be seen in this link: /cfs-file/__key/communityserver-discussions-components-files/138/robot_5F00_usb3_5F00_hub_5F00_board_5F00_v10020220216.pdf

1. The pin definition of TUSB8041 is different in datasheet and EVM schematic, could you help check which is right? 

TUSB8041 EVM: /cfs-file/__key/communityserver-discussions-components-files/138/tusb8041papevm.pdf

TUSB8041 d/s: /cfs-file/__key/communityserver-discussions-components-files/138/6747.TUSB8041.pdf

2. The resistor on USB_R1 is different also.  9.53k ohm in d/s and 9.09k ohm in EVM, could you help check it?

3. Can TUSB8041 work when leave I2C pin floating. And what are the general configurations in E2PROM?

Thanks and looking forward to your reply.



  • Hi Jasper,

    1. The TUSB8041PAP schematic uses the PAP - TUSB8041-Q1 part

    TUSB8041RGC schematic uses the RGC - TUSB8041 part: - we can provide the PCB / SCH file if needed.

    2.  The R1 resistor can be adjusted. 9.53K is the recommended nominal value:

    3. I2C can be left unconnected.  SMBUSz should be left unconnected or pulled up to prevent unexpected SMBUS mode entry.  This app note provides an overview of the EEPROM registers:

    Schematic feedback:

    • Leave GANGED unconnected since the power controls are not used.
    • USB_VBUS is a detection input and should only be high when an active host is connected.
    • Make sure if there are on-board USB 3.0 connections they connect TX to RX and RX to TX.
    • There is an internal pullup on GRSTz, the external pullup could impact reset timing if U5 is not populated and a passive reset is used.
    • USB-IF requires overcurrent reporting through the hub for compliance, but functionally it is not required.