<?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>VSCode debugger exception</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/120373/vscode-debugger-exception</link><description>I am using VSCode with the nRF Connect extension (latest) and SDK 2.9.1. 
 I made my new app from the Bluetooth Peripheral sample. 
 When I try to debug I get the following exception: 
 
 Here is the call stack: 
 
 I started getting this yesterday and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 01 Apr 2025 18:27:05 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/120373/vscode-debugger-exception" /><item><title>RE: VSCode debugger exception</title><link>https://devzone.nordicsemi.com/thread/530068?ContentTypeID=1</link><pubDate>Tue, 01 Apr 2025 18:27:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:669d3125-4ac0-46f7-9904-941ac5c5baf7</guid><dc:creator>Tony</dc:creator><description>&lt;p&gt;Turns out you are partially correct. I had several breakpoints all over the code. I decided to remove all breakpoints and put just one where I wanted it. i was able to debug by starting the debug, that just runs but isn&amp;#39;t really running. Then I hit the restart button mentioned above and it starts over and breaks in the idle loop infinite loop and when I hit run it hits my breakpoint.&lt;/p&gt;
&lt;p&gt;This leads me to believe that the issue was one of my breakpoints being in a bad spot causing that exception.&lt;/p&gt;
&lt;p&gt;No idea where or how so closing this ticket.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: VSCode debugger exception</title><link>https://devzone.nordicsemi.com/thread/530065?ContentTypeID=1</link><pubDate>Tue, 01 Apr 2025 18:10:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1e7dc532-1c8b-480c-9cf4-de4b189dc604</guid><dc:creator>Tony</dc:creator><description>&lt;p&gt;How do I hit even the first breakpoint? I am getting this exception right off the bat.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: VSCode debugger exception</title><link>https://devzone.nordicsemi.com/thread/530064?ContentTypeID=1</link><pubDate>Tue, 01 Apr 2025 18:03:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c0b62329-e37c-46ab-837d-1b4bb47ae2e9</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;Normal behaviour for any of the single core MCU once softdevice/BT was enabled.&lt;/p&gt;
&lt;p&gt;The softdevice will always fault due to the BT timing violation when the MCU was stopped for debugging. &lt;/p&gt;
&lt;p&gt;Breakpoints will work when set before app start, but you will never be able to &amp;quot;continue&amp;quot;.&lt;/p&gt;
&lt;p&gt;The only exception is on the NRF5340 dual core MCU - because the debugger won&amp;#39;t stop the network core here.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>