<?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>BLE Advertising and breakpoints</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/97223/ble-advertising-and-breakpoints</link><description>I&amp;#39;m just getting started with an Adafruit ItsyBitsy nRF52840 and a Raspberry Pi Pico debugger running OpenOCD, using CLion as my IDE. 
 Everything works pretty well but I am having difficulty setting breakpoints if I enable BLE advertising. If I disable</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 01 Mar 2023 22:32:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/97223/ble-advertising-and-breakpoints" /><item><title>RE: BLE Advertising and breakpoints</title><link>https://devzone.nordicsemi.com/thread/412852?ContentTypeID=1</link><pubDate>Wed, 01 Mar 2023 22:32:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:479a7093-733f-4851-b64f-f504f3b09dd7</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;You either set the breakbpoints before starting, or you just reset the device. Otherwise its debugging via UART/RTT like its 1980.&lt;/p&gt;
&lt;p&gt;Using breakpoints properly requires the dual core NRF5340.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Advertising and breakpoints</title><link>https://devzone.nordicsemi.com/thread/412851?ContentTypeID=1</link><pubDate>Wed, 01 Mar 2023 22:25:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5291ccdf-f21a-4699-b7bf-6b2faff788f2</guid><dc:creator>MerseyViking</dc:creator><description>&lt;p&gt;Thanks Turbo, that makes sense. Is there any way to relax the timers or disable them? How does everyone else debug code when the BLE softdevice is running? Other than logging, or disabling BLE entirely.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Advertising and breakpoints</title><link>https://devzone.nordicsemi.com/thread/412850?ContentTypeID=1</link><pubDate>Wed, 01 Mar 2023 22:19:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:170c4b8c-ee73-4e2f-a7e1-31c7abec53fa</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;The softdevice checks for BTLE timing violations with the timer(s).&lt;/p&gt;
&lt;p&gt;Toggeling a breakpoint in the IDE usually halts the MCU for a short while - can be long&amp;nbsp; enough to upset those checks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>