https://devzone.nordicsemi.com/f/nordic-q-a/17029/do-i-have-to-worry-about-the-address-of-softdevice-app-etc-when-using-nrfgo-studioIt is to my understanding that you DO have to worry about that when using keil download function or other means to program either the softdevice or your program to the nrf514xx /nrf518xx devices, but is the same thing necessary for nRFgo studio? And whaten-USTelligent Community 13Mon, 17 Oct 2016 07:54:17 GMThttps://devzone.nordicsemi.com/thread/65318?ContentTypeID=1Mon, 17 Oct 2016 07:54:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e8c8b088-10cd-4268-8ced-d55042fd1f57Petter Myhre<p>Maybe <a href="https://www.youtube.com/watch?v=tZjlixQPO-Q">this</a> video explains it.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/65317?ContentTypeID=1Fri, 14 Oct 2016 01:18:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:11446785-091d-4061-82c5-d0e7d0105737Mitch996<p>Well I&#39;m just gonna slack it on and ask how exactly does nrf51xxx devices interact with the softdevice and my compiled firmware? As in, how does it know where in the memory does my firmware begin? Or, maybe the firmware address were given by a .s file (configurable in keil, that magic wand button), and relevant softdevice information can then be found in the firmware (decided by include header files)? I could use a bit more detail. Thanks in advance.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/65316?ContentTypeID=1Thu, 13 Oct 2016 10:11:49 GMT137ad170-7792-4731-bb38-c0d22fbe4515:765c36c9-7435-4118-852b-94d3bb209cc9Wojtek<p>Assuming that you don&#39;t compile SoftDevice by yourself (obviously), and you take it from the SDK - hex has correct addresses inside, so you don&#39;t have to worry. You can read more about hex format <a href="https://en.wikipedia.org/wiki/Intel_HEX">here</a>, so you could understand it better. Same for the application - it is flashed to location, where it is supposed to be flashed according to the compilation settings.</p><div style="clear:both;"></div>