TPS65987DDH: URGENT charge problems on smartphone with a dead battery

Hello,

I use the evk board and I got the same problem , but I've got more details with the debugs mode tool. see below some screen shot :

The status

The boot Flags :

The CC communication 

Hi David,

It seems like the PD controller is operating as it should, it's trying to be the Source and is sending out Source Capabilities. However, from the PD log, it doesn't seem to be receiving any communication or a request for one of the PDOs from the smartphone. 

Could you try using a different smartphone as well and maybe after that testing with a different USB Charger?

Thank you,

Hari

Hi Hari,

This smartphone is charging when it is plug to a HUB, PC, or power charger USB,  with à USB2.0 cable, in this case there is no USB 3.0 protocol . The PD should work when this happen ?

The smartphone is not power on, is in dead battery sate . and when I use à USB C to USB 2.0 cable the smartphone is not charging.

Do you think I didn't set correctly the configuration of the PD ?

Best regards

Hi Hari,

 do you understand why in PD protocol in the line 1, 2, 3 The PD sen SOP_PRIME ? , and why in the line 5 with have a good CRC, and the system restar?

Best regard

David

Hi David, 

Could you also show you Data Status register in debug mode? Also, if you could share any scope captures of the CC, D+/D- and VBUS pins that would also be helpful.

So you're saying when you use the EVM with the smartphone still with some charge, you can see it charging but then when it is completely in dead battery it won't charge? Have you also tested this with other smartphones?

 The PD also isn't sending the SOP_PRIME messages, these are more the Type-C cable communications. There doesn't seem to be any resets in the PD log, it will just send the Source Capabilities message until it receives a response.

david Laurent said:

I but the power supply of the smartphone VUSB_SP on the Vbus1 and Vbus2 of the TPS65987. And the 5V of the charger to PP_HV1 et PP_HV2

Could you elaborate on this a little more, I'm not sure I understand here as I thought you were just using a cable to connect to the smartphone.

Also, I looked at your project configurations and I can suggest that in Port Control register you can try to enable BC 1.2 DCP advertisement for the Charger Advertise Enable field.

Thank you,

Hari

Hi Hari,

to be more efficient I did a pdf document of the goal our project and the test we  have made.

Presentation of charging prb to TI.pdf

also you will find the project file use on the evaluation board .

DFP mode test.pjt

It will be good if we can chat about this problem

I'm  waiting your answer.

Best regards 

David 

Hi Hari,

I found how to create the problem it is when the A50 ( smartphone ) is power off state, it is plug to receptacle USB C by a cable to TPS65987 EVM. You power up the board , the A50 it is charging . If I power of the board ( our case it is when our product it is taking out of the charger) and after few second I power on the EVM board the A50 it is not charging.

Below the scope when the power is turning off :

Hi David,

It seems the phone is not being responsive to any of the source capabilities. I took a look at your project configurations and have some suggestions you can try.

In Port Configuration register, you may provide VCONN support for both UFP/DFP. Also, in Port Control, I would recommend checking the boxes for Initiate Process to Sink, Process Swap to Sink, and Process Swap to Source, as well as the externally powered bit. Then, in your Source Capabilities register, it may also help to select USB capable option for the PDOs.

Thank you,

Hari

Hi Hari,

thank you for your help, but I try that you ask for and this change nothing. I have further question :

About the Boot configuration I choose BP_waitFor3V3_internal (0.24) and safe configuration do I need to change ?

Also if I plug and unplugged the smartphone nothing change

But if I plug the smartphone to the Samsung adaptateu is charge (9V 1A)  and if  I reconnected to the EVM is start recharge normally . Do I need to put somme pull up or pull down on the line CC. for the moment only CC1 is connected the CC2 line is not connected.

below the config register as you ask me :

Best regards

David

Hi Hari

Hari Patel1 said:

So you're saying when you use the EVM with the smartphone still with some charge, you can see it charging but then when it is completely in dead battery it won't charge? Have you also tested this with other smartphones?

I tried with an ASUS smartphone and I get the same problem.

There is no thinks to do to force the PD to be in source mode when it detects the barrel jack ?

Best regards

David

Hi Hari,

I'm right to connect only one CC line between the smartphone and the PD ?

Thank you for your answer

David

Hi David,

No I recommend connecting both CC lines because it will depend on the orientation and the pull down resistors which will determine which CC line gets connected. 

Also, yes I noticed you don't have the barrel jack event on the IO Config register. I would recommend having this GPIO event configured and you will have to just connect the GPIO that you choose to the barrel jack output, SYS_PWR for example. Both of these 2 things may be causing the issue.

In addition, you may also have to adjust your peak current settings in the Source Capabilities, PDO1. Instead of 100% you may need to select 130% or so as it seems like it could also be an OCP issue.

Thank you,

Hari

Hi Hari;

I made some new test and some news change in the project:

First it is my new project : DRP mode barel jack 0 source 1A.pjt

Because My charger can charge more than 1A under 5V, I change the source capability , also my board is always connecter to the smartphone I decide to change the receptacle type to : UCB C plug , like this I'v didn't have any more the SOP' message.

But When the Smartphone is not ON and I charge it sometime the system go in the loop and it is not possible to stop it event if I stop the charge ....

Below the packet message from the T2C Lecroy analyser :

and the scope of the line ;

Thank you in advance for your help

Best regards

David

Hi David, 

This looks like it may be OCP or OVP issue. I noticed a few settings you could change. The SOP' messages you're mentioning is communication from the Type-C cable. Those messages are not an issue, simply the messages from the connector. Therefore, I believe when you change it to a USB-C Plug I believe it's acting as a cable. You may reference the USB-IF PD Specification and the Cable Connector Specification documents for more detailed information regarding this. 

Therefore, in Port Configuration, I would recommend changing it back to being a Standard fully-featured Type-C receptacle. In addition, if you'd like to use the OVP Trip Point value that you currently have of 14.72 V, I would recommend changing the Over Voltage Protection Usage field to Disconnect VBUS if voltage exceeds the OVPTripPoint.

Also, in Port Control, I would recommend changing the Type-C current field to 3A (Strongest Pullup) option. This won't necessarily change your source capabilities but it will allow more current should the port partner require it.

Thank you,

Hari