Hi, I am evaluating the nrf52832 and the Softdevice for potential use in a new product.
The product has neither display nor keyboard. It therefore makes sense to use Just Works bonding
for security. MITM protection is not required. The product's operation shall be controlled by an Android smartphone.
I started the evaluation by running two examples from the Nordic SDK, namely,
..\nRF5_SDK_15.3.0_59ac345\examples\ble_peripheral\ble_app_cscs\pca10040\s132\arm5_no_packs
..\nRF5_SDK_15.3.0_59ac345\examples\ble_peripheral\ble_app_hrs\pca10040\s132\arm5_no_packs
These examples use Just Works bonding, which is what I need.
nRF Connect has been used to test the communication between the Android phone and a nrf52832-based board.
In both tests, the smartphone failed to bond with the nRF52832. The following log messages were outputted
to the serial terminal.
<info> app: Heart Rate Sensor example started.
<info> app: Fast advertising.
<warning> peer_manager_gcm: The local database has changed, so some subscriptions
to notifications and indications could not be restored for conn_handle 0
<warning> peer_manager_handler: Local DB could not be applied: conn_handle: 0, peer_id: 1
<info> app: Connected.
<info> app: GATT ATT MTU on connection 0x0 changed to 247.
<info> app: GATT ATT MTU on connection 0x0 changed to 247.
<info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Bonding, error: 133
<info> app: BLE_GAP_EVT_AUTH_STATUS: status=0x85 bond=0x0 lv4: 0 kdist_own:0x0 kdist_peer:0x0
<info> app: Fast advertising.
<info> app: Disconnected, reason 19.
It might be worth mentioning that I have deleted all bond information in the smartphone before the pairing process began.
Did I miss anything in the tests? Any help would be be greatly appreciated.
Further information:
Development platform:
Laptop Lenovo Ideapad 330S
Windows 10 Home Version 1803
Nordic SDK: nRF5_SDK_15.3.0_59ac345
Mobile phone used:
Asus Zenfone 2 (Android version 5, API level 21).
