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: BC1.2 implementation and event mapping

Part Number: TPS65987D
Other Parts Discussed in Thread: TPS65987, TPS65988

Hi Team,

Looking through the TRM for the TPS65987/88 as well as the application configuration tool V5.01 and have a question on the BC1.2 implementation.

My customer would like to use the BC1.2 detection to do 2 things.

  1. Detect a USB2 non-PD source via an A to C adaptor as well as a general type C connector (an example would be a USB key) and turn on the OTG function of the charger.
  2. Disconnect the USB bus from the host processor so that the bus resistances do not contaminate the BC1.2 detection.

In the TRM there are 2 events (I’m assuming to the 88 and not the 87)  Event #123 and #124 which are BC1.2_Host_Pull_Down_Enable for port 1 and port 2.

I do not see these available as GPIO events in any version of the configuration tool that supports the TPS65987 or 88.

Is this something that could manually added to the XML file of the project or is this something that would need to be added to the software by TI?

We know we can do this by utilizing an external MCU, however we are  trying to take advantage of the I2C master to control the battery charger.

Digging through the template files for the TPS65988DDH_Advanced_v5_01.tpl and TPS65987DDH_DRP_host_displayport_v5_01.tpl and found the following.

The GPIOEventDictList is different between the two devices, which is understandable given that the 88 is a dual port device, however the TRM makes no indication that the GPIO event map is different between the two.  Based on the TRM I would have assumed that the Event numbers would have been the same, but that only Port 1 would have applied.

In the template for the TPS65988 I found the following:

 

    {'name' : 'Port 0 Custom On HS Mux Event', 'inout' : 'output', 'number' : 123 },

    {'name' : 'Port 1 Custom On HS Mux Event', 'inout' : 'output', 'number' : 124 },

(lines 8550 and 8551)

The indices at the end of each line correspond to the BC1.2 events in the TRM.  There are no similar settings in the TPS65987DDH template.  I also don’t see a debug accessory index in the 987 template.

Is this something that will be addressed in a future update or can the customer make the changes themselves or do they need to look into switching to the TPS65988?

If they do need to move to the TPS65988 and each switch is only 5A, is it possible to parallel them into a single channel if both ports are configured the same?

Thanks!

  • Hi Joey,

    GUI tool version 5.01 has a few errors in it which we failed to catch during the release. We are in the process of releasing the updated version of the tool that has all of these items fixed. This version of the tool should be available later this month. Apologies for the confusion.

    Thank you,
    Eric
  • Hi Eric,

    Can you explain further what errors in the GUI tool 5.01 and how they relate my above questions?

    Re-stating my questions again.

    In the TRM there are 2 events (I’m assuming to the 88 and not the 87)  Event #123 and #124 which are BC1.2_Host_Pull_Down_Enable for port 1 and port 2.

    I do not see these available as GPIO events in any version of the configuration tool that supports the TPS65987 or 88.

    Is this something that could manually added to the XML file of the project or is this something that would need to be added to the software by TI?

     If they do need to move to the TPS65988 and each switch is only 5A, is it possible to parallel them into a single channel if both ports are configured the same?

     

  • Joey,

    These fields were not added to the latest config GUI in error. The latest GUI will have all of these fields configurable. Apologies for the confusion.

    Thanks,
    Eric
  • Thanks Eric. Will look out for the new GUI.

    As a follow up, if the customer ran the 998 in 987 emulation mode, which port is disabled?

    Can they choose to not run in 87 emulation mode and instead parallel both channels to reduce the RDS on of the internal FETs if the configuration of both ports is the same in terms of PDO. Current would still be 5A max. I imagine that I would have to parallel the CC connections and only use the BC1.2 operation of one of the USB connections.
  • Hi Joey,

    If they run the 988 in 987 emulation mode, Port B/Port 1 would be disabled. Port A/Port 0 would be the functional port.
    This mode would not work on the 988 since the CC connections are set up for dual port applications.

    Thanks,
    Eric