2021-08-17 04:58 AM
I'm trying to use OOB pairing with the blueNRG1, using the latest DK3.2.1 (stack V2.1c). There is no example available, the security example has all security examples with exception of OOB.
I'm trying to use LE legacy mode for now, but LE secure is also a possibility. The documentation lists the functions aci_gap_set_oob_data/aci_gap_get_oob_data to set/get the OOB keys, but I'm missing a function to enable OOB?
When I search the stack for the keyword OOB i found the following defines:
#define OOB_AUTH_DATA_ABSENT (0x00)
#define OOB_AUTH_DATA_PRESENT (0x01)
Which function takes these defines as an input?
2021-08-25 02:25 AM
Bump
2021-08-26 07:48 PM
Please refer to the sample script in BlueNRG GUI:
C:\Program Files (x86)\STMicroelectronics\BlueNRG GUI 3.2.1\Application\scripts\OOB
Basically the script would be an example of usage on ACI_GAP_SET_OOB_DATA and ACI_GAP_GET_OOB_DATA.
After device initialization, first step on master device is to generate OOB using the ACI_GAP_SET_OOB_DATA (with Device_Type = 0x00).
Then, according to the OOB scheme being Random or Confirm, script calls the ACI_GAP_GET_OOB_DATA with respectively Device_Type = 0x01 for generating Random value and Device_Type = 0x02 for Confirm value, and set them on the slave device with ACI_GAP_SET_OOB_DATA API.