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.

LAUNCHXL-CC26X2R1: Watchdog does not reset

Part Number: LAUNCHXL-CC26X2R1


Hello. I have a test program that is heavily based on "rfEasyLinkEchoTx_CC26X2R1_LAUNCHXL_tirtos7_ccs" and I am trying to add a watchdog. I set up my task in exactly the same way as in that example. I have added the watchdog to syscfg and use the following code to initialize the watchdog:

Watchdog_Params watchdogParams;
Watchdog_init();
Watchdog_Params_init(&watchdogParams);
watchdogParams.resetMode = Watchdog_RESET_ON;
watchdogParams.debugStallMode = Watchdog_DEBUG_STALL_ON;
watchdog = Watchdog_open(CONFIG_WATCHDOG_0, &watchdogParams);
if (watchdog == NULL) while(1);

During my code execution I have a call to `Watchdog_clear(watchdog);` but for the sake of this test I disable that. The problem is that in the test the watchdog does not reset the device. 

I can confirm that the watchdog is firing as I would expect by adding a callback option to the watchdog params, and that callback is called when I would expect it to be. But even when that callback is called, the device does not reset. Does anybody have any idea what I am doing wrong? 

For the record I can confirm that the watchdog works by running the example program "watchdog_CC26X2R1_LAUNCHXL_tirtos7_ccs" and I believe I am using the watchdog the same way in my application. But in the watchdog example the device does reset and in my application is does not. 

Thank you! 

  • Hi,

    The watchdog example does set the reload value (Watchdog_setReload) -- can you try something similar?

    Once you enter the watchdog callback, can you share a register dump for WDT?
    (In CCS: Window --> Show View --> Memory Browser; then, navigate to the WDT register address 0x40080000).

    Additionally, more details on Watchdog can be found in the Technical Reference Manual, Chapter 17).

    Thanks,
    Toby