DFU Example hardfaults

RE: DFU Example hardfaults

bjorn-spockeli — Wed, 30 Nov 2016 09:23:07 GMT

Hi Joep,

when the softdevice is enabled and there is BLE activity then it is difficult to debug an application since the softdevice interrupts have the highest priority. Thus, when a softdevice interrupt triggers the real-time requirements will be broken by the breakpoint you set in your application, it will assert immediately and this is an unrecoverable fault unless you reset chip.

It is possible to set the PRIMASK bit, which allows you to debug until the next sd_ - function call, you can read more about it in the posts I have linked to below.

devzone.nordicsemi.com/.../

Best regards

Bjørn

RE: DFU Example hardfaults

Joep — Tue, 29 Nov 2016 11:42:00 GMT

That is going back 10y in time... When we debug an application not using a bootloader we can debug w/o problems, also using the Softdevice. Ofcourse stopping the program while SD is busy may cause communication issues due to timeouts, but hardfaults?

RE: DFU Example hardfaults

Alex — Tue, 29 Nov 2016 10:13:12 GMT

RTT debug output.

RE: DFU Example hardfaults

Joep — Tue, 29 Nov 2016 10:12:03 GMT

Thanks for your answer Alex, but how on earth I would debug a program then???

RE: DFU Example hardfaults

Alex — Tue, 29 Nov 2016 09:47:39 GMT

You can't run after break if SD started. It is how it works. So if you put break point before SD started you can continue without hard fault. After SD started it is impossible.