nrf51822: Is it possible to update softdevice and bootloader with fota in one single update package?

[Nobody13]

I am testing the Nordic nrf51822 chip.

I have rewritten a bootloader example allowing firmware updates via Bluetooth LE (FOTA). A mobile phone will sent the update package via nRFToolbox app. Firmware and bootloader updates works good. Softdevice updates seems to work also. I am using softdevice 110 version 8.0.2.

Working with Keil IDE and especially its functions "Pack Installer", "Select Software Packs…", "Manage Run-Time Environment" I have detected several incompatibilities between softdevice and bootloader. If I change softdevice to version to 8.0.3 the Manage Run-Time Environment dialog appears showing an incompatibility. It seems if I change the softdevice version I need a new bootloader version.

If this chip is used in an other device, and its customer want to update the chip, its means an update of softdevice and bootloader in one update package and an additional firmware update (package). Therefore I generated am update package via nrfutil containing bootloader and softdevice and copied it to the mobile phone. However nRFToolbox app doesn't want this file and refuses upload. Why?

So my question is: Is it possible to update softdevice and bootloader with fota in one single update package?

Of course, customer may send the device for update to us. We open the device, put the cable on, update the whole chip, mount the device and send is back. However this is not what we want.

Or does it mean the softdevice version shall not be modified over the whole device livetime?

[Hung Bui]

Hi somebody,

• I would suggest to use the independent .zip file for the SDK instead of using packs. The .zip SDK file can be found here.

• Yes, you can do bootloader and softdevice at the same time. Could you take a screenshot when "However nRFToolbox app doesn't want this file and refuses upload" ? Also please upload your .zip DFU file that has the bootloader and softdevice, also the script you used for nrfutil to generate it.

[Nobody13]

Found solution after checking package generation.

The problem was simple. App nrfToolbox shows a "invalid file" status after selecting file update package.

The solution is really easy. Obviously nrfToolbox does not like plus character in file name of update package. If there is one in file name, nrfToolbox shows a "invalid file" status and refuses update button.