<?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>NRF52811_xxAA_REV2 verify failed with firmware compiled against nRF5 SDK v17.1.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/118828/nrf52811_xxaa_rev2-verify-failed-with-firmware-compiled-against-nrf5-sdk-v17-1-0</link><description>Hi, 
 We have a project based on NRF52811_xxAA_REV1 running on multiple devices without any problem. 
 Nordic announced recently newer version of SoC (REV2, aka B0) and since nrf5 SDK is present in &amp;quot;compatible downloads&amp;quot; I was (almost) sure, current firmware</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 11 Feb 2025 09:48:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/118828/nrf52811_xxaa_rev2-verify-failed-with-firmware-compiled-against-nrf5-sdk-v17-1-0" /><item><title>RE: NRF52811_xxAA_REV2 verify failed with firmware compiled against nRF5 SDK v17.1.0</title><link>https://devzone.nordicsemi.com/thread/522382?ContentTypeID=1</link><pubDate>Tue, 11 Feb 2025 09:48:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d4f16f08-77c0-4640-89c3-d92c11b1f5ca</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thank you for sharing your solution to the issue.&lt;/p&gt;
&lt;p&gt;I did find it a bit strange that an &lt;code&gt;--eraseall&lt;/code&gt; is needed, since the &lt;code&gt;--recover&lt;/code&gt; should already have erased all user available non-volatile memory. Nevertheless, it looks like use of watchdog timer could explain behavior like the one you see, yes, as described in &lt;span&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/84461/nrfjprog-verify-fails-with-chiperase"&gt;nrfjprog verify fails with chiperase&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards,&lt;br /&gt;Terje&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52811_xxAA_REV2 verify failed with firmware compiled against nRF5 SDK v17.1.0</title><link>https://devzone.nordicsemi.com/thread/522352?ContentTypeID=1</link><pubDate>Tue, 11 Feb 2025 08:15:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e44f96ac-5bbc-4fe9-a099-6590979402ff</guid><dc:creator>Mateoosh</dc:creator><description>&lt;p&gt;OK, I&amp;#39;ll reply to myself, since I made it work:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Based on&amp;nbsp;&lt;span&gt; &amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/84461/nrfjprog-verify-fails-with-chiperase"&gt;nrfjprog verify fails with chiperase&lt;/a&gt;&amp;nbsp;i introduced an --eraseall step , so instead of:&lt;/span&gt;&lt;/p&gt;
&lt;pre&gt;&lt;span&gt;nrfjprog -f nrf52 --recover&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span&gt;nrfjprog -f nrf52 --program fw.hex --verify&lt;/span&gt;&lt;/pre&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;(this workflow works with REV1 perfectly)&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I ran:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;pre&gt;&lt;span&gt;nrfjprog -f nrf52 --recover&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span&gt;nrfjprog -f nrf52 --eraseall&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span&gt;nrfjprog -f nrf52 --program fw.hex --verify&lt;/span&gt;&lt;/pre&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;and REV2 verify was OK, device runs :-)&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>