Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Upgrading project from nRF51 with SDK8 to nRF52 with SDK14

Hi! We've got a nRF51 based device where the firmware was developed on SDK version 8 (reportedly based on its hrs_c example) with S110 softdevice.
We are now developing a new version of the hardware based on nRF52. It is a good time to also upgrade the SDK version to the most recent one.

We are faced with two challenges: nRF51 --> nRF52, and SDK 8 --> SDK 14. And, I guess, S110 --> S140…ish? I am admittedly a bit hazy still on how this scheme works.
It would be nice if these can be done in two steps, so that we can e.g. verify on the old hardware that the SDK upgrade has been successful, to not have to troubleshoot two issues simultaneously. However, it seems that SDK8 does not support nRF52, and SDK14 does not support nRF51. SDK12 seems to be the last version to support nRF51.

However, judging from the fact that the diff between their respective examples/ble_central/ble_app_hrs_c/main.c files weighs over 900 lines, the differences between SDK12 and SDK14 seem extremely major, so there would be significant of work in first porting the firmware to SDK12 and then further porting it to SDK14.

Am I mistaken? How do you recommend I should proceed?

Related