this is using the mbed os version 5-13-1
Diff: source/BleManager.h
- Revision:
- 78:07bb86e3ce14
- Parent:
- 77:0b505d1e15f4
- Child:
- 79:a2187bbfa407
--- a/source/BleManager.h Fri Mar 15 23:25:30 2019 +0000
+++ b/source/BleManager.h Sat Mar 16 13:05:52 2019 +0000
@@ -22,6 +22,7 @@
#include <mbed.h>
#include "ble/BLE.h"
#include "SecurityManager.h"
+#include "common_types.h"
/** This example demonstrates all the basic setup required
* for pairing and setting up link security both as a central and peripheral
@@ -53,7 +54,8 @@
public SecurityManager::EventHandler
{
public:
- SMDevice(BLE &ble, events::EventQueue &event_queue, BLEProtocol::AddressBytes_t &peer_address);
+ SMDevice(BLE &ble, events::EventQueue &event_queue,
+ BLEProtocol::AddressBytes_t &peer_address, ble_config_t ble_config);
virtual ~SMDevice();
@@ -125,6 +127,7 @@
protected:
BLE &_ble;
+ ble_config_t ble_config;
events::EventQueue &_event_queue;
BLEProtocol::AddressBytes_t &_peer_address;
ble::connection_handle_t _handle;
@@ -135,7 +138,8 @@
* a change in link security. */
class SMDevicePeripheral : public SMDevice {
public:
- SMDevicePeripheral(BLE &ble, events::EventQueue &event_queue, BLEProtocol::AddressBytes_t &peer_address);
+ SMDevicePeripheral(BLE &ble, events::EventQueue &event_queue,
+ BLEProtocol::AddressBytes_t &peer_address, ble_config_t ble_config);
virtual void start();
@@ -150,7 +154,8 @@
/** A central device will scan, connect to a peer and request pairing. */
class SMDeviceCentral : public SMDevice {
public:
- SMDeviceCentral(BLE &ble, events::EventQueue &event_queue, BLEProtocol::AddressBytes_t &peer_address);
+ SMDeviceCentral(BLE &ble, events::EventQueue &event_queue,
+ BLEProtocol::AddressBytes_t &peer_address, ble_config_t ble_config);
virtual void start();