LAUNCHXL-CC2640R2: Pairing Failed Reason

Neville Frank

Hi,

Is there a way to identify the pairing failed reason.

For example, is paring failed due to wrong pairing keys or pairing failed due to timeout.

Currently, in GAPBOND_PAIRING_STATE_COMPLETE we will be able to know if the pairing is a success or not. Is it possible to identify the reason for pairing failure.

Thanks and Regards,

Neville

over 3 years ago

+1 Nima over 3 years ago

TI__Expert 6565 points

Hi Neville,

Thank you for posting in the E2E forums,

Neville Frank said:
Is it possible to identify the reason for pairing failure.

Please check the UART output for the device. Error codes can be seen there. The gapbondmgr.h file has defined macros for these errors. Additionally, if you are looking for firm explanations of these errors check the core Bluetooth specification, particularly Vol 3. Part H under the Pairing Failed section.

Hope that helps!

0 Neville Frank over 3 years ago in reply to Nima

Prodigy 20 points

Hi,

Thanks for your reply, now able to see the different error codes. When the wrong pairing key is entered we are getting 0x04 which is SMP_PAIRING_FAILED_CONFIRM_VALUE, but when we are not entering the pairing keys it will go to timeout (30-second timeout) and we are getting an error code of 0x17 which does not match with Pairing failure status values of BLE5 API documentation (https://software-dl.ti.com/simplelink/esd/simplelink_cc2640r2_sdk/2.20.00.49/exports/docs/ble5stack/ble_user_guide/doxygen/ble/html/group___g_a_p_bond_mgr___pairing___failed.html#ga235429663c8e55eb3f5315939025e5ad) can you please help me understand regarding this error code.

Thanks and Regards,

Neville

+1 Nima over 3 years ago in reply to Neville Frank

TI__Expert 6565 points

Hi Neville,

Neville Frank said:
it will go to timeout (30-second timeout) and we are getting an error code of 0x17 which does not match with Pairing failure status values of BLE5 API documentation

This error code can be located in the bcomdef.h file that contains type definitions and macros for the BLE stack, and is located in the SDK directory. For example, the path to this file is: simplelink_cc2640r2_sdk_5_10_00_02\source\ti\ble5stack\inc\bcomdef.h. You can find more codes here. Additionally, here is a list of functions that return this error code. You can use our debugging guide to try to narrow down the function returning this error.

Hope that helps!

Nima Behmanesh

Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

Bluetooth®︎

Bluetooth forum

LAUNCHXL-CC2640R2: Pairing Failed Reason