Tom Gilbert / Mbed 2 deprecated Q_BLE_SecureHeartRate

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 Bluetooth Low Energy

Diff: main.cpp

Revision:
10:d391a5f1df7c
Parent:
9:b1cde75ccbbc
Child:
11:70342535895d
--- a/main.cpp	Tue May 24 15:15:03 2016 +0000
+++ b/main.cpp	Fri May 27 16:52:32 2016 +0000
@@ -22,7 +22,7 @@
 BLE        ble;
 DigitalOut led1(LED1);
 
-const static char     DEVICE_NAME[]        = "HRM_SEC";
+const static char     DEVICE_NAME[]        = "UWOT";
 static const uint16_t uuid16_list[]        = {GattService::UUID_HEART_RATE_SERVICE,
                                               GattService::UUID_DEVICE_INFORMATION_SERVICE};
 static volatile bool  triggerSensorPolling = false;
@@ -86,11 +86,8 @@
     /* Initialize BLE security */
     bool enableBonding = true;
     bool requireMITM   = true;
-    uint8_t pass[6] = {'1', '2', '3', '4', '5', '6'};
+    uint8_t pass[] = {'0', '1', '2', '3', '4', '5', '6'};
     ble.securityManager().init(enableBonding, requireMITM, SecurityManager::IO_CAPS_DISPLAY_ONLY, pass);
-    // to see if the behaviour is any different, try claiming we have Keyboard & Display capability on this peripheral
-    // also making sure to no longer specify a static password
-    //ble.securityManager().init(enableBonding, requireMITM, SecurityManager::IO_CAPS_KEYBOARD_DISPLAY, NULL);
     
     /* Set callback functions */
     ble.gap().onConnection(connectionCallback);