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: FTDI to I2C GUI for two devices

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

Hello,

I have two questions:

1) Can we have TPS65981_2_6_7_8 Application Customization Tool accessing two TPS65987 devices through the FTDI/I2C interface, one though I2C1, the other through I2C2? 

2) Is the TPS65987 I2C1 default slave after the POR so ready for the FTDI/I2C GUI or not?

Thanks,

George

  • Hi George,

    1. Just to let you know that in TPS65987D, I2C1 can be master/slave, default is slave and I2C2 is always slave. I2C1 address is configurable through ADCIN2 but I2C2 is fixed to 0x38. So if the 2 devices have the same address, the GUI will configure those devices in the I2C bus. You have to be careful and see if this is what you want. Obviously the GUI will run to whatever the I2C address set there.

    2. Yes, by default I2C1 is slave.

    Regards,

    Peter

  • Hi Peter,

    Thank your for the response.

    To be clarified, can GUI detect two different TPS65987D devices and configure them respectively, provided 1st TPS65987D I2C1 (address 0x23) and 2nd TPS65987D I2C2 (address 0x38)are in the same FTDI/I2C bus?

    Thanks,

    George

    https://www.analog.com/en/products/ltc6560.html

  • Hi George,

    How do you differentiate I2C2 that is in device 1 from device 2 as both have the same addresses.

    In GUI adapter menu, the GUI will write to whatever I2C address written there.

    Regards,

    Peter

  • Hi Peter,

    Please allow me rephrase in another way:

    can GUI detect two different TPS65987D devices and configure them respectively, provided 1st TPS65987D I2C1 (address 0x23, though its pin 27/28) and 2nd TPS65987D I2C2 (address 0x38, through its pins 32/33)are in the same FTDI/I2C bus?

    That is said, for the 1st TPS65987D, the I2C1 (address 0x23, though its pin 27/28) instead of I2C2 will share I2C bus with 2nd TPS65987D I2C2 (address 0x38, through its pins 32/33). Can GUI detect both and configure them respectively?

    Thanks,

    George

  • Hi George,

    The GUI can only detect what's connected to I2C1 based on EVM connections but not I2C2.

    Regards,

    Peter

  • Hi Peter,

    Sorry, do you mean "GUI can only detect what's connected to I2C1" or "GUI can only detect what's connected to I2C2"? From the schematic PSIL060A(001)_Sch.pdf, I2C2 is associated with the FTDI/I2C. Is this the EVM connections you referred to, or am I missing something here?

    And, how GUI know its FTDI/I2C connecting to I2C1 or I2C2? Does it mean GUI only detect address 0x38 as its I2C device? Can you send a link where I can find this information?

    Thanks,

    George

  • Hi George,

    In this TPS65987D EVM, FTDI is connected to I2C2, I was looking at TPS65988D EVM which has I2C1 connected to the FTDI IC.

    So yes GUI only sweeps what's connected to I2C2 in TPS65987D and will only show 0x38.

    You can connect other I2C protocol to write to I2C1 in the other TPS65987D device.

    Some protocol analyzer like Aardvark allow using scripting.

    Regards,

    Peter

  • Hi Peter,

    I am confusing. So you do have EVM with I2C1 connected to FTDI IC? Can you share this schematic? Is there some descriptions from TI docs saying only I2C2 can be used for GUI? The reason I am asking because in the "USB to I2C/SPI Adapter Setting " Menu, I see "Manually Enter I2C Debugging Address" Option allowing different I2C addresses entered.

    Thanks,

    George

  • Hi George,

    What is your test setup actually? Are you planning to use TI EVM and our GUI or just the GUI but with your boards?

    If EVM, then the interface is based on what's connected to the FTDI. For TPS65987D it's I2C2 and TPS65988D is I2C1, we don't have other version of EVM.

    You can find the TPS65988D schematic here.

    The EVM user guide will show what's connected. 

    The manual I2C address allows you to configure different I2C address from the physical interface connected. 

    Regards,

    Peter

  • Hi Peter,

    Yes, we would like to use GUI with our board, where two TPS65987D on board, 1st TPS65987D I2C1 (address 0x23, though its pin 27/28) and 2nd TPS65987D I2C2 (address 0x38, through its pins 32/33)are in the same FTDI/I2C bus. Is this able to be supported by GUI?

    Thanks,

    George

  • Hi George,

    So what do you see the I2C address when you run the sweep I2C address in adapter menu?

    Regards,

    Peter

  • Hi Peter,

    It is in design stage.. I want to make sure design is working. So i would like to get some insight to the GUI which i cannot find in the documentation.

    Thanks,

    George

  • Hi George,

    Have you looked at this guide for example section 2.10? I don't know your design exactly but do you intend to use flash for each TPS65987D device? You can always load your device configuration into flash separately with any I2C adapter. Our GUI can save your project configuration in binary or json which you can use with any other tool. I don't have an EVM that has both I2C interfaces connected to FTDI to test with GUI, but we have customers using multiple TPS65987D devices on their board so it's not an issue there. 

    Just curious, what's the reason you use 2 TPS65987D and with 2 different I2C interfaces?

    Regards