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.

TPS25750: TPS25750+BQ25792 use gui 7.0.4 problem

Part Number: TPS25750
Other Parts Discussed in Thread: BQ25790, , USB-PD-CHG-EVM-01, TIDA-050047, BQ25792

hi,

   when i use TPS25750 + bq25790, use gui 7.0.4 , eeprom downloads successful.  

    However, if the USB C TYPE is connected while the battery is connected, the TPS25750 does not give power (PPHV =0V), and it can not charge.

    i monitor i2c data between TPS25750 and bq25790,

  •    the first group of data is different, and the data is as follows.

  •    1. 0xd6 0x16 0xc0
  •    2. 0xd6 0x01 0x04 0xec
  •    3. 0xd6 0x03 0x01 0x2c
  •    4. 0xd6 0x06 0x01 0x2c
  •    5. 0xd6 0x05 0x2e

 then,  the group of data is the same from the second group . it sends data periodic.the data is as follows.

   1. 0xd6 0x10 0x80

   2. 0xd6 0x14 0x1c

   3. 0xd6 0x11 0x00

   4. 0xd6 0x12 0x00

   5. 0xd6 0x08 0x0f

   6. 0xd6 0x09 0x0f

   7. 0xd6 0x01 0x04 0xec

   8. 0xd6 0x03 0x01 0x2c      and then cyclic

  However, if the battery is removed and reconnected while the USB C TYPE is connected, the TPS25750 outputs power, and it could charge.


Can you explain why?
  • Hi Lu,

    Can you provide your schematic for me to review? Can you also confirm your test setup, if I understand correctly whenever you have battery connect to BQ device and then connect the Type-C controller you do not see any output voltage and whenever you have Type-C already connected but then reconnect battery you see an output voltage?

    Whenever you connect the Type-C connector with the battery already connected, can you measure your output voltage from BQ device? Can you capture I2C transactions for this as well?

    Regards,

    Brandon

  • The hardware is the USB-PD-CHG-EVM-01,the hardware should be fine. I configure the gui according to the Design Guide: TIDA-050047 using the gui 7.0.4

    ,  and then download to the eeprom.

     yes,you understand correctly.  when i have battery connect to BQ device and then connect the Type-C controller, there is no output voltage. the i2c data is on above.   

      when i  connect the Type-C connector with the battery already connected, there is no  output voltage from BQ device .     the i2c data on the above is for this condition.

      DO there has any bug in the gui 7.0.4. if you have the USB-PD-CHG-EVM-01 pad, you could try to download the eeprom according to the Design Guide: TIDA-050047 using the gui 7.0.4.   and Look at the phenomenon on your side if it is the same?

  • when i have battery connect to BQ device and then connect the Type-C controller, there is no output voltage. I use mcu to read the tps25750 status according to the TPS25750 TRM.The STATUS REG(0X1A) show, VbusStatus(bit 21:20) =11b(Not within any of the other specified ranges),UsbHostPresent(bit23:22)=00b(No host present. This means that no far-end device is presently providing VBUS or the PD Controller power role is Source. )  .The PD_STATUS REG(0X40),HardResetDetails(bit21:16)=09h(Required by policy engine: Sink_WaitForCapabilities).

    I try to use 4cc command "GSkC", but the outputdata is 0x3(Task rejected).  so what should I do next?

    can you try it in USB-PD-CHG-EVM-01 board? or should you send me the factory configuration of USB-PD-CHG-EVM-01, the bin file and json file is also need.

    Thinks!

  • Hi Lu,

    Can you send me your JSON so I can review and flash to EVM here and are you able to capture PD logs?

    When you say your connecting a charger, what is this charger? Is this source, sink or DRP?

    Regards,

    Brandon

  • Hi Brandon,

    Please check the attachment, which is Lu's .json. They can't capture the PD logs. Please help them capture the PD logs. In his description, the way is to sink power from type C to battery. What's more, Lu wants you to check the I2C communication data of TPS25750 and BQ25792.

    I have seen his i2c data, 0x6d is not the I2C address of BQ, which should be 0x6B.

    {"questionnaire":{"version":"7.0.4.4","answers":[0,0,2,1,0,null,1,null,1,null,0,12.6,3.4,0.6,0.6],"options":{},"configID":"0000","vendorID":"0000"}}

    Thanks,

    Gust

  • Hi Gust and Lu,

    I was able to load your configuration onto a USB-C-PD-CHG-EVM and the configuration itself is fine and device behaves normally as it should. I was also able to capture I2C transactions between TPS25750 and BQ25792 and they are the correct transactions to slave address 0x6b to configure for a 3S battery, please see my capture.

    It seems maybe your I2C decoder is chunking data or shifting. Try and deleting data before I2C communication to BQ device and see if that correct I2C decoding.

    I was also able to capture PD logs and the device is sinking the requested PDO correctly as it should, please see log:

    I was only using a 5V, 3A source to test with.

    The device also operates normally as it should since the BQ device will goes through a test sequence to see if a battery is attached before it will enable the converter. Therefore, if you have battery connected then connect Type-C cable the device will operate as it should since the BQ device sees a battery connected and the TPS25750 will send the I2C commands to configure for charging. Whenever you disconnect the battery and reconnect it, the BQ device would have disabled the converter and will only be re-enabled until we send another charge configuration I2C transaction which will not be triggered since the TPS25750 has no way of handling this battery condition. Therefore, the only way you will get this to work is if you have a connect condition on the PD to send the I2C events to BQ device.

    The BQ device may issue an interupt whenever battery is connected, however PD will not be able to handle this interupt. You would need an MCU to handle this interupt, then use I2C read and write through PD to configure BQ device for this condition.

    Regards,

    Brandon