This code example demonstrates the implementation of a simple BLE Environmental Sensing Profile. It shows how to send environmental parameters like temperature by sending simulated temperature values over the BLE connection using the Cypress WiFi-BT combo SoCs supported in AnyCloud SDK. Instructions provided in this document are applicable for all supported kits in the ModusToolbox™ software environment.
- ModusToolbox™ software v2.1
- Programming Language: C
- Associated Parts: PSoC® 6 MCU parts with BLE, CYW43012, CYW4343W
- PSoC 6 Wi-Fi BT Prototyping Kit (CY8CPROTO-062-4343W) - Default target
- PSoC 62S2 Wi-Fi BT Pioneer Kit (CY8CKIT-062S2-43012)
- CYW9P62S1-43012EVB-01
- PSoC 62 Wi-Fi BT Pioneer Kit
This example uses the kit’s default configuration. See the respective kit guide to ensure that the kit is configured correctly.
This code example consists of two parts: a GAP Peripheral and a GAP Central.
For the Central, download and install the CySmart™ app for iOS or Android.
You can also use the CySmart Host Emulation Tool Windows PC application if you have access to the CY5677 CySmart BLE 4.2 USB Dongle. You can also use other Android or iOS apps that support the Environmental Sensing service.
Scan the following QR codes from your mobile phone to download the CySmart app.
Install a terminal emulator if you don't have one. Instructions in this document use Tera Term.
-
Click the New Application link in the Quick Panel (or, use File > New > ModusToolbox Application).
-
Pick a kit supported by the code example from the list shown in the Project Creator - Choose Board Support Package (BSP) dialog.
When you select a supported kit, the example is reconfigured automatically to work with the kit. To work with a different supported kit later, use the Library Manager to choose the BSP for the supported kit. You can use the Library Manager to select or update the BSP and firmware libraries used in this application.
To access the Library Manager, right-click the application name from the Project Workspace window in the IDE, and select ModusToolbox > Library Manager.
You can also just start the application creation process again and select a different kit.
If you want to use the application for a kit not listed here, you may need to update the source files. If the kit does not have the required resources, the application may not work.
-
In the Project Creator - Select Application dialog, choose the example.
-
Optionally, update the Application Name and Location fields with the application name and local path where the application is created.
-
Click Create to complete the application creation process.
For more details, see the Eclipse IDE for ModusToolbox User Guide: {ModusToolbox install directory}/ide_{version}/docs/mt_ide_user_guide.pdf.
-
Download and unzip this repository onto your local machine, or clone the repository.
-
Open a CLI terminal and navigate to the application folder.
On Linux and macOS, you can use any terminal application. On Windows, navigate to the modus-shell directory ({ModusToolbox install directory}/tools_<version>/modus-shell) and run Cygwin.bat.
-
Import the required libraries by executing the
make getlibscommand.
-
Follow the instructions from the CLI section to download or clone the repository, and import the libraries using the
make getlibscommand. -
Export the application to a supported IDE using the
make <ide>command. -
Follow the instructions displayed in the terminal to create or import the application as an IDE project.
For more details, see the "Exporting to IDEs" section of the ModusToolbox User Guide: {ModusToolbox install directory}/ide_{version}/docs/mtb_user_guide.pdf.
-
Connect the board to your PC using the provided USB cable through the KitProg3 USB connector.
-
Use your favorite serial terminal application and connect to the KitProg3 COM port. Configure the terminal application to access the serial port using the following settings.
Baud rate: 115200 bps; Data: 8 bits; Parity: None; Stop: 1 bit; Flow control: None; New line for receive data: Line Feed(LF) or Auto setting
-
Program the board.
-
Using Eclipse IDE for ModusToolbox:
-
Select the application project in the Project Explorer.
-
In the Quick Panel, scroll down, and click <Application Name> Program (KitProg3).
-
-
Using CLI:
From the terminal, execute the
make programcommand to build and program the application using the default toolchain to the default target. You can specify a target and toolchain manually:make program TARGET=<BSP> TOOLCHAIN=<toolchain>Example:
make program TARGET=CY8CKIT-062S2-43012 TOOLCHAIN=GCC_ARMNote: Before building the application, ensure that the deps folder contains the BSP file (TARGET_xxx.lib) corresponding to the TARGET. Execute the
make getlibscommand to fetch the BSP contents before building the application.
After programming, the application starts automatically. Observe the messages on the UART terminal, and wait for the device to make all the required connections.
-
-
To test using the CySmart mobile app, do the following (see equivalent CySmart app screenshots in Figure 1):
-
Turn ON Bluetooth on your Android or iOS device.
-
Launch the CySmart app.
-
Press the reset switch on the supported kit to start sending advertisements.
-
Swipe down on the CySmart app home screen to start scanning for BLE Peripherals; your device ("Thermistor") appears in the CySmart app home screen. Select your device to establish a BLE connection. Once the connection is established, the LED1 changes from OFF state to always ON state.
-
Select the 'Environment Sensing' Profile from the carousel view.
-
Select an 'GATT DB' on the 'Environmental Profile' screen.
-
Select Environmental Sensing Service from the list and tap Notify.
The temperature values will be updated every 5 seconds in different representations such as ASCII and HEX.
Figure 1. Testing with the CySmart App on Android
-
-
Use the KitProg3 COM port to view the Bluetooth stack and application trace messages in the terminal window.
Figure 2. Log Messages on KitProg3 COM Port
You can debug the example to step through the code. In the IDE, use the <Application Name> Debug (KitProg3) configuration in the Quick Panel. For more details, see the "Program and Debug" section in the Eclipse IDE for ModusToolbox User Guide: {ModusToolbox install directory}/ide_{version}/docs/mt_ide_user_guide.pdf.
This code example is written in a way that is generic across multiple devices and platforms. The code example application runs on the Arm® Cortex® core of the PSoC 6 MCU device. The functionality of the code example will remain the same on all the supported kits; the application was developed using the ModusToolbox.
This application demonstrates the BLE peripheral capability of the supported kit. The simulated temperature value is sent over BLE to a Central device, and to the UART as debug trace messages. This project demonstrates the following features:
- BLE Environment Sensing Service (ESS) – GATT Read and Notify functionality
- Debug Trace messages
- Connection with one Central device
- Connection status indication through LED
The project consists of the following files:
Table 1. Important User-Application-Related Source Files
| File Name | Comments |
|---|---|
| main.c | Contains the main() function, which is the entry point for execution of the user application code after device startup. |
| app_bt_cfg.c, app_bt_cfg.h | Contain the runtime Bluetooth stack configuration parameters such as device name and advertisement/ connection settings. Note that the name that the device uses for advertising (“Thermistor”) is defined in app_bt_cfg.c. |
| app_bt_gatt_handler.c, app_bt_gatt_handler.h | Contain the code for the Bluetooth stack GATT event handler functions. |
| cycfg_gatt_db.c, cycfg_gatt_db.h | Contain the GATT database information generated using the Bluetooth Configurator tool. These files reside in the GeneratedSource folder under the application folder. |
Figure 3. BLE Environmental Sensing Service Application
This flowchart provides an overview of the Environmental Sensing Profile application. The Environmental Sensing Profile in this application consists of one of the Bluetooth SIG-defined services, namely the Environment Sensing Service (ESS). This project implements only the Temperature characteristic from the Environmental Sensing service. This characteristic supports notification and read operations, which allow the GATT Server to send data to the connected GATT Client device whenever new data is available, and a read to be performed from the GATT Client device.
The Bluetooth Configurator provided by ModusToolbox makes it easier to design and implement the GATT DB. The Bluetooth Configurator generates the cycfg_gatt_db.c and cycfg_gatt_db.h files. All Environmental Sensing profile-related variables and functions are contained in these files. When the GATT DB is initialized after Bluetooth Stack initialization, all profile-related values will be ready to be advertised to the Central device. See the ModusToolbox Bluetooth Configurator Guide for details.
The code example generates dummy temperature values between 20 degree and 30 degree celsius. Every 5 seconds, the temperature varies by 1 degree celsius. A timer callback gives this simulated temperature value, which is then sent every 5 seconds to the Central device when connected and GATT notifications are enabled by the Central.
When the Peripheral device is connected, LED1 will be ON; when it is disconnected, LED1 will be OFF. To turn the LED ON and OFF, generic GPIO functions are used to drive the output pin HIGH or LOW. The LEDs present in the supported kits are active LOW LEDs, which means that the LED turns ON when the GPIO is driven LOW.
The app_bt_gatt_handler.c and app_bt_gatt_handler.h files handle the functionality of GATT callbacks from the Central device. On receiving a connection request, the Bluetooth stack gives a GATT event to the application of wiced_bt_gatt_evt_t type. For example, the LED toggle functionality is implemented in the GATT connection callback. On a disconnection event, the code resets the Client Characteristic Configuration Descriptor (CCCD) value so that on a reconnect event, notifications will be disabled.
In app_bt_cfg.c, all the runtime Bluetooth stack configuration parameters are defined; these will be initialized during Bluetooth stack initialization. Some of the configurations include the device name, connection interval, advertisement interval, advertisement channels to use, number of client connections, and maximum transmission unit (MTU). You also have the flexibility to configure the buffer pool size, which helps in optimizing the memory and transmission rate depending on the application use case.
The project also contains app_bt_util_functions.c and app_bt_util_functions.h which provide APIs to see meaningful messages in debug logs in the debug UART. Most of the status messages in Bluetooth stack are represented in enumerated values. These functions allow you to view the respective strings instead of the enumerated values.
This section explains the ModusToolbox resources and their configuration as used in this code example. Note that all the configuration explained in this section has already been done in the code example. ModusToolbox stores the configuration settings of the application in the design.modus file. This file is used by the graphical configurators, which generate the configuration firmware. This firmware is stored in the application’s GeneratedSource folder.
-
Device Configurator: The Device Configurator is used to enable/configure the peripherals and the pins used in the application. For detailed information on how to use it, see the Device Configurator Guide.
-
Bluetooth Configurator: The Bluetooth Configurator is used for generating/modifying the BLE GATT database. For detailed information on how to use it, see the Bluetooth Configurator Guide.
| Application Notes | |
|---|---|
| AN228571 – Getting Started with PSoC 6 MCU on ModusToolbox | Describes PSoC 6 MCU devices and how to build your first application with ModusToolbox |
| AN221774 – Getting Started with PSoC 6 MCU on PSoC Creator | Describes PSoC 6 MCU devices and how to build your first application with PSoC Creator |
| AN210781 – Getting Started with PSoC 6 MCU with Bluetooth Low Energy (BLE) Connectivity on PSoC Creator | Describes PSoC 6 MCU with BLE Connectivity devices and how to build your first application with PSoC Creator |
| AN215656 – PSoC 6 MCU: Dual-CPU System Design | Describes the dual-CPU architecture in PSoC 6 MCU, and shows how to build a simple dual-CPU design |
| Code Examples | |
| Using ModusToolbox | Using PSoC Creator |
| Device Documentation | |
| PSoC 6 MCU Datasheets | PSoC 6 Technical Reference Manuals |
| Development Kits | Buy at www.cypress.com |
| CY8CKIT-062-BLE PSoC 6 BLE Pioneer Kit | CY8CKIT-062-WiFi-BT PSoC 6 WiFi-BT Pioneer Kit |
| CY8CPROTO-063-BLE PSoC 6 BLE Prototyping Kit | CY8CPROTO-062-4343W PSoC 6 Wi-Fi BT Prototyping Kit |
| CY8CKIT-062S2-43012 PSoC 62S2 Wi-Fi BT Pioneer Kit | CY8CPROTO-062S3-4343W PSoC 62S3 Wi-Fi BT Prototyping Kit |
| CYW9P62S1-43438EVB-01 PSoC 62S1 Wi-Fi BT Pioneer Kit | CYW9P62S1-43012EVB-01 PSoC 62S1 Wi-Fi BT Pioneer Kit |
| Libraries | |
| PSoC 6 Peripheral Driver Library (PDL) and docs | psoc6pdl on GitHub |
| Cypress Hardware Abstraction Layer (HAL) Library and docs | psoc6hal on GitHub |
| RetargetIO - A utility library to retarget the standard input/output (STDIO) messages to a UART port | retarget-io on GitHub |
| FreeRTOS library and docs | FreeRTOS on GitHub |
| Middleware | |
| CapSense® library and docs | capsense on GitHub |
| Links to all PSoC 6 MCU middleware | psoc6-middleware on GitHub |
| Tools | |
| Eclipse IDE for ModusToolbox | The multi-platform, Eclipse-based Integrated Development Environment (IDE) that supports application configuration and development for PSoC 6 MCU and IoT designers. |
| PSoC Creator | The Cypress IDE for PSoC and FM0+ MCU development. |
Document Title: CE230294 – mtb-example-anycloud-ble-ess
| Version | Description of Change |
|---|---|
| 1.0.0 | New code example |
© Cypress Semiconductor Corporation, 2020. This document is the property of Cypress Semiconductor Corporation and its subsidiaries (“Cypress”). This document, including any software or firmware included or referenced in this document (“Software”), is owned by Cypress under the intellectual property laws and treaties of the United States and other countries worldwide. Cypress reserves all rights under such laws and treaties and does not, except as specifically stated in this paragraph, grant any license under its patents, copyrights, trademarks, or other intellectual property rights. If the Software is not accompanied by a license agreement and you do not otherwise have a written agreement with Cypress governing the use of the Software, then Cypress hereby grants you a personal, non-exclusive, nontransferable license (without the right to sublicense) (1) under its copyright rights in the Software (a) for Software provided in source code form, to modify and reproduce the Software solely for use with Cypress hardware products, only internally within your organization, and (b) to distribute the Software in binary code form externally to end users (either directly or indirectly through resellers and distributors), solely for use on Cypress hardware product units, and (2) under those claims of Cypress’s patents that are infringed by the Software (as provided by Cypress, unmodified) to make, use, distribute, and import the Software solely for use with Cypress hardware products. Any other use, reproduction, modification, translation, or compilation of the Software is prohibited. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CYPRESS MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS DOCUMENT OR ANY SOFTWARE OR ACCOMPANYING HARDWARE, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. No computing device can be absolutely secure. Therefore, despite security measures implemented in Cypress hardware or software products, Cypress shall have no liability arising out of any security breach, such as unauthorized access to or use of a Cypress product. CYPRESS DOES NOT REPRESENT, WARRANT, OR GUARANTEE THAT CYPRESS PRODUCTS, OR SYSTEMS CREATED USING CYPRESS PRODUCTS, WILL BE FREE FROM CORRUPTION, ATTACK, VIRUSES, INTERFERENCE, HACKING, DATA LOSS OR THEFT, OR OTHER SECURITY INTRUSION (collectively, “Security Breach”). Cypress disclaims any liability relating to any Security Breach, and you shall and hereby do release Cypress from any claim, damage, or other liability arising from any Security Breach. In addition, the products described in these materials may contain design defects or errors known as errata which may cause the product to deviate from published specifications. To the extent permitted by applicable law, Cypress reserves the right to make changes to this document without further notice. Cypress does not assume any liability arising out of the application or use of any product or circuit described in this document. Any information provided in this document, including any sample design information or programming code, is provided only for reference purposes. It is the responsibility of the user of this document to properly design, program, and test the functionality and safety of any application made of this information and any resulting product. “High-Risk Device” means any device or system whose failure could cause personal injury, death, or property damage. Examples of High-Risk Devices are weapons, nuclear installations, surgical implants, and other medical devices. “Critical Component” means any component of a High-Risk Device whose failure to perform can be reasonably expected to cause, directly or indirectly, the failure of the High-Risk Device, or to affect its safety or effectiveness. Cypress is not liable, in whole or in part, and you shall and hereby do release Cypress from any claim, damage, or other liability arising from any use of a Cypress product as a Critical Component in a High-Risk Device. You shall indemnify and hold Cypress, its directors, officers, employees, agents, affiliates, distributors, and assigns harmless from and against all claims, costs, damages, and expenses, arising out of any claim, including claims for product liability, personal injury or death, or property damage arising from any use of a Cypress product as a Critical Component in a High-Risk Device. Cypress products are not intended or authorized for use as a Critical Component in any High-Risk Device except to the limited extent that (i) Cypress’s published data sheet for the product explicitly states Cypress has qualified the product for use in a specific High-Risk Device, or (ii) Cypress has given you advance written authorization to use the product as a Critical Component in the specific High-Risk Device and you have signed a separate indemnification agreement. Cypress, the Cypress logo, Spansion, the Spansion logo, and combinations thereof, WICED, PSoC, CapSense, EZ-USB, F-RAM, and Traveo are trademarks or registered trademarks of Cypress in the United States and other countries. For a more complete list of Cypress trademarks, visit cypress.com. Other names and brands may be claimed as property of their respective owners.