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: Is it required to stream "low region" binaries to PD chip on every initialization if you don't want to use an external EEPROM?

Part Number: TPS25751

Tool/software:

We are planning on using TPS25751 in a couple of new products. I have an EVM here and we've programmed the EEPROM on it a few times using the USBCPD Application Customization tool.

Our application is a dense board so any chips we can eliminate the better, external EEPROM included.

I have gathered enough from the datasheet and related documents to know that this Patch can be up to 17kB (36kB - 2KB) / 2. The example shown in a related thread on this forum streams over 5440 bytes. When I use the USBCPD Application Customization tool and generate a C array or .bin file, it's outputting 13200 bytes or 13180 depending on the method (most likely due to padding to page size).

Here's my question. If I don't have an external EEPROM for the TPS25751 to ping-pong load from, do I have to stream up to 17kB to the TPS25751 every time it's initialized? Is it updating its firmware everytime I do this? Is there a way for me to configure the chip without forcing a firmware update each time? I would prefer sending PD Contract info / Config info to the chip during initialization, something that would be on the order of hundreds of bytes not several thousand.