<?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>Restarting debug session fails on firmware verification</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/102735/restarting-debug-session-fails-on-firmware-verification</link><description>I have problem with debugging board with nRF9160 with VS Code. If I start debugging for fully erased chip it works just fine but if I try to restart debugging it throws an error and I have to fully erase the chip to get things going. 
 There is some keys</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 11 Aug 2023 06:19:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/102735/restarting-debug-session-fails-on-firmware-verification" /><item><title>RE: Restarting debug session fails on firmware verification</title><link>https://devzone.nordicsemi.com/thread/440863?ContentTypeID=1</link><pubDate>Fri, 11 Aug 2023 06:19:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0cff891e-b3c1-457d-8dae-8f8bdd056502</guid><dc:creator>mmade</dc:creator><description>&lt;p&gt;Yes I&amp;#39;m using secure boot.&lt;/p&gt;
&lt;p&gt;I tested Segger Ozone and it is okay to use as a workaround.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Restarting debug session fails on firmware verification</title><link>https://devzone.nordicsemi.com/thread/440724?ContentTypeID=1</link><pubDate>Thu, 10 Aug 2023 12:02:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:22c0cca0-88af-4583-8fc1-ca0ac3fd448e</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Unfortunately, this is a problematic scenario with the vs code debugger; ie. attaching the debugger without flashing. I will report this internally.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I suspect that you&amp;#39;re using secure boot (ie. the immutable bootloader)?&lt;/p&gt;
&lt;p&gt;If yes, then you need to erase the device between each flash operation, as it will write to UICR.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;As a workaround, you could use Segger Ozone as a debugger and see if this works better for you.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>