<?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>Does enabling APPROTECT block DFU (BLE update via MCUboot)?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/125032/does-enabling-approtect-block-dfu-ble-update-via-mcuboot</link><description>Hi, 
 I’m working with an nRF52840 that supports Bluetooth Low Energy updates via MCUboot. 
 We want to enable APPROTECT on our production units to prevent competitors from attaching a debugger. To do this, we run the following command: 
 nrfjprog --memwr</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 21 Oct 2025 12:03:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/125032/does-enabling-approtect-block-dfu-ble-update-via-mcuboot" /><item><title>RE: Does enabling APPROTECT block DFU (BLE update via MCUboot)?</title><link>https://devzone.nordicsemi.com/thread/552060?ContentTypeID=1</link><pubDate>Tue, 21 Oct 2025 12:03:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1c140cfc-bba9-42d0-ac61-5e3ad2ef5957</guid><dc:creator>Wouter Van Bastelaere</dc:creator><description>&lt;p&gt;Hi Hung,&lt;/p&gt;
&lt;p&gt;thanks for your time.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m using nRF Connect SDK version 2.7.0.&lt;/p&gt;
&lt;p&gt;At this point, I&amp;rsquo;m unable to reproduce the issue, either on a minimal setup or on our original configuration where it was first observed.&lt;/p&gt;
&lt;p&gt;While it&amp;rsquo;s a bit concerning that the problem has disappeared, there&amp;rsquo;s not much I can do without being able to reproduce it.&lt;br /&gt;For now, I&amp;rsquo;ll consider this issue closed, unless it reappears in the future.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Wouter&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does enabling APPROTECT block DFU (BLE update via MCUboot)?</title><link>https://devzone.nordicsemi.com/thread/551802?ContentTypeID=1</link><pubDate>Fri, 17 Oct 2025 11:01:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9d6c7642-6084-4212-9e21-a8b8a0161fbf</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Wouter,&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t&amp;nbsp;see a reason why enable APPROTECT would cause problem with DFU.&amp;nbsp;&lt;br /&gt;When you observed that &amp;quot;&lt;span&gt;The update starts and almost immediately completes, reporting “Success”.&amp;quot; did you full erase the chip before flashing the application before DFU ? What can happen is that if the image is already on the secondary slot, it will not be transmitted again.&amp;nbsp;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Could you try to reproduce the issue on a simple smp server sample ? Please check if you can find any log from MCUBoot.&amp;nbsp;&lt;br /&gt;Which SDK version you are on&amp;nbsp; ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>