TPS25751: patch bundle image loading into the TPS25751 IC

Mayank Mirajkar

Part Number: TPS25751
Other Parts Discussed in Thread: TPS26750,

Tool/software:

Dear Texas Instruments Support Team,

Thank you for your valuable and prompt response.

In accordance with your recommendations for improved trackability, I have initiated a new thread. For further information, please refer to the previous conversation via the following link:
[Refer to link: https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1544525/tps25751-request-for-guidance-on-suitable-pd-controller-for-simultaneous-charging-and-data-transfer-via-host-usb-type-c-upstream-port-of-usb-hub/6000877]

We would appreciate your detailed guidance on the following points:

According to the TI document titled "Application Note for TPS25751 and TPS26750 EEPROM Update Over I2C," please confirm the following connection required for updating the EEPROM patch bundle image via the host MCU.
- EEPROM with I2C Controller of TPS25751 IC
- Host MCU with I2C Target of TPS25751 IC

Can you confirm if the Host MCU is responsible for updating the EEPROM patch bundle image through the TPS25751 IC? Is this the sole method for updating the EEPROM patch bundle image?

Is it feasible for the Host MCU to directly update the EEPROM patch bundle image with the EEPROM connected to the TPS25751 IC? If so, please provide a detailed explanation of the process, including example code.

What is the minimum EEPROM size required for the patch bundle image?

Could you please clarify the differences between "Generate low region binary file" and "Generate full flash binary file" as presented in the Export section of the USBCPD Application Customization web tool?

Based on my current understanding:
- The "low region binary file" is intended for updating the EEPROM patch bundle image via the TPS25751 IC through the host MCU.
- The "full binary file" is designed for directly updating the EEPROM patch bundle image via the host MCU.
- Could you please confirm whether my understanding is correct? If not, we would be grateful for your guidance on this matter.

Thank you once again for your continued support and guidance.

Best regards,
Mayank Mirajkar

24 days ago

0 Aya Khedr 23 days ago

TI__Mastermind 30332 points

Hi Mayank,

Thank you for reaching out!

Mayank Mirajkar said:
According to the TI document titled "Application Note for TPS25751 and TPS26750 EEPROM Update Over I2C," please confirm the following connection required for updating the EEPROM patch bundle image via the host MCU.

EEPROM with I2C Controller of TPS25751 IC

Host MCU with I2C Target of TPS25751 IC

See the below block diagram from the TPS25751 datasheet for I2Cc and I2Ct connections.

Mayank Mirajkar said:
Can you confirm if the Host MCU is responsible for updating the EEPROM patch bundle image through the TPS25751 IC? Is this the sole method for updating the EEPROM patch bundle image?

Yes, the TPS25751 is capable of updating the EEPROM image, assuming an initial image is already present on the EEPROM. The method highlighted in the application note referenced is intended for in-field updates. The TPS25751 is not responsible for programming an empty EEPROM.

Mayank Mirajkar said:
What is the minimum EEPROM size required for the patch bundle image?

A full flash binary image is ~32kB.

Mayank Mirajkar said:
The "low region binary file" is intended for updating the EEPROM patch bundle image via the TPS25751 IC through the host MCU.

The "full binary file" is designed for directly updating the EEPROM patch bundle image via the host MCU.

Could you please confirm whether my understanding is correct? If not, we would be grateful for your guidance on this matter.

Your understanding is correct.

The EEPROM is divided into two regions, high region and low region, to allow for it being updated without invalidating the previous Patch Bundle until the new Patch Bundle has been verified.

Best Regards,

Aya Khedr

0 Mayank Mirajkar 13 days ago in reply to Aya Khedr

Prodigy 80 points

Dear Texas Instruments Support Team,

I would like to express my gratitude for your prompt and valuable response.

Following our previous discussion, we have configured the TPS25751D IC patch bundle image with the EEPROM using the Full Flash binary file downloaded from the USBCPD Application Customization web tool. We have programmed various Full Flash binaries into the EEPROM and tested our board with the iPad A16.

Q1	Select your TPS25751 Configuration
Q2	What is the Maximum power that can be sourced?
Q3	What is the required sink power or power consumed?
Q4	What is the preferred power role ?
Q5	What is the supported USB Highest Speed?
Q6	Do you have a preferred data role?
Q7	Does your device plan to Support BC 1.2 and other legancy charging schemes?
Q8	Do you support Liquid detection on the Type-C connector?
Q9	Do you have a Vendor ID provided by the USB-IF?
Q10	Do you have a desired Product ID?

	Changes in to Web GUI (USBCPD_Application_Customization_Tool)
Full Flash File No.	Question & Answer	Advanced Configuration	Result
1	Q1 - 2 Index Q2 - 15W (5V) Q3 - 15W (5V) Q4 - Power Source Q5 - USB 2 Q6 - DRP Q7 - No Q8 - No Q9 - No Q10 - No	Port Configuration (0x28) - TypeC State machine - DRP Port Control (0x29) - TypeC Current - 1.5A	Charging Host Device Not Communication
2	Q1 - 2 Index Q2 - 15W (5V) Q3 - 15W (5V) Q4 - Power sink Q5 - USB 2 Q6 - DRP Q7 - No Q8 - No Q9 - No Q10 - No	Port Configuration (0x28) - TypeC State machine - DRP Port Control (0x29) - TypeC Current - 1.5A	Not Charging Host Device Not Communication
3	Q1 - 2 Index Q2 - 15W (5V) Q3 - 15W (5V) Q4 - Power Source Q5 - USB 2 Q6 - DFP Q7 - No Q8 - No Q9 - No Q10 - No	Port Configuration (0x28) - TypeC State machine - DRP Port Control (0x29) - TypeC Current - 1.5A	Charging Host Device Not Communication
4	Q1 - 2 Index Q2 - 15W (5V) Q3 - 15W (5V) Q4 - Power Source Q5 - No USB data Q6 - NA Q7 - No Q8 - No Q9 - No Q10 - No	Port Configuration (0x28) - TypeC State machine - DRP Port Control (0x29) - TypeC Current - 1.5A	Charging Host Device Not Communication

However, we consistently encounter communication issues between the iPad and our board.

Notably, our PCB board successfully communicates with the iPad A16 when the TPS25751D IC daughter board is not connected.

We would appreciate your detailed guidance on the following points:

Our primary objective is to enable simultaneous charging and data transfer through the same USB Type-C port (host side). We have selected the PD controller based on your recommendation.
What specific changes to the configuration of the Full Flash binary should be made in order to load the EEPROM using the USBCPD Application Customization web tool?
Currently, what modifications should we implement to fulfil our primary requirements?

Please find attached the schematic of the TPS25751D daughter board as well as our PCB board. It is important to note that we have replaced the TUSB320LB with the TPS25751D IC on the daughter board.

/cfs-file/__key/communityserver-discussions-components-files/196/SCH_5F00_TRACKRIG-MINI_5F00_TI_5F00_-DAUGHTER-BOARD-_5F00_REV_5F00_1V0_5F00_07AUG2025.pdf

Thank you once again for your continued support and guidance.

Best regards,
Mayank Mirajkar

0 Aya Khedr 11 days ago in reply to Mayank Mirajkar

TI__Mastermind 30332 points

Hi Mayank,

I will review and provide feedback by end of week.

Best Regards,

Aya Khedr

Power management

Power management forum

TPS25751: patch bundle image loading into the TPS25751 IC