3.5 Bluetooth® Low Energy Multiple Advertising Sets
This section assist users in enabling BLE Multiple Advertising Sets on the Curiosity board using the MCC. In this application example, two sets of advertisements are implemented. For more details, refer to section “4.4.2.10 Advertising Sets” of BLUETOOTH CORE SPECIFICATION Version 5.4 | Vol 6, Part B.
Users can either choose to 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 are incrementally structured upon one another. Recommendation is to follow the examples in order, by learning the basic concepts first and then progressing to the more advanced topics.
Recommended Reading
- BLE Software Specification
- Getting Started with WME Bluetooth Low Energy Applications
Hardware Requirement
Tool | Qty |
---|---|
Curiosity Board | 1 |
Micro USB cable | 1 |
Android/iOS smartphone | 1 |
st
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.
Smart Phone App
- Light Blue iOS/Android app available in stores
Programming the Precompiled
.hex
file or Application Example
Programming the .hex
File using MPLAB X IPE
-
Import and program the Precompiled Hex file: “
<Harmony Content Path>\Wireless_apps_ble\apps\two_set_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 “
two_set_adv_xxxx.X
" where xxxx refer to device (for example: WBZ451, project file:two_set_adv_wbz451.X
) located in “<Harmony Content Path>\wireless_apps_ble\apps\two_set_adv\firmware
” using MPLAB X IDE
For more details on finding the Harmony content path, refer to Installing the MCC Plugin.
Demonstration
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-58. 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-59. 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 link Configuring FreeRTOS in Getting Started with WME Bluetooth Low Energy Applications from Related Links.
- Verify Device Information
Service component setting as shown in the
Figure 3-60. Device Information Service - For WBZ451
- Verify if the project
graph window has all the expected components, as illustrated in the
following figure:
- Verify if the project
graph window has all the expected components, as illustrated in the
following figure:
- For WBZ351
- Verify if the project
graph window has all the expected components, as illustrated in the
following figure:
Figure 3-61. Project Graph
- Verify if the project
graph window has all the expected components, as illustrated in the
following figure:
- Change BLE Stack Component
configuration as illustrated in the following figure.
Figure 3-62. BLE Stack Figure 3-63. BLE Stack
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