QSG120 - Silicon Labs
QSG120: Silicon Labs AppBuilder-Based
Bluetooth® Smart C-SDK Quick-Start Guide
This quick-start guide provides basic information on configuring,
building, and installing both SoC and NCP Bluetooth Smart
applications using the AppBuilder-based C-SDK and an
EFR32™BG or Blue Gecko Module Wireless Starter Kit.
This guide is designed for new users of the Silicon Labs AppBuilder-based Bluetooth
Smart C-SDK. It provides instructions to get started using the example applications provided with the C-SDK to demonstrate different Bluetooth Smart functionality.
KEY FEATURES
• Product overview
• Setting up your development environment
• Discovering the Bluetooth Smart C-SDK
• Working with example applications using
the SoC or NCP demo for Smart Phone
• About other example applications
• Flashing the pre-built demonstration files
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Product Overview
1
Product Overview
Before following the procedures in this guide you must have
•
Purchased your Bluetooth Smart Wireless Starter Kit (WSTK).
•
•
SLWSTKT6020A EFR32BG Wireless Starter Kit or
SLWSTK6101A Blue Gecko Module Wireless Starter Kit
•
Registered on the Silicon Labs Website, for access to the Bluetooth Smart C-SDK.
•
Downloaded the required software components. A card in your WSTK contains a link to a Getting Started page, which will direct you
to links for the Silicon Labs software products.
•
This Quick Start Guide can also be used with SLWSK6000A EFR32MG 2.4 GHz Mesh Networking kit.
1.1
NCP and SoC Bluetooth Smart Applications
The Bluetooth Smart C-SDK allows you to develop System-On-Chip (SoC) software applications in C language on a single microcontroller, but it also supports interfacing an external host microcontroller to another microcontroller (Network Co-Processor, NCP) running the
Bluetooth Smart stack over a UART interface using the C language BGAPI protocol. This document gives you a guide on how to get
started with the sample applications for both models.
1.2
Software Components
To develop Silicon Labs Bluetooth Smart applications using the C-SDK, you will need the following:
•
The Simplicity Studio development environment, which incorporates AppBuilder. AppBuilder is an interactive GUI tool that allows you
to configure a body of Silicon Labs-supplied code to implement applications. Simplicity Studio also includes Profiler, which enables
power profiling of code in real time by measuring power consumption; Network Analyzer, which captures a trace of wireless network
activity; and the Hardware Configurator, which automatically generates code for hardware peripherals and port I/O, as well as other
tools helpful for developers. Online help for AppBuilder and other Simplicity Studio modules is provided.
•
The Silicon Labs Bluetooth Smart C-SDK supports highly customized development using the Bluetooth Smart protocol. It incorporates
a collection of libraries, including the Bluetooth Smart stack libraries, which you can link to your applications.
•
IAR Embedded Workbench for ARM 7.30 or later, used as a compiler in the Simplicity Studio development environment. You can
download IAR EWARM 7.30 from the Silicon Labs support portal.
•
If you are working with the NCP model you also need:
•
•
Cygwin package, which includes the make tool and the x86 compiler used to build NCP host code (from https://cygwin.com/index.html). Figure 30, Figure 31, and Figure 36 were taken from the Cygwin terminal.
GCC ARM Embedded Toolchain v. 4.9 (from https://launchpad.net/gcc-arm-embedded) for building the NCP target application
code. The path of the GCC ARM toolchain has to be specified as a GCCPATH environment variable accessible in the Cygwin
terminal, for example:
GCCPATH="c:/SiliconLabs/SimplicityStudio/v3/developer/toolchains/gnu_arm/4.9-2015q3"
In addition, you will interact with many of the Bluetooth Smart example applications through the Blue Gecko app downloaded to your iOS
or Android smartphone.
For iOS: In the App Store, search for Blue Gecko and download the Silicon Labs Blue Gecko WSTK App.
For Android: In the Google Play store, search for Blue Gecko and install the Blue Gecko App.
1.3
Support
Registered users can access the Silicon Labs support portal at https://www.silabs.com/support. Use the support portal to contact Customer Support for any questions you might have during the development process.
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 1
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Product Overview
1.4
Documentation
The SDK installer provides a documentation index (in documentation/index.htm and also linked from a Start Menu entry) that contains
links to documentation locations. Simplicity Studio provides links to hardware documentation and other appnotes.
For more information about the following topics, see the referenced documentation:
•
Information about modifying these sample applications or writing new applications is provided in UG136, Silicon Labs Bluetooth®
Smart SoC Application Developers Guide (installed with the Bluetooth Smart C-SDK)
•
Development of BRD4300A (BGM111 Bluetooth Smart Modules) in BGScript programming language is provided in QSG107,
SLWSTK6101A Quick-Start Guide (on the Silicon Labs website). This document covers C language only.
•
The Bluetooth Smart Stack, the BGAPI protocol, and the software architecture are discussed in QSG108, Blue Gecko Bluetooth®
Smart Software Quick-Start Guide (on the Silicon Labs website).
•
Application development in IAR Embedded Workbench is covered in AN975, Bluetooth Smart Application Development with IAR.
•
Additional features of Simplicity Studio of interest to developers are documented in AN0822, Simplicity Studio™ User Guide, and
AN0823, Simplicity Configurator User Guide (available through the Application Notes tile in the Simplicity perspective).
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 2
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Setting Up Your Development Environment
2
Setting Up Your Development Environment
2.1
Install Third-Party Tools
Install third-party tools, such as IAR Embedded Workbench for ARM (see section 1.1 for the list).
2.2
Install your Silicon Labs Stack or Software Development Kit
Install Silicon Labs software (see section 1.1 for more information).
Note: If you had installed an earlier version of Simplicity Studio, uninstall it before installing the latest release.
2.3
Connect your Hardware
Connect your WSTK, with radio board mounted, to your PC using a USB cable.
Note: For best performance in Simplicity Studio, be sure that the power switch on your WSTK is in the Advanced Energy Monitoring or
“AEM” position (Figure 1).
Figure 1. EFR32BG on a WSTK
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 3
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Setting Up Your Development Environment
2.4
Install Simplicity Studio
During installation, Simplicity Studio obtains updates and additional packages specific to your connected hardware.
1. As soon as Simplicity Studio launches, it searches for updates. This operation can take several minutes.
Figure 2. Checking for Software Updates
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 4
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Setting Up Your Development Environment
2. Once software update is complete, Simplicity Studio checks for connected hardware. If you have not connected your WSTK, you are
prompted to do so (Figure 3). Connect your hardware and, when the screen changes to show that the hardware has been found, click
[Finish].
Figure 3. Connect a Kit Before and After Connection
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 5
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Setting Up Your Development Environment
3. Simplicity Studio then installs software packages related to your connected hardware (Figure 4). This procedure can take some time,
during which the green progress indicator may appear stationary. However, the update steps above the progress indicator are continuously refreshed.
Figure 4. Installation Update
4. After update is complete, restart Simplicity Studio.
5. Once restart is complete, a menu of setup tasks is displayed (Figure 5). Select Initial Setup and then click [Launch setup].
Figure 5. Setup Tasks
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 6
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Setting Up Your Development Environment
6. A kit selection dialog is displayed (Figure 6). Your connected kit should be selected. Click [Next >].
Figure 6. Kit Selection Dialog
7. A part selection dialog is displayed (Figure 7). Your connected part should be selected. Click [Next >].
Figure 7. Part Selection Dialog
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 7
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Setting Up Your Development Environment
8. A Build Environment Configuration dialog is displayed that shows detected items (Figure 8). If a Toolchain or SDK is not shown, you
can click Add… to configure it now, or configure it later from the Settings control. Adding an SDK is described in section 3, Discovering
the Bluetooth Smart C-SDK. Click [Finish]. The Simplicity perspective, described in the next section, is displayed.
Figure 8. Build Environment Configuration
9. The software sample applications were tested with the WSTK Board Controller Software Build 435. This WSTK firmware package or
later must be installed on your kit. To update your WSTK board controller firmware, click on the Kit Manager tile in the Simplicity
perspective (Figure 9). Your firmware will be updated to latest version automatically (Figure 10).
Figure 9. Kit Manager Tile
Figure 10. Kit Manager with Latest Board Controller Firmware
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 8
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Setting Up Your Development Environment
2.5
Navigation in Simplicity Studio
Simplicity Studio is built on the Eclipse platform. As such, it is broken up into different “perspectives,” each of which allows access to a
specific set of functionality. Simplicity Studio starts up in the “Simplicity perspective,” sometimes referred to as the “Home Screen”
(Figure 11).
Figure 11. Simplicity Studio's Simplicity Perspective
From the Simplicity perspective, you can discover devices, configure Simplicity Studio, or navigate to another perspective for application
development.
The Simplicity perspective shows large tile icons that represent the various sets of functionality within Simplicity Studio. Clicking a tile
opens a different perspective. When you are in a different perspective, you can always return to the Simplicity perspective or any other
perspective at any time by clicking on one of the tile icons in the top right-hand corner of your screen (Figure 12).
Figure 12. Navigation Tile Icons
Your detected hardware is shown in the Detected Hardware panel in the lower left of the Simplicity perspective. If you change connected
hardware and it does not auto-detect, click [Refresh Detected Hardware].
Three controls in the upper right (Figure 13) allow you to maintain part-specific packages, install updates to the core Simplicity Studio
software, and change configuration settings.
Figure 13. Maintenance Tools
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 9
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Discovering the Bluetooth Smart C-SDK
3
Discovering the Bluetooth Smart C-SDK
If you are discovering the C-SDK from the Build Environment Configuration Add … step described in section 2.4, Install Simplicity Studio,
go to step 4. If you are discovering the SDK after initial setup, begin with step 1.
1.
Click the Settings icon (Figure 14) on the top right-hand corner of the Simplicity perspective to open the Preferences window.
Figure 14. Settings Icon
2. In the Preferences window’s left frame, click Simplicity Studio > SDKs to open the configuration dialog (Figure 15).
Figure 15. Silicon Labs SDK Configuration
3. Click [Add].
4. Browse to the location where you have installed the C-SDK and click [OK].
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 10
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Discovering the Bluetooth Smart C-SDK
5. Verify the software has detected the Bluetooth Smart SDK (Figure 16) and click [OK].
Figure 16. Add SDKs
6. Click [OK] to return to the starting configuration page.
7. Click [Finish] (from initial configuration) or [OK] (from the settings icon).
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 11
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Working with Example Applications
4
Working with Example Applications
When working with example applications in the Silicon Labs AppBuilder-based Bluetooth Smart C-SDK, you will execute the following
steps:
1. Select an example application.
2. Generate application files.
3. Compile and flash the application to the EFR32BG on the WSTK. If you are working with an NCP example, you will also make and
run the host application on your computer.
4. Interact with the application using the WSTK and the Blue Gecko app.
These steps are described in detail in the following sections.
4.1
Selecting an Example Application
The Bluetooth Smart C-SDK comes with a number of example applications. This guide provides instructions for building, loading, and
interacting with the both the SoC and NCP variants of the Demo for the Smart Phone App. See section 5, About Other Example Applications for more information on using the other example applications. The SoC examples are also provided as pre-built binary files, allowing
you to bypass the generating and compiling steps. See section 6, Flashing the Pre-Built Demonstration Files for instructions.
The Demo for the Smart Phone App allows you to use the WSTK and the client Blue Gecko app in the following modes:
•
Health Thermometer mode: In this mode, the server sends temperature measurement values and other related data from its onboard temperature sensor. The service is intended for healthcare and fitness applications. It demonstrates how information can be
transferred from server to client.
•
Beaconing mode: In this mode, the server sends device-specific information to the clients in its proximity. It transmits its universally
unique identifier (UUID) in its advertising packets, which can be picked up by a compatible client device. This feature demonstrates
how data can be transmitted to the client without a connection.
•
Immediate Alert Service (Key Fobs) mode: In this mode, the client device sends immediate alert level updates based on the proximity of the server device. This service demonstrates how information can be transferred from client to server.
1. In the Simplicity perspective, click the Software Examples tile (Figure 17).
Figure 17. Software Examples Tile
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 12
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Working with Example Applications
2. In the New Example dialog (Figure 18), enter the kit, part, and SDK. Kit and part will be filled by Simplicity Studio if the hardware was
detected and displayed in the Simplicity perspective (Figure 17).
Figure 18. New Example Project Dialog
3. Click [Next].
4. Select an example from the list (Figure 19). For the purposes of this guide, select either the SoC demo for Smart Phone App or the
NCP demo for Smart Phone App.
a)
b)
Figure 19. SoC (a) and NCP (b) Example Project Lists
5. Click [Next].
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 13
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Working with Example Applications
6. If you wish, change the default project name or location in the Project Configuration Dialog (Figure 20). If you are building an NCP
example, you will need the location later in the procedure. Click [Finish].
Figure 20. Project Configuration Dialog
4.2
Generating the Application Source Files
1. When you finish creating your example project, an AppBuilder General tab opens (Figure 21). Click [Generate].
Figure 21. AppBuilder General Tab
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 14
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Working with Example Applications
2. In the Overwrite Dialog (Figure 22), if necessary, uncheck ble-xxx-callbacks.c, and check efr32xxx.hwconf. Click [OK].
Figure 22. Overwrite Dialog
3. Once generation is complete, a dialog reporting results is displayed (Figure 23). Click [OK].
Figure 23 Generation Confirmation Dialog
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 15
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Working with Example Applications
4.3
Flashing and Interacting with the Application
The procedure to flash and run the application differs depending on whether you are using an SoC example or an NCP example.
4.3.1 SoC Example
1. After you click [OK] on the Generation Confirmation dialog, the AppBuilder General tab returns. Click [Debug] to compile and flash
the application to the EFR32.
Figure 24. AppBuilder Debug Control
2. A dialog shows the procedure’s progress (Figure 25). Wait until flashing has completed and a debug window is displayed.
Figure 25. Flash Progress
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 16
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Working with Example Applications
3. In the Debug window, click [Resume] to start the application running on the WSTK (Figure 26).
Figure 26. Debug Window
Next to the Resume control are Suspend, Disconnect, Reconnect, and Stepping controls. Click [Disconnect] (
ready to exit Debug mode.
) when you are
4. The application should display on the WSTK LCD (Figure 27).
Figure 27. Example Application Display
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 17
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Working with Example Applications
5. In the Blue Gecko app, touch Health Thermometer (Figure 28a).
a)
b)
c)
Figure 28. Blue Gecko App - SoC Results
6. Touch the device (Figure 28b). The app displays the measured temperature, and a fixed timestamp (Figure 28c).
To demonstrate the retail beacon mode, briefly (< 2s) press PB0 on the WSTK until the display changes to BEACON MODE. Touch
Retail Beacon on the Blue Gecko app. The app displays details about the broadcasting device.
To demonstrate the Key Fobs mode, briefly press PB0 on the WSTK until the display changes to Advertising MODE. Touch Key Fobs
on the Blue Gecko app. Touch [FIND] next to the displayed device (Figure 29a). On the WSTK, the LED flicker frequency indicates the
proximity of the smartphone. The frequency increases as the smartphone is moved closer, and decreases and finally stops as the
smartphone is moved further away.
a)
b)
Figure 29. Blue Gecko App - Key Fobs
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 18
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Working with Example Applications
4.3.2 NCP Example
1. After you have generated the example, open a console window and change to the project folder. A .mk file should be in the list of files
in that directory
Figure 30. Project Folder List
2. Make sure GCCPATH variable is set as described in section 1.2, Software Components.
3. Enter make -f <filename>.mk where <filename> is the name of the .mk file in your project folder. At the end of make, exehost and exe-target bins are created in the exe folder. Process output and the bin contents are shown in Figure 31.
Figure 31. Make Output
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 19
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Working with Example Applications
4. In Simplicity Studio, return to the Simplicity perspective and click the Flash Programmer tile (Figure 32).
Figure 32. Flash Programmer Tile
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 20
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Working with Example Applications
5. In the Flash Programmer dialog, click [Browse] to go to the exe-target folder and select the hex binary image (Figure 33).
Figure 33. Flash Programmer Dialog
6. After you have selected the image, click [Program]. A dialog shows the procedure’s progress (Figure 34). Wait until flashing has
completed and the dialog closes.
Figure 34. Flash Progress
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 21
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Working with Example Applications
7. Open your computer’s device manager interface and note the JLink CDC UART port number (Port 25 in Figure 35).
Figure 35. Windows Device Manager with JLink CDC UART Port Assigned
8. In the console, execute the host application and enter the JLink port number (Figure 36). Demo application information should be
displayed in the console window after the application starts.
Figure 36. Host Application Execution
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 22
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Working with Example Applications
9. In the Blue Gecko app, touch Health Thermometer (Figure 37a).
a)
b)
c)
Figure 37. Blue Gecko App - NCP Results
10. Touch the device (Figure 37b). The app displays a fixed temperature, and an actual timestamp (Figure 37c).
The other functions are the same as for the SoC version. To demonstrate the retail beacon mode, briefly (< 2s) press PB0 on the WSTK
until the display changes to BEACON MODE. Touch Retail Beacon on the Blue Gecko app. The app displays details about the broadcasting device.
To demonstrate the Key Fobs mode, briefly press PB0 on the WSTK until the display changes to Advertising MODE. Touch Key Fobs
on the Blue Gecko app. Touch [FIND] next to the displayed device. On the WSTK, the LED flicker frequency indicates the proximity of
the smartphone. The frequency increases as the smartphone is moved closer, and decreases and finally stops as the smartphone is
moved further away.
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 23
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
About Other Example Applications
5
About Other Example Applications
Most of the other example applications are available in both SoC and NCP versions and are built and flashed to the EFR32BG using the
same procedures as described for the Demo example.
The following examples provide demo functionality but as stand-alone applications. You can use the corresponding Blue Gecko app
functions to interact with them just as you can with the demo.
•
Health Thermometer Profile: In this profile, the server sends temperature measurement values and other related data from its onboard temperature sensor. The service is intended for healthcare and fitness applications. The example demonstrates how information
can be transferred from server to client.
•
Apple iBeacon: The iBeacon Service allows Bluetooth accessories a simple and convenient way to send iBeacons to iOS devices.
The example advertises non-connectable iBeacons. The beacon plugin used in this example can also be configured for the AltBeacon
or EddyStone beacon formats.
•
Find Me Profile: In this profile, the client device sends immediate alert level updates based on the proximity of the server device. The
example demonstrates how information can be transferred from client to server.
Other examples for both SoC and NCP that may be used with the Blue Gecko app’s general Bluetooth Smart service browser are:
•
Cycling Power profile: This profile enables a Collector device to connect and interact with a Cycling Power Sensor for use in sports
and fitness applications. The example implements the Cycling Power Sensor (Server) Role in the Cycling Power Profile. The device
acts as a Peripheral.
•
Cycling Speed and Cadence profile: This profile enables a Collector device to connect and interact with a Cycling Speed and
Cadence Sensor for use in sports and fitness applications. The example implements the Cycling Speed and Cadence Sensor (Server)
Role in the Cycling Speed and Cadence Profile. The device acts as a Peripheral.
•
Heart Rate profile: This profile enables a Collector device to connect and interact with a Heart Rate Sensor for use in fitness applications. The example implements the Heart Rate Sensor (Server) Role in the Heart Rate Profile. The device acts as a Peripheral.
•
Proximity profile: This profile enables proximity monitoring between two devices. The example implements the Proximity Reporter
(Server) Role in the Proximity Profile. The device acts as a Peripheral.
•
HID over GATT profile: This profile defines how a device with Bluetooth low energy wireless communications can support HID
services over the Bluetooth low energy protocol stack using the Generic Attribute Profile. The example implements the HID Device
(Server) Role in the HID over GATT profile - Server role. The device acts as a Peripheral.
After starting any of these applications on the WSTK, in the Blue Gecko app touch BLE Stack & Profile Test (Figure 38a). The app
displays Bluetooth Smart devices in the area. Touch a device to see additional details.
a)
b)
c)
Figure 38. Blue Gecko App - BLE Stack & Profile Test
Other example applications are:
•
Apple Notification Center - client: The Apple Notification Center Service (ANCS) gives Bluetooth accessories that connect to iOS
devices through a Bluetooth low-energy link a simple and convenient way to access many kinds of notifications generated on iOS
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 24
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
About Other Example Applications
devices. The example implements the Notification Consumer (Client) Role in the Apple Notification Center Service. The device acts
as a Peripheral.
•
Basic server role: This is an empty skeleton project where the device acts as a Peripheral and Server, but only the GAP service is
included. Services can be easily added by checking plugin options in the .isc file on the Plugins tab.
•
Cable Replacement Service - client and server roles: Specifics provided below.
The SoC cable replacement service examples together demonstrate how two devices can exchange data over a Bluetooth Smart link.
The demonstration uses two WSTKs.
1. Flash the first with the Cable Replacement Service - Server role example. It will act as Bluetooth Smart Peripheral.
2. Flash the second with the Cable Replacement Service - Client role. It will act as Bluetooth Smart Central.
3. Open your computer’s device manager interface and note the JLink CDC UART port number of each device.
4. Open a serial terminal session for each of these ports.
5. Push the Reset button on the Server WSTK and then on the Client WSTK. The connection process is displayed on the serial terminal
screens. After the devices are connected, text typed in one of the serial terminals appears on the other (Figure 39).
Figure 39. Cable Replacement Service Terminal Displays
Finally, your example list may contain a file empty_ble. Do not use this example.
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 25
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Flashing the Pre-Built Demonstration Files
6
Flashing the Pre-Built Demonstration Files
The SoC examples also are provided as pre-built binary files, ready to be flashed and used.
1.
In the Simplicity perspective, click the Demos tile (Figure 40).
Figure 40. The Demos Tile
2. Select a demonstration file and click [Finish] (Figure 41)
Figure 41. Demonstration Selection Dialog
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 26
QSG120: Silicon Labs AppBuilder-Based Bluetooth® Smart C-SDK Quick-Start Guide
Flashing the Pre-Built Demonstration Files
3. A dialog shows the procedure’s progress. Wait until flashing has completed, the dialog closes, and a Profiler window opens.
Figure 42. Flash Progress
silabs.com | Smart. Connected. Energy-friendly
Rev. 0.3 | 27
Smart.
Connected.
Energy-Friendly
Products
Quality
www.silabs.com/products
www.silabs.com/quality
Support and Community
community.silabs.com
Disclaimer
Silicon Laboratories intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using
or intending to use the Silicon Laboratories products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and
"Typical" parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Laboratories reserves the right to
make changes without further notice and limitation to product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the
included information. Silicon Laboratories shall have no liability for the consequences of use of the information supplied herein. This document does not imply or express copyright licenses
granted hereunder to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any Life Support System without the specific written consent
of Silicon Laboratories. A "Life Support System" is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant
personal injury or death. Silicon Laboratories products are not designed or authorized for military applications. Silicon Laboratories products shall under no circumstances be used in
weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons.
Trademark Information
Silicon Laboratories Inc.® , Silicon Laboratories®, Silicon Labs®, SiLabs® and the Silicon Labs logo®, Bluegiga®, Bluegiga Logo®, Clockbuilder®, CMEMS®, DSPLL®, EFM®, EFM32®,
EFR, Ember®, Energy Micro, Energy Micro logo and combinations thereof, "the world’s most energy friendly microcontrollers", Ember®, EZLink®, EZRadio®, EZRadioPRO®, Gecko®,
ISOmodem®, Precision32®, ProSLIC®, Simplicity Studio®, SiPHY®, Telegesis, the Telegesis Logo®, USBXpress® and others are trademarks or registered trademarks of Silicon Laboratories Inc. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. All other products or brand
names mentioned herein are trademarks of their respective holders.
Silicon Laboratories Inc.
400 West Cesar Chavez
Austin, TX 78701
USA
http://www.silabs.com
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement