Using DFU Bootloader with an application on a newer SDK version

[matkusch]

Hello,

i am using the DFU Bootloader from the version 15.3.0 of the nrf connect SDK with the softdevice version 7.0.1 on a nrf52832.

In Addition i am using a modified HID example from the 16.0.0 nrf connect SDK where i manually added the DFU functionality.

So far everything was working, yet i was wondering if there could be any negative effects with this combination:

1. The bootloader from an older version of the nrf connect SDK, than the main application

2. Using the softdevice version 7.0.1 which apparently isn't supported on 15.3.0

3. Should i downgrade softdevice to version 6.1.1 which is compatible to both SDK versions if point 1 wont cause any issues?

Greetings

[Hung Bui]

Hi Mat, 

It's not suggested to use Softdevice v7.0.1 with the bootloader made for softdevice v6.1.1 

Have you updated the header file (ble_*.h ) to the new softdevice's header files ? Or you simply used the same header files on Softdevice v6.1.1 

Softdevice v6.1.1 and Softdevice v7.0.1 are quite similar and it may work when you replace them but there is no guarantee that there would be no problem. 

I would suggest to update the bootloader to the bootloader we have in SDK v16. 

Note that the current SDK is v17.0. 

[matkusch]

Thanks,

i didn't modify the ble_*.h at all, i just changed the loader file path to the newer SD version, and the SD ID for the DFU zip files, and everything was working fine after that. I'll use the bootloader from the v16 SDK mitigate any negative effects.