This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

52840dk Segger debug exception when using softdevices.

Debugging in Segger serial example from mesh

It runs and responds to commands, but when paused or hits breakpoint - single step or continue gets to address 0xa60, continue logs the message:

app_error_weak.c,   96, Softdevice assert: 154516:0

Are there some required debugger setting whne debugging with softdevices?

I was debugging sample project without the softdevice without problems - possibly there is another issue.

  • Your application will not work if the softdevice asserts. The connection will break. Either way, you should just try to not start advertising or connecting if you want to step in your code. If that isn't viable, then you must use the logging tools. 

    There is something called Monitor Mode Debugging. I have not tested this myself, but that may be something you want to look into if you need to step through parts of your code. It is a bit of work to get it up and running, but if you need it, I guess you can try.

  • Yes, I got the app note about it from Segger, definitely will try it, but at the moment it is a second priority. I need to resolve the dfu examples issues.

    Posted some questions which could help forward, but still not clear why dfu example overwrites bootloader at 0x1f000, why there is no bootloader for 840, if I load bootloader with nrfjprog, how is the UICR getting set.

    In parallel building some framework to comm with serial, cannot use Python on my controller - Coldfire on Netburner module.

    Could you see the case 243613? There is no reply at all for 3 days ...

    Piotr

  • I didn't notice before now that you are using Mesh. I am not sure what DFU example you refer to, or what bootloader you are pointing to (mesh/"normal"). I believe it is better that you follow it up in the ticket you already have. I will ask the engineer that is assigned to that ticket to have a look at it.

Related