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.

TPS65987D: Power Duo Mode Issue

Part Number: TPS65987D
Other Parts Discussed in Thread: TPS65987

Hello,

I am just testing with the TPS65987EVM and the Application Customization Tool for my new project.
I want to design a USB-C 20V 3.5A Sink with the TPS65987. For this I would use the TPS65987 in Power Duo Mode.
I configured PP1 and PP2 as Sink Only and activated the Power Duo Mode in the Customization Tool and configured two Sink PDO’s. One for 5V the second for 20V.
With switch 6 of S4 activated (Boot Mode = NoWait) this setting is working and both PP1 and PP2 are switched through.
But in Boot Mode = Wait for3V3_Internal only PP1 is switching on. PP2 is switched off. P3V3 is running. The rest of the configuration is running. Only PP2 is not working - Why?

Regards Markus

  • Hi Markus,

    Are you operating the EVM from dead battery state or as a powered sink (power jack connected to EVM)? If it's operating from dead battery state, you'll need to send 4cc command 'Dbfg' (Clear Dead Battery Flag) for the PD to operate normally. 

    Thanks and Regards,
    Raymond Lin

  • Hi Raymond,

    thanks for your fast replay.
    Yes, I am operating the EVM in dead battery mode. No external power is connected.

    How can I send the 4cc command. Only with an additional Microcontroller?
    I don’t want to add an additional Microcontroller to my design (cost sensitive).
    Can I reset the flag with a GPIO?

    This comment to the BP_WaitFor3V3_Internal config I read, but I understood it in this way, that the Controller opens the PP1 Path, an external regulator makes the 3.3V  for VIN_3V3 and the controller is booting his configurations  and everything is fine.

    In your USB-C-PD-DUO-EVM board you solve this with the NoWait option. Is this a suitable way to solve this? Or will we get in trouble with this?

    Is there another way to solve such a design.

    Thank you very much.
    Regards Markus

  • Hi Markus,

    The TPS65987EVM comes with a built-in FTDI chip that can act as a microcontroller. When the EVM is powered on and the micro-USB port is connected to your computer, you can access 'Debug Mode' through our GUI which includes more features to test with, including sending 4cc commands listed available in our Technical Reference Manual. 

    Here is a link to a tutorial that walks through how to set up debug mode, section starts at 2:34 minute mark: https://training.ti.com/tps6598x-gui-tool-displayport-alternate-mode-debugging?context=1140344-1140208 

    What is the current setting you have enabled on ADCIN1 and ADCIN2? 

    Thanks and Regards,

    Raymond Lin

  • Hi Raymond,

    the final solution is a own PCb, not the EVM. In this I don’t want to implement a microcontroller,  FTDI or something else. It is very cost sensitive.

    My settings:
    Switch 1-3 Off
    Switch 4-6:
    4 only on -> there I have the problems with the powerpath
    6 only on -> the powerpath is working

    My Questions:
    1. Is NoWait mode ok or will I become in trouble with this mode – in any thinkable possibilities with USB-C? (Your Duo EVM is using this mode)
    2. Are there other solutions to delete this flag? (GPIO or something else)
    3. Can solve the external powerpath this problem?

    Regards Markus

  • Hi Markus,

    Let me check internally and get back to you by Wednesday!

    Thanks and Regards,

    Raymond Lin

  • Hi Markus,

    1. This is the behavior of BP_NoWait:

    There should be no issues with this setup, when switch 6 is enabled this is the default configuration:

    2. You can use GPIO input event "Barrel_Jack_Event", when this GPIO input event is toggle high the PD controller will clear the dead battery flag and attempt a Power Role Swap to become a Source (refer to the technical reference manual for more information):

    3. Test out the configuration above and see if this resolves the external powerpath issue. 

    Thanks and Regards,

    Raymond Lin