TPS65983 configtool ver.2.9 and Apex Creek

Hi,

We will check this in our system. How did you check if 5V is outputted correctly? Did you measure the VBUS for this? Anyway, we will see if this is a bug in the tool and fix it if so.

Regards,

Arun

Dear Arun

I connect Ash-Creek (TBT3 bus power) device and cannot be powered. and I measure the Vbus, the voltage is 0. It looks like the PP_5V0 power path doesn't work.

Hi,

Ash-Creek is not currently supported by us currently. For BPD devices you have to use the BPD HV or BPD HVE templates. The BPD HV uses the HV(Internal path) and BPD HVE uses the external power path(HVE).

Regards,
Arun

Dear  Arun

That's not correct. the problem is the PP_5V0 is no current output anymore. I tried a  USB-C mouse still not working.

According to Apex Creek reference design,the PP_5V0 should support 5V@3A output capability. but now is 0.

I used a lot of configtool version but only ver.2.9 has this issue.

Anderson

Dear Arun

I don't know if you understand what I mean. Please see the picture. The PP_5V should supply 5V@3A output, but it's zero now. No current voltage no current.

Understood. We will check this on our EVM boards. Did you check this on Port A or PortB? 

Regards,

Arun

Dear Arun

Port A and B don't have power either.

Hi Anderson,

I Just checked this on our EVM. I was able to establish a 5V contract. Do you have PD analyzer like Lecroy or Ellisys? Can you post the trace from these analyzers?

Regards,
Arun

Dear Arun

Sorry, I don't have such analyse tool to trace the PD communication process. I think I will ask Intel to check this issue,too.

I found not only the power, but also the USB-C reverse plug function failed. It's only one direction can be detected now. But if I return back to use Ti configtool 2.7, everything works normal.

My environment is Apex Creek with intel DSL6540(B1) with NVM rev.21. And Ti TPS65983 with configtool rev.2.9 (FW 0X345)

Thanks for your help.

Anderson

Hi,

Unfortunately I don't have a Intel reference design at my disposal to check this. I will ask my colleagues to check this out. 

Since you mention this was working with v2.7, I suspect something has gone wrong in the templates for the second port. When I check here with EVM, I am checking only the first port. 

We will post whatever finding we have here. If there is a bug we will come with newer version of the tool with this fixed.

Regards,

Arun