DFU & IOS & Bonding

[Mohamed O.Abouzeid]

Hi guys,

in my application, I'm trying to do multiple fota, I succeed at the first time & after that I can jump again to the bootloader, but after that something is going wrong, bonds with bootloader are erased and I cannot connect to it again even it had finished the timeout and back again to the original firmware, I don't if someone face this problem before.

one more thing, I couldn't do multiple fota with IOS, I couldn't even jump to "dfutarg or bootloader" again because my new device is defined in the paired list & it's already connect to it through the settings, that's why I don't know how to jump again to the bootloader to do fota.

finally, for my final product, how can I avoid using "App_error_check". is there any standard method to do this or I have to do it my self.

kindly be noted that I'm using sdk12 and one of the examples called 'ANCS".

thanks.

[Hung Bui]

@mohamed: How did you bond to the device (when the "Pair with this device?"pop up appear) ? You bond when you are in bootloader mode or you bond when you are in application mode (ANCS)?

If you bond in application mode and you don't want to lose bond after you do DFU, you would need to define how much space you want to reserve for the bond information.

If you are using the secure bootloader from SDK v12, you can have a look here

You would need to match the APP_DATA_RESERVED size with the size of the fds (or pstorage) you used for peermanager/device manager. On SDK v12 it's 3 virtual page (3kB on nRF51 and 12kB on nRF52)