• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 532 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.

TMS320F28069M: unrolling stack trace on watchdog reset

Mathew Maher49
Expert 2125 points

Part Number: TMS320F28069M

when the watchdog is setup for automatic reset, is there any way to breakpoint it before the reset occurs?

Got a rare-and-random reset occuring in the software: it'd be good to identify any watchdog timeouts and unroll the call stack to identify whats going wrong.

  • 0
    TI__Genius 17315 points

    Mathew,

    As you may know, the watchdog on the F28069 can also be configured to generate an interrupt rather than a reset.  Perhaps you place a trap (ESTOP) in the watchdog ISR and then debug what caused it, including checking the stack.  The ISR would look something like:

    interrupt void WAKEINT_ISR(void)    // PIE1.8 @ 0x000D4E  WAKEINT (LPM/WD)
    {
     PieCtrlRegs.PIEACK.all = PIEACK_GROUP1;  // Must acknowledge the PIE group
     
    // Next two lines for debug only - remove after inserting your ISR
     asm (" ESTOP0");       // Emulator Halt instruction
     while(1);
    }

    In our F28x7x and F28004x devices we have a 'Reset Cause' register which contains the cause of the last reset (i.e. sticky bits maintain state with multiple resets), however this is not available on the F2806x devices.

    To learn more about using the watchdog to generate an interrupt, please see lab 5 in the F2806x workshop at:

    https://training.ti.com/c2000-mcu-device-workshops

    I hope this helps.  If this answers your question, please click the green "Verified Answer" button.  Thanks.

    - Ken

  • 0 in reply to Ken Schachter
    TI__Genius 17315 points

    Mathew,

    It's been a while since I have heard from you last. Therefore, I am assuming that my last reply resolve your issue and I will close this thread. If this isn’t the case, please reject this resolution or reply to this thread. If this thread locks, please make a new thread describing the current status of your issue. Thank you.

    - Ken