4.1.2.5 BLE Connection

Introduction

This document will help users enable advertisements and connection on WBZ351 Curiosity board using MPLAB Code Configurator(MCC) BLE Advertisement is Broadcasting of small packets to peer devices. In BLE, a peripheral device always starts with advertisements. Advertisement packets enable a central or observer to discover and connect to a peripheral.

Users can choose to just run the precompiled Application Example hex file on the WBZ351 Curiosity Board and experience the demo or can go through the steps involved in developing this Application from scratch

It is recommend to follow the examples in order, by learning the basic concepts first and then progressing to the more advanced topics.

Recommended Reading

1. BLE Software Specification

2. FreeRtos BLE App Initialize

3. BLE Legacy Advertisements

Hardware Requirement

SDK Setup

1. Getting started with Software Development

Software Requirement

1. TeraTerm

Smartphone App

1. Light Blue

Programming the precompiled hex file or Application Example

Programming the hex file using MPLABX IPE

1. Precompiled Hex file is located in "<Harmony Content Path>\wireless_apps_pic32cxbz3_wbz35\apps\ble\building_blocks\peripheral\peripheral_conn\hex" folder

2. For more details on the steps, go to Programming A Device .

   Note: Ensure to choose the correct Device and Tool information

Programming the Application using MPLABX IDE

1. Follow steps mentioned in of Running a Precompiled Example document

2. Open and program the Application Example "peripheral_conn.x" located in "<Harmony Content Path>\wireless_apps_pic32cxbz3_wbz35\apps\ble\building_blocks\peripheral\peripheral_conn\firmware" using MPLABX IDE

For more details on how to find the Harmony Content Path, refer to hInstalling a Mcc Pluggin

Demo Description

This Application Example enables users to transmit Connectable and Scannable Undirected BLE Advertisements.On reset demo will print "Advertising" on a terminal emulator like TeraTerm, this denotes start of advertisements. Central device scanning these advertisements can issue connection request and get connected with this device. Upon connection demo prints "Connected" message on terminal window

Testing

Connect the WBZ351 Curiosity board to PC, program the precompiled hex file or application example as mentioned. Open TeraTerm @ (Speed: 115200, Data: 8-bit, Parity: none, stop bits: 1 bit, Flow control: none). Reset the board. Upon reset, "Advertising" message is displayed on the TeraTerm. User can open the LightBlue App on Smartphone to scan for Advertisements. Device with device name "Microchip" will appear.

Select the device to get connected, after successful connection user can view the advertisement data.

Terminal output

Users can use another WBZ351 Curiosity Board configured as BLE Connection(central) instead of using a Smartphone App

Developing the Application from Scratch Using the MPLAB Code Configurator

1. Create a new MCC Harmony Project. For more details, refer to 3.4 Creating a New MCC Harmony Project.

2. Import component configuration: This step helps users setup the basic components and configuration required to develop this application. The imported file is of format .mc3 and is located in the path "<Harmony Content Path>\wireless_apps_pic32cxbz3_wbz35\apps\ble\building_blocks\peripheral\peripheral_conn\firmware\peripheral_conn.X". For more details on how to import the component configuration, refer to Import existing App Example Configuration .

   Note: Import and Export functionality of Harmony component configuration will help users to start from a known working setup of MCC configuration

3. Accept Dependencies or satisfiers, select Yes

4. Verify if the Project Graph window has all the expected configuration

VerifyIing Advertisement and Connection Configuration

1. Select BLE_Stack component in project graph

   

Generating a Code

For more details on code generation, refer to 13.2 MPLAB Code Configurator(MCC) Code Generation.

Files and Routines Automatically generated by the MCC

After generating the program source from MCC interface by clicking Generate Code, the BLE configuration can be found in the following project directories

The OSAL, RF System, BLE System initialization routine executed during program initialization can be found in the project files. This initialization routine is automatically generated by the MCC

The BLE stack initialization routine excuted during Application Initialization can be found in project files. This intitialization routine is automatically generated by the MCC. This call initializes and configures the GAP, GATT, SMP, L2CAP and BLE middleware layers.

Autogenerated, advertisement data format

Header Files

• ble_gap.h: The header file contains BLE GAP functions and is automatically included in the app.c file.

Function Calls

MCC generates and adds the code to initialize the BLE Stack GAP, GATT, L2CAP and SMP in APP_BleStackInit() function

• APP_BleStackInit() is the API that will be called inside the Applications Initial State -- APP_STATE_INIT in app.c

User Application Development

Include

• User action is required as mentioned User Action

• definitions.h in all the files where UART will be used to print debug information

Set PUBLIC Device Address

• BLE_GAP_SetDeviceAddr(&devAddr);

    BLE_GAP_Addr_T devAddr;
    devAddr.addrType = BLE_GAP_ADDR_TYPE_PUBLIC;
    devAddr.addr[0] = 0xA1;
    devAddr.addr[1] = 0xA2;
    devAddr.addr[2] = 0xA3;
    devAddr.addr[3] = 0xA4;
    devAddr.addr[4] = 0xA5;
    devAddr.addr[5] = 0xA6;

    // Configure device address
    BLE_GAP_SetDeviceAddr(&devAddr);

Starting Advertisement

• BLE_GAP_SetAdvEnable(0x01, 0);

  

Connected & Disconnected Events

• All the possible GAP, GATT, SMP and L2CAP Event handlers are available in file app_ble_handler.c, users can implement application code to denote Connection State here.

  

Users can exercise various other BLE Advertisement functionalities by using BLE Stack API

Where to go from here

• 4.1.2.6 BLE Transparent UART with External Flash OTA