RE: User breakpoints management

Gianluca — Fri, 13 Dec 2019 12:11:23 GMT

Thanks Edvin, i have understood.

RE: User breakpoints management

Edvin — Wed, 11 Dec 2019 14:33:02 GMT

Hello,

The reason why the softdevice asserts is, as you say, because the softdevice is loosing time sensitive time slots. Unfortunately, there is not much we can do about this.

There is something called Monitor Mode debugging, where it doesn't actually stop the CPU while you step, but in my opinion, this is more work than just using logging to see what's happening instead of debugging when you are developing.

I assume you are using the Mesh SDK there are two error handlers. One designed for the Mesh SDK, and one designed for the "normal" SDK.

I suggest that you add the define "DEBUG" to your preprocessor defines. Go to project settings by right clicking the project name, and follow the instructions here:

What does the log say then?

NB don't set a breakpoint. Look at what the error handler prints in the log.

You can set a breakpoint if you want to know what happens at one point in time, and you can step a few time until the application realize that the softdevice has missed some events. Then you need to restart the application and set a new breakpoint.

Best regards,

Edvin