https://devzone.nordicsemi.com/f/nordic-q-a/109102/breakpoint-in-application-software-crushes-the-applicationHi, when I set a breakpoint in my application SW, after few steps over or into, the application crushes, and jumps to app_error_weak.c and stops on SW breakpoint in line #100: I&#39;m using: MURATA: MBN52832 SDK - 17.0.2 (nRF5SDK1702d674dde) en-USTelligent Community 13Mon, 11 Mar 2024 15:25:50 GMThttps://devzone.nordicsemi.com/thread/473260?ContentTypeID=1Mon, 11 Mar 2024 15:25:50 GMT137ad170-7792-4731-bb38-c0d22fbe4515:902c6c60-910e-4c20-9d25-4c2746d0e41fSimonr<p>Hi</p> <p>Please check out <a href="https://wiki.segger.com/nRF52_Series_Devices#Monitor_Mode_Debugging_on_Nordic_nRF52">this wiki page from SEGGER</a> on how to debug nRF52 devices. Here you have a monitor mode that specifically lets you run without making the SoftDevice timing out as you debug.</p> <p>Best regards,</p> <p>Simon</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/473061?ContentTypeID=1Sun, 10 Mar 2024 10:29:48 GMT137ad170-7792-4731-bb38-c0d22fbe4515:614aa4b6-0f5f-43f0-a397-98ff79afd38dRan Aricha<p>So, how can I debug my SW behavior upon BLE message?</p> <p>Can the debugger turn off&nbsp;BLE upon breakpoint?</p> <p>Can&nbsp;I configure the soft-device to ignore such timing error (the BLE can be malfunction afterward...)?</p> <p>If I will use s112 instead on s132, will it help?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/473060?ContentTypeID=1Sun, 10 Mar 2024 10:10:36 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f134297a-3fd8-4a24-8712-1b0f33f8daccTurbo J<p>Normal and intended behavior.</p> <p>Softdevice checks the very strict BTLE timings and will thus always assert after hitting a breakpoint unless BT was completely turned OFF.</p><div style="clear:both;"></div>