app timer causing assertion after disconnection event

RE: app timer causing assertion after disconnection event

Susheel Nuguru — Thu, 20 Aug 2015 12:20:05 GMT

thanks for coming back to update this thread. Ill mark your answer as accepted.

RE: app timer causing assertion after disconnection event

Wed, 19 Aug 2015 22:47:37 GMT

The problem turned out to be that when the GATT client disconnected the system automatically started advertising again. In my advertising event handler I started an app_timer to control LED animations. When the advertising started advertising again automatically there was a repeated call to app_timer_start for the timer that was already started. The system was apparently not amused and crashed.

RE: app timer causing assertion after disconnection event

Susheel Nuguru — Wed, 05 Aug 2015 05:00:42 GMT

set the breakpoint in assert handler, run in debugger and when the breakpoint hits, see the call stack. You will know which function called it

RE: app timer causing assertion after disconnection event

Tue, 04 Aug 2015 22:12:27 GMT

Sorry for the delayed response, but I am in China working on bringing up production on the board we hope to replace with the Nordic solution. Unfortunately I do not know where the assertion is coming from. The error handler does not provide a value for the line number and filename or even error code parameters. Is there a way to find out?

RE: app timer causing assertion after disconnection event

Susheel Nuguru — Mon, 03 Aug 2015 07:21:40 GMT

If the app_timer_stop statement is commented out, where do you get assertion?