Other Parts Discussed in Thread: TPS25751,
Tool/software:
Hello TI Support,
We are currently using the TPS25751 and BQ25798 in our design with the configuration as described below. We are encountering an issue where the system fails to charge the battery from the secondary input when the USB-C port (primary input) is damaged. Your assistance in diagnosing and resolving this issue would be greatly appreciated.
System Configuration Overview (Block Diagram Attached):
-
Primary Input: USB-C port connected to
VAC1
of the BQ25798 via the TPS25751. -
Secondary Input: Connected to
VAC2
of the BQ25798. -
TPS25751 Setup:
-
Operating in DRP mode.
-
No USB data (D+/D- connected).
-
SBU1/SBU2 are not used – Liquid Detection is disabled.
-
EEPROM image configured (
{ "questionnaire": { "device": "TPS25751", "toolBuildVersion": "1.0.2", "answers": [ null, 0, 0, 1, 0, 0, 3, 0, 1, 1, 1, 0, 4, 3, 8.4, 1.5, 0.12, 0.4, 0 ], "vendorId": "0000", "productId": "0000", "version": "1.0.0.2" }, "configuration": { "data": { "selected_ace": [ { "register": 6, "data": [ 54, 48, 48, 48, 0, 0, 0, 0 ] }, { "register": 22, "data": [ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3 ] }, { "register": 40, "data": [ 2, 0, 46, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3 ] }, { "register": 41, "data": [ 210, 0, 152, 0 ] }, { "register": 50, "data": [ 1, 168, 42, 200, 144, 1, 32, 44, 209, 2, 0, 44, 177, 4, 0, 244, 65, 6, 0, 244, 65, 6, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ] }, { "register": 51, "data": [ 2, 150, 144, 1, 0, 150, 208, 2, 0, 44, 177, 4, 0, 244, 65, 6, 0, 69, 65, 6, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ] }, { "register": 55, "data": [ 59, 96, 9, 12, 180, 144, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ] }, { "register": 66, "data": [ 26, 0, 8, 0 ] }, { "register": 92, "data": [ 12, 12, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 0, 0, 0, 4, 0, 0, 0, 0, 0, 0, 0, 4, 0, 0, 48, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ] }, { "register": 112, "data": [ 0 ] }, { "register": 119, "data": [ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 127, 0 ] }, { "register": 122, "data": [ 0, 0, 0, 0 ] }, { "register": 123, "data": [ 0, 2, 255, 255, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ] }, { "register": 125, "data": [ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ] }, { "register": 126, "data": [ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ] }, { "register": 152, "data": [ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ] } ] } } }
-
-
ACDRV1 / ACDRV2: Properly implemented with FETs for VAC1 and VAC2 path control.
-
Battery Charging: Allowed via both USB-C (VAC1) and secondary input (VAC2).
-
Battery Discharging/OTG: Enabled over USB port through PP5V rail derived from a buck converter.
- Here is the block diagram explaining the connections
When the USB-C port is damaged, we expect the charger to fall back and allow charging from the secondary input (VAC2). However, in this failure mode:
-
The battery does not charge via the secondary input.
-
The BQ25798 register
Charger_Control_3
(0x12) changes from the default0x00
to0x20
. -
The OTG_OVP/OTG_UVP flag is being set in
FAULT_FLAG_1
(0x27).
This behavior seems to be inhibiting VAC2 charging when the primary VAC1 input (USB-C port) is compromised.
-
Can you explain what might cause the
REG12
value to change to0x20
in this scenario? -
Under what conditions does OTG_OVP/OTG_UVP gets triggered, especially when OTG was not actively engaged from our side?
-
Is there any possibility that the TPS25751 is sourcing 5V back into the system unintentionally?
-
How can we ensure a robust fallback to the secondary input (VAC2) when VAC1 path is faulty or unpowered?
Any insights or troubleshooting suggestions with this configuration would be greatly appreciated.
Thank you,