|
部分客户找不到我们蓝牙通信时，返回的param->status值都有哪些，该值主要在枚举enum hl_err中：具体值如下： enum hl_err { /// No error GAP_ERR_NO_ERROR = 0x00, // ---------------------------------------------------------------------------------- // ------------------------- ATT Specific Error ------------------------------------ // ---------------------------------------------------------------------------------- /// No error ATT_ERR_NO_ERROR = 0x00, /// 0x01: Handle is invalid ATT_ERR_INVALID_HANDLE = 0x01, /// 0x02: Read permission disabled ATT_ERR_READ_NOT_PERMITTED = 0x02, /// 0x03: Write permission disabled ATT_ERR_WRITE_NOT_PERMITTED = 0x03, /// 0x04: Incorrect PDU ATT_ERR_INVALID_PDU = 0x04, /// 0x05: Authentication privilege not enough ATT_ERR_INSUFF_AUTHEN = 0x05, /// 0x06: Request not supported or not understood ATT_ERR_REQUEST_NOT_SUPPORTED = 0x06, /// 0x07: Incorrect offset value ATT_ERR_INVALID_OFFSET = 0x07, /// 0x08: Authorization privilege not enough ATT_ERR_INSUFF_AUTHOR = 0x08, /// 0x09: Capacity queue for reliable write reached ATT_ERR_PREPARE_QUEUE_FULL = 0x09, /// 0x0A: Attribute requested not existing ATT_ERR_ATTRIBUTE_NOT_FOUND = 0x0A, /// 0x0B: Attribute requested not long ATT_ERR_ATTRIBUTE_NOT_LONG = 0x0B, /// 0x0C: Encryption size not sufficient ATT_ERR_INSUFF_ENC_KEY_SIZE = 0x0C, /// 0x0D: Invalid length of the attribute value ATT_ERR_INVALID_ATTRIBUTE_VAL_LEN = 0x0D, /// 0x0E: Operation not fit to condition ATT_ERR_UNLIKELY_ERR = 0x0E, /// 0x0F: Attribute requires encryption before operation ATT_ERR_INSUFF_ENC = 0x0F, /// 0x10: Attribute grouping not supported ATT_ERR_UNSUPP_GRP_TYPE = 0x10, /// 0x11: Resources not sufficient to complete the request ATT_ERR_INSUFF_RESOURCE = 0x11, #if (CONFIG_BLE_VERSION >= BLE_VERSION_51) /// 0x12: The server requests the client to rediscover the database. ATT_ERR_DATABASE_OUT_OF_SYNC = 0x12, /// 0x13: The attribute parameter value was not allowed. ATT_ERR_VALUE_NOT_ALLOWED = 0x13, #endif /// 0x80: Application error (also used in PRF Errors) ATT_ERR_APP_ERROR = 0x80, // ---------------------------------------------------------------------------------- // -------------------------- L2C Specific Error ------------------------------------ // ---------------------------------------------------------------------------------- /// Message cannot be sent because connection lost. (disconnected) L2C_ERR_CONNECTION_LOST = 0x30, /// Invalid PDU length exceed MTU L2C_ERR_INVALID_MTU_EXCEED = 0x31, /// Invalid PDU length exceed MPS L2C_ERR_INVALID_MPS_EXCEED = 0x32, /// Invalid Channel ID L2C_ERR_INVALID_CID = 0x33, /// Invalid PDU L2C_ERR_INVALID_PDU = 0x34, /// Connection refused - no resources available L2C_ERR_NO_RES_AVAIL = 0x35, /// Connection refused - insufficient authentication L2C_ERR_INSUFF_AUTHEN = 0x36, /// Connection refused - insufficient authorization L2C_ERR_INSUFF_AUTHOR = 0x37, /// Connection refused - insufficient encryption key size L2C_ERR_INSUFF_ENC_KEY_SIZE = 0x38, /// Connection Refused - insufficient encryption L2C_ERR_INSUFF_ENC = 0x39, /// Connection refused - LE_PSM not supported L2C_ERR_LEPSM_NOT_SUPP = 0x3A, /// No more credit L2C_ERR_INSUFF_CREDIT = 0x3B, /// Command not understood by peer device L2C_ERR_NOT_UNDERSTOOD = 0x3C, /// Credit error, invalid number of credit received L2C_ERR_CREDIT_ERROR = 0x3D, /// Channel identifier already allocated L2C_ERR_CID_ALREADY_ALLOC = 0x3E, /// Unknown PDU L2C_ERR_UNKNOWN_PDU = 0x3F, // ---------------------------------------------------------------------------------- // -------------------------- GAP Specific Error ------------------------------------ // ---------------------------------------------------------------------------------- /// Invalid parameters set GAP_ERR_INVALID_PARAM = 0x40, /// Problem with protocol exchange, get unexpected response GAP_ERR_PROTOCOL_PROBLEM = 0x41, /// Request not supported by software configuration GAP_ERR_NOT_SUPPORTED = 0x42, /// Request not allowed in current state. GAP_ERR_COMMAND_DISALLOWED = 0x43, /// Requested operation canceled. GAP_ERR_CANCELED = 0x44, /// Requested operation timeout. GAP_ERR_TIMEOUT = 0x45, /// Link connection lost during operation. GAP_ERR_DISCONNECTED = 0x46, /// Search algorithm finished, but no result found GAP_ERR_NOT_FOUND = 0x47, /// Request rejected by peer device GAP_ERR_REJECTED = 0x48, /// Problem with privacy configuration GAP_ERR_PRIVACY_CFG_PB = 0x49, /// Duplicate or invalid advertising data GAP_ERR_ADV_DATA_INVALID = 0x4A, /// Insufficient resources GAP_ERR_INSUFF_RESOURCES = 0x4B, /// Unexpected Error GAP_ERR_UNEXPECTED = 0x4C, /// Feature mismatch GAP_ERR_MISMATCH = 0x4D, // ---------------------------------------------------------------------------------- // ------------------------- GATT Specific Error ------------------------------------ // ---------------------------------------------------------------------------------- /// Problem with ATTC protocol response GATT_ERR_INVALID_ATT_LEN = 0x50, /// Error in service search GATT_ERR_INVALID_TYPE_IN_SVC_SEARCH = 0x51, /// Invalid write data GATT_ERR_WRITE = 0x52, /// Signed write error GATT_ERR_SIGNED_WRITE = 0x53, /// No attribute client defined GATT_ERR_ATTRIBUTE_CLIENT_MISSING = 0x54, /// No attribute server defined GATT_ERR_ATTRIBUTE_SERVER_MISSING = 0x55, /// Permission set in service/attribute are invalid GATT_ERR_INVALID_PERM = 0x56, // ---------------------------------------------------------------------------------- // ------------------------- SMP Specific Error ------------------------------------- // ---------------------------------------------------------------------------------- // SMP Protocol Errors detected on local device /// The user input of pass key failed, for example, the user canceled the operation. SMP_ERROR_LOC_PASSKEY_ENTRY_FAILED = 0x61, /// The OOB Data is not available. SMP_ERROR_LOC_OOB_NOT_AVAILABLE = 0x62, /// The pairing procedure cannot be performed as authentication requirements cannot be met /// due to IO capabilities of one or both devices. SMP_ERROR_LOC_AUTH_REQ = 0x63, /// The confirm value does not match the calculated confirm value. SMP_ERROR_LOC_CONF_VAL_FAILED = 0x64, /// Pairing is not supported by the device. SMP_ERROR_LOC_PAIRING_NOT_SUPP = 0x65, /// The resultant encryption key size is insufficient for the security requirements of /// this device. SMP_ERROR_LOC_ENC_KEY_SIZE = 0x66, /// The SMP command received is not supported on this device. SMP_ERROR_LOC_CMD_NOT_SUPPORTED = 0x67, /// Pairing failed due to an unspecified reason. SMP_ERROR_LOC_UNSPECIFIED_REASON = 0x68, /// Pairing or Authentication procedure is disallowed because too little time has elapsed /// since last pairing request or security request. SMP_ERROR_LOC_REPEATED_ATTEMPTS = 0x69, /// The command length is invalid or a parameter is outside of the specified range. SMP_ERROR_LOC_INVALID_PARAM = 0x6A, /// Indicates to the remote device that the DHKey Check value received doesn't /// match the one calculated by the local device. SMP_ERROR_LOC_DHKEY_CHECK_FAILED = 0x6B, /// Indicates that the confirm values in the numeric comparison protocol do not match. SMP_ERROR_LOC_NUMERIC_COMPARISON_FAILED = 0x6C, /// Indicates that the pairing over the LE transport failed due to a Pairing Request sent /// over the BR/EDR transport in process. SMP_ERROR_LOC_BREDR_PAIRING_IN_PROGRESS = 0x6D, /// Indicates that the BR/EDR Link Key generated on the BR/EDR transport cannot be /// used to derive and distribute keys for the LE transport. SMP_ERROR_LOC_CROSS_TRANSPORT_KEY_GENERATION_NOT_ALLOWED = 0x6E, // SMP Protocol Errors detected by remote device /// The user input of passkey failed, for example, the user canceled the operation. SMP_ERROR_REM_PASSKEY_ENTRY_FAILED = 0x71, /// The OOB Data is not available. SMP_ERROR_REM_OOB_NOT_AVAILABLE = 0x72, /// The pairing procedure cannot be performed as authentication requirements cannot be /// met due to IO capabilities of one or both devices. SMP_ERROR_REM_AUTH_REQ = 0x73, /// The confirm value does not match the calculated confirm value. SMP_ERROR_REM_CONF_VAL_FAILED = 0x74, /// Pairing is not supported by the device. SMP_ERROR_REM_PAIRING_NOT_SUPP = 0x75, /// The resultant encryption key size is insufficient for the security requirements of /// this device. SMP_ERROR_REM_ENC_KEY_SIZE = 0x76, /// The SMP command received is not supported on this device. SMP_ERROR_REM_CMD_NOT_SUPPORTED = 0x77, /// Pairing failed due to an unspecified reason. SMP_ERROR_REM_UNSPECIFIED_REASON = 0x78, /// Pairing or Authentication procedure is disallowed because too little time has elapsed /// since last pairing request or security request. SMP_ERROR_REM_REPEATED_ATTEMPTS = 0x79, /// The command length is invalid or a parameter is outside of the specified range. SMP_ERROR_REM_INVALID_PARAM = 0x7A, /// Indicates to the remote device that the DHKey Check value received doesn't /// match the one calculated by the local device. SMP_ERROR_REM_DHKEY_CHECK_FAILED = 0x7B, /// Indicates that the confirm values in the numeric comparison protocol do not match. SMP_ERROR_REM_NUMERIC_COMPARISON_FAILED = 0x7C, /// Indicates that the pairing over the LE transport failed due to a Pairing Request sent /// over the BR/EDR transport in process. SMP_ERROR_REM_BREDR_PAIRING_IN_PROGRESS = 0x7D, /// Indicates that the BR/EDR Link Key generated on the BR/EDR transport cannot be /// used to derive and distribute keys for the LE transport. SMP_ERROR_REM_CROSS_TRANSPORT_KEY_GENERATION_NOT_ALLOWED = 0x7E, // SMP Errors triggered by local device /// The provided resolvable address has not been resolved. SMP_ERROR_ADDR_RESOLV_FAIL = 0x20, /// The Signature Verification Failed SMP_ERROR_SIGN_VERIF_FAIL = 0x21, /// The encryption procedure failed because the slave device didn't find the LTK /// needed to start an encryption session. SMP_ERROR_ENC_KEY_MISSING = 0x22, /// The encryption procedure failed because the slave device doesn't support the /// encryption feature. SMP_ERROR_ENC_NOT_SUPPORTED = 0x23, /// A timeout has occurred during the start encryption session. SMP_ERROR_ENC_TIMEOUT = 0x24, // ---------------------------------------------------------------------------------- //------------------------ Profiles specific error codes ---------------------------- // ---------------------------------------------------------------------------------- /// Application Error PRF_APP_ERROR = 0x80, /// Invalid parameter in request PRF_ERR_INVALID_PARAM = 0x81, /// Inexistent handle for sending a read/write characteristic request PRF_ERR_INEXISTENT_HDL = 0x82, /// Discovery stopped due to missing attribute according to specification PRF_ERR_STOP_DISC_CHAR_MISSING = 0x83, /// Too many SVC instances found -> protocol violation PRF_ERR_MULTIPLE_SVC = 0x84, /// Discovery stopped due to found attribute with incorrect properties PRF_ERR_STOP_DISC_WRONG_CHAR_PROP = 0x85, /// Too many Char. instances found-> protocol violation PRF_ERR_MULTIPLE_CHAR = 0x86, /// Attribute write not allowed PRF_ERR_NOT_WRITABLE = 0x87, /// Attribute read not allowed PRF_ERR_NOT_READABLE = 0x88, /// Request not allowed PRF_ERR_REQ_DISALLOWED = 0x89, /// Notification Not Enabled PRF_ERR_NTF_DISABLED = 0x8A, /// Indication Not Enabled PRF_ERR_IND_DISABLED = 0x8B, /// Feature not supported by profile PRF_ERR_FEATURE_NOT_SUPPORTED = 0x8C, /// Read value has an unexpected length PRF_ERR_UNEXPECTED_LEN = 0x8D, /// Disconnection occurs PRF_ERR_DISCONNECTED = 0x8E, /// Procedure Timeout PRF_ERR_PROC_TIMEOUT = 0x8F, /// Client characteristic configuration improperly configured PRF_CCCD_IMPR_CONFIGURED = 0xFD, /// Procedure already in progress PRF_PROC_IN_PROGRESS = 0xFE, /// Out of Range PRF_OUT_OF_RANGE = 0xFF, // ---------------------------------------------------------------------------------- //-------------------- LL Error codes conveyed to upper layer ----------------------- // ---------------------------------------------------------------------------------- /// Unknown HCI Command LL_ERR_UNKNOWN_HCI_COMMAND = 0x91, /// Unknown Connection Identifier LL_ERR_UNKNOWN_CONNECTION_ID = 0x92, /// Hardware Failure LL_ERR_HARDWARE_FAILURE = 0x93, /// BT Page Timeout LL_ERR_PAGE_TIMEOUT = 0x94, /// Authentication failure LL_ERR_AUTH_FAILURE = 0x95, /// Pin code missing LL_ERR_PIN_MISSING = 0x96, |