• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 63 subscribers
  • Views 369 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TPS25751: INTEGRATION OF TPS25751 with BQ25792

Jefin George
Prodigy 100 points
Part Number: TPS25751
Other Parts Discussed in Thread: BQ25792,

Tool/software:

We are using the TPS25751 as the PD controller and the BQ25792 as the battery charger IC in our design. I have a few questions regarding their integration:

  1. Can the TPS25751 PD controller by default communicate with the BQ25792 charger IC via the I2C lines, given that the BQ25792 has a specific I2C address?

  2. What is the specific application of the ADCIN1 and ADCIN2 pins? Can ADCIN1 and ADCIN2 be connected to the same voltage divider in the circuit?

  3. In our design, we have not included an EEPROM since we have a processor in the circuit. The PD controller and the processor are both connected to the I2C bus. Are there any additional considerations or configurations required for this setup?

  4. What is the application of the I2Ct_IRQ and I2Cc_IRQ pins?

  • 0
    TI__Mastermind 37855 points

    Hi Jefin,

    Jefin George said:
    Can the TPS25751 PD controller by default communicate with the BQ25792 charger IC via the I2C lines, given that the BQ25792 has a specific I2C address?

    Yes, the TPS25751 has some default I2C communication that is enabled when you select a configuration that supports the BQ25792 in the TPS25751 App Customization Tool(Online GUI). All of the compatible BQ devices have an I2Ct address of 0x6B, which is set in the TPS25751 firmware when communicating with the BQ devices.

    One thing to keep in mind is that the I2C messaging from the PD is fixed and typically is not changed unless a bug fix or key feature is needed. See this comment from another thread for some information on the writes we do and additional I2C capability.

    Jefin George said:
    What is the specific application of the ADCIN1 and ADCIN2 pins? Can ADCIN1 and ADCIN2 be connected to the same voltage divider in the circuit?

    The ADCIN pins are required for boot configuration and specify TPS25751 I2Ct address, boot behavior (where to load the fw image from, what power supply to use), as well as dead battery behavior.

    See section 8.3.6 and 8.4.1 for more information.

    What is important is that the ADCIN pins can measure the correct voltage at boot, so yes, they could be connected to the same divider. For initial proof of concept boards we typically recommend individual dividers for each pin, especially when not set on the ADCIN config, as it provides flexibility in the design.

    Jefin George said:
    In our design, we have not included an EEPROM since we have a processor in the circuit. The PD controller and the processor are both connected to the I2C bus. Are there any additional considerations or configurations required for this setup?

    You will need the ADCIN dividers set appropriately and will need to set up your processor to handle the PBMx flow described in the TRM. (section 5.3)

    Regarding the divider settings, make sure to understand the boot behavior in dead battery. If you expect the USB-C port to work properly in dead battery, you will need to use one of the dead battery configurations that enables the sink path by default so your system and processor can receive power in order to program the PD controller.

    Jefin George said:
    What is the application of the I2Ct_IRQ and I2Cc_IRQ pins?

    The I2Cc_IRQ pins are currently unused, but may be used in the future. They would be for handling interrupts from I2C peripheral devices.

    The I2Ct_IRQ pins are used to assert IRQs to I2C host devices on the I2C bus. In your system, it will be used to indicate to the MCU that the TPS25751 is ready to be programmed over I2C.

    There is also a configurable I2C interrupt mask register (0x16) that allows customers to enable specific PD related interrupts to notify the I2C host of specific events. This interrupt mask asserts the I2Ct_IRQ pin.

    Thanks and Regards,

    Chris