4 years, 6 months ago.

SoftDevice version that is provided with nrf52_dk platform in mbedos5.

I am assuming when I compile my BLE application with the Nordic nrf52_dk platform the softdevice is also compiled into the resulting hex file. I was wondering how do you figure out the version of the softdevice being compiled into the hex file or is it possible to choose a particular version of the SoftDevice?

Thanks, Ajay.

Question relating to:

The nRF52 Development Kit is a single-board development kit for Bluetooth Smart, ANT and 2.4GHz proprietary applications using the nRF52 Series SoC. This kit supports both development for nRF52832 SoCs.

2 Answers

4 years, 6 months ago.


You can call the member function "BLE::getVersion" to get the version of the internal stack. As Andrzej said, the current version of the softdevice is V2.0.0 for the NRF52.

Accepted Answer
4 years, 6 months ago.

SoftDevice is not compiled but it is merged in post-build step (sd *.hex file is included in mbed-os sources). For nrf52 you have fixed version of SoftDevice132 v 2.0.0. Used SoftDevice is assigned per a target - you can't to select other version.

Thanks Andrzej. However if I am right there is a new version of the SoftDevice132 v3.0.0. Is there any plan on when the new version of the SoftDevice would be merged into the post-build step. I am currently using the online compiler to compile my application. so even in this online compiler scenario the post build step merges the sd*.hex file?

posted by Ajay Kashyap 02 Nov 2016

Yes - on-line IDE invoke post build merge as well.

posted by Andrzej Puzdrowski 03 Nov 2016