https://devzone.nordicsemi.com/f/nordic-q-a/1342/s110-seems-to-crash-after-device-discovery-from-master-control-panelHi, My setup is a nRFgo QFAA FA with S110 v.6.0.0 and Motherboard. I am using the latest SDK 5.1.0. The Master Control Panel drives the nrf51822 USB development dongle. I&#39;m trying to implement a Serial Cable Replacement use case based on the Hearten-USTelligent Community 13Wed, 29 Jan 2014 20:05:27 GMThttps://devzone.nordicsemi.com/thread/6117?ContentTypeID=1Wed, 29 Jan 2014 20:05:27 GMT137ad170-7792-4731-bb38-c0d22fbe4515:76ef375b-c6b5-486d-9dae-c52968342814Richard von Lehe<p>I&#39;ve seen similar problems and when doing the exact same sequences between Eclipse controlling the gdb-server and a command-line gdb client, the command-line gdb client works better. In my case, I am able to hit a breakpoint I set at on_ble_evt in ble_app_lbs, but when I try the same thing via eclipse, I get this as the call stack: 0xfffffffe &lt;signal handler called&gt;() at 0xfffffff1 0x11498 &lt;signal handler called&gt;() at 0xfffffff9 app_sched_event_get() at app_scheduler.c:143 0x16c80 app_sched_execute() at app_scheduler.c:175 0x16d48 main() at main.c:658 0x14f80</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/6116?ContentTypeID=1Tue, 14 Jan 2014 10:29:39 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b5046eed-0bf5-4dc5-8106-0b7130a4469aOle Morten<p>I&#39;d recommend you to remove the reset from app_error_handler and put an infinite loop and a breakpoint there, to see if you hit any errors in your application. Also, I&#39;d also recommend you to try running your application with the GDB command line debugger and see if the behavior is different, since I&#39;ve sometimes seen strange behavior from Eclipse.</p> <p>Finally, make sure that you use the official startupfiles from the SDK.</p><div style="clear:both;"></div>