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

TPS6594-Q1: How do I exit the long window mode when I use the watchdog

Xibin Feng
Prodigy 150 points
Part Number: TPS6594-Q1

Hi：

    I config and enbale the watchdog,the pin nESROUT will active low when the time reach the long window time,How can I do to exit the longwidow mode and enter the window 1 and window 2 mode

  • 0
    TI__Mastermind 49371 points

    Hi Xibin,

      Please see the datasheet section copied below:

      8.3.11.3 MCU to Watchdog Synchronization
      In order to go out of the Long Window and start the first watchdog sequence, the MCU must do the following:
    • Clear bits WD_PWRHOLD (more detail in Section 8.3.11.4)
    • Apply a pulse signal with a minimum pulse-width tWD_pulse on the pre-assigned GPIO pin in the case the
    watchdog is configured for Trigger mode, or
    • Write four times to WD_ANSWER[7:0] in the case the watchdog is configured for Q&A mode
    When the MCU fails to get the watchdog out of the Long Window before the configured Long
    Window time interval (tLONG_WINDOW) elapses, the device goes through a warm reset, and sets the
    WD_LONGWIN_TIMEOUT_INT. This bit latched until the MCU writes a ‘0’ to it ‘1’ to clear it.

    Thanks!

    Phil

  • 0 in reply to Phil Yi
    Prodigy 150 points

    Hi Phil

            I config the Q&A mode and clear the bits WD_PWRHOLD,the bit WD_PWRHOLD=0, then I Write four times to WD_ANSWER[7:0],but I read the bits 

    WD_BAD_EVENT ,the WD_BAD_EVENT =1,I don`t know why there is a bad event,How can I find the cause of the bad event

  • 0 in reply to Xibin Feng
    Prodigy 150 points

    I read the the register  WD_ERR_STATUS,the  WD_ERR_STATUS=0x22,the bits WD_ANSW_ERR =1 and WD_TIMEOUT=1,Did I send the wrong answer?

  • +1 in reply to Xibin Feng
    TI__Mastermind 49371 points

    Hi Xibin,

      It looks like wrong answers cause these bits WD_ANSW_ERR =1 and WD_TIMEOUT=1. Please follow the instruction below:

      A WD answer is a 32-bit word that is split into four answer bytes: Answer-3, Answer-2, Answer-1, and Answer-0.
     The watchdog receives an answer-byte when the MCU writes to the WD_ANSWER[7:0] bits. For each question, the watchdog requires four correct answer-bytes from the MCU in the correct timing and order (Answer-3, Answer-2, and Answer-1 in Window 1 in the correct sequence, and Answer-0 in Window 2) to detect a good event.

    Thanks!

    Phil