Need confirmation on what is going wrong in hex file created using mergehexhttps://devzone.nordicsemi.com/f/nordic-q-a/124237/need-confirmation-on-what-is-going-wrong-in-hex-file-created-using-mergehexHi, Please note that I am using below setup NRF SDK17.0.2 Softdevice 7.2.0 For one of my application, I am trying to generate combined hex file with DFU, Softdevice, Bootloader settings and application file using mergehex command as below en-USTelligent Community 13Tue, 09 Sep 2025 18:10:39 GMTRE: Need confirmation on what is going wrong in hex file created using mergehexhttps://devzone.nordicsemi.com/thread/548284?ContentTypeID=1Tue, 09 Sep 2025 18:10:39 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ff4d03b7-3c43-49f8-adad-9b20e7cc7432Hieu<p>Hi Dinesh,</p> <p>When you load the hex file(s), the Programmer has full context of the different regions, so it can visualize the different flash region as described in the files.</p> <p>When you read back from the flash memory, the app doesn&#39;t have any context, so it just split the regions if there is several blank region in between.</p> <p>Meanwhile, the MBR writes some data to FF8-FFF, so the Programmer app thinks that FF8-FFF and the bootloader is a continuous daya region, and visualize it as such.</p> <p>In short, there is nothing wrong.</p> <p></p> <p style="text-align:left;">Hieu</p><div style="clear:both;"></div>