<?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>What&amp;#39;s the difference between this hex files with _mbr suffix and how do you generate them?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/56135/what-s-the-difference-between-this-hex-files-with-_mbr-suffix-and-how-do-you-generate-them</link><description>in SDK/examples/peripheral/blinky/ hex 
 there is one file 
 blinky_pca10056 _mbr .hex 
 
 in 
 SDK/examples/peripheral/blinky/pca10056/ mbr /ses/Output/Release/Exe 
 there&amp;#39;s one file 
 blinky_pca10056 _mbr .hex 
 
 I have compared the content of these</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 03 Jan 2020 13:15:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/56135/what-s-the-difference-between-this-hex-files-with-_mbr-suffix-and-how-do-you-generate-them" /><item><title>RE: What's the difference between this hex files with _mbr suffix and how do you generate them?</title><link>https://devzone.nordicsemi.com/thread/227417?ContentTypeID=1</link><pubDate>Fri, 03 Jan 2020 13:15:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d4cb84f6-0418-4384-a368-3791336312d8</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I will answer in reversed order.&lt;/p&gt;
&lt;p&gt;2. The&amp;nbsp;blinky_pca10056_mbr.hex that is generated under &amp;lt;SDK&amp;gt;/examples/peripheral/blinky/pca10056/mbr/ses/Output/Release/Exe is the result when building the SES project&amp;nbsp;blinky_pca10056_mbr.emProject. This includes only the blinky application, but it starts at page 1 (FLASH_START=0x1000), making room for the MBR in page 0. It also reserves the first 8 bytes of RAM for the MBR, so&amp;nbsp;RAM_START is set to&amp;nbsp;0x20000008 (instead of&amp;nbsp;0x20000000 as is the case for the non-mbr project). Code execution always starts from address 0, so this will only work if you also flash the MBR .hex file.&lt;/p&gt;
&lt;p&gt;1. The&amp;nbsp;blinky_pca10056_mbr.hex from &amp;lt;SDK&amp;gt;/examples/peripheral/blinky/hex is the result of merging the .hex file generated as described above and the MBR .hex file from &amp;lt;SDK&amp;gt;\components\softdevice\mbr\hex\. This is done for convenience since that allows you to just flash that single file to test, instead of having to flash both .hex files separately (or merge them yourself).&lt;/p&gt;
&lt;p&gt;You can merge the files yourself if you want using the mergehex tool that is part of &lt;a href="https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools"&gt;nRF Command Line Tools&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>