Mesh: 0xDEADBEEF on Debugger Halt

[mesh777]

I have functioning firmware which produces 0xdeadbeef if I halt debugger. Is it not intended by the SoftDevice in normal operation?

How to debug this issue?

[Karl Ylvisaker]

Hello,

I have functioning firmware which produces 0xdeadbeef if I halt debugger. Is it not intended by the SoftDevice in normal operation?

The SoftDevice will assert if it is unable to meet its timing-critical deadlines because it is unable to use the CPU.
This is what happens when the CPU is halted, and the SoftDevice has an upcoming BLE event it needs to handle.
When the SoftDevice is given back control of the CPU again it will immediately assert.
Please take a look at this answer by my colleague Susheel, for a more in-depth explanation.

Best regards,
Karl