<?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 Desktop - Programmer - Unexpected memory regions after DFU</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/62342/nrf-connect-desktop---programmer---unexpected-memory-regions-after-dfu</link><description>Hello, 
 I am working on the Nordic DFU to develop a bootloader for OTA update on our product. 
 So far I just ported the Secure Bootloader from Nordic examples. No functionality has been changed. 
 Testing the DFU with different security settings and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 14 Jun 2020 18:01:46 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/62342/nrf-connect-desktop---programmer---unexpected-memory-regions-after-dfu" /><item><title>RE: nRF Connect Desktop - Programmer - Unexpected memory regions after DFU</title><link>https://devzone.nordicsemi.com/thread/254856?ContentTypeID=1</link><pubDate>Sun, 14 Jun 2020 18:01:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9aadd24a-e88d-47e2-9749-4f21dcd66f22</guid><dc:creator>davege</dc:creator><description>&lt;p&gt;You are absolutely right Vidar! I looked at the content, and those are effective the tag from FDS (1 swap and 2 data).&lt;/p&gt;
&lt;p&gt;Thanks for immediately pointing at that and your very quick reply!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect Desktop - Programmer - Unexpected memory regions after DFU</title><link>https://devzone.nordicsemi.com/thread/253979?ContentTypeID=1</link><pubDate>Tue, 09 Jun 2020 09:23:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dd2f4e6e-4fd9-42c2-bcf8-7595afd2a89b</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;FDS will tag each of its allocated flash page with a magic word on first boot, see &lt;span&gt;&lt;a title="Page tag" href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/lib_fds_format.html?cp=7_1_3_56_2_1#lib_fds_format_page"&gt;Page tag&lt;/a&gt;&lt;/span&gt;. Did you initialize the peer manager in your app? In that case, those three pages that are shown in the app data region (&lt;span&gt;&lt;a title="Memory layout" href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/lib_bootloader.html?cp=7_1_3_5_0_7#lib_bootloader_memory"&gt;Memory layout&lt;/a&gt;&lt;/span&gt;)&amp;nbsp; are going to be from the &lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/lib_fds.html"&gt;FDS &lt;/a&gt;(peer manager inits FDS to handle NV storage).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>