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

CC2674R10: Watchdog in faulted scenario cc2674r10

Joe Markel
Prodigy 150 points
Part Number: CC2674R10


It appears the watchdog doesn't fire in a faulted scenario (e.g. faultISR()). Assuming the interrupts are disabled at this point, hence the timer not triggering? We'd like to avoid modifying the startup code with custom fault handlers at this point. There is a mention of an AON Watchdog Timer in the data sheet, but we have not found anything related to properly configuring this (if this would even resolve the scenario).

Please advise.

Thanks

  • 0
    TI__Guru**** 218207 points

    Hi Joe,

    There are two options for Watchdog control with the CC2674R10:

    I have noticed either option explains that once started/enabled, the Watchdog timer can only be stopped by a hardware reset.  The HardFault condition is also described in the TRM (Section 5.1.2) which indicates an inability to preempt operation.  How are you currently configuring the Watchdog?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 150 points

    Hi Ryan,

    I think what was missing (Stuart briefed me on this), was the call to WatchdogResetEnable(). What I'm finding is the device will reset in a faultISR situation when the WDT_CTL_RESEN bit is set. Seem ok?

    Thanks

  • 0 in reply to Joe Markel
    TI__Guru**** 218207 points

    WatchdogResetEnable enables the capability of the watchdog timer to issue a reset to the processor after a second timeout condition by setting the WDT_CTL_RESEN bit.  Does this resolve your issue?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    TI__Genius 10660 points

    Joe,

    Are you using the regular "not always on" watchdog. If so, then the DriverLib API (source/ti/devices/cc13x4_cc6x4/driverlib) you quote is required to enable device reset.

    As Ryan correctly points out, I checked and confirmed that the TI Driver implementation (source/ti/drivers/watchdog) uses the "always on" watchdog, and is always going to result in a device reset if it expires.

    Thanks,

    Stuart