I've tested the OOB function using 2 BLE MCU WBA54,
case 1, one provide the OOB data then send to the other
case 2, both proved the OOB data then send to each other
2 cases are OK, pairing success and bonded.
OOB data provide use:
ret = aci_gap_set_oob_data(0x00, 0x00, 0x00, 0x00, 0x00, 0x00);
ret = aci_gap_get_oob_data(0x01, &addtype, address, &len, random);
ret = aci_gap_get_oob_data(0x02, &addtype, address, &len, confirm);
OOB data set use:
ret = aci_gap_set_oob_data(0x01, addtype, address, 0x01, 16, random);
ret = aci_gap_set_oob_data(0x01, addtype, address, 0x02, 16, confirm);
There is a problem when I want to use OOB pairing with IOS, for IOS cannot provide OOB data or force OOB pairing request, now the only possible way is WBA54 provide the OOB data and send to IOS and also force OOB pairing feature.
But when WBA54 only provide OOB data, it seems that it cannot trigger the OOB in SMP pairing feature exchange.
I've tested that the OOB feature will be triggered only when aci_gap_set_oob_data(0x01, addtype, address, len, random), aci_gap_set_oob_data(0x02, addtype, address, len, confirm) was used, and the address type and MAC address should be same as connected peer address.
* @PAram OOB_Data_Len Length of OOB data
* Values:
* - 0: SC Random/Confirm generation (OOB_Data and OOB_Data_Type are not
* used)
* - 16
from the parameter indication, len could be 0 to indicate data are not used, so I tried to use len = 0 as input to force OOB pairing, it indeed force OOB pairing, but SMP pairing Failed with confirm value failed.
also, I've tried using
mode |= (1 << 4);
mode |= (1 << 5);
mode |= (1 << 7);
aci_hal_write_config_data(CONFIG_DATA_SMP_MODE_OFFSET, CONFIG_DATA_SMP_MODE_LEN, &mode)
to forbid the the other pairing method after OOB data was generated, but SMP will be failed with unspecified Reason
what can I do if WBA54 only provide OOB data and also force the OOB feature?
