• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 651 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.

TPS65986: When does TPS65986 access SPI-Flash??

Eric S
Expert 5640 points

Part Number: TPS65986

Would like to understand all cases where TPS65986 will effectively re-boot from SPI-Flash.   Understand that POR event will do this, but have also been told that all PD HardReset events will cause this as well.  However, experimentation has shown that some HardReset events will not cause the registers to re-boot to default.  Specifically, they triggered PD HardReset, with the HardResetDetails (Register 0x40, bits 21:16) value of 000101b (NoResponseTimeOut) or 001001b (Sink_WaitForCapabilities).    The simplest way to actually initiate this, is to plug-in a non-PD, BC1.2 charger, which causes these HardReset events.

 

I would not think that a “No Response” because the charger is not a PD Charger, should cause us to completely re-boot the chip, so I’m suspicious of the comment that “PD HardReset causes us to re-boot”.   It would seem to me, that some of the HardReset reasons listed in our Register 0x40 description, would not require a complete device re-boot which requires accessing SPI-Flash.   From this Table we provide, can we determine which HardReset codes will initiate a re-boot of the chip from SPI-Flash, and which ones will not?  

 

Thank you.

  • 0
    TI__Genius 16370 points
    Eric, The device does error-recovery on encountering some of these fault conditions (like, NoResponse), and as part of that sequence, the PD contract is renegotiated. Now, if the device was operating in dead-battery mode, obviously, this VBUS loss will result in a system-reset - The device also does system-reset if it was operating as a SRC and VIN3V3 is either removed or has a glitch. Is either of these conditions true for your tests?

    BR,
    Praneet
  • 0 in reply to Praneet Kumar
    TI__Expert 5640 points

    Praneet,

    Okay, but this still doesn't fully answer my question.   We are trying to understand ALL conditions that will cause the device to re-boot from SPI-Flash.   Perhaps asked a different way, is there a particular register/bit we can query, whenever there is a Hard or Soft Reset event...  that will tell us a re-boot took place?   Right now, just trying to understand how to identify when run-time configurations have been erased and replaced with default values, so that we can re-configure those settings.

    Thank you.

  • 0 in reply to Eric S
    TI__Genius 16370 points

    Eric,

    In addition to the conditions listed in my previous post, the device as well does a system-reset on below events:

    • Device not in dead-battery, and VIN3V3 is lost
    • Command 'GAID'/'Gaid' executed by the host
    • Device operating as SRC, and VIN3V3 is removed
    • Device Hard Faults
    • Device operating as SNK and in dead-battery condition, and the type-c cable is detached
    • OVP event while the device was in dead-battery condition

    BTW, what is the use-case that would require your application to do a run-time configuration of the device?

    -/Praneet

  • 0 in reply to Praneet Kumar
    TI__Genius 16370 points
    Eric,

    I'm closing this thread since you've initiated an offline discussion on the topic.
    After our discussion, I'll post the summary here for the benefit of the forum.

    -/Praneet