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.

TUSB1046A-DCI: TUSB1046A-DCI

Part Number: TUSB1046A-DCI
Other Parts Discussed in Thread: TUSB1064

Dear TI Sirs

Regarding with TUSB1046A-DCI plan was to use the possibility to implement USB3.1 and Displayport equalizations by EQ settings based on programmed values of each of the EQ registers not EQ settings based on sampled states of the EQ pins (SSEQ[1:0], EQ[1:0] and DPEQ[1:0]). DPEQ0/A1 is connected to GND and SSEQ0/A0 is connected to 1 because of I2C address setting. In order to save PCB space rest of configure resistors are not included. Above mentioned ought to be arranged by setting EQ_OVERRIDE bit 1 in General Registers (address = 0x0A). If EQ_OVERRIDE bit 1 then EQ settings can be changed in Displayport and USB3.1 Control/Status Register.

 

I noticed that when EQ_OVERRIDE is set 1 and USB3.1 only mode is enabled before connection of USB Type-C connector (with Alt Mode interface) EQ_OVERRIDE bit will be reset to 0 when connector is connected. Also if EQ_OVERRIDE is set 1 before removal of USB Type-C connector it will reset to 0 after USB Type-C connector. Is this correct?

 

When:

  • EQ settings values have been changed in Displayport and USB3.1 Control/Status Registers EQ_OVERRIDE bit being 1 and USB3.1 only mode selected.

 

  • USB Type-C connector connecting and reconnecting will be done (connecting and reconnecting cause EQ_OVERRIDE to be set 0)

 

  • Which EQ values will be used in equalization either changed values from Displayport and USB3.1 Control/Status Registers or sampled state of the EQ pins (SSEQ[1:0], EQ[1:0], and DPEQ[1:0])?

 

TUSB1064 seems to have very much same register structure as TUSB1046A-DCI. Does it behave in the same way as TUSB1046A-DCI?

  • Pekka

    TUSB1046/1064 will not change its EQ_OVERRIDE bit on its own when USB Type-C is plugged/unplugged. Would you please check the firmware of the PD controller to make sure the PD controller is not writing to the registers when Type-C is plugged/unplugged?

    Thanks
    David