<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>No normal continuation after hitting a breakpoint</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/25791/no-normal-continuation-after-hitting-a-breakpoint</link><description>I’m debugging the ble_app_blinky demo on a nRF52840-Preview-DK board (BOARD_PCA10056, S140). The device name in the debug configuration is nrf52832_xxaa. 
 Each time a breakpoint has been hit and I press Resume, there is no normal program continuation</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 09 Oct 2017 21:31:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/25791/no-normal-continuation-after-hitting-a-breakpoint" /><item><title>RE: No normal continuation after hitting a breakpoint</title><link>https://devzone.nordicsemi.com/thread/101578?ContentTypeID=1</link><pubDate>Mon, 09 Oct 2017 21:31:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d2ee7cd4-d5b0-4faf-810b-6b96bf8d3f20</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;Please search for the many posts here about debugging with the softdevice. You basically can&amp;#39;t do it. Once the softdevice starts advertising and most certainly when it&amp;#39;s in connection it has very strict timing requirements. You can break, once, and see where it is, but you can&amp;#39;t resume again or the softdevice will assert.&lt;/p&gt;
&lt;p&gt;Also see the blog post from last year on monitor mode debugging which will allow you to debug with the softdevice running, for a while.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>