Bonding randomly loss after DFU

[Moh]

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

[Amanda Hsieh]

Hi, 

I am seeing ble bonding lost randomly on firmware side.

Did you add the related codes as this course https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-5-bluetooth-le-security-fundamentals/topic/blefund-lesson-5-exercise-2/?

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.

Did you check if the "Erase application settings" is disabled every time?

Regards,
Amanda H.

[Thibaud]

Hello

I am facing the same issue. I feel like it is related to the application size even if the settings partition is exactly the same in both partitions manager.

I explain myself : I programmed 2 different versions (47 and 50) of my BLE peripheral application in 2 application slots of 1 product. Both versions have differences, not related to advertising or pairing, but they ended up not having the same size. I connect my product in v50 to my phone with bounding etc, everything is fine I can reset either my phone or my product and they re connect automaticaly.  When I swap my product in v47 with nRF Connect application for smartphone I can't connect to my phone anymore, I have disconencted reason 19 in the log of my product meaning bouding informations have been lost. But if i swap back my product to v50 I can connect again. 

Here is screenshots illustrating my words : 

Screenshot from the programmer of nRF Connect for Desktop, showing both application are of different sizes.

 

v47 partitions manager

v50 partitions manager

My applications are based on sdk v2.5.0.

May the issue come from the settings_load() function ? Maybe instead of looking to a particular address it is using the difference between the end of the application and the beginning of settings storage partition ?

[Thibaud]

Hi I've tested again and even with a same sized version of my application I can't re connect after swapping images. It can't be related to slot 0 or slot 1 because Mcuboot is always starting at slot 0, after DFU it is swapping images so your new image is in Slot 0.

[Amanda Hsieh]

 Mohsin and   Thibaud, Do you update with the same pm_static.yml for the original and new image?

[Moh]

Yes I did

[Amanda Hsieh]

I am using nrf connect sdk v2.6.0.

Since v2.6.0 is quite old, could you try to use v3.1.0?

You can refer to https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-5-bluetooth-le-security-fundamentals/topic/blefund-lesson-5-exercise-2/ or test with l5_e2_sol. 

[Thibaud]

Hello I tried to update to SDK v2.9.0 once and I have kconfig option deprecated and my app is not building anymore. I followed this tutorial when I made my application. I am also using the same partitions management between my 2 versions. I can try with ble peripheral sample in both sdk v2.5.0 and v3.1.0 to see if I have different behavior.