TIDA-050047: TIDA-050047:

Dear Hussein,

Can you please describe your setup? Are you attaching a PD source or a PD sink to the TIDA-050047? Do you have a battery attached? How is the multimeter connected?

Thanks,

Mike Emanuel

Dear Michael, 

The purpose of the test was to measure the no-load current in PD sink mode to check the efficiency of the controllers. To perform the test, I soldered the multimeters in series to L3 to measure the input current. There is no battery connected.
Also, I want to connect an e-load to TP1 and check the efficiency of the controller at different current values.

Thanks, 

Hussein

Hussein,

How to you have the TPS25750 configured?

Have you connected any other equipment or cables to the PCB?  

It is difficult for me to answer your questions until I know how the part is configured.

Hi Chuck,

The part is configured like follows:
1. source and sink (default)
2. 60 W (20)
3. 100 W(20)
4. power sink
5.6.7.8. NO
9. BQ25790 or BQ25792
10. 16.8 V
11. 5 A
12. 0.6 A
13. 0.08 A

The jumpers JP1 and JP3 are populated.
I do not have any other devices connected to the board except the multimeter and the USB-PD plug.

Do you have test result of the efficiency for the TPS25750?

Thank you 

Hussein,

Do you know what PD contract has been negotiated?  

I want to make sure that I understand the status of the TPS25750 in this test to see what the power should be.

Once we know that status of the TPS25750, then we can work through the status of the BQ25792 to measure the system efficiency.

I do not have a USB C analyzer. But why is that important? Can you please explain more? 

Hussein,

The USB C analyzer will tell me what state the TPS25750 is in and why.

This will help me with determining the state of the TPS25750 to figure out what power state it should be at.

Thank you for the information. Is there any other way to find out which PD contract was negotiated? As I said, I do not have a USB-C analyser?

Hussein,

Let me think about how best to address this without knowing the PD state?

What version of the GUI did you use to configure the board?  

I can also generate a configured binary for you with our upcoming firmware fix that may address this issue

Chuck,

I have used the version 7.0.1.

My understanding is that the PD contract is at least not completely wrong if the voltage is correct. What is unclear is the maximum allowable current. The fact that the Eval board consumes too much current has nothing to do with the PD contract. Is that correct?

 It would be great if you could generate a configured binary file.

Thank you, Mr. Chuck

Hussen,

The fact that the voltage is correct points me to the issue.  I will need to provide you with a configured binary with our latest firmware patch that has need been released with the Web GUI. It will fix the current limit issue you are seeing.

I will provide this patch tomorrow.

Chuck,

That's great. Thank you again
Could you please describe the issue and clarify what exactly is the fix?

Hussein,

I will be putting together a post on what went wrong and what is fixed in the next release.  I will be posting it early next week.

Chuck, 
If you have generated a ready configured binary, could you please send it to me?

Thank you

Hi Chuck, 
Have you posted it? If so, please mention the link here. 
Thank you. 

Hussein,

We have been addressing issues detected during internal testing and will post the GUI as soon as they are all resolved.

I will update this thread with the link once it is updated.