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

DFU & Bonding problem

hello everybody,

I'm working in a project & have to do something like security for the connection & be able to do updates to firmwares, someone suggested that doing bonding, exhanging the IRK addresses & add to whitelist & next time advertise with the whitelist only & reject any other connection, this is a short discription about what I need to do, I'm successful at doing FOTA at the first time then bonding with the new firmware but failed to do multiple FOTA, I'm attaching the log file logfile.txt to show you the result when I'm trying to do FOTA when I'm bonded to the central, note that I'm using s110 softdevice & here is the code: main.c

I'm not able to use s130 because it tells me as the photo:

image description

Note that the packages I'm using is the latest version released :) :)

Parents
  • From what you have described, my understanding is that the first attempt to perform FOTA works fine for you, then you do the bonding and then later again trying to perform FOTA with a bonded peripheral, fails. There seem to be multiple workarounds but I think the best solution is to upgrade to NRF51822 IC revision 3, Softdevice S100 v8.0.0 and SDK 10.0.0, Since the support for sharing bond information between Bootloader and the Application was first implelemented from Softdevice v8.0.0 onwards. I'm also currently in the process of migrating my application to the above compatibility matrix, while keeping the IC revision to '2' still.

    OOTH, I've tested FOTA multiple times with success with the following Compatibility matrix (see below) and with one caveat that I delete the bond information before I perform FOTA and it works fine everytime for me :)

    • NRF51822 IC revision: 2
    • Softdevice: s110, v 7.1.0
    • SDK: v6.1.0
    • Android Application: Nordic's Android APP (nrf Toolbox and nrf MCP)
Reply
  • From what you have described, my understanding is that the first attempt to perform FOTA works fine for you, then you do the bonding and then later again trying to perform FOTA with a bonded peripheral, fails. There seem to be multiple workarounds but I think the best solution is to upgrade to NRF51822 IC revision 3, Softdevice S100 v8.0.0 and SDK 10.0.0, Since the support for sharing bond information between Bootloader and the Application was first implelemented from Softdevice v8.0.0 onwards. I'm also currently in the process of migrating my application to the above compatibility matrix, while keeping the IC revision to '2' still.

    OOTH, I've tested FOTA multiple times with success with the following Compatibility matrix (see below) and with one caveat that I delete the bond information before I perform FOTA and it works fine everytime for me :)

    • NRF51822 IC revision: 2
    • Softdevice: s110, v 7.1.0
    • SDK: v6.1.0
    • Android Application: Nordic's Android APP (nrf Toolbox and nrf MCP)
Children
No Data
Related