How to proceed for migrating from 'SoftDevice_132_3.0.0' to newest SoftDevice and SDK?

[Mircea Coman]

Hi,

We have a device based on nrf_52840, SoftDevice_132_3.0.0 and SDK_12.3.0, using BLE for communicating to a PhoneApp and UART for communicating to a washing machine.

The device is in production and it's being delivered to clients for 2+years already.

We are thinking about migrating to SoftDevice_S140 which might fix some problems we have (erasing/writing specific flash pages) : see https://devzone.nordicsemi.com/f/nordic-q-a/41744/sd_flash_page_erase-returns-nrf_error_forbidden

We hope this might improve other areas, as advertising.

Can you tell us how it would be best / easiest to aproach such a migration? I've researched a little bit the SoftDevice versions and iterations available and also SDK versions and there's a lot of version to choose from (both SD and SDK) - each coming with its migration guide.

We are concerned this migration might take a lot of time and might introduce new issues which we don't want, of course :-)

Any suggestions will be apreciated.

Thank you in advance.

[Jared]

Hi,

It depends a bit on your application, such as the complexity and what libraries you're using such as DFU, bonding etc. There has been some big changes since SDK 12.3.0. One of the most important ones were introduced in SDK 14.0.0. Softdevice events are now delivered to the application atomically, after the application registers itself as a BLE stack event observer. See this. 

I think the easiest and best method would be to start with a new SDK BLE example and then integrate your code into that example.

regards

Jared