Bluetooth Low Energy
This is a demonstration of how to create a GATT service and characteristic.
Dependencies: BLE_API mbed nRF51822
Fork of
BLE_EvothingsExample_GATT
by 
Austin Blackstone
Intro
This code demonstrates how to use the BLE_API to create a GATT service and characteristic to toggle a LED on / off.
Overview
This code is a demonstration of how to create a custom service (UUID=0xA0000) with two characteristics, a read only characteristic (UUID=0xA001) and a write characteristic (UUID=0xA002). What is written to the write characteristic will be copied across to the read characteristic and broadcast out. If a single byte is written it will be used to toggle the on board LED, if more than 1 byte is written the data will be written out to the terminal. The default max size is 10bytes.
Video
This is a video of how to use this example. Please note that in this video Android is used to read / write the characteristics. This could just as easily been done with the Evothings App listed below or an equivalent iOS app. Any app that can read/write characteristics could have been used.
Details
characteristic and service UUID's are initialized here
UUID's
uint16_t customServiceUUID = 0xA000; uint16_t readCharUUID = 0xA001; uint16_t writeCharUUID = 0xA002;
We set up the list of available UUID's that will be advertised as part of the GAP advertising packet here. (it is good form to make this match the services you are actually advertising, so in this case we should set it to be 0xA000, but we are choosing to set it to 0xFFFF so it is easier to distinguish on the scanning app)
Set_ServiceID's
static const uint16_t uuid16_list[] = {0xFFFF};
...
ble.accumulateAdvertisingPayload(GapAdvertisingData::COMPLETE_LIST_16BIT_SERVICE_IDS, (uint8_t *)uuid16_list, sizeof(uuid16_list)); // UUID's broadcast in advertising packet
Next we set up the characteristics and then put them together into a service. Notice that each characteristic has a maximum of 10Bytes of Value space, this can be expanded up to 512B.
Setup_Service_&_Characteristics
// Set Up custom Characteristics
static uint8_t readValue[10] = {0};
ReadOnlyArrayGattCharacteristic<uint8_t, sizeof(readValue)> readChar(readCharUUID, readValue);
static uint8_t writeValue[10] = {0};
WriteOnlyArrayGattCharacteristic<uint8_t, sizeof(writeValue)> writeChar(writeCharUUID, writeValue);
// Set up custom service
GattCharacteristic *characteristics[] = {&readChar, &writeChar};
GattService customService(customServiceUUID, characteristics, sizeof(characteristics) / sizeof(GattCharacteristic *));
Next we setup the writeCharCallback() function that will be called when a BLE onDataWritten event is triggered (when someone writes to a characteristic on the device). This function will check to see what characteristic is being written to and then handle it appropriately. In this case there is only one writable characteristic so its redundant, but good form for more complex service/characteristic combinations.
On_Characteristic_written_to_callback
void writeCharCallback(const GattCharacteristicWriteCBParams *params)
{
// check to see what characteristic was written, by handle
if(params->charHandle == writeChar.getValueHandle()) {
// toggle LED if only 1 byte is written
if(params->len == 1) {
led = params->data[0];
...}
// print the data if more than 1 byte is written
else {
printf("\n\r Data received: length = %d, data = 0x",params->len);
...}
// update the readChar with the value of writeChar
ble.updateCharacteristicValue(readChar.getValueHandle(),params->data,params->len);
}
}
...
// register callback function
ble.onDataWritten(writeCharCallback);
...
The last thing to do is register the service with the BLE object so it is available.
Add_Service_to_BLE_Object
...
// add our custom service
ble.addService(customService);
...
Viewing Data
You can use either the LightBlue app on iOS or the nRF Master Control Panel application on Android to view the advertising data. Alternatively you can use a custom GATT Evothings App to view the data.
Evothings?
Evothings is a rapid prototyping environment that uses cordova to enable you to rapidly develop smartphone applications in Javascript. Please download the Evothings workbench to your computer and the Evothings client to your smartphone. The Evothings workbench will come with a program called "mbed Evothings GATT", this Evothings Smartphone program is meant to be used with the embedded mbed code. For instructions on how to use evothings please see the reference section below.
Reference
Revision 22:406127954d1f, committed 2015-11-09
- Comitter:
- andresag
- Date:
- Mon Nov 09 17:08:47 2015 +0000
- Parent:
- 21:73f42c00b1db
- Commit message:
- Update example to comply with initialisation changes in BLE API.
Changed in this revision
diff -r 73f42c00b1db -r 406127954d1f BLE_API.lib --- a/BLE_API.lib Tue Oct 20 13:48:13 2015 +0000 +++ b/BLE_API.lib Mon Nov 09 17:08:47 2015 +0000 @@ -1,1 +1,1 @@ -http://mbed.org/teams/Bluetooth-Low-Energy/code/BLE_API/#d494ad3e87bd +http://mbed.org/teams/Bluetooth-Low-Energy/code/BLE_API/#a097e1be76f4
diff -r 73f42c00b1db -r 406127954d1f main.cpp
--- a/main.cpp Tue Oct 20 13:48:13 2015 +0000
+++ b/main.cpp Mon Nov 09 17:08:47 2015 +0000
@@ -1,7 +1,6 @@
#include "mbed.h"
#include "ble/BLE.h"
-BLE ble;
DigitalOut led(LED1, 1);
uint16_t customServiceUUID = 0xA000;
uint16_t readCharUUID = 0xA001;
@@ -10,14 +9,14 @@
const static char DEVICE_NAME[] = "ChangeMe!!"; // change this
static const uint16_t uuid16_list[] = {0xFFFF}; //Custom UUID, FFFF is reserved for development
-// Set Up custom Characteristics
+/* Set Up custom Characteristics */
static uint8_t readValue[10] = {0};
ReadOnlyArrayGattCharacteristic<uint8_t, sizeof(readValue)> readChar(readCharUUID, readValue);
static uint8_t writeValue[10] = {0};
WriteOnlyArrayGattCharacteristic<uint8_t, sizeof(writeValue)> writeChar(writeCharUUID, writeValue);
-// Set up custom service
+/* Set up custom service */
GattCharacteristic *characteristics[] = {&readChar, &writeChar};
GattService customService(customServiceUUID, characteristics, sizeof(characteristics) / sizeof(GattCharacteristic *));
@@ -27,22 +26,22 @@
*/
void disconnectionCallback(const Gap::DisconnectionCallbackParams_t *)
{
- ble.gap().startAdvertising();
+ BLE::Instance(BLE::DEFAULT_INSTANCE).gap().startAdvertising();
}
/*
- * handle writes to writeCharacteristic
+ * Handle writes to writeCharacteristic
*/
void writeCharCallback(const GattWriteCallbackParams *params)
{
- // check to see what characteristic was written, by handle
+ /* Check to see what characteristic was written, by handle */
if(params->handle == writeChar.getValueHandle()) {
- // toggle LED if only 1 byte is written
+ /* toggle LED if only 1 byte is written */
if(params->len == 1) {
led = params->data[0];
(params->data[0] == 0x00) ? printf("led on\n\r") : printf("led off\n\r"); // print led toggle
}
- // print the data if more than 1 byte is written
+ /* Print the data if more than 1 byte is written */
else {
printf("Data received: length = %d, data = 0x",params->len);
for(int x=0; x < params->len; x++) {
@@ -50,38 +49,56 @@
}
printf("\n\r");
}
- // update the readChar with the value of writeChar
- ble.updateCharacteristicValue(readChar.getValueHandle(), params->data,params->len);
+ /* Update the readChar with the value of writeChar */
+ BLE::Instance(BLE::DEFAULT_INSTANCE).gattServer().write(readChar.getValueHandle(), params->data, params->len);
}
}
+/*
+ * Initialization callback
+ */
+void bleInitComplete(BLE::InitializationCompleteCallbackContext *params)
+{
+ BLE &ble = params->ble;
+ ble_error_t error = params->error;
+
+ if (error != BLE_ERROR_NONE) {
+ return;
+ }
-/*
- * main loop
-*/
-int
-main(void)
-{
- /* initialize stuff */
- printf("\n\r********* Starting Main Loop *********\n\r");
- ble.init();
ble.gap().onDisconnection(disconnectionCallback);
ble.gattServer().onDataWritten(writeCharCallback);
- /* setup advertising */
+ /* Setup advertising */
ble.gap().accumulateAdvertisingPayload(GapAdvertisingData::BREDR_NOT_SUPPORTED | GapAdvertisingData::LE_GENERAL_DISCOVERABLE); // BLE only, no classic BT
ble.gap().setAdvertisingType(GapAdvertisingParams::ADV_CONNECTABLE_UNDIRECTED); // advertising type
ble.gap().accumulateAdvertisingPayload(GapAdvertisingData::COMPLETE_LOCAL_NAME, (uint8_t *)DEVICE_NAME, sizeof(DEVICE_NAME)); // add name
ble.gap().accumulateAdvertisingPayload(GapAdvertisingData::COMPLETE_LIST_16BIT_SERVICE_IDS, (uint8_t *)uuid16_list, sizeof(uuid16_list)); // UUID's broadcast in advertising packet
ble.gap().setAdvertisingInterval(100); // 100ms.
- // add our custom service
+ /* Add our custom service */
ble.addService(customService);
- // start advertising
+ /* Start advertising */
ble.gap().startAdvertising();
+}
- // infinite loop waiting for BLE interrupt events
+/*
+ * Main loop
+*/
+int main(void)
+{
+ /* initialize stuff */
+ printf("\n\r********* Starting Main Loop *********\n\r");
+
+ BLE& ble = BLE::Instance(BLE::DEFAULT_INSTANCE);
+ ble.init(bleInitComplete);
+
+ /* SpinWait for initialization to complete. This is necessary because the
+ * BLE object is used in the main loop below. */
+ while (ble.hasInitialized() == false) { /* spin loop */ }
+
+ /* Infinite loop waiting for BLE interrupt events */
while (true) {
- ble.waitForEvent(); //Save power
+ ble.waitForEvent(); /* Save power */
}
}
\ No newline at end of file
diff -r 73f42c00b1db -r 406127954d1f mbed.bld --- a/mbed.bld Tue Oct 20 13:48:13 2015 +0000 +++ b/mbed.bld Mon Nov 09 17:08:47 2015 +0000 @@ -1,1 +1,1 @@ -http://mbed.org/users/mbed_official/code/mbed/builds/34e6b704fe68 \ No newline at end of file +http://mbed.org/users/mbed_official/code/mbed/builds/9296ab0bfc11 \ No newline at end of file
diff -r 73f42c00b1db -r 406127954d1f nRF51822.lib --- a/nRF51822.lib Tue Oct 20 13:48:13 2015 +0000 +++ b/nRF51822.lib Mon Nov 09 17:08:47 2015 +0000 @@ -1,1 +1,1 @@ -http://mbed.org/teams/Nordic-Semiconductor/code/nRF51822/#088f5738bf18 +http://mbed.org/teams/Nordic-Semiconductor/code/nRF51822/#bf85bf7e73d5