<?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>S120 stack re-writing itself?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/5222/s120-stack-re-writing-itself</link><description>Our application uses the S120 stack, and a bootloader. We want the bootloader to be able to update both our application software and the S120 stack (preserving the MBR). 
 We create a single binary image from the S120 and application hex files, using</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 07 Feb 2015 13:36:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/5222/s120-stack-re-writing-itself" /><item><title>RE: S120 stack re-writing itself?</title><link>https://devzone.nordicsemi.com/thread/18298?ContentTypeID=1</link><pubDate>Sat, 07 Feb 2015 13:36:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7e1d17c3-19f0-486a-bdd2-12802e8036f7</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Michael,&lt;/p&gt;
&lt;p&gt;Yes, address 0xC00 is belong to the MBR and the MBR does use that page of the flash to store configuration data and will erase them when needed.&lt;/p&gt;
&lt;p&gt;You can try to use mergehex.exe and hex2bin.exe tool to combine hex file and convert it to binary. As far as I can see, it will leave the gap as 0xFFFF.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>