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.

TPS65988EVM: Bus-powered configuration start-up issue

Part Number: TPS65988EVM

Hi,

We are designing a system with Dual USB Type C connectors. PD Port1 will only support USB PD charger whereas a battery-powered device will be connected to PD Port 2.

The following are the use cases:

We would like to support bus-powered HUB on EVM , when VBUS1 (Charger only, Sink) --> PPHV1 = PPHV2 <--> VBUS2 (phone, Source/Sink).

Therefore, we have shorted PP_HV1 & PP_HV2 J11 (8&7) and to (4&3) to support this configuration.

Connected the barrel jacks 20V, open the new project and try to clear Dead battery bit first in Debug mode ==> We got - Reject_CMD  

1. How can we clear the Dead battery bit? 

2. How can after clearing the  Dead battery bit to disconnect the barrel jacks 20V and connect the external charger to PD1 or phone to PD2 without the power interruption?

3. We've tried to configuration the ADCIN1 for BP_NoWait + Configuration 2. Any of S2 switch (4,5,6) setup can't provide the required voltage divider 0.2-0.28  (0.66 - 0.92V)?

Maybe I need to keep the MISO line low S6 during the PD reset in order to get into this configuration or create and program the flash bundle and power up form there?

Thanks

Vitaliy

  • Hello Vitaliy,

    I've assigned this issue to the relevant expert who will respond to you shortly

  • Hi Vitaliy,

    Is there a reason you shorted PP_HV1 and PP_HV2 to VBUS1 and VBUS2? This may cause some issues. You would like to use Port 1 as a sink with a USB Type-C charger and Port 2 as a source/sink with a phone, is this correct?

    Also what were you testing when you connected the barrel jack in debug mode? To clear the Dead Battery Flag you need to execute the 4CC Command 'DBfg' to clear the flag.

    For your second and third questions, are you trying to have your EVM power up in dead battery mode via 20V barrel jack and then connect an external charger to Port 1 which could source power to the PD controller and then connect a phone to Port 2 which could sink power from the PD controller?

    Could you provide some scope captures, your project file and diagrams to help me understand the issue some more?

    Thank you,

    Hari

  • Hi Hari,

    I've enclosed the slides that described our bus-powered HUB configuration.

    I am trying to implement the same configuration on TPS65988 EVM. 

    - Short  J11-7 & J11-8 pins (PP_HV1&2 pins)

    - Short it with external wire to J11-3 & J11-4  pins = SYS_PWR

    - Replace R20 to 300k resistor and Enable S2-5 (ADCIN1 0.2-0.28 DIV) in order to enable the "BP_NoWait" power-up configuration. + Configuration2 (UFP only (internal switch) 5 V at 0.9-A to 3-A sink capability). 

    Now, I apply PD charger 18W to J2 PORT-A connector (PD Port1 controller). The PD controller power-up and enables the internal power path.

    The VBUS1 is connected via the internal power path to PP_HV1 which is shorted to PP_HV2 = SYS_PWR. The SYS_PWR is got 5V from the external charger VBUS1 and enables all internal HUB regulators.

    The PD controller gets VIN_3V3 externally. 

    1. I am not sure what the power-up mode was used by the PD controller.  It seems that PD is power up in "BP_WaitFor3V3_Internal" + Safe Configuration because the SPI_MISO pin is high by default?

    How, can I allow by default the following power up configuration -  "BP_NoWait" + Configuration2 (UFP only (internal switch) 5 V at 0.9-A to 3-A sink capability)? Keep the S6 pressed while the charger insertion and power-up?

    2. Do I still need to clear the "DEAD-battery Flag" by the tool in the debug mode after the power-up?

    3. I open the new Project and selected the TPS65988 config.

    What setup should I select - UFP, DFP, DRP host or DRP power? because my PD Port1 & 2 is operated in different modes?

    Thanks

    Vitaliy

    Configuration 23.06.20.ppt

  • Hi Hari,

    Could you please answer? It's already week is open.

    Thanks

    Vitaliy

  • Hi Vitaliy,

    Yes I think I understand your configuration. If your calculations are good, I think the configuration you are looking for will work.

    1. If your PD controller already had power via VIN_3V3 externally, it shouldn't boot up in dead battery mode. It will attempt to load your configurations automatically from a host or Flash. To boot it in the ROM Default Configuration, yes you would hold down the S6 button while it is booting up on VIN_3V3.

    2. You do not need to clear the dead battery flag, as it will boot normally as long as VIN_3V3 is provided at the time you plug in your Type-C cable.

    3. In the GUI, you should be able to select DRP when creating a new project and then once it's loaded, you should see two different tabs, one for Port 1 and one for Port 2 where you can program them individually to operate in different modes.

    Thank you,

    Hari

  • Hi Hari,

    Thanks for your confirmation.

    I am loaded the NEW project DRP and tried to set up both PD controllers according to my configuration. After, that I have Flash from the current project the serial flash. Now, disconnect the charger from PD port1 and connect it again. I see that SYS_PWR getting into a 9V power contract, meaning at least PD1 has been configurated correctly. 

    The SPI_MISO is high by default and ADCIN1 is set-up for 300k PU & 100k PD (divider of 0.2-0.28). 

    MISO=1

    1. BP_WaitFor3V3_Internal

    2. Safe Configuration(1): The internal power switch from VBUSx to PP_HVx is enabled for the port receiving power. The device does not continue to start-up or attempt to load device configurations until VIN_3V3 is present.

    Therefore, because I keep S6 non pressed and MISO=1 upon the charger insertion and power up, the internal path is enabled and sys_pwr is getting 9V contract from the connected charger.

    I assume in this case, PD is downloaded finally the Flash patch and PD is successfully power-up. How can I confirm it?

    Now, if I keep S6 pressed MISO=0 upon the charger insertion and power up, the internal path is disabled and sys_pwr is 0V. 

    MISO=0

    1. BP_NoWait

    2. Configuration2: UFP only (internal switch) 5 V at 0.9-A to 3-A sink capability TBT Alternate Modes not enabled DisplayPort Alternate Mode not enabled

    I can't understand what is the issue here? Why the power path does not enable during the power-up and the sys_pwr?

    The bottom line for my bus-powered HUB configuration, I would like to enable the power path first when the external power source (charger or device) is connected and download the flash configuration.

    What is the ADCIN1 set-up you can suggest to me to use?

    Thanks

    Vitaliy

  • Hi Vitaliy,

    It seems like your configurations worked and loaded it from Flash. To confirm this, you can use a USB Power Delivery Analyzer device which logs details of the CC messages to see which contract got negotiated and etc. Alternatively, you could also run the board using the GUI in debug mode where you will be able to see the Status Register and such to see which contract is negotiated, the PD controller role and other register information.

    For your second scenario that's strange it didn't load up the Default Configuration 2 as that setting should be fine. When you attempt this, nothing else is plugged in, and then you plug in an external adaptor to power VIN_3V3 is that correct? In this case, the PD controller should power up normally, not in dead battery mode and set it for Configuration 2 if that's what is set. Could you confirm if VIN_3V3 is powered before plugging in the Type-C connection and holding the MISO button?

    If you are trying to boot up in dead battery mode, it will rely on VBUS being powered to program it to Configuration 2, when MISO=0 for BP_NoWait.  Could you provide a scope capture of the boot up sequence? You could also double check the ADC value is set to the appropriate value when the board receives power so it doesn't accidentally set to a different configuration and that VBUS is powered correctly.

    Thank you,

    Hari