TPS65987D: The SMBus review for our new design

Hi ,

Thanks for reaching out.

One of our team members will respond to it shortly.

Hi Shubha,

We have pending for this issue and it is urgent, please kindly help to confirm the SMBus register is well or not. thanks.

Hi ,

Can you please share the I2C and PD logs captured

Hi Shubha,

Pleas advise how to get the I2C PD logs, thanks.

Hi Shubha,

I will clarify my question that it maybe make you feel confused:

1. Our CPU is Intel Core Ultra 5, 125U and it is connect to TPS65987DDK directly;

2. We have no TPS65987DDKEVM and FTDI USB-to-SPI/I2C tool to use the TPS6598X-CONFIG GUI, so we only configure the PD in the GUI

and export program from the GUI and load the program to TPS65987DDK by the SPI, so we can't get the I2C PD logs from the project;

3. Now, we can get the PD or USB3.0 signal from CPU if the CPU force output the PD or USB3.0 signal; The function is normal;

4. As we know, TPS65987DDK is automatic recognition the PD or USB3.0 interface; 

5. But we can't get the PD or USB3.0 signal if we use the TPS65987DDK automatic recognition function if the signal are PD or USB3.0 signal;

6. Plesae kindly review our .pjt file and schematic that is there any error for our configuration, we have no idea how to judge the I2C data is right or not;

7. We read the I2C single and logic analyzer for the type-C Forward and backward insertion waveform:

8. The .pjt for your evaluating, and can you help to provide the right . pjt configuration to us, thanks.

5516.SBC-7133.pjt

Hi Shubha,

Can you send your email in the private message, and we can communicate in the email, this issue is urgent, thanks.

Hi Zhang, 

I'm reviewing the PJT and have couple follow-up questions:

1. Double checking with you, are you using DK or DH version of TPS65987? Based on your description it seems like you're using DK in your system but the PJT you provided is intended for DH which is an older version of DK. Using a DH binary will not work with DK. 

2. Which version of the GUI are you using to create your configuration? Did you used the latest v6.1.4 to create your config? 

3. Are you using any Intel Reference Design for this project? 

Thanks and Regards,

Raymond Lin

Hi Raymond,

We are now use the TPS65987DDJ in our board but we use the GUI for Vision 6.1.4 and DDH firmware, and now, the USB 3.0 is well, but the PD is also 

abnormal, please kindly review below question:

1. The DDJ and DDH firmware is mutually compatible or not?

2. If we need to apply the latest vision GUI for TPS65987DDJ?

3. Plesae review below I2C waveform and .pjt file that if there are any error, thanks.

SBC-7133_0709.pjt

Hi Zhang, 

Zhang Liang said:

1. The DDJ and DDH firmware is mutually compatible or not?

DDH and DDJ firmware are not compatible. You need to use the correct device PJT. 

Zhang Liang said:

2. If we need to apply the latest vision GUI for TPS65987DDJ?

DDJ is specifically only for TBT3 applications, if you're not designing a TBT3 Intel Reference Design (i.e. DP only or other Intel Reference Design) you'll need to use a different part depending on the reference design. 

Zhang Liang said:

3. Plesae review below I2C waveform and .pjt file that if there are any error, thanks.

Please confirm which Intel Reference Design and which PD device you are trying to use. DH, DJ and DK should be treated as different devices and their configs/GUI needs to align. 

Thanks and Regards,

Raymond Lin

Hi Raymond,

Please refer to below reply:

Raymond Lin said:

DDJ is specifically only for TBT3 applications, if you're not designing a TBT3 Intel Reference Design (i.e. DP only or other Intel Reference Design) you'll need to use a different part depending on the reference design. 

Yes, our TYPE-C is the USB3/ Disply but not the TBT3;

Raymond Lin said:

Please confirm which Intel Reference Design and which PD device you are trying to use. DH, DJ and DK should be treated as different devices and their configs/GUI needs to align. 

The reference design is Intel CRB 724004_MTL_H_LPDDR5x_T3_RVP_TDK_Rev2p0, but the CRB PD controller of the reference design isn't TPS65987D.

Why is TPS65987D is used in a MTL design? THPS65987D cannot be used here. We don't support designs that don't follow the reference design