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: When TPS25750 is used in combination with BQ25792,Part of the time, when the battery is connected first and then the USB PD charger is connected, there is a situation where it cannot be charged

Part Number: TPS25750
Other Parts Discussed in Thread: BQ25792

Hey,

We have created a bin file that can be written to EEPROM using USBCPD_application_Customization Tool. After entering the file, when we first insert the battery and then insert the USB PD charger, there will be no current at the USB PD charger, only voltage, as shown in the figure 1.

fig. 1

When we first insert the USB PD charger and then insert the battery, the battery will resume charging, as shown in Figure 2.

fig. 2

Another issue is that after the battery is charged, the charging protocol does not seem to charge according to the USB PD protocol. From the content shown in Figure 1 and Figure 2, the charging type is APPLE2.4 or BC1.2 (both situations may occur). But when we use a USB tester for testing, we can find that the configured charging protocol is USB PD, as shown in Figure 3.

fig. 3

However, when we attempt to change the output mode to PD and raise the voltage to 9V, the battery will no longer charge, as shown in Figure 4.

fig. 4

The circuit diagram of TPS25750 is shown in Figure 5 and Figure 6, and the circuit diagram of BQ25792 is shown in Figure 7. We believe that the probability of TPS25750 configuration errors is higher. When the device is connected to the battery but not to the charger and the BQ25792 module ADC register is opened through I2C, we found that the values are normal except for the input voltage. However, when the USB PD charger is inserted, the input voltage is still 0. In addition, when we tried to directly connect TYPE-C input to BQ25792 and found that this was feasible in a short period of time, but it caused severe overheating.

Fig.5

Fig.6

Fig.7

The overall problem can be summarized as follows:

  1. When the module is connected to the battery first and then to the USB PD charger, the module will encounter a problem of not being able to charge. Is it a configuration issue with the bin file generated by us using USBCPD_application_Customization Tool? If that's the case, how should we configure it? Or should I use I2Cs to configure TPS25750?
  2. When the module is configured to charge in USB PD mode, the charging method is not USB PD. Is there a configuration issue with the bin file generated by us using USBCPD_application_Customization Tool? If that's the case, how should we configure it?

The bin file and json file configured by USBCPD_application_Customization Tool are attached.

Thank you very much.

{
  "questionnaire": {
    "device": "TPS25750",
    "toolBuildVersion": "1.0.2",
    "answers": [
      null,
      4,
      4,
      3,
      1,
      0,
      3,
      0,
      1,
      1,
      0,
      12.6,
      2,
      0.4,
      0.4
    ],
    "vendorId": "0000",
    "productId": "0000",
    "version": "1.0.0.2"
  },
  "configuration": {
    "data": {
      "selected_ace": [
        {
          "register": 6,
          "data": [
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0
          ]
        },
        {
          "register": 22,
          "data": [
            10,
            48,
            48,
            77,
            0,
            0,
            0,
            0,
            0,
            0,
            3
          ]
        },
        {
          "register": 50,
          "data": [
            0,
            168,
            42,
            44,
            145,
            1,
            38,
            44,
            209,
            2,
            0,
            44,
            177,
            4,
            0,
            244,
            65,
            6,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0
          ]
        },
        {
          "register": 51,
          "data": [
            4,
            44,
            145,
            1,
            16,
            44,
            209,
            2,
            0,
            44,
            177,
            4,
            0,
            44,
            65,
            6,
            0,
            69,
            65,
            6,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0
          ]
        },
        {
          "register": 92,
          "data": [
            127,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            16,
            0,
            0,
            0,
            0,
            0,
            0,
            48,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            12,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            7,
            8,
            9,
            10,
            0,
            0,
            1,
            0,
            0,
            0,
            0,
            0,
            0
          ]
        },
        {
          "register": 117,
          "data": [
            0,
            0,
            0,
            0
          ]
        }
      ]
    }
  }
}

