• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 64 subscribers
  • Views 218 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.

TPS25750: Return to PTCH mode from APP mode during AlwaysEnableSink

Jeff LaBundy
Intellectual 300 points
Part Number: TPS25750

Hi there—I have integrated the TPS25750 with our Android platform; I can successfully apply a patch bundle exported from the web GUI and the device functions normally.

Although it is unlikely the patch bundle will change in the future, I must make sure our platform can apply a new patch bundle as part of an OTA upgrade in the future. To that end, I have the following questions:

  1. Since my platform uses AlwaysEnableSink mode instead of NegotiateHighVoltage, I cannot use the GO2P command to return to patch mode. After browsing various E2E threads, it seems the GAID command can perform this function by resetting the device altogether, although it seems rather invasive—the IC may NAK any I2C communication for roughly one second following receipt of the command, and the entire power path is open until the new patch bundle is applied. Are there any alternative methods to return to patch mode?
  2. We need a way to embed a version string in the patch bundle; it seems register 0x06 (CUSTUSE) can serve this purpose. I do not happen to see a way to program this register using the web GUI—can TI advise how to do edit this memory location? Perhaps we can use an offline hex editor.

On a related note, maybe I can take this opportunity to point out some minor inconsistencies in the user manual:

  • The example code on pages 54–57 is difficult to read due to its lack of indentation, and refers to workarounds for which the manual gives no context (e.g. WORKAROUND_WAIT_AFTER_GAID and WORKAROUND_IGNORE_CMDxCMPLT_BURST_TX). Are these important?
  • The patch version referenced in the manual (F509.04.02) seems to lag that which is exported by the latest web GUI (FWF509.05.61_0003).
  • Table 3-9 bytes 5 and 6 should be labeled bytes 4 and 5, respectively.
  • Several bit fields throughout chapter 2 are missing (e.g. register 0x2D bytes 1–4 bits 17, 20–23 and 25–26). These are likely reserved, but many other reserved bits are shown—perhaps some internal text is not conditionalized properly.

Thank you in advance for your support and please let me know in case I can clarify any of my questions or observations.