3.1 Bluetooth® Low Energy Legacy Advertisements
This section helps users enable Bluetooth® Low Energy Advertisements on the Curiosity Board using the MPLAB Code Configurator (MCC). In this basic application example, the advertisement interval will be set to 1 sec.
Users of this section can choose to either run the precompiled application example
.hex
file on the Curiosity board and experience the demo or can go
through the steps involved in developing this application from scratch.
These examples build on top of one another. We strongly recommend following the examples in order, to learn the basic concepts first before progressing to the more advanced topics.
Recommended Reading
- BLE Software Specification
- Getting Started with WME Bluetooth Low Energy Applications
Hardware Required
Tool | Qty |
---|---|
Curiosity Board | 1 |
Micro USB cable | 1 |
Android/iOS Smartphone | 1 |
Power Debugger/Multimeter | 1 |
Software Requirement
- MPLAB X IPE: For programming the precompiled hex file.
- MPLAB X IDE: For programming the application example.
- Teraterm: Terminal Emulator for displaying UART output.
Programming the Precompiled Hex File or Application Example
Programming the .hex
File using MPLAB X IPE
- Precompiled
.hex
files are located in “<Harmony Content Path>wireless_apps_ble\apps\legacy_adv\hex\
” folder. - For more information on the
programming steps, refer to the Programming a Device in MPLAB IPE.Note: Users must choose the correct device and tool information.
Programming the Application using MPLAB X IDE
- Follow the steps mentioned in Running a Precompiled Example
- Open and program the
application example “
legacy_adv_xxxx.X
” where xxxx refer to device ( for example: WBZ451, project file:legacy_adv_wbz451.X
) located in “<Harmony Content Path>\wireless_apps_ble\apps\legacy_adv\firmware
” using MPLAB X IDE.
For more details on finding the Harmony content path, refer to Installing the MCC Plugin.
Demo Description
Developing the Application from Scratch Using MCC
- Create a new MCC Harmony Project by selecting the device. For more details, refer to Creating a New MCC Harmony Project.
- Launch the MCC from the toolbar
as illustrated below. The project graph will open with the default
components.
Figure 3-21. MCC - In the Device Resources window,
expand Libraries > Harmony > Wireless > Application
Services. Then, click the Plus Symbol to add the BLE
Config App Service Component to the project
Figure 3-22. BLE Config App Service - All BLE Stack related components will be added into the project graph. Accept dependencies or satisfiers by selecting Yes.
- For configuring BLE Config App Service component based on the device refer to Adding BLE Config App Service Component to Project Graph and Selecting the Device in Getting Started with WME Bluetooth Low Energy Applications from Related Links.
- To enable digital and communication interfaces, refer to Enabling Digital Input/Output and Communication Interfaces Through System Hardware Definition (SHD) component in Getting Started with WME Bluetooth Low Energy Applications from Related Links.
- For FreeRTOS component settings refer to the Configuring FreeRTOS in Getting Started with WME Bluetooth Low Energy Applications from Related Links.
- For WBZ451
- Verify if the project
graph window has all the expected components, as illustrated in the
following figure:
Figure 3-23. Project Graph
- Verify if the project
graph window has all the expected components, as illustrated in the
following figure:
- For WBZ351
- Change FreeRTOS
Component setting as illustrated in the following figure
Figure 3-24. FreeRTOS Component - Verify if the project
graph window has all the expected components. as illustrated in the
following figure:
Figure 3-25. Project Graph
- Change FreeRTOS
Component setting as illustrated in the following figure
- Change BLE Stack Component
configuration as illustrated in the following figure.
Figure 3-26. BLE Stack Configuration Figure 3-27. BLE Stack Configuration
Generating a Code
For more details on code generation, refer to the MPLAB Code Configurator (MCC) Code Generation.
Files Containing User Application Code
Source Files | Usage |
---|---|
app.c | Application State machine, includes calls for Initialization of all BLE stack (GAP,GATT, SMP, L2CAP) related component configurations |
app_ble_callbacks.c | All the event functions related to GAP, GATT, SMP and L2CAP events that user can use or modify. |
app_utility.c | Contains generic utility functions that serve the purpose of providing reusable, common functionalities that can be applied across various parts of a program. |
app.c
is auto generated and has
a state machine based application code sample. Users can use this template to
develop their application. Main application logic is implemented in void
APP_Tasks()
function.app.c
app.c