• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 246 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

TPS65982: Over-writing TPS65982 internal 'appcode' in OTP memory, rather than using SPI flash memory or UART

TPS65982: I2C Configuration and Boot Code Sequence over UART

MattLin
Intellectual 1050 points
Part Number: TPS65982
Other Parts Discussed in Thread: TPS65987D

With just the boot code running, how much of the i2c host interface is brought up and available for an external host acting as the i2c master to access? From the flow chart of initialization it looks like the I2C should be brought up before the boot code is uploaded from either SPI or UART. Is this true? The main concern is that if there are bus in the base FW that may prevent i2c host interface from coming up.  This seems unlikely but want confirmation that the original OTP boot code is sufficient for bringing up the i2c host interface for communication to an external i2c master.

Based on various documents, the configuration file can be uploaded vis SPI Flash, UART, or I2C (https://www.ti.com/lit/an/slvae21a/slvae21a.pdf?ts=1588374241011 and https://www.ti.com/lit/an/slva783a/slva783a.pdf?ts=1588380254167). The UART is typically used as a way for multiple PD devices to communicate and to download the app fw. The PD controller configured with 0 ohm for the i2c addr resistor will be configured as UART master and a UART slave can download the app code fw from the UART master.  Since we are configured as a UART master, we would probabaly need to reconfigure ourselves to become a UART slave and then download from some other node configured as UART master. Is this true and can you elaborate on how the configuration can be done over UART as this is the least documented variation of how to upload the configuration file in both the datasheet and additional resources, app notes, and white papers. 

Regards,
Matt

  • 0
    TI__Mastermind 30000 points

    Hi Matt,

    First, I would recommend using the TPS65987D if you have not already built your system. This is our latest PD controller, and would recommend to make the migration towards that.

    As far as the patch update, I would recommend using the external SPI flash implementation. From your perspective, this would be the easiest implementation since the PD controller will handle loading the firmware image from the patch on its own.