4.2.6 BLE ANPC Application

Getting Started

Getting Started with Peripheral Building Blocks

Introduction

This section helps users to enable the BLE Alert Notification Profile Client (ANPC) on the WBZ351 Curiosity board using the MCC. In this application example, BLE ANPC functions in the Peripheral role and is paired with the BLE ANPS application which functions in the Central role.

Users can choose to run the precompiled application example .hex file on the WBZ351 Curiosity Board and experience the demo or 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 Reads

  1. BLE Software Specification
  2. FreeRTOS BLE App Initialize
  3. BLE ANPS Application

Hardware Requirement

Table 4-46. Hardware Requirement

Tool

Quantity

WBZ351 Curiosity Board

3

Micro USB cable

2

SDK Setup

Software Requirement

Smart phone App

  • None

Programming the Precompiled Hex File or Application Example

Programming the .hex File using MPLAB X IPE

  1. Import and program the precompiled .hex file located in "<Harmony Content Path>\wireless_apps_pic32cxbz3_wbz35\apps\ble\advanced_applications\ble_anpc_app\hex\ble_anpc_app.X.production.hex
  2. Import and program the precompiled .hex file located in "<Harmony Content Path>\wireless_apps_pic32cxbz3_wbz35\apps\ble\advanced_applications\ble_anps_app\hex\ble_anps_app.X.production.hex
  3. For more details on the steps, go to Programming A Device.
    Note: Users must choose the correct Device and Tool information

Programming the Application using MPLAB X IDE

  1. Follow steps mentioned in the Running a Precompiled Example.
  2. Open and program the application example "ble_anpc_app.X" located in: <Harmony Content Path>\wireless_apps_pic32cxbz3_wbz35\apps\ble\advanced_applications\ble_anpc_app\firmware\ble_anpc_app.X using MPLAB X IDE.
  3. Open and program the application example "ble_anps_app.X" located in: : <Harmony Content Path>\wireless_apps_pic32cxbz3_wbz35\apps\ble\advanced_applications\ble_anps_app\firmware\ble_anps_app.X using MPLAB X IDE.

For more details on finding the Harmony content path, refer to Installing the MCC Plugin

Demo Description

This application demonstrates on simulating an ANPC on the Curiosity board. The on-board User button, LED and UART are used as user interface during the demo.

  • Type of Pressing on User Button
    • Press: Press the button for less than 500 ms
    • Long press: Press the button for more than 500 ms
  • LED Behavior
    • All LEDs are OFF
    • Blue LED flashes one time every 3 seconds
    • Blue LED flashes two times every 3 seconds
    • Blue LED flashes two times every 1.5 seconds
  • UART Settings
    • Baud Rate/Speed: 115200
    • Parity: None
    • Data Bits: 8
    • Stop Bits: 1
    • Flow Control: None
    • Character Encoding: UTF-8

Testing

Experience the Demo using two WBZ351 Curiosity boards configured as Peripheral and Central device

This section assumes that a user has already programmed the “ble_anps_app.X” and “ble_anpc_app.X” application on two WBZ351 Curiosity boards.

  1. Board 1 – WBZ351 Curiosity Board Programmed with “ble_anpc_app.X”. Once programmed, the board’s LED will Flash once every 3 seconds and wait for a new connection within 60 seconds.
    1. Open TeraTerm and configure as mentioned below:
      Terminal Settings
      • Baud Rate/Speed – 115200 (as configured in SERCOM configuration)
      • Parity – None
      • Data Bits – 8
      • Stop Bits – 1
      • Flow Control – None
      Figure 4-214. Tera Term Settings

      For terminal setup configuration, go to Setup>Terminal and set the “New-line” of Receive to LF then click OK

      For Serial port setup and connection, go to Setup>Serial Port

      Note: For more details on setting the “Serial Port” and “Speed”, refer to COM Port Setup.
    2. Reset the board (on-board Reset), Upon Reset, “ANPC init” will be displayed in Tera Term.
      Figure 4-215. Tera Term
  2. Board 2 – WBZ351 Curiosity Board Programmed with “ble_anps_app.X”. Once programmed, the ANPS device will establish a new connection with the ANPC device.
  3. Once connection is established, the ANPC device stores the pairing data with the ANPS device and the ANPC device’s LED will Flash twice every 1.5 seconds. The following logs will also be displayed in Tera Term.
    Figure 4-216. Tera Term
  4. Press the user button on the ANPS device to send a new alert notification to the ANPC device and the following will be displayed in Tera Term.
    Figure 4-217. Tera Term
  5. Press the User button on the ANPS device again to send an unread alert notification to the ANPC device and the following will be displayed in Tera Term.
    Figure 4-218. Tera Term
  6. Press the User button on the ANPC device to disable the Client Characteristic Configuration Descriptor (CCCD) for new/unread alerts on the ANPS device and the following will be displayed in Tera Term.
    Figure 4-219. Tera Term
  7. Press the User button on the ANPS device to try to send a new/unread alert notification to the ANPC device. As evidenced in Tera Term, the new/unread alert notification is not received by the ANPC device.
  8. Unplug the USB cable of the ANPC device then plug it in again. The ANPC device will establish a reconnection with the ANPS device within 30 seconds and the ANPC device’s LED will again blink twice every 1.5 seconds.
  9. Now, unplug the USB cable of the ANPS device and program the ANPS precompiled .hex file or application example in another Curiosity board.
    Note: Since the ANPC device stored pairing data with the ANPS device, it will not yet attempt a connection with the ANPS Device 2.
  10. Long press the User button on the ANPC device so that it accepts a new connection within 60 seconds. Once connection is established with the ANPS Device 2, the ANPC device’s LED will blink twice every 1.5 seconds.

Developing this Application from Scratch using MCC

This section explains the steps required by a user to develop this application example from scratch using MCC

Note: It is recommended that new users of MCC to go through the overview.

  1. Create a new MPLAB MCC Harmony Project. For more details, refer to 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\advanced_applications\ble_anpc_app\firmware\ble_anpc_app.X\ble_anpc_app.mc3".
    For more details on importing the component configuration , refer to Importing 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. as illustrated in the following figure:
    Figure 4-220. Project Graph

Verify MCC Component Settings

  1. Select Alert Notification Profile component in project graph, to open component configuration and configure as illustrated in the following figure.
    Figure 4-221. Alert Notification Profile Configuration

  2. Select BLE Stack component in project graph, to open component configuration and configure as illustrated in the following figure.

    Figure 4-222. BLE Stack Configuration

Generating a Code

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

Files and Routines Automatically Generated by the MCC

After generating the program source from the MCC interface by clicking Generate Code, the BLE configuration source and header files can then be found in the following project directories.
Figure 4-223. Project File
The OSAL, RF System and BLE System initialization routine executed during program initialization can be found in the project file. This initialization routine is automatically generated by the MCC.
Figure 4-224. initialization.c
The BLE stack initialization routine executed during Application Initialization can be found in project files. This initialization routine is automatically generated by the MCC. This call initializes and configures the GAP, GATT, SMP, L2CAP and BLE middleware layers.
Figure 4-225. app_ble.c
Figure 4-226. Auto Generated Advertisement Data Format
Table 4-47. Source Files

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.c

Source Code for the BLE stack related component configurations, code related to function calls from app.c

app_ble_handler.c

All GAP, GATT, SMP and L2CAP Event handlers

src\app_ble\app_anpc_handler.c

Handle ANPC event from application level

src\config\default\ble\profile_ble\ ble_anpc\ble_anpc.c

Handle ANPC event from profile level

Note: app.c is autogenerated and has a state machine-based application code sample. Users can use this template to develop their own application.

Header Files

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

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 must be included in all the files where UART will be used to print debug information.
    Note: definitions.h is not specific to just UART peripheral, instead it must be included in all application source files where peripheral functionality will be exercised.

Configure the Advertisement:

  • APP_BleConfigBasic();
  • The below code snippet sets the Advertising Data and Scan Response Data of the ANPC application that will be used by the ANPS device to connect.
    Figure 4-227. APP_BleConfigBasic()

Starting Advertisement:

  • APP_EnableAdv(bPaired ? APP_ADV_TYPE_WITH_BOND_ADV: APP_ADV_TYPE_ADV)
    Figure 4-228. app.c

Connected and Disconnected Events:

  • All the possible GAP, GATT, SMP and L2CAP event handlers are available in app_ble_handler.c. Users can implement their own application code to denote Connection State here.
    Figure 4-229. app_ble_handler.c

Initialize ANPC:

  • ANPC functionality initialization is done in APP_BleStackInitAdvance()
    Figure 4-230. app_ble.c

Implement ANPC:

  • ANPC is implemented in ble_anpc.c and BLE_ANPC_BleEventHandler() will handle all ANPC events.
    Figure 4-231. ble_anpc.c

Firmware FSM (Finite State Machine)

This application firmware implements an ANPC on the Curiosity board.

  • APP_ANPC_STATE_IDLE: application remains in the Idle mode
  • APP_ANPC_STATE_ADV: application is waiting for a new connection within timeout_adv seconds.
  • APP_ANPC_STATE_WITH_BOND_ADV: application is waiting for a reconnection within timeout_with_bond_adv seconds.
  • APP_ANPC_STATE_CONN: application is prepared to send commands/receive notifications.
    Figure 4-232. Finite State Machine
Table 4-48. Time out Parameters

Variable

Value

Description

timeout_adv

60 seconds

The timeout of advertising without bond

timeout_with_bond_adv

30 seconds

The timeout of advertising with bond

Table 4-49. LED vs. State

Firmware State

LED behavior

APP_ANPC_STATE_IDLE

All LEDs are OFF

APP_ANPC_STATE_ADV

Blue LED flashes once every 3 seconds. (ON: 50 ms, OFF: 2950 ms)

APP_ANPC_STATE_WITH_BOND_ADV

Blue LED flashes twice every 3 seconds. (ON: 50 ms, OFF: 50 ms)

APP_ANPC_STATE_CONN

Blue LED flashes twice every 1.5 seconds (ON: 50 ms, OFF: 150 ms)