CC2642R: Restart on exceptions

Hi Martin,

What about implementing a watchdog?

You can find documentation and an example project in the SimpleLink CC13x2/CC26x2 SDK.

Yes I have a watchdog already, I forgot about that. In release build do all the handlers just implement a while(1) loop?

Hi Martin,

Yes, in release build you will have the most aggressive approach for code footprint saving, which will trap exceptions and errors with while(1). If you have a look in your simple_peripheral_app.cfg, this will be because both "m3Hwi.excHandlerFunc" and "Error.raiseHook" are set to null. 

If you want to decode exceptions and handle errors in any other manner, you could change either or both of these to:

m3Hwi.enableException = true;     // Decode and print exceptions, raise errors
//m3Hwi.enableException = false;  // Do not decode or print, but still raise errors
//m3Hwi.excHandlerFunc = null;    // Trap in while(1)

//Error.raiseHook = Error.print;
//Error.raiseHook = null;                  // Trap in while(1)
Error.raiseHook = "&myErrorFxn";  // Handle error in custom function

Best regards,

Vetle

actually, I went back and looked at the case that made me ask this question and it looks like the watchdog won't fix it.

I was calling Semaphore_post on an uninitialized semaphore, i.e.

static Semaphore_Struct sem;

Semaphore_post(Semaphore_handle(&sem));

The watchdog wasn't firing, stepping through Semaphore_post() I thought the problem was that Hwi_disable() was called so I added a handler:

m3Hwi.excHookFunc = "&execHandlerHook";

void execHandlerHook(void *ctx)
{

Hwi_restore(0);

while (1);

}

but this didn't work either, I guess because execHandlerHook is called in the context a HWI (?)  so the watchdog is blocked. I am now using:

void execHandlerHook(void *ctx) {  SysCtrlSystemReset();  }

so I guess this opens up the original question, will this handle all cases?