TPS65994AE: Where is the register about TBT3 cable support CLx information?

CJ Kao

Prodigy 75 points

Part Number: TPS65994AE
Other Parts Discussed in Thread: TPS65994, , TPS65994BH, TPS66994

Tool/software:

Hi TI,

I'd like to confirm the TPS65994 series with USB4 ECN(CLx support of TBT3 Cable) implementation.

If the register of 65994 is support TBT3 cable CLx support capability.

Please let me know how to read the registers through I2C.

Thank you.

8 months ago

0 Tommy Lin 8 months ago

TI__Mastermind 31690 points

Hi,

May I know which TPS65994 device you are looking at? AE, BF, or BH?

Regards

0 CJ Kao 8 months ago in reply to Tommy Lin

Prodigy 75 points

Hi Tommy,

TPS65994AE

If that could not support which version could support the ECN.

Thank you.

0 Tommy Lin 8 months ago in reply to CJ Kao

TI__Mastermind 31690 points

Hi,

For the support and to pass PD 3.1.1.8 compliance you will need to use TPS65994BH. Please also keep in mind after April 2025 you will need to move to a different device because after April 2025 everything needs to go through PD 3.2.

Regards

0 CJ Kao 8 months ago in reply to Tommy Lin

Prodigy 75 points

Hi Tommy,

Thanks for your update.

I would like to study to read the TBT3 cable support CLx capability with TPS65994BH and TPS66994?

Could you provide some advisory to us?

BTW, I cannot find the key word CLx/CL1/CL2/CL0s in 6599xBH TRM.

Thank you.

0 Tommy Lin 8 months ago in reply to CJ Kao

TI__Mastermind 31690 points

Hi,

We store those information in the Received SOP Prime Identity data object register as the CLx information will be in the cable response. We did not break the fields down because different cable will have different number of VDOs.

Regards

0 CJ Kao 8 months ago in reply to Tommy Lin

Prodigy 75 points

Hi Tommy,

Is the SOP Prime identity data store in 0ffset 0x49h(3.49 Received SOP Prime Identity Data Object Register of BH TRM)?

Could you provide an example let us understand?

Thank you.

0 Tommy Lin 8 months ago in reply to CJ Kao

TI__Mastermind 31690 points

Hi,

Do you mean like an i2c read transaction and the PD log that has SOP' message?

Regards

0 CJ Kao 8 months ago in reply to Tommy Lin

Prodigy 75 points

Yes.

0 Tommy Lin 8 months ago in reply to CJ Kao

TI__Mastermind 31690 points

Hi,

I will try to get the capture to you by the end of this week. Dallas is anticipating a winter storm so it might cause some delay.

Regards

0 CJ Kao 7 months ago in reply to Tommy Lin

Prodigy 75 points

Hi,

Hope you are doing well.

Could you provide some captures to us?

Thank you.

0 Christodulos Tsongas 7 months ago in reply to CJ Kao

TI__Genius 12905 points

CJ,

Winter storm delayed us + Tommy is out. Are you looking for TBT logs of a valid connection?

0 CJ Kao 7 months ago in reply to Christodulos Tsongas

Prodigy 75 points

Hi Chris,

We'd like to study how to read the cable capability information from 65994BH through I2C.

0 Christodulos Tsongas 7 months ago in reply to CJ Kao

TI__Genius 12905 points

CJ, I have gathered logs of reading the SOP' 0x49 register and the PD logs of the transaction so you can see the PD SOP' response as well. https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/USB4-Cable-with-TBT-SVID-_2D00_-Enter-TBT.tdchttps://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/SOP_5F00_prime_5F00_0x49.sal

Hope these help!

0 CJ Kao 7 months ago in reply to Christodulos Tsongas

Prodigy 75 points

Hi Chris,

Sorry to bother you.

We are not PD expert and we have some questions about the registers 0x49.

1. How to confirm the value of 0x49 is valid.

Is when 0x49[7:6] = 1?

2. Which registers indicate the CLx support of cable?

Could you provide detail description for every bit of 0x49 register?

3. I found the 0x49 register also in the 994AE TRM.

Is that mean 994AE also support to read CLx support of cable?

Could you please kindly give us some advice?

Thank you.

0 Christodulos Tsongas 7 months ago in reply to CJ Kao

TI__Genius 12905 points

We are also unfamiliar with what this CLx is. From context of the ECR, this seems to be about optical cables.

The decoding of the 0x49 register is dependent on the cable response which is why the fields are generic in the TRM. I believe this field is being discussed in ECN: