PIC32CX-BZ3

Introduction
1 Secure Boot and Signature Header Generation
2 Getting Started with WBZ351 Curiosity Board
This section covers evaluation board features and running the preprogrammed demo example
3 Getting Started with Software Development
This section gives a detailed information on the steps to install IDE, compiler, tool chain, BLE, Zigbee stacks and application examples on the PC.
4 Bluetooth Low Energy Applications
This section provides details on documentation describing the steps to test and develop the precompiled BLE application examples.
- 4.1 Building Block Examples
- 4.2 Advanced Applications
  - 4.2.1 BLE Sensor with Touch
  - 4.2.2 BLE Throughput
    This section describes in detail the example of PIC32CXBZ3/WBZ35 BLE Throughput evaluation using Microchip MBD App and the factors affecting the BLE throughput.
  - 4.2.3 BLE ANCS Application
  - 4.2.4 BLE Proximity Monitor
  - 4.2.5 BLE Proximity Reporter
  - 4.2.6 BLE ANPC Application
  - 4.2.7 BLE ANPS Application
  - 4.2.8 BLE HID over GATT Profile Service
- 4.3 HCI Application
- 4.4 BLE Virtual Sniffer
- 4.5 PIC32CXBZ3/WBZ35 Three-Wire PTA Coexistence Design
5 Getting Started with Zigbee Applications
6 Flashing hex from MPLAB DISCOVER using MPLAB IPE
This section provides a detailed procedure of how to download an already existing application hex file from MPLAB DISCOVER and flash the hex file into WBZ351 Curiosity Board using MPLAB IPE.
7 Adding Chip Peripherals
This section describes how to add analog/digital peripherals to the application
8 Low Power Design
This section explains in detail on how to enable the low power modes – Sleep/Standby or Deep Sleep/Backup modes in the design.
9 Firmware and OTA Updates
This section documents how to enable firmware updates in the design, whether it is serial or Over The Air (OTA)
10 Wireless System and Board Support Services
11 Application Timer Service
12 Support Documentation
This section has documentation that is generic and used as supporting document with the application example documentation.
13 Software API Guide
Microchip Information

Service Behaviors

Disconnection Behavior

When this service is instantiated in a device and the connection is lost for any reason, the device shall start alerting to the current link loss alert level.

If the current link loss alert level is “No Alert,” no alerting shall be done on this device.

If the current link loss alert level is “Mild Alert,” the device shall alert.

If the current link loss alert level is “High Alert,” the device shall alert in the strongest possible way.

The specific action that occurs in the device for the mild and high alerts is implementation specific.

For example, this could include flashing lights, making noises, moving, or other methods to alert the user.

This alert continues until one of the following conditions occurs:

an implementation-specific timeout
user interaction on this device
the physical link is reconnected