<?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>MBRPARAMADDR in SDS</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/36344/mbrparamaddr-in-sds</link><description>Hi, 
 
 In softdevice spec, we have the following figure. 
 
 However our bootloader code shows that MBRPARAMADDR is 0x7E000 while BOOTLOADERADDR is 0x78000. In this case, MBRPARAMADDR should be above BOOTLOADERADDR which is shown wrong in SDS. could</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 09 Jul 2018 12:46:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/36344/mbrparamaddr-in-sds" /><item><title>RE: MBRPARAMADDR in SDS</title><link>https://devzone.nordicsemi.com/thread/139823?ContentTypeID=1</link><pubDate>Mon, 09 Jul 2018 12:46:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ae0a359d-02ef-4d80-a9a3-bbe3bf21e912</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Kevin,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I agree that the figure is a little bit misleading. However, our bootloader is just an example of how a bootloader can be implemented. So it&amp;#39;s not obligated that the&amp;nbsp;MBRPARAMADDR has to be above the bootloader address. If customer can define that the swap area shouldn&amp;#39;t occupy the&amp;nbsp;MBRPARAMADDR address, then he should be fine. The text in the SDS also didn&amp;#39;t imply that the&amp;nbsp;MBRPARAMADDR has to be below the&amp;nbsp;BOOTLOADERADDR.&lt;/p&gt;
&lt;p&gt;It of course should be nicer to demonstrate that the MBRPARAMADDR&amp;nbsp;is above the bootloader , as how we implemented it in the current bootloader. I can report this back to the team .&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>