Migration from SDK_17.0.0 to SDK_17.0.2

[karanbakshi]

Hi All,

Currently I am using SDK_17.0.0 for nRF52832 with Softdevice S132_V7.0.1. I come to know about release of SDK_17.0.2 with highly recommendation to migrate from SDK_17.0.0 to SDK_17.0.2.

Here I have some question regarding migration if anybody can help me.

1. Should I migrate to each new released SDK every time? I am asking this because some time our application is in production phase and it become difficult to immediate migration to new SDK and then QA of it and also DFU in already produced devices.
2. How can I confirm that migration to new released SDK is necessary for or related to my application? 
3. Same question 1 and 2 for new released softdevice also.

Regards,

Bipin Patel

[Kenneth]

Hi,

I recommend to check the release notes for new nRF5 SDK and SD if any are applicable for your application or product. Typically minor releases where we only change the last digit 'x' in the release version N.M.x is a pure fix with no change to api or features. Personally I would be on a lookout for these in specific, because considering all the work that is also required on our end to test, qualify and release a new version, this is not something we do lightly unless it is necessary to release. However the fix may not be applicable your product, but do check the release notes if any are. The latest release notes is available by downloading the SDK and SD releases.

Best regards,
Kenneth

[karanbakshi]

Hi Kenneth,

I understand your points. But sometime it is very difficult to make sure that changes in new SDK or SD will affect anyway to device functionality or not. 

For example, I have application on SDK_17.0.0. Now in release note of SDK_17.0.2, It is highly recommended to migrate on 17.0.2 who are using 17.0.0 currently but I can't find anything in release note which could affect my application at first look.

In such cases, can you suggest what should we consider?

Regards,

Bipin Patel

[Kenneth]

karanbakshi said:

but I can't find anything in release note which could affect my application at first look.

I think most changes were due to compatibility with the nRF52820 (MDK files), so that may be right if you are developing for the nRF52832 yes. These are typically bundled with the nRF5 SDK, but you can also download the latest MDK files from:
https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-MDK/Download#infotabs 

It is recommended to update the MDK files to include latest errata's.

Best regards,
Kenneth

[karanbakshi]

Hi Kenneth,

If there is a no change related to nRF52832 then is it find if I only update MDK? Basically in every new Firmware release, I always check for latest available MDK version.

Regards,

Bipin Patel

[CheMax]

but, what's about SoftDevice? This has been updated too, for example s132v7.0.1 >>>> s132v7.2.0. this is clearly not related to support for the nRF52820 chip)).

SDK 17.0.2 has Release note. 

If you look at the link, it will become clear that several errors in the libraries have been fixed, and compatibility with IDE has been improved. Do not be lazy to read the documentation, sometimes they write useful things there.