SoC - Thermometer Client
This sample application demonstrates the operation of a client device in a multi-slave BLE topology. Silicon Labs Bluetooth stack supports simultaneous connection for up to eight slave devices at one time. This sample application illustrates how to handle simultaneous connection to four thermometer peripheral devices.
Getting Started
To get started with Bluetooth and Simplicity Studio, see QSG169: Bluetooth® SDK v3.x Quick Start Guide.
To get familiar with client and server roles, see GATT Server and Client Roles.
To learn more about master and slave roles, see Master and Slave Roles.
To learn more about multi-slave BLE topology, see Multi-Slave Topology.
You may also like to read Bluetooth Connection Flowcharts to understand the BLE connection procedures.
Evaluating the Application
To evaluate this application, you need one EFR32/BGM device running the SoC Thermometer Client sample application, and at least one (but no more than four) peripheral devices running the SoC Thermometer application. The following figure shows the topological setup for testing this sample app.
When the client boots, it starts Sanning/Discovering advertising devices. It initiates a connection with those devices that contain the Health Thermometer service in their advertising packets.
After a connection is established, the client discovers the Health Thermometer service from the remote GATT database. After the service discovery is completed, the client discovers the thermometer characteristics and enables indications sent from a remote GATT server. The main GATT procedures are represented in the following state diagram.
After programming the devices, open your terminal emulator and connect to your client device over its serial port. Set baud rate to 115200. Power on the slave thermometer devices and observe the output readings on your terminal.
Troubleshooting
Note that NO Bootloader is included in any Software Example projects. However, when a precompiled demo is flashed, both bootloader and application images are loaded onto the device.
- To flash an example which doesn't have a corresponding prebuilt demo, SoC-Empty demo can be flashed before your application in order to load the bootloader.
- For your custom application, create your own bootloader project and flash it to your device before flashing your application.
- When you flash your application image to the device, use the .hex or .s37 output file. Flashing .bin files may overwrite (erase) the bootloader.
- On Series 1 devices (EFR32xG1x), both first stage and second stage bootloaders have to be flashed. This can be done at once by flashing the *-combined.s37 file found in your bootloader project after building the project.
- More information is available in UG103: Bootloading fundamentals and UG266: Silicon Labs Gecko Bootloader User's Guide.
Before programming the radio board mounted on the WSTK, make sure the power supply switch the AEM position (right side) as shown below.
Resources
UG103.14: Bluetooth® LE Fundamentals
QSG169: Bluetooth® SDK v3.x Quick Start Guide
UG434: Silicon Labs Bluetooth ® C Application Developer's Guide for SDK v3.x
Report Bugs & Get Support
You are always encouraged and welcome to report any issues you found to us via Silicon Labs Community.