https://devzone.nordicsemi.com/f/nordic-q-a/13832/application-file-is-not-working-after-with-bootloaderHi.. Everyone, i am using nrf52 with softdevice 132. i used peer manager. i am able to able to flash softdevice, bootloader and application. but after that application file is not working on my board. i had also refer this links.. link 1 en-USTelligent Community 13Wed, 18 May 2016 07:30:35 GMThttps://devzone.nordicsemi.com/thread/52853?ContentTypeID=1Wed, 18 May 2016 07:30:35 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6931d077-7740-42b2-85fe-19137bfc674fVidar Berg<p>Some common ways of setting the bank valid flag from the <a href="https://devzone.nordicsemi.com/blogs/685/common-faq-on-dfu/"><strong>DFU FAQ</strong></a>:</p> <ul> <li>Use programmer to write directly 0x01 to that address of BOOTLOADER_SETTINGS_ADDRESS (0x0003FC00).</li> <li>Modify the bootloader firmware to write 0x01 to that address using attribute . It&#39;s the same way as we did on writing to NRF_UICR_BOOT_START_ADDRESS the value of BOOTLOADER_REGION_START (see bootloader_setting_arm.c)</li> <li>Combine the a hex that specifically set the byte to 0x01 at BOOTLOADER_SETTINGS_ADDRESS with the hex file of your application. You can also combine the bootloader hex and softdevice file to that combination, to create a single hex file for all of them. This solution is described here. The app_valid_setting_apply.hex is the hex that does the trick. This is very useful when you are doing gang programming.</li> </ul> <p>I would suggest the 2nd approach also proposed in one of the threads you linked to if want to include the bootloader setting in the .hex file.</p><div style="clear:both;"></div>