3.13 Bluetooth® Low Energy Multirole Multilink Transparent UART
This section helps users in creating a Multirole Multilink device and sending/receiving characters between connected BLE devices over Microchip proprietary Transparent UART Profile. The Multilink central enables users to connect multiple peripheral devices to a central device. The Multilink central device acts as peripheral device and is connected to an another central device which is a smart phone (android or ios MBD application). The central is MBD application and peripheral devices in this tutorial are Curiosity boards.
Users can either choose to just 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.
Recommended Reading
- BLE Software Specification
- Getting Started with WME Bluetooth Low Energy Applications
Hardware Requirement
Tool | Qty |
---|---|
Curiosity Board | 3 (min) |
Micro USB cable | 3 |
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.
Smartphone App
- Light Blue
Programming the precompiled hex file or Application Example
Programming the .hex
File using MPLAB X IPE
- Precompiled
.hex
file is located in “<Harmony Content Path>\wireless_apps_ble>\apps\multirole\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
“
mr_ml_trp_uart_xxxx.X
” where xxxx refer to device (for example: WBZ451, project file:mr_ml_trp_uart_wbz451.X
) located in “<Harmony Content Path>\wireless_apps_ble>\apps\multirole\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 MPLAB Code Configurator from
the toolbar as illustrated below. The project graph will open with the default
components.
Figure 3-146. 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-147. 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. Additionally Change BLE
Config App Service component configuration Number of links to 3 as
illustrated in the following figure
Figure 3-148. BLE Config App Service - Add and verify Transparent App
Service Component setting as illustrated in the following figure
Figure 3-149. Transparent App Service - 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-150. Project Graph
- 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-151. Project Graph - Verify FreeRTOS Component
setting for Tick Mode and modify as illustrated in the following figure
Figure 3-152. FreeRTOS Configuration - Verify SERCOM Component
setting for Enable Run in Standby and modify as illustrated in the following
figure
Figure 3-153. SERCOM Configuration
- 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-154. BLE Stack Configuration Figure 3-155. BLE Stack Configuration Figure 3-156. BLE Stack Configuration
Users can exercise various other BLE functionalities by using BLE Stack API
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_trspc_callbacks.c | All the event functions related to trspc event
handles that user can use or modify. |
app_trsps_callbacks.c | All the event functions related to trsps event
handles 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