Using the nRF51 device in a Bluetooth LE Central role

This tutorial shows how to use the nRF51 devices in the Bluetooth LE Central role, communicating to the peripheral devices. We will create a simple firmware that will query the button state from the TI CC2650 SensorTag and display it using the on-board LEDs.

We will show how to extract the relevant data from the SensorTag attribute table and how to modify the Nordic examples to communicate with a previously unsupported device like the SensorTag. Before you begin, install VisualGDB 5.0, get a CC2650 SensorTag and follow the basic nRF51 tutorial to ensure you can program your board.

  1. Begin with launching the VisualGDB Embedded Project Wizard and specifying the project name and path:01-wizard
  2. By default, the wizard will create an embedded binary from a sample. Continue with that setting:02-binary
  3. On the next page select your nRF51 device from the list:03-device
  4. On the Sample page select the Bluetooth LE Heart Rate Service Client sample (don’t confuse it with the Heart Rate Service Device) and specify your board type that can be found on a sticker on the board:04-sample
  5. Select a debugging method for your board. In this example we will use the on-board Segger J-Link with the Segger software package. Enable the “reset device after programming” checkbox, as otherwise the softdevice initialization code will be skipped resulting in strange crashes:05-debug
  6. Press “Finish” to create the project. As stopping the Bluetooth-enabled nRF51 firmware on a breakpoint would result in loss of packets and a reset, we will use debug logging to report various events happening in the firmware. Find the uart_init() function to see the UART parameters used by the sample. By default the baud rate is 38400 and the hardware flow control is enabled. 06-uart
  7. Open VisualGDB Project Properties and enable the Raw Terminal on the COM port connected to your board. In this tutorial we will use the port provided by the on-board Segger J-Link. Follow this tutorial for more details:07-terminal
  8. The HRS client sample registers clients for 2 Bluetooth LE services: heart rate service and battery level service. As the Nordic Bluetooth LE framework has a limit on the maximum client count, remove the calls to brs_c_init() and bas_c_init() from main() before adding a new client. You can also update the welcome message to indicate the new function of the example. Then press F5 to ensure that the firmware is successfully programmed into nRF51 and started: 08-log
  9. We will now modify the sample to report information about all nearby Bluetooth LE devices. First of all, change the scan_start() function to scan without white lists:
  10. Also replace the BLE_GAP_EVT_ADV_REPORT handler in on_ble_evt() with the code that prints the contents of the advertising packet:
  11. Press F5 to build the code and start debugging. Insert the battery into the CC2650 SensorTag or press the power button on it if the battery is already inserted:09-button
  12. Observe the output in the COMx window in Visual Studio. It should show the advertising packets received from the SensorTag:10-adv
  13. A typical advertising packet contains one or more fields in the following format: <field length> <field type><field data>. The list of field types can be found here and the field length includes the field type field. The advertising packet in the example contains 2 fields: “Flags = 0x05″ and “Incomplete UUID List = 0xAA10 (accelerometer service)”. To see more details from the SensorTag, we need to actively request them by sending scan requests. This is done by setting m_scan_param.active = 1 in scan_start(). Update the scan_start accordingly() and start the new firmware:11-advex
  14. The extended advertisement packet send in response to our active scan requests contains the SensorTag name in the LOCAL_NAME field (type=09). We will now change the BLE_GAP_EVT_ADV_REPORT handling code to connect to the devices that report their name as “CC2650 SensorTag”:
  15. If you start the new firmware, you will see that it is constantly resetting itself because we have not registered any clients:12-reset
  16. To register a client to the Simple Keys service (see the SensorTag profile for details) we need to call the ble_db_discovery_evt_register() function for the service with a UUID of 0xFFE0 (which is a shortcut for 0000FFE0-0000-1000-8000 00805F9B34FB as defined by the Bluetooth LE specification):
  17. Create an empty btnserv_discover_handler() function and set a breakpoint inside it:
  18. Finally call button_service_client_init() from main() after the call todb_discovery_init() and run the new firmware. Once the breakpoint is hit, use the Watch window to explore the contents of p_evt:13-service
  19. The contents of p_evt shows that the discovery logic has discovered a service with a UUID of 0xffe0 with 1 characteristic (UUID=0xffe1) and the characteristic configuration descriptor value is 0x4a. This matches the information from the SensorTag profile:14-table
  20. To start receiving notifications when a button is pressed, we need to write the values of 01:00 to the CCCD register. This is done by modifying the btnsrv_discover_handler() as follows:
  21. Finally we need to handle the HVX notifications that the CC2650 SensorTag will send. Create the following function and call it from ble_evt_dispatch() after all other calls:
  22. Build and start the new firmware and see how pressing buttons on the SensorTag turns on the LEDs on nRF51:2boards
  23. The COMx window in Visual Studio should show the “Button HVX” messages produced by the HVX event handler:15-log
  24. You can use the “Show on Code Map” and “Find All References” commands to find the code in the Nordic Bluetooth LE stack that accesses certain variables. E.g. search for references to the cccd_handle field:16-cccd
  25. By putting a breakpoint on the line that assigns it and checking the values of the related variables you can see that the cccd_handle gets the handle to a descriptor with a UUID of 0x2902 that matches the Client Characteristics Configuration Descriptor mentioned in the SensorTag Profile:17-desc