https://devzone.nordicsemi.com/f/nordic-q-a/27615/dfu-ota-bootloader-with-bonding-info-sdk-14-2-0-failsHi, We are having problems trying to integrate support for maintaining application context and bonding info across firmware OTA updates on our NRF52 (nRF52832) based board. The problem is that we can&#39;t find a working combination of bootloader anden-USTelligent Community 13Tue, 28 Nov 2017 12:27:48 GMThttps://devzone.nordicsemi.com/thread/109067?ContentTypeID=1Tue, 28 Nov 2017 12:27:48 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d557dec9-f807-43a2-bc0d-ec2dbb9c16f1Hung Bui<p>Hi Nate,</p> <p>I would not suggest to test with the precompile hex file but to build your own bootloader (with your public key) and the .zip file with your own private key.</p> <p>Could you let me know which SDK you used on your previous bootloader and application ? Did you set the correct <a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v14.2.0/lib_bootloader_dfu_banks.html?cp=4_0_0_3_5_1_2_2#lib_bootloader_dfu_appdata">Preserving application data</a> as described here ? ,to preserver the bond information.</p> <p>Note that on earlier version of the SDK (SDK 13 and earlier) we don&#39;t support bond information forwarding when doing DFU. You still can preserve bond information but when doing OTA DFU the link is open. I&#39;m not sure it&#39;s a requirement of you that the link should be encrypted when doing DFU or not. The &quot;with bond&quot; in the precompiled hex files are about the bond forwarding for encryption when doing DFU.</p> <p>You should test first with just no bond to check if the application data is preserved or not.</p><div style="clear:both;"></div>