Bonding randomly loss after DFU

Hi there,

I am using nrf connect sdk v2.6.0. I have noticed that after DFU update, I am seeing ble bonding lost randomly on firmware side. I did uncheck Erase Application Settings before DFU and I tried on both Device Manager app as well as nrf connect app and on both Android/IOS. I am attaching dts snippet and prj.conf for reference.

Thanks M

&flash0 {

	partitions {
		compatible = "fixed-partitions";
		#address-cells = <1>;
		#size-cells = <1>;

		boot_partition: partition@0 {
			label = "mcuboot";
			reg = <0x00000000 0x0000C000>;
		};
		slot0_partition: partition@c000 {
			label = "image-0";
			reg = <0x0000C000 0x00076000>;
		};
		slot1_partition: partition@82000 {
			label = "image-1";
			reg = <0x00082000 0x00076000>;
		};

		/*
		 * The flash starting at 0x000f8000 and ending at
		 * 0x000fffff is reserved for use by the application.
		 */

		/*
		 * Storage partition will be used by FCB/LittleFS/NVS
		 * if enabled.
		 */

		app_storage_partition: partition@f8000 {
			label = "appstorage";
			reg = <0x000f8000 0x00006000>;
		};
		storage_partition: partition@fe000 {
			label = "storage";
			reg = <0x000fe000 0x00002000>;
		};
	};
};

6786.prj.conf

Parents Reply
  • Hi  , its not quite a solution since storing the bonding info in nvs partition won't help as I still need to store it to BLE stack. Issue is that when I update DFU, bonding info are lost from BLE stack. Keeping copy of last bonding won't help as I still need to find a way to restore it in ble stack by reading the nvs partition upon power up and if bonding is lost in the stack, rewrite to it so that App side doesn't complain.

Children
Related