https://devzone.nordicsemi.com/f/nordic-q-a/77681/mesh-0xdeadbeef-on-debugger-haltI 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?en-USTelligent Community 13Tue, 20 Jul 2021 11:46:56 GMThttps://devzone.nordicsemi.com/thread/320875?ContentTypeID=1Tue, 20 Jul 2021 11:46:56 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7dd0d1aa-f726-444f-98cc-20bfca533340Karl Ylvisaker<p>Hello,</p> [quote user=""]I have functioning firmware which produces 0xdeadbeef if I halt debugger. Is it not intended by the SoftDevice in normal operation?[/quote] <p>The SoftDevice will assert if it is unable to meet its timing-critical deadlines because it is unable to use the CPU.<br />This is what happens when the CPU is halted, and the SoftDevice has an upcoming BLE event it needs to handle.<br />When the SoftDevice is given back control of the CPU again it will immediately assert.<br />Please take a look at this answer <a href="https://devzone.nordicsemi.com/f/nordic-q-a/9622/application-debug-with-softdevice">by my colleague Susheel, for a more in-depth explanation</a>.<br /><br />Best regards,<br />Karl</p><div style="clear:both;"></div>