<?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>nRF Connect for VSCode debugger not hitting breakpoint</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/125179/nrf-connect-for-vscode-debugger-not-hitting-breakpoint</link><description>Hello, 
 whenever I try to debug my nRF Connect SDK application, I have problems with the nRF Connect for VSCode debugger in such an extent, that I can&amp;#39;t use it. 
 When I have started the debugger It breaks at the beginning of the main function, as expected</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 23 Oct 2025 13:56:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/125179/nrf-connect-for-vscode-debugger-not-hitting-breakpoint" /><item><title>RE: nRF Connect for VSCode debugger not hitting breakpoint</title><link>https://devzone.nordicsemi.com/thread/552272?ContentTypeID=1</link><pubDate>Thu, 23 Oct 2025 13:56:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:098c6599-70d7-4b03-944c-577d1f9973f5</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;Which MCU is that? You will get a fatal error in all of the single core MCUs (i.e. everything except NRF5340) when setting a breakpoint while BTLE was running.&lt;/p&gt;
&lt;p&gt;Reason is that the debugger messes with the sensitive BTLE timing (checked via HW timers) a little too much.&lt;/p&gt;
&lt;p&gt;Workaround: Reset MCU, set breakpoints&amp;nbsp;&lt;em&gt;before&lt;/em&gt; enabling BTLE in main.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>