BIN_IN_POST.bin

  • 已经收到了您的案例,调查需要些时间,感谢您的耐心等待。

  • Hi,

    There may be issues with bin file configuration and hardware circuitry.

    We do not have any cases of TPS25750 being used in conjunction with BQ25792, but the hardware and configuration can refer to the official development board

    www.ti.com.cn/.../BQ25792EVM

  • Hello Taylor

    Thank you very much for your support. However, based on the phenomenon, I believe that the possibility of this issue being caused by abnormal hardware circuits or programs in BQ25792 is extremely low.

    In addition to the phenomenon described in the previous post (software can read the degree of BQ25792 register when not charged, and only BQ25792 can be charged when TPS25750 is not placed), we have other evidence pointing to BQ25792 working normally.

    We have read the register readings of the BQ25792 module when the battery is charged (I=500mA) and when it is not charged (I=0A) (see attachment), and we believe that the module should be able to charge normally in both register configurations.The phenomenon described at 0A is more like BQ25792 being ready but not receiving input voltage(voltage was not measured directly at VBUS in Figure 6).

    Another phenomenon that can explain the problem is that when I briefly short circuited 3.3V and GND on the entire board, the module was able to return to normal charging state, which seems to be similar to the TPS25750 module entering the 'PTCH' mode.

    Of course, there may also be issues with the BQ25792 setting, as register 0x1C displays the connected charger type as "Unknown adapter" during charging. If some assistance can be provided in this regard, it would be very helpful.

    Best Regards,
    pengchao wang

    * Created: Wed May 28 14:27:49 CST 2025
    *
    * Format: Register Name  tab Character,\t  Register Address  tab Character,\t  Hexadecimal register value.
    * Device: BQ25790_92
    * BQZ Container: Charger_2_01-bq25790_92.bqz
    *
    REG00	1A
    REG01	04EC
    REG03	0064
    REG05	24
    REG06	012C
    REG08	C3
    REG09	05
    REG0A	A3
    REG0B	00DC
    REG0D	4B
    REG0E	3D
    REG0F	60
    REG10	85
    REG11	40
    REG12	00
    REG13	01
    REG14	16
    REG15	AA
    REG16	C0
    REG17	7A
    REG18	54
    REG19	0032
    REG1B	00
    REG1C	00
    REG1D	01
    REG1E	00
    REG1F	00
    REG20	00
    REG21	00
    REG22	00
    REG23	00
    REG24	00
    REG25	00
    REG26	00
    REG27	00
    REG28	00
    REG29	00
    REG2A	00
    REG2B	00
    REG2C	00
    REG2D	00
    REG2E	B0
    REG2F	00
    REG30	00
    REG31	0000
    REG33	0000
    REG35	0000
    REG37	0000
    REG37	0000
    REG3B	26B0
    REG3D	26CA
    REG3F	02A7
    REG41	0040
    REG43	0017
    REG45	0017
    REG47	00
    REG48	08
    * Created: Wed May 28 14:38:52 CST 2025
    *
    * Format: Register Name  tab Character,\t  Register Address  tab Character,\t  Hexadecimal register value.
    * Device: BQ25790_92
    * BQZ Container: Charger_2_01-bq25790_92.bqz
    *
    REG00	1A
    REG01	04EC
    REG03	00C8
    REG05	29
    REG06	0032
    REG08	0A
    REG09	0A
    REG0A	A3
    REG0B	00DC
    REG0D	4B
    REG0E	3D
    REG0F	60
    REG10	80
    REG11	00
    REG12	00
    REG13	01
    REG14	1C
    REG15	AA
    REG16	C0
    REG17	7A
    REG18	54
    REG19	0032
    REG1B	8F
    REG1C	70
    REG1D	01
    REG1E	00
    REG1F	00
    REG20	00
    REG21	00
    REG22	00
    REG23	00
    REG24	00
    REG25	00
    REG26	00
    REG27	00
    REG28	00
    REG29	00
    REG2A	00
    REG2B	00
    REG2C	00
    REG2D	00
    REG2E	B0
    REG2F	00
    REG30	00
    REG31	01D7
    REG33	006E
    REG35	11D8
    REG37	11BC
    REG37	11BC
    REG3B	2708
    REG3D	2750
    REG3F	02A8
    REG41	0049
    REG43	001D
    REG45	001C
    REG47	00
    REG48	08

  • According to your description, possible root causes include: TPS25750 configuration error, PD negotiation failure, I2C communication issues, and power/ground design defects. You can focus on checking the PD negotiation process, such as using tools to capture PD communication data packets and confirm where the problem lies