https://devzone.nordicsemi.com/f/nordic-q-a/60324/dfu-issue-with-centralHi, We have a Central device with a bootloader and wish to have OTA update feature. We have added code for it to advertise on a certain condition of a button press. Once it starts advertising we are able to connect using nrf_connect and then attempt aen-USTelligent Community 13Mon, 20 Apr 2020 16:51:18 GMThttps://devzone.nordicsemi.com/thread/245641?ContentTypeID=1Mon, 20 Apr 2020 16:51:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:66e22530-b4ca-45a3-948a-2d7805469e10Siddhesh<p>Hi Vidar,<br />We debugged the bootloader code and arrived at the conclusion that the softdevice was having issues enabling in the dfu_transport layer.<br />The issue was with a mismatch in clock configuration(CLOCK_LF_SRC, CLOCK_LF_ACCURACY, etc.) for Softdevice in the sdk_config between the application and bootloader. Once we used the same settings in both places, the DFU process worked successfully.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/245466?ContentTypeID=1Mon, 20 Apr 2020 09:16:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1d4b73f9-5e01-4f26-9776-d45e52c1c758Vidar Berg<p>Hi,</p> <p>Are you able to debug the bootloader code while the nrf connect client sends the DFU start command to your main application? In that case, please place a breakpoint at the beginning of bootloader main() to check if the application actually jumps to be bootloader. The CPU register content may give a clue of where the program is stuck when it is in the unknown state (e.g., check if the program counter value is in the bootloader, Softdevice, or application&#39;s address range).&nbsp;</p><div style="clear:both;"></div>