Fork of BLE_SecureHeartRate : should this 'work' i.e. require a secure connection on an nRF51-DK? Hopefully I'm just missing something obvious - or is this broken?
Dependencies: BLE_API mbed nRF51822
Fork of BLE_SecureHeartRate by
Diff: main.cpp
- Revision:
- 11:70342535895d
- Parent:
- 10:d391a5f1df7c
diff -r d391a5f1df7c -r 70342535895d main.cpp --- a/main.cpp Fri May 27 16:52:32 2016 +0000 +++ b/main.cpp Fri May 27 16:55:05 2016 +0000 @@ -87,7 +87,7 @@ bool enableBonding = true; bool requireMITM = true; uint8_t pass[] = {'0', '1', '2', '3', '4', '5', '6'}; - ble.securityManager().init(enableBonding, requireMITM, SecurityManager::IO_CAPS_DISPLAY_ONLY, pass); + ble.securityManager().init(enableBonding, requireMITM, SecurityManager::IO_CAPS_KEYBOARD_DISPLAY, pass); /* Set callback functions */ ble.gap().onConnection(connectionCallback);