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

Revision:
7:e8dfe1c97c71
Parent:
6:715150f7f293
Child:
8:32cdc49c027e
--- a/main.cpp	Sat Jun 20 23:44:08 2015 +0000
+++ b/main.cpp	Tue Sep 29 12:05:32 2015 +0000
@@ -27,7 +27,7 @@
                                               GattService::UUID_DEVICE_INFORMATION_SERVICE};
 static volatile bool  triggerSensorPolling = false;
 
-void disconnectionCallback(Gap::Handle_t handle, Gap::DisconnectionReason_t reason)
+void disconnectionCallback(const Gap::DisconnectionCallbackParams_t *params)
 {
     printf("Disconnected!\r\n");
     ble.startAdvertising(); // restart advertising
@@ -59,9 +59,9 @@
 void securitySetupCompletedCallback(Gap::Handle_t handle, SecurityManager::SecurityCompletionStatus_t status)
 {
     if (status == SecurityManager::SEC_STATUS_SUCCESS) {
-        printf("Security success\r\n", status);
+        printf("Security success\r\n");
     } else {
-        printf("Security failed\r\n", status);
+        printf("Security failed\r\n");
     }
 }