No matter how you configure the SecurityManager, the pairing protocol ends up with "SEC_STATUS_UNSPECIFIED" (0x88) at the "pairingResult" event, in the peripheral's side (Mbed API). On the central's side, it ends up with a timeout.
Board: Arduino Nano 33 BLE.
Tested both in Android (nRF app) and Windows 10 (with BT 5.0 radio).
Core version: tested both 2.6.1 and current master branch (downloaded FEATURE_BLE and BLE driver folders, only)
Pairing is mandatory in Windows 10 API in order to retrieve services and characteristics, so this is a blocking issue.
No matter how you configure the SecurityManager, the pairing protocol ends up with "SEC_STATUS_UNSPECIFIED" (0x88) at the "pairingResult" event, in the peripheral's side (Mbed API). On the central's side, it ends up with a timeout.
Board: Arduino Nano 33 BLE. Tested both in Android (nRF app) and Windows 10 (with BT 5.0 radio). Core version: tested both 2.6.1 and current master branch (downloaded FEATURE_BLE and BLE driver folders, only)
Pairing is mandatory in Windows 10 API in order to retrieve services and characteristics, so this is a blocking issue.
This is the involved code (not the full code):
and the event handler: