This example program shows how to set up a GAP advertising packet to broadcast data from the device out to anyone who may be listening.

Dependencies:   BLE_API mbed nRF51822

Fork of BLE_EvothingsExample_GAP by Austin Blackstone


This code is meant to demonstrate how to use the GAP advertising layer to transmit data. Keep in mind you only have 26B of data in the Manufacturer data field to use.

Video of use


Fill in the data you want to transmit by changing the following line, try using the string representation by changing hte "CHangeThisData" field or send hex data by altering the hex data field.

// You have up to 26 bytes of advertising data to use.
const static uint8_t AdvData[] = {"ChangeThisData"};             // example of character data
//const static uint8_t AdvData[] = {0x01,0x02,0x03,0x04,0x05};   // example of hex data

Name Device

Optionally you can give your device a name by uncommenting the following two lines

//const static char     DEVICE_NAME[]        = "ChangeMe!!"; // change this
//ble.accumulateAdvertisingPayload(GapAdvertisingData::COMPLETE_LOCAL_NAME, (uint8_t *)DEVICE_NAME, sizeof(DEVICE_NAME));

Add Disconnection Callback

This code is bare bones and as such does not restart advertising when disconnected from a device. To add this functionality into your code please add the following callback

// Restart advertising when phone app disconnects
void disconnectionCallback(Gap::Handle_t handle, Gap::DisconnectionReason_t reason)

and the following initialization to your main function


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 Evothings App to view the data.


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. In the Evothings Workbench you will find an example program called "mbed Evothings GAP", this Evothings Smartphone App is meant to be used with the above embedded mbed code. For instructions on how to use Evothings please see the reference section below.



RevisionDateWhoCommit message
15:7e06fce6e4f8 2016-01-12 andresag Add missing license information to source code. default tip
14:1c15d473b42f 2016-01-12 andresag Update example to latest BLE API.
13:827dd2b32bb8 2015-04-02 mbedAustin removed whitespace and ran code linter/cleanup
12:06c984252bd1 2015-04-02 mbedAustin fixed small issue with API change
11:c9c0c4586c5f 2015-04-02 mbedAustin updated the libraries
10:1298728d050c 2015-03-18 mbedAustin updated library that was causing a conflict
9:4241e0bac7b3 2015-03-18 mbedAustin updated library revisions
8:5442739198ec 2015-03-17 mbedAustin Added comments and disconnection callback option
7:f9a2fa5b1d43 2015-03-10 mbedAustin changed default advertising data as most phones display it in hex, not ascii
6:a7595838d240 2015-03-10 mbedAustin final commit
5:fff16d283dcf 2015-03-10 mbedAustin Added name service to make device easier to find in crowded room
4:d602b1c3aef4 2015-03-10 mbedAustin made device connectable instead of non-connectable, this is to allow iOS devices to connect and display the advertising info, because no iOS app will just show the advertising data, they have to connect... grrr....
3:e9646631084f 2015-03-10 mbedAustin Publishing for use in Meetup;
2:7d230e007eee 2015-02-14 mbedAustin removed custom class file as it wasnt needed
1:0692bee84264 2015-02-13 mbedAustin Initial Commit of Evothings custom GAP example App
0:5375be4301ed 2015-01-28 mbedAustin Initial Base, nothing written, just a skeleton program with libraries