TPS65982: TPS65982 in sink mode I_PP_EXT current can't read from ADC

Hello,

I need your GUI version and firmware version, as mentioned in the other thread.

Thanks,

Emma

Hi, Emma

The FW configure tool version and base FW version show as below

Hello,

I will check in to see if that fix is in the firmware you are looking for.

Thanks,

Emma

Hello, Emma

Any update?

Hello,

I am still following up on this. I will get back with you tomorrow afternoon. 

Thanks,

Emma

Hello,

I am still in the process of looking into this firmware fix. I will be out next week and will return the following week. I will follow up with you then.

Thanks,

Emma

Hello,

Can it fixed by firmware?

Hello,

Yes the firmware fix for this should be there. Can you explain how you are reading the ADC?

Thanks,

Emma

Hello,

When I negotiated as Source, then use I2C command to show all tps ADC, I_PP_EXT can show the Source current successfully;

When I negotiated as Sink and relay to flip the SENSEP/SENSEN, use I2C command to show all tps ADC, SENSEP can show the negotiation voltage is 5V, but I_PP_EXT show the current is 0.0000 mA, I can sure current have flow through the sense resistor.

Hello,

I see you have a mux for the sense lines. The firmware automatically flips the sensing internal in the TPS65982 so I believe this mux is causing the issue. Can you leave the mux in one position and see if you see the same behavior?

Thanks,

Emma

Hello,

I keep the Relay same with Source mode, and when I negotiated as sink, I_PP_EXT still can't read the current

TPS65982 Datasheet shows that need to flip the SENSEP/SENSEN, and the Demo board also filp when as Sink.

Hello,

Are you able to see this behavior using the EVM? If so I can test from my side as well.

Thanks,

Emma

Yes， It shows the same behavior using EVM,

1.Using the EVM negotiated as Sink, and keep R5 R3 stuff

I_PP_EXT shows current 0.00000mA

2. NC R5 R3, stuff R6 R2, same result

Below Link also use EVM and also the same issue

e2e.ti.com/.../2280701

Hello,

This does appear to be a firmware issue. Please allow me a few days to talk with the firmware team to understand next steps.

Thanks,

Emma