Softdevice

RE: Softdevice

Håkon Alseth — Tue, 24 Apr 2018 07:06:16 GMT

In debug mode: when you're hitting a breakpoint, you're halting the CPU, but not the peripherals running in the background. This means that all your timers, RTCs, UART, SPI, etc. are all still running and can potentially set events that leads to interrupts.

This is what the softdevice does as well. it has it's own timekeeping to ensure things happen in a certain order, and if the order is mixed up; the softdevice will thrown an assertion to the application.

There's quite a few threads on this subject already. Search for "debug softdevice" in the forum.

Best regards,

Håkon

RE: Softdevice

Marco — Fri, 20 Apr 2018 13:01:34 GMT

Maybe I'm missing something but... if we can't step through the program how are we supposed to debug it?

All we can do is set breakpoints and inspect the program state. It's better than nothing but... this sounds like a big deal.

RE: Softdevice

Håkon Alseth — Thu, 01 Mar 2018 12:03:01 GMT

Hi,

You're stuck in the assert handling routine in the softdevice.

Note that if you are in debug mode, and hit a breakpoint, single stepping through will cause a timing related assertion in the softdevice.

If this is an assertion that occurs when running the firmware as normal, you can add the define "DEBUG" to your project and recompile/flash to enable blocking assertions so that you can get more detailed information on what and where the issue occurs.

Best regards,

Håkon