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.

TPS65986: BC1.2 detection problems (DCP showing as SDP)

Part Number: TPS65986

We have a few BCv1.2 DCP capable chargers (1) Apple 10W,  (2) Apple 12W, (3) CableMatters 72W that  TPS65986 detects/reports as SDP in our system. A bit stranger, The Cable Matters charger (3) is hit/miss, inconsistent:- more on the side of SDP (Haven’t tracked the frequency that closely to give a percentage).

 

We tried the same set of chargers with off-the-shelf devices: Google Nexus 6P, and Pixel 2. With both devices all the above chargers are detected as DCP.

 

Question(s)/Comment(s):

    1. Is there some known issue surrounding DCP detection?
    1. Any troubleshooting hints specific to TPS. The only difference I see in the register dump 0x00 to 0x72 is 0x1A Status Register - SDP versus DCP. No other difference.

  • Hi Eric,

    I'm sorry you're having problems. Firstly, I would like to do some modification on Apple chargers. 

    Apple chargers don't follow BC1.2 specs. BC1.2 can only support up to 7.5W(5V/1.5A). I have done the test on Apple 12W adapter without any load, the voltage on D+ and D- is 2.7V which means clearly that Apple 12W adapter is not BC1.2 DCP or SDP. 

    Unfortunately, we don't have the Cable Matters charger at hand, it can support up to 75W, please make sure if it can be used as a standard BC1.2 charger.

    The register 0x3F can check the power status of BC1.2 shown in picture below:

    For more information, the link below might help better understand the Apple charger.

    On an Apple 12W USB Charger, how are the D+ and D- lines configured?

    I hope it helps and solves your problem, PLEASE select  This resolved my issue  

    Best Regards,

    Hao

  • This answer about allowed DCP power levels is NOT true, to my understanding.  Per BC1.2 spec, one of the updates from BC1.1 to BC1.2, was specifically to allow DCP to output more than 1.5A.   Figure 4-2, in section 4.4.1 seems to specifically show a Green Line that goes up to ~4.75A, and comment "All Curves Allowed".  I tried to paste below, hopefully it comes through. 

    However, I understand for DCP, D+/D- should be shorted, and as you found, the Apple Charger had 2.7V, which is clearly not shorted.   Any recommendation on how to deal with these, and get more of the available power from the charger?   (SDP reporting will cause current clamp at 500mA, to be spec compliant, right?)

  • Hi Eric,

    Unfortunately, your understanding about DCP seems to be not correct. The required operating range for DCP is in the thick red box  shown in the picture below.  

    As for the 5A in the picture, it’s the requirements from USB2.0 spec, please refer to USB2.0 section 7.2.1.2.1 and read carefully.

    As I mentioned, Apple adapter doesn’t apply to BC1.2. So there’s no way to do the detection for Apple adapter with TPS65986.

    I hope this helps and answers your question, PLEASE select  This resolved my issue 

    Best Regards,

    Hao

  • Update to this question....   we better understand and agree that the original 2 chargers are not BC1.2 compliant, and TPS65986 does not have non-compliant charger detection feature.   However, we've done some testing with a new charger we believe is BC1.2 compliant, and are getting varying detection report sometimes as DCP, sometimes as SDP.  Would like to understand if you have any ideas, or have done any testing with this charger:

    Motorola:  https://www.motorola.com/us/products/turbo-power-15-wall-charger

    Characteristics

    • VBUS [no load] ~5.1V
    • D+/D-  ~15R (zero(0) voltage drop across this pins)

    Observation(s):

    1. Detection is still inconsistent. Failure rate as high as 20% where detected as SDP.
    2. It seems that there are periods when the detection is consistent even after 20 retries. But when it detection start's failing i.e. SDP detected, failure rate is as high as 20%.

    We also checked register dumps after successful detect (DCP) and unsuccessful (SDP) and only differences are in 0x3F and 0x6E registers (note:  0x6E is tagged as "reserved" in TRM)

     

    After DCP successful detect:

    0x3F:  3:  02 73 00

    0x6E:  9:  08 40 20 b8 07 01 00 00 00


    After SDP unsuccessful detect

    0x3F:  3:  02 13 00

    0x6E:  9:  08 40 20 18 47 01 00 00 00

      1. Hi Eric,

        We will try to duplicate it and work with our firmware team, and I will reply when it's confirmed.

        Best Regards,
        Hao
      2. Hao,

        Have you been able to test/replicate?   Also, do you have a list of BC1.2 compliant chargers that we have tested with, that we can provide?   Thanks.

      3. Hi Eric,

        I have tried over 50 times about the detection of BC1.2 DCP over 4 ports, all the result showed the detection were correct:

        I cannot duplicate the failure as you mentioned in the lab.

        From the description of the Motorola wall charger, it's not a BC1.2 compliant product. Please make sure the charger used by customer is a real BC1.2 compliant one. 

        I hope it helps and solves your problem, PLEASE select  This resolved my issue  

        Best Regards,

        Hao