nRF5 SDK v17.0.2
Macros
Peer Manager defined security errors

Macros

#define PM_CONN_SEC_ERROR_PIN_OR_KEY_MISSING   (PM_CONN_SEC_ERROR_BASE + 0x06)
 Encryption failed because the peripheral has lost the LTK for this bond. See also 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 (Bluetooth Core Specification).
 
#define PM_CONN_SEC_ERROR_MIC_FAILURE   (PM_CONN_SEC_ERROR_BASE + 0x3D)
 Encryption ended with disconnection because of mismatching keys or a stray packet during a procedure. See the SoftDevice GAP Message Sequence Charts on encryption (GAP Message Sequence Charts), the Bluetooth Core Specification 4.2, sections 6.B.5.1.3.1 and 3.H.3.5.5 (Bluetooth Core Specification), and BLE_HCI_CONN_TERMINATED_DUE_TO_MIC_FAILURE.
 
#define PM_CONN_SEC_ERROR_DISCONNECT   (PM_CONN_SEC_ERROR_BASE + 0x100)
 Pairing or encryption did not finish before the link disconnected for an unrelated reason.
 
#define PM_CONN_SEC_ERROR_SMP_TIMEOUT   (PM_CONN_SEC_ERROR_BASE + 0x101)
 Pairing/bonding could not start because an SMP time-out has already happened on this link. This means that no more pairing or bonding can happen on this link. To be able to pair or bond, the link must be disconnected and then reconnected. See Bluetooth Core Specification 4.2 section 3.H.3.4 (Bluetooth Core Specification).
 

Detailed Description

The first 256 numbers, from PM_CONN_SEC_ERROR_BASE to (PM_CONN_SEC_ERROR_BASE + 0xFF), correspond to the status codes in Bluetooth status codes.


Documentation feedback | Developer Zone | Subscribe | Updated