• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 62 subscribers
  • Views 2508 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 109363
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Persist Bond Information Across DFU

Cory Mast

Hello,

I am currently working on a project based on the ANCS demo from the SDK. Everything is working great with the exception of bonding and DFU. The first step is to connect and bond to my device. The next step is to start the DFU bootloader. I am starting DFU from a custom characteristic and I can successfully DFU a new application to my board. The problem is that when the DFU is finished, i have to forget the bond on my iOS device and then repair the iOS device to my ANCS device. Essentially I would like to Bond to my ANCS device, start and complete the DFU process, and then have my iOS device reconnect to my ANCS device automatically without having to repair the two devices. Is it not possible to make the bonding information persist across a DFU? Am i doing something wrong?

Here is some code from dfu_types.h

#define BOOTLOADER_REGION_START         0x0003C000
#define BOOTLOADER_SETTINGS_ADDRESS     0x0003FC00

#define DFU_APP_DATA_RESERVED           0x1000
#define DFU_BANK_PADDING                (DFU_APP_DATA_RESERVED % (2 * CODE_PAGE_SIZE))

Im not quite sure what Im doing wrong and any help or direction anyone can provide would be greatly appreciated.

Thanks!

Cory

Related