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.

TPS65987D: Problems about Programming for SPI-Flash Less Systems

Part Number: TPS65987D
Other Parts Discussed in Thread: TPS65987, , TPS65988

Hi Team,

follow the PDF -- "TPS65987DDH Host Programming for SPI-Flash Less Systems" Application Report: SLVA972–May 2018; 

we use a STM32F407 demo board as an external host, connect with TPS65987 over I2C.Our BusPowerZ Configurations  is :

BP_ECWait_internal Infinite Wait

 We plug a PD charger type C,when power on, TPS65987  enter into PTCH mode, then STM32F407 will download the patch bundles to TPS65987, after download successfully, TPS65987  will reboot,and enter into PTCH mode again, that is not we wanted. Normally, it should enter into APP mode after download patch.

But if we plug a normal type C(just supply 5V), execute the above procedure, after download successfully, TPS65987  will not reboot , it can enter into APP mode, it is OK.

So what is the different ? How to make it work normally when plug a type C cable with PD charger?

Best Regards,

peng

  • Hi peng,

    In your use case, you are booting the TPS65987D in "dead battery mode". The only source of power is VBUS in this case. It sounds like the PD adapter is getting disconnected after the Firmware loading is complete, causing VBUS to drop to 0V and renegotiate. This would cause the TPS65987D to lose its power and the config would be lost. I would suggest checking to ensure the PD adapter does not lose its voltage during your FW loading. 

    Thank you,
    Eric

  • Hi Eric,

    yes, as your said, the only source is PD adapter, after the Firmware loading is complete, VBUS drops to 0 V.  I tried several PD chargers, all the same

    But if I use a normal adapter(5V,1A, not support PD protocol), it will be OK, VBUS doesn't drop to 0 V after firmware loading is complete.

  • Hello,

    What is the last 4CC Command you are sending after you have completed the patch loading? It seems that something you are sending from the EC is causing the disconnect.

    Thanks,
    Eric

  • Hi Eric,

    Thanks for your reply.

    The sequence of patch loading is followed by the PDF"TPS65987 and TPS65988 SPI Less Host Programming Over I2C", the picture below.

    The last 4CC command is PTCc. And I don't think it causing the disconnect, because when I use a normal adapter(not PD adapter), it doesn't cause disconnect.  

  • Hello,

    Sending the PTCc command should not cause a disconnect. Please ensure your configuration is set up to allow for High Voltage PD Sinking. If the configuration is not set correctly, you can see a disconnect.

    Can you please use a PD analyzer to see what the PD data is during the patch loading and disconnect? This would tell us more about what is happening and how to resolve it.

    Thanks,
    Eric

  • Hello,Eric,

    I am not sure my configuration is right,attached is my configuration profile. Could you help to check it?

    I don't have PD analyzer, so I can't to analyze it.

    Thanks

    20190530_ufp.pjt

  • Hello,

    Today I found something.

    I just test Apple PD power charger befor, today I use another charger(named Ugreen, also support PD protocol), it is OK!! After patch loading completed, it will not reboot !

    I think there must be something different about PD protocl between Apple power  charger with others. 

  • Hello,

    I agree it could be based on the Apple charger. If you would like to see what the issue is, you can use a PD analyzer to take a PD trace. This would let you know what in the PD protocol is causing the disconnect.

    Thanks,
    Eric