https://devzone.nordicsemi.com/f/nordic-q-a/12073/how-does-the-nrfjprog-know-the-addresses-of-area-to-programI&#39;m curious. I believe I can set it up in the keil &quot;options-&gt;target&quot; tab. I get it that as long as I don&#39;t cause the softdevice and my program to &quot;overlap&quot;, it is fine, but I clearly cannot guarantee there wouldn&#39;t be a huge &quot;gap&quot; between the endingen-USTelligent Community 13Tue, 23 Feb 2016 07:25:38 GMThttps://devzone.nordicsemi.com/thread/45689?ContentTypeID=1Tue, 23 Feb 2016 07:25:38 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fe318b06-352c-4db0-8bbd-245253ff0e20Einar Thorsrud<p>The firmware you supply to nrfjprog (no matter if it is application, SoftDevice, bootloader or something else) is in <a href="https://en.wikipedia.org/wiki/Intel_HEX">Intel HEX</a> format. This file contains the address along with the data. This means that the addresses are decide when you build the hex file, and not by nrfjprog.</p> <p>If you change the start address of your application in Keil, you will see that the hex file changes accordingly (note that just moving your application to a random address will make it fail, as it of course has to be in the expected location, but you can do it to see how the hex file works.</p> <p>If you analyze the hex file in a editor you should note that in addition to the address field of every line (byte second and third byte) there is often a shorter line with record type (byte four) Extended Linear Address. This specify the upper 16 bits of the 32-bit absolute address for all subsequent data records. For example, this is always needed for the application hex file when the SoftDevice is used, as the address will be higher than 16 bit.</p><div style="clear:both;"></div>