SDK 13 to SDK 14.2 upgrade mess !

RE: SDK 13 to SDK 14.2 upgrade mess !

Kyle Krueger — Thu, 21 Dec 2017 11:52:22 GMT

They could definitely do better, but I think they are improving.

RE: SDK 13 to SDK 14.2 upgrade mess !

JB21 — Thu, 07 Dec 2017 00:07:17 GMT

Thanks Kyle, The migration guide was not included in the downloadable docu, so I did not see it. Thanks for your pointer.

IIt took me 2 days to get my code running again, initially I had planned an hour for it. I expected some code changes, but not to be forced to create makefile and sdk_config.h from scratch.

Nordic should have provided some conversion tools, and better documentation.

Further, the docu should specify for each function which module has to be included into the makefile.

For example I could not get the saadc linked until I searched the example folder and discovered that now 2 modules have to be included in the makefile. You can't make our life any harder than that. I feel forced to do parttime reverse engineering.

RE: SDK 13 to SDK 14.2 upgrade mess !

Kyle Krueger — Mon, 04 Dec 2017 15:43:09 GMT

From 13.0 to 14.2 is a major upgrade. I agree it could be made easier to follow the process, but I think that Nordic is working hard to improve this process. In the past, migration guides were not included, but for both SDK V13 and V14, a new section has been included to help ease the transition. The renaming of the softdevice_handler, and many other files are mentioned there. Here is the SDK14 migration guide

If you are still having issues after reading the migration guide, I would recommend sorting all of your source files and includes in the Makefile into four categories. Nordic core files, Nordic Module files that you use, third party files, and lastly your custom files. Once you have done this, it is much easier to find out which ones are missing or renamed.

As for improvements going to SDK 14, two great reasons I can think of are proper support for the Buttonless DFU Updates, and some BLE5 support.

Furthermore, I think the API has improved in a few aspects (albeit regressed in some). These improvements should help keep your code more maintainable; if your project is intended to have a long lifetime this is important!

In addition, better support on devzone (more people will be using the latest).