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: Power sink firmware developement

Part Number: TPS25750
Other Parts Discussed in Thread: BQ25790, BQ25792,

Hello,

I'm considering using the TPS25750D in a power sink-only battery charger design. I want to do little to no firmware development, so I just wanted to know if this part takes care of all PD negotiations. Can I set the max PPHV voltage and current with a simple I2C write, or do I need to implement a PD firmware stack in a host controller? Thanks!

  • The TPS25750D operates fully independently without the need for MCU intervention for most applications.

    If you review the Application Configuration GUI, you will see that with as few is 10 simple questions, you can fully configure the TPS25750D for application as long as you pick the correct charger.

    For the TPS25713 or TPS25731 you will need a MCU to manage charger termination and any advanced features that you want to use, but if you select either BQ25790 or BQ25792, then the TPS25750 and charger can fully manage the battery charging process.

    Please reach out the the Charger team for any specific questions regarding charger selection or me for further assistance with the TPS25750D

  • Hi Chuck,

    Thanks for the reply! I'm planning on using the BQ25792 actually. I looked at the configuration GUI, but I'm not planning on using the EVM, so I'm still not 100% sure what configuration I need to do to make sure everything works properly. It looked to me like there was a Sink capabilities register (TX_SINK_CAPS) that can be written to to define the sink capabilities. So if I have a host MCU and I write a configuration to this register, the TPS25750D would start at Sink PDO1 and negotiate up to the highest available PDO profile automatically? Besides this, is there any more configuration that must be done? This is all assuming no EEPROM to load a configuration from (I would configure the port controller on host startup). And last question, if no configuration is loaded, will the TPS25750D provide standard USB 2.0/3.0 low voltage/current to the PP5V, which I could use as a low power VIN to the BQ25792?

  • Timothy,

    The last 4 items in the GUI need to be configured to match your battery needs.  This configuration will need to be loaded either through an EEPROM or from the Host MCU.

    The TPS25750 will manage all of the power negotiation without intervention from the MCU.  The BQ25792 supports charger termination, so it is able to almost fully manage the battery with our configuration options.

    We support a mode called AlwaysEnableSink which will give you a 5V contract upon connection that provides power on PPHV for system boot of the MCU which intern can configure the TPS25750 using the PBM flow described in the TRM.