• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 64 subscribers
  • Views 460 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TPS2546: Samsung Galaxy S20 doesn't charge in CDP/SDP2 mode

Beyazıt cengiz
Prodigy 90 points
Part Number: TPS2546

Hi,

In our own application, TPS2546 doesn't charge Samsung Galaxy S20 in CDP and SDP2 mode.

As a standard application for us, we use "1111" configuration for CTL and ILLUM_SEL pins. CTL1 configured as logic high by SW and others hardwired to logic high.

According to datasheet , charger should be configured as CDP mode with "1111" config and it can automatically switch to SDP2 . 

We checked almost 20 newly phones and only S20 didn't charge in this configuration.

When I checked 0110 configuration(with rework)(DCP auto), S20 charged with almost 500mA. Data lines disconnected. Vbus discharged.

Does S20 not support Bc1.2?

Do you have a suggestion to use CDP mode or SDP2 mode(without discharge) with S20? 

BR

Beyazıt

  • 0
    TI__Mastermind 30000 points

    Hello,

    I do not have insight on if the S20 implements BC1.2 support. My suggestion is to keep the charger in CDP mode if you system requires USB2.0 data capabilities. If your system does not require USB2.0 data, then you can put the TPS2546 in DCP_AUTO mode. 

  • 0 in reply to Adam Mc Gaffin
    Prodigy 90 points

    Hi Adam,

    We performed a series of test with TPS2546. According to our test results, TPS2546 charge S20 only in DCP mode. There is no need to data capability for android systems, but we need to stay CDP mode for data capabilities MSC and Apple devices.

    As you can see at below Figure1, primary detection and secondary detection correctly performed with S20. Then charging and enumeration started . After the enumeration charging was stopped. You can observe indirectly charging current on Vbus voltage drop at Figure2.

    Summary, If we use only charge cable(no physical data lines), it started to charge. If we use DCP mode it start to charge( data line disconnected). If we use CDP or SDP mode with data + charge cable, it start to charge and enumeration. After enumeration, charge was stopped.

    Do you have an idea, why charging stopped after enumeration? 

    BR

    Beyazıt

    Figure1 : CDP Mode/ Samsung S20

    Figure2 : CDP Mode / S20 / Vbus Monitoring(Dp not measured)

  • 0 in reply to Beyazıt cengiz
    TI__Mastermind 30000 points

    Hello,

    In your second figure with the CDP charging, VBUS seems to drop to 0V after a period of time. Is this due to something on your end? i.e removing the probes while the scope is still capturing. 

    Are you able to capture the FAULT pin in addition to VBUS/DM? The FAULT pin is active low so I am curious if this is triggering before VBUS drops low.