mbed and SD132 v3?

[petermeter]

Hello!

I am developing with mbed. According to nRFgo Studio, the hex file generated by the mbed compiler already contains the following SoftDevice: S132_nRF52_2.0.0 (Id: 0x0081) Since a certain BT 4.2 feature (data length extension) is needed by my app, I will have to change the SoftDevice to v3.1.0.

In nRFgo Studio, there are sections "Program SoftDevice" and "Program Application". I tried downloading s132_nrf52_3.1.0_softdevice.hex and programming it to my device with "Program SoftDevice" without success.

Can the SD in the mbed generated hex file changed with nRFgo Studio or with any other tool?

Any answer is appreciated!

P.

[Jørgen Holmefjord]

Hi,

You can't simply flash another softdevice and get access to the new features. There are API changes between s132 v2.0.0 and v3.x.0, which will cause errors if used with code written for another softdevice. The Flash requirements of the softdevices are also different, meaning you might overwrite part of your application if replaing the softdevice in the hex-file.

mbed OS currently only support the following softdevice/SDK combinations:

nRF51 series and nRF52832: SDK 11 with S13x v2.0.x softdevice.

nRF52840: SDK13 with S140 v5.0.0 1.alpha softdevice

We might add support for more SDK/softdevice combinations in the future, but S132 versions greater than v2.0.x softdevice is not supported.

If you require BT 4.2 (or BT 5) features, I suggest you take a look at our latest SDK, which have support for DLE, LE secure connections, up to 20 concurrent connections, and 2 Mbit high-throughput mode (currently only SDK support in SDK 13 alpha, but production ready softdevice is available).

Best regards,

Jørgen