CC3235MODASF: Watchdog multiple callback

Cedric Gerber

Part Number: CC3235MODASF
Other Parts Discussed in Thread: CC3200, CC3235SF, SYSBIOS

Hi,

I do not understand fully the behavior of the watchdog

I configure it like:

const WatchdogCC32XX_HWAttrs watchdogCC3220SHWAttrs[CC3220SF_LAUNCHXL_WATCHDOGCOUNT] = {
    {
        .baseAddr = WDT_BASE,
        .intNum = INT_WDT,
        .intPriority = (~0),
        .reloadValue = (uint32_t)80000000*30 /* 30 second period at default CPU clock freq, first call trigs warning callback, second call trigs reset */
    }
};

    Watchdog_init();

    Watchdog_Params_init(&params);

    params.resetMode = Watchdog_RESET_ON;
    params.callbackFxn = (Watchdog_Callback) &WatchdogCallback;
    params.debugStallMode = Watchdog_DEBUG_STALL_ON;

    handle = Watchdog_open(CC3220SF_LAUNCHXL_WATCHDOG0, &params);
    if (handle == NULL)
    {
        ERROR_PRINT("Could not open watchdog");
        return -1;
     }

Then just to validate that it works fine I just start, init the watchdog and wait 30sec.

11:27:51 Wait watchdog
11:28:21 First callback, followed by many callbacks until restart
11:28:51 Restart

My questions:

Why is the callback called multiple times? I'm quite sure it was not the case previously.

I am using:

CC3235modasf with sp_4.7.0.3_3.1.0.5_3.1.0.26

over 5 years ago

0 Vincent Rodriguez over 5 years ago

TI__Mastermind 28285 points

Hi Cedric,

Take a look at section 10.1 in our TRM - https://www.ti.com/lit/ug/swru465/swru465.pdf

The watchdog callback on first call will reset the timer and set the interrupt. If this happens again without clearing the interrupt the device will reset.

BR,

Vince

0 Cedric Gerber over 5 years ago in reply to Vincent Rodriguez

Expert 2310 points

Hi Vince,

Thanks for the pointer to the doc. However according to the doc I shall get 1 interrupt which calls the callback, and a second interrupt which generates the reset. Instead I get a few thousands interrupts (1 each few microsec) between the first interrupt and the "reset interrupt".

I'm not sure if it's a configuration issue or a sdk/service pack issue.

Cédric

0 Jan D over 5 years ago in reply to Cedric Gerber

Guru 80205 points

Hi Cédric,

I think this is a normal behaviour of CC32xx WDT peripheral. If I remember properly, I saw same behaviour when I worked on CC3200. This was long time ago, TI-RTOS and Driverlib API layer was used. You are using TI Drviers, you have same behaviour. Unfortunately I don't remember if I was able figure-out any workaround.

Jan

0 Cedric Gerber over 5 years ago in reply to Jan D

Expert 2310 points

Hi Jan,

Thanks for your reply!

I think this is new in one of the last sdk of the cc3235. I used to have a mechanism where I set the watchdog time to 1sec in the callback to avoid having to wait for twice the watchdog period. Now this is broken since the endless callback calls keep resetting the watchdog period.

Cédric

0 Vincent Rodriguez over 5 years ago in reply to Cedric Gerber

TI__Mastermind 28285 points

Hi Cedric,

Are you running the watchdog example from the SDK?

0 Cedric Gerber over 5 years ago in reply to Vincent Rodriguez

Expert 2310 points

Hi,

My code is based on the watchdog example, the only difference is that I do not have the while(1) in the callback.

Cédric

0 Vincent Rodriguez over 5 years ago in reply to Cedric Gerber

TI__Mastermind 28285 points

Cedric,

Sorry for the delay, i haven't had a chance to test this. I plan on getting some results this week.

BR,

Vince

0 Vincent Rodriguez over 5 years ago in reply to Vincent Rodriguez

TI__Mastermind 28285 points

Hi Cedric,

Tested this with SDK 4.1 and didn't have the same issues. I see the Watchdog callback after 10 secs, then 10 secs later a restart. Replace the files in your example with these and let me know if you get the same result.

BR,

Vince

/cfs-file/__key/communityserver-discussions-components-files/968/watchdog.c

/cfs-file/__key/communityserver-discussions-components-files/968/watchdog.syscfg

0 Cedric Gerber over 5 years ago in reply to Vincent Rodriguez

Expert 2310 points

Hi Vince,

I made a minimal project for the launchpad cc3235sf so it's easier to reproduce.

/cfs-file/__key/communityserver-discussions-components-files/968/sensor_5F00_cc3235_5F00_launchpad.zip

I have the issue with SDK 4.2.

Do you see the same issue?

Thanks,

Cédric

0 Vincent Rodriguez over 5 years ago in reply to Cedric Gerber

TI__Mastermind 28285 points

Hi Cedric,

I can reproduce your issue. I can tell this project was a migration from older SDKs, and is using XDC Tools and sysbios that are not supported anymore. My suggestion would be the following -

1. Test the default watchdog example in the SDK (use my files above). Lets see if the issue doesn't reproduce.

2. If that works, use this project as the base and add your previous source files. Use TI-Drivers as much as you can for the WDT and UART, and fix any include issues you might have.

BR,

Vince

0 Cedric Gerber over 5 years ago in reply to Vincent Rodriguez

Expert 2310 points

Hi Vince,

Thanks for testing my project!

I will test tomorrow the watchdog example.

Just a few questions to understand better.

I see that syscfg generates the files CC3235SF_LAUNCHXL.c and CC3235SF_LAUNCHXL.h, does it do anything else?

Not sure what you mean with obsolete xdc tools and sysbios, I'm using latest xdc tools and the cfg file looks very much the same as in the cfg file used by the watchdog example (tirtos_builds_....). Is there something else I'm missing?

Thanks

Cédric

0 Cedric Gerber over 5 years ago in reply to Cedric Gerber

Expert 2310 points

Hi Vince,

I made more tests this morning and can pinpoint the issue to syscallback.

If in the .cfg file I use SysMin or SysStd instead there is only one watchdog callback as expected.

I am using SysCallBack to be able to print logs to uart.

Can you reproduce it?

Thanks,

Cédric

0 Vincent Rodriguez over 5 years ago in reply to Cedric Gerber

TI__Mastermind 28285 points

Hi Cedric,

Glad you found the issue!

Personally don't have alot of experience uses those internal functions to print out over uart. I suggest moving all of those to Display prints that utilize TI drivers.

BR,

Vince

0 Cedric Gerber over 5 years ago in reply to Vincent Rodriguez

Expert 2310 points

Hi Vince,

From what I understand, I have to use Syscallback and System_printf as I do currently if I want to output to Uart the logs as well as the debugging info (for instance stack overflow faults are currently printed out on UART).

According to this doc it seems an expected use case: http://dev.ti.com/tirex/explore/node?node=ANqagjxZxWnBRB7bx0EnOw__pTTHBmu__LATEST

Can you loop in someone with experience on print over uart or Syscallback?

Thanks,

Cédric

0 ToddMullanix over 5 years ago in reply to Cedric Gerber

TI__Guru* 96960 points

Hi Cédric,

Take a look at the SimpleLink Academy module on Debug Output: https://dev.ti.com/tirex/explore/node?node=AFP7qrknctNrPgCKeGadww__fc2e6sr__LATEST

If you have questions about it, please start a new thread (to minimize the length of this one).

Todd

0 Cedric Gerber over 5 years ago in reply to ToddMullanix

Expert 2310 points

Hi Todd,

This link is what I used to configure my project. (I posted it just above your post ; ))

The issue is: when I use Syscallback, I get thousands of callbacks per second from the watchdog until the reset. This is not documented nor expected.

Now that I know, it's not much of an issue so I will live with it. I hope it does not have another similar bad effect on another module somewhere else.

Do as you please with the information ; )

Cédric

Wi-Fi

Wi-Fi forum

CC3235MODASF: Watchdog multiple callback