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.

Compiler/CC3220SF-LAUNCHXL: watchdog issues

Part Number: CC3220SF-LAUNCHXL

Tool/software: TI C/C++ Compiler

Hello:

I have the watchdog timer setup in a CC3220  project and it is operating and functioning as expected. I kick the watchdog in my code every so often and the program runs just fine (I have this project saved in flash so it will automatically run after a power cycle or reset).

The problem I am having is: If I connect to the same board and run a debug version of another project ontop of it (where the new debug project isn't referencing the watchdog at all) - the watchdog from the program loaded into flash "seems" to still be running and stopping my debug session. While I am running my debug project, after a certain amount of time passes, the debug session is interrupted and the processor resets (I see the indication of the debugger being interrupted and disconnected from code composer and the resident project in flash starts up).

q1. Is the watchdog from flashed project still running while I'm running a debug (ram) loaded version of a project?

q2. Is there a way to disable the watchdog while running a debug session ontop of a flashed project?

Thanks in advance...

Dave...

  • Hi Dave,

    Please see TRM section of watch dog timer ( www.ti.com/.../swru465.pdf ).

    1. Once you enable watch dog, there is no way how deactivate watchdog by software way. To disable watch dog you need do hardware reset. If you don't want refresh WDT at your debug session, you need remove your app. in sFlash.

    2. No. Once you start your code flash flash with WDT, you need update WDT in you debug session.

    3. WDT in CC32xx devices have one good feature. By bit STALL in WDTTEST register you can stop WDT counting in case MCU is stopped by debugger (stopped at breakpoint). I am not sure if this feature is default or can be enabled in case of TI drivers are used.

    Jan
  • Thank you Jan!
    I appreciate the feedback - I reflashed the unit with software that never enables the watchdog and ran a debug session ontop of it - seems to work just fine!