RE: Updating to new SDK and SoftDevice: What happens on the Development Kits

Marte Myrvold — Thu, 21 Apr 2022 13:21:43 GMT

Yes, that is correct.

RE: Updating to new SDK and SoftDevice: What happens on the Development Kits

brianreinhold — Thu, 21 Apr 2022 08:38:07 GMT

Okay, so that answers both cases. The update to 17.1.0 made no difference in my case, and if it had, the correct version of SoftDevice would be deployed.

RE: Updating to new SDK and SoftDevice: What happens on the Development Kits

Marte Myrvold — Thu, 21 Apr 2022 08:06:04 GMT

Hi,

The S140 SoftDevice versions used in nRF5 SDK v17.0.2 and v17.1.0 are the same, namely v7.2.0. You can see the supported SoftDevices in the introduction of a SDK versions documentation, see nRF5 SDK v17.1.0 and nRF5 SDK v17.0.2. We also have a compatibility matrix where you can see the compatibility between SoftDevices and SDKs, see Compatibility Matrix > SDKs and SoftDevices for more information.

When building and flashing a project in SES where the SoftDevice is configured to be used the SoftDevice will be programmed together with the application. This is by default the case for the Bluetooth examples, so it should be programmed in your case as well unless you have removed this configuration. If you want to program the SoftDevice separately you can find the firmware in <nRF5_SDK_root>/components/softdevice/s140/hex, or you can download it from here: S140 Download. You can program the SoftDevice using nrfjprog (nrfjprog --family nRF52 --program HEX) or with the Programmer app in nRF Connect for Desktop.

Best regards,

Marte