RE: SDK config Pairing options explanation

Kenneth — Wed, 02 Mar 2022 13:17:07 GMT

For new development I strongly recommend to check out nRF Connect SDK instead:
Development: https://webinars.nordicsemi.com/introducing-nrf-connect-for-vs-code-5
(Installation video: https://www.youtube.com/playlist?list=PLx_tBuQ_KSqEt7NK-H7Lu78lT2OijwIMl)
BLE video: https://webinars.nordicsemi.com/developing-bluetooth-low-energy-6)

If you are familiar with the nRF5 SDK and BLE, you may find this useful:
https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/software/posts/building-a-ble-application-on-ncs-comparing-and-contrasting-to-softdevice-based-ble-applications

But to answer your error codes:

4352 is in hex 0x1100, so likely from peer_manager_types.h:
#define PM_CONN_SEC_ERROR_DISCONNECT (PM_CONN_SEC_ERROR_BASE + 0x100) /**< @brief Pairing or encryption did not finish before the link disconnected for an unrelated reason. */

4102 is in hex 0x1006, so likely from peer_manager_types.h:
#define PM_CONN_SEC_ERROR_PIN_OR_KEY_MISSING (PM_CONN_SEC_ERROR_BASE + 0x06) /**< @brief Encryption failed because the peripheral has lost the LTK for this bond. See also @ref BLE_HCI_STATUS_CODE_PIN_OR_KEY_MISSING and Table 3.7 ("Pairing Failed Reason Codes") in the Bluetooth Core Specification 4.2, section 3.H.3.5.5 (@linkBLEcore). */

Not sure which example you are looking at, but you may find the hid keyboard or mouse example reference for bonding support if you want to continue with the nRF5 SDK. Also check out documentation for peer manager if you haven't:
https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/lib_pm_usage.html

Best regards,
Kenneth