Enabling LESC Peripheral in Softdevice S113 SDK 17.0.1

[Anil Sinha]

Hi,

As mentioned in subject line, I am trying to enable BLE SC peripheral in SDK 17.0.1 with softdevice S113. I have enabled the PM_LESC_ENABLED macro in sdk_config and started getting linker errors and I am fixing them by including the source files or include paths. I have following questions-

1- Does this softdevice version support BLE SC even after I enable the code?

2- Are there specific SDK defines which I should enable which might fix these linker issues ? If anybody has done this exercise before ?

Any input will be a great help.

regards,

Anil

[Jimmywong2003]

I think you can refer to the HRM or HID example which has the LESC example.

It has the sdk_config.h to specify the LESC option.

[Vidar Berg]

As Jimmy suggested, it's best to start with an example that has LESC enabled by default. For instance, the ble_app_hrs example. There are quite a few crypto related dependencies you will have to add manually if you start with another project that don't include LESC.

1. Yes, the Softdevice supports it. Which chip are you using? I can make you a 's113' project for the ble_app_hrs example if it helps.

2. If you have enabled the LESC settings, then the linker errors are likely caused by missing dependencies.

[Anil Sinha]

Hi Vidar,

I was able to build my application with LESC flag enabled (used GLS example) however I am still getting "Pairing not supported" error.

#define BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP       0x85  /**< Pairing not supported.  */

I am using Nordic nRF52840 softdevice S132 peripheral.

My central device connects in LEGACY_ONLY mode however not with LESC_ONLY.

Any inputs are greatly appreciated.

regards,

Anil

[Vidar Berg]

Hi Anil,

The peer manager on the peripheral will return BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP if a pairing request is rejected as Einar mentions in this post: https://devzone.nordicsemi.com/f/nordic-q-a/37837/sdk15-paring-problem/145821#145821. You can also get this error if you are calling sd_ble_gap_sec_params_reply('BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP') from your application code outside of the peer manager module.

Regards,

Vidar