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: Dead battery configuration

Part Number: TPS25751
Other Parts Discussed in Thread: BQ25756

Tool/software:

Hi! I was reading about the Power delivery controller and i was wondering which of these modes in a dead battery configuration will work best for my aplication. What would be the selection criteria between one mode or another? It's just i am having some trouble understanding the different modes.
Thanks in advance!

  • Hi Juan, 

    Thank you for reaching out!

    Please see the following thread for more information on the methods in which the patch bundle can be loaded onto the device. 

    1- When loading the patch from an EEPROM, it is recommended to configure ADCINx as SafeMode.

    2- When loading the patch from an EC/MCU, it is recommended to use either AlwaysEnableSink (when there is a battery charger in the system) or NegotiateHighVoltage (no battery charger). 

    Please let me know if you have additional questions/concerns. 

    Best Regards, 

    Aya Khedr 

  • Hey Aya! Thanks for your response i have still the following doubts:

    1: If there is a bq25756 in the system does it mean that the pd controller controls  the bq (I2C controller from PD connected to bq) or only that it exists in the system? (Just asking to clarify that when the datatsheet says when there is a bq)


    2.When we have a MCU controlling the battery charger and the PD independently, can we use both dead battery configuration (Always Enable Sink, Negotiate high voltage) or only always enable sink?


    3. Independently the dead battery configuration, the booting sequence is always the following? BOOT-> PTCH -> APP I have doubts if depending on the dead battery configuration this sequence changes. 

    Thanks in advance!

  • Hi Juan, 

    1. Yes, its in the case when the PD controller is controlling one of the supported battery chargers via I2C. 

    2. In this case, we would recommend AlwaysEnableSink in order to enable the sink path to provide power to the system while loading the patch bundle over I2Ct.

    3. It typically follows that sequence, yes. See the following table for descriptions of each mode:

     

    Best Regards, 

    Aya Khedr 

  • Thanks Aya! Only two things:

    1. With the respect with the second answer why is it recommended using AlwaysEnableSink instead of NegotiatieHighVoltage? is it because that way we sink currrent faster without having loaded the patch and NegotiateHighVoltage we need to wait untill the patch is loaded to sink current. 

    2. Which is the difference between AlwaysEnableSink and NegotiateHighVoltage ? Is it NegotiateHighVoltage is continously searching for the high voltage the source can provide and the AlwaysEnableSink  has a fixed voltage or do they have other difference.

    Thank you kindly.
    Juan

  • Hi Juan, 

    1.The NegotiateHighVoltage dead battery configuration will load a "default" configuration onto the device in which it will enter APP mode and negotiate a PD contract before the MCU loads the patch bundle. This is not valid to use with our supported battery chargers because there will be no I2C communication from the PD to the BQ before the patch bundle is loaded onto the device. 

    On the other hand, AlwaysEnableSink will enable the sink path but not load any "default" configuration until the patch bundle is loaded onto the device. 

    2. See my comment above. 

    Best Regards, 

    Aya Khedr 

  • Ok perfect that does it, thank you so much Aya!
    Best regards
    Juan.