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.

TPS65987D: Bug of TPS65987DH when I23C behaves as master

Part Number: TPS65987D
Other Parts Discussed in Thread: TPS55288, TPS65987

Dear TI,

I met a problem in my design in which TPS65987DH is used. The I2C3 interface of 987DH behaves as an I2C master to control a buck-boost converter. But I didn't capture any I2C logs when the I2C trigger event happened. 

So I made two experiments with TPS65987EVM(not DJEVM). The only difference between these two is that one sets I2C1 as master and the other sets I2C3 as master. The rest settings in FW including I2C Record Index are all the same.

When the I2C trigger event happens, only the one with I2C1 as master can output I2C data I want(the slave address 0x74), but the one with I2C3 as master has no actions. 

Could you please check the FW if it is wrong or something missing when I choose I2C3 to be host compared with the version where I2C1 behaves as master. 

Or if there is a bug here, thanks.

BTW, I tried different GUI version, GUI6.1.1,6.2.3,6.2.8, the results are same.

TPS65987_TPS55288_Reference_I2C3_GUI6.2.3_987DDH.pjtTPS65987_TPS55288_Reference_I2C1_GUI6.2.3_987DDH.pjt

  • Hi Jiayu,

    I took a look at your project files and it seems to be the same between the two except the change in I2C master. I'm wondering if maybe the I2C events might not have triggered to send the commands. Are you testing both projects in the same scenario, if so could you describe your test setup? Also, after you changed the I2C master to I2C3 did you also change the pins accordingly on the board to match? 

    Are you able to scope the I2C SCL and SDA pins using I2C1 vs I2C3 in trigger mode? 

    If you haven't already, I would also recommend checking out the Using I2C Master in TPS65987D and TPS65988 PD Controllers application note as it describes more in detail about setting up the I2C.

    Thank you,

    Hari

  • Hi Hari,

     1. Yes, I tested both projects in the same scenario, just with different FW above.

     2. Setup as below, only on 987DHEVM.

    3.  After I changed the I2C master to I2C3, Yes, I also changed the pins accordingly on the board to match. I have checked the HW connection, it's OK, believe it.

    4. Maybe you can duplicate this issue on a 987DHVEVM, just remind, not 987DJEVM

    when I2C1 is set as master:

    When I2C3 is set as master:

  • Hi Jiayu,

    Thank you for providing the pictures. I will try to replicate on my end and see if I run into the same issue and give you an update next week.

    Regards,

    Hari

  • Hi Hari,

    Thanks a lot.

    BTW, I created a JIRA on this issue too. And it seem to be assigned to Prajith but no reply up to now. Let you know this situation in case of waste of BU resource.

    For more details and latest updates, you can refer to https://jira.itg.ti.com/browse/PI_USBC-3420?filter=-2. I have no idea who will be in charge of this issue. 

    Thanks again.

  • Hi Jiayu,

    It seems like Prajith gave some feedback on JIRA and will be debugging it some more. I would recommend to continue this issue on JIRA and uploading the screenshots from here to JIRA as well for Prajith.

    Thank you,

    Hari