CC2652R: OOB Pairing

Hitoshi Sugawara

Part Number: CC2652R
Other Parts Discussed in Thread: SYSCONFIG, BLE-STACK

Hi Experts,

Regarding the pairing (OOB), it seems that the configuration for GAPBOND_OOB_ENABLED is necessary.
However, there is no item to configure in Sysconfig GUI.
Is it necessary to add it to the file ti_ble_config.c which Sysconfig outputs?

Also, if there are any documents which are related to the OOB Pairing for GAP Bond Manager and LE Secure Connections, could you please share the files?

Thank you for your kind support.
Best regards,
Hitoshi

over 3 years ago

0 Clément over 3 years ago

TI__Guru* 94498 points

Hi Hitoshi-san,

Could you please review our documentation about OOB Pairing and let me know if you have more questions?

Thanks and regards.

0 Hitoshi Sugawara over 3 years ago in reply to Clément

TI__Mastermind 18660 points

Hi Clement,

I have informed it to the customer.
If there is any further questions, let me post onto the thread.
Thank you and best regards,
Hitoshi

0 Hitoshi Sugawara over 3 years ago in reply to Hitoshi Sugawara

TI__Mastermind 18660 points

Hi Clement,

They are following the procedure. https://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_5_10_00_48/docs/ble5stack/ble_user_guide/html/ble-stack-5.x/gapbondmngr-cc13x2_26x2.html#out-of-band-pairing

Quetions:
1) Is it no problem if GAPBondMgr_SetParameter(GAPBOND_OOB_ENABLED, sizeof(uint8_t), &oobEnabled); is called at first?
Currently, it is called at the initializing the tasks by the customer's SW.

2) With OOB BT spec., Central uses BD_Addr_a, Ca, and ra and Peripheral uses BD_Addr_b, Cb, and rb for the communication.
It seems that BT-Stack does not support any APIs which set Cb nor rb.
Does this mean that it is not necessary because the Central BD_Addr_a is acquired by BLE communication and the created Cb and rb are already known by each other?

3) If the step 1 to 6 are done, does BLE-Stack make pairing automatically and the event, that the bonding is completed, is noticed after the Pairing_Request is received from the Central?

Hope I am making sense.
Thank you for your check.
Best regards,
Hitoshi

+1 Clément over 3 years ago in reply to Hitoshi Sugawara

TI__Guru* 94498 points

Hi,

1) It should not be a problem. You should only make sure the OOB is enabled before receiving the request.

2) This is handled behind the scene by the Bluetooth Stack . As a result the BD_Addr_b, Cb, rb, etc. are not exposed to the application. If you are curious you could use BLE sniffer to see the PDUs being exchanged.

3) This will depend on the way the device is configured. Three pairing mode exist "Pairing is not allowed", "Wait for a pairing request" and "Initiate a pairing request". You can select the mode you need using SysConfig (RF STacks > BLE > Bond Manager > Pairing Mode.

I hope this will help,

Best regards,

0 Hitoshi Sugawara over 2 years ago in reply to Clément

TI__Mastermind 18660 points

Hi Clement,

Thank you for your skillful support.
It was resolved.

Best regards,
Hitoshi

Bluetooth®︎

Bluetooth forum

CC2652R: OOB Pairing