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.

TUSB1064: TUSB1064 cannot be recognized as USB3.1 by laptop.

Part Number: TUSB1064

Hi team,

My customer is using TUSB1064 in a product. The D+/D- pair of Type C connector is connected to MCU and the other signal lines of Type C connector is connected to TUSB1064.

Customer configures TUSB1064 to the USB3.1 mode and plugs the product to a laptop. But the laptop cannot recognize this product as a USB3.1 product. We also tried to configure TUSB1064 to the USB3.1+DP mode. But it cannot be recognized as USB3.1 either. We checked the USB cable and confirmed the cable is OK because laptop can recognize a USB3.1 cell phone through the same cable.

So do you have any advice on this issue?

What' s more, customer has below questions:

1. When TUSB1064 is powered up, what's the default mode without configuring any register? Is it default USB3.1 mode?

2. If we want to configure TUSB064 to DP 4 lanes mode, do we need to configure other register besides configuring 0x0a=0x02.

Thanks.

Best regards,

Wayne

  • Wayne,

    Has the tried both cable orientations? Could you provide a simple block diagram of the application and the schematic?

    1. This is correct TUSB1064 is in USB3.1 mode by default but also in the "no flip" configuration.

    2. You should also consider the AUX to SBU configuration after power. 

  • Hi Malik,

    Thanks for your reply. We tried both orientations of the cable. For one orientation, the board can be recognized as USB2.0 by laptop but cannot be recognized as USB3.0. For the other orientation, the board cannot even be recognized as USB2.0. 

    I will send you a schematic in a separate email. Thanks.

    Best regards,

    Wayne 

  • Wayne,

    Does the customer have the device in I2C mode? From the schematic it appears the device is in GPIO mode not I2C mode. Could you confirm if the I2C_EN pin is pulled up during testing (i.e. I2C_EN = 1 or F)? If device is in GPIO mode and FLIP & CTL0 pin is being used for I2C, this would cause the pin to be pulled high when there is no I2C communication and leave TUSB1064-DCI stuck in a USB 3.1 with Flip mode. This could explain why the device works with only one cable orientation.

    What cable length is the customer testing with depending on estimated loss the EQ level will need to be changed? To debug the current issue I recommend using the shortest cable possible to help eliminate the possibility of improper EQ setting.