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.

TPS65987DDJ: TPS65987DDJ FW update problem

Part Number: TPS65987DDJ
Other Parts Discussed in Thread: TPS65987D

Dear all,

My customer use TPS65987DDJ in their notebook application, and they need update the FW using EC with external EEPROM, they find it will last one hour to update the FW, what can be checked to find the reason?

Could you please help give some suggestions?

Thanks.

  • Hey John,

    If your customer has not already done so, I would recommend that they read through the following application on how to best implement a system where the EC sends the patch bundle to the PD controller.

    http://www.ti.com/lit/an/slvae18/slvae18.pdf

    It should not take an hour though. The speed of the update is determined by how quickly the EC pushes the information on the I2C line. Do you have an I2C capture of the messages sent between the EC and PD controller during the patching phase?

  • Hi  Adam,

    The link you shared is the materials related to the I2C master setting.

    If we captured the I2c information between EC and PD, how to analyze the information?

    There should be lots of information on the I2C line, am I right?

    Thanks.

  • Hi John,

    I may have misunderstood your original post then. Is the PD controller receiving the patch bundle from the EC or an EEPROM connected only to the PD controller?

    Also, would you be able to share what platform this is going into? Is it a Thunerbolt dock or a monitor?

  • Hi Adam,

    This is notebook application using the DJ version.

    The platform is Comet lake, Customer connect the external EEPROM to PD, and during the debug, they need update the FW into thee EEPROM, but it stuck and are not able to update the FW successfully.

    And sometimes, during the update process, it fails, PD can not work any more.

    Could you please help give suggestions how to check the problem and solve the problem?

    Thanks.

  • Hi  Adam,

    Do we have any documents for the DJ version to show the update flow over I2C from EC to external Flash?

    Thanks.

  • Hi John,

    Would you also be able to share which version of the configuration tool you are using as well as what firmware image you are using?

    Is the platform a Thunderbolt system?

    Would you also walk through how are they currently updating the EEPROM? What are they connecting to the EEPROM, what are they using to flash the image onto the EEPROM?

  • Hi Adam,

    The version of configuration tool is 6.2.3, the firmware image is F807_12_37.

    No Thunderbolt is required, just full function PD.

    The update step is using the low region file, update the FW using EC to the external EEPROM using I2C.

    The EEPROM is connected to the PD controller only.

    The hardware design was checked previously.

    Could you please help give some suggestions how to check the problem?

    Thanks.

  • Hi Adam,

    Could you please help give some suggestions?

    Thanks.

  • Hi John,

    If your system is not a Thunderbolt system, you must instead use the TPS65987D. This device is the TPS65987DDH and you are currently using the TPS65987DDJ. The DJ device is intended for Thunderbolt application while the DH is intended for non-TBT host applications. Moving forward, you will need to transition to this device before your customer goes to production. You will need to get the new EVM, samples, and start using the following configuration tool once you transition to DH

    http://www.ti.com/tool/TPS6598X-CONFIG

    For your current system, when generating the binary image to flash onto the EEPROM, you will click BINARY -> SAVE BINARY then click on 'Full Flash Image'. Then using some type of programmer, we typically use Aardvark and Total Phase Flash Center, flash the binary file onto the EEPROM. Perform a power cycle, and the new binary image should be loaded onto the PD controller