Bluetooth: Peripheral Bond Management Service (BMS)
The peripheral BMS sample demonstrates how to use the GATT Bond Management Service (BMS).
Requirements
The sample supports the following development kits:
Hardware platforms |
PCA |
Board name |
Board target |
|---|---|---|---|
PCA10156 |
|
||
PCA10175 |
|
||
PCA10095 |
|
||
PCA10040 |
|
||
PCA10056 |
|
The sample also requires a Bluetooth® Low Energy dongle and nRF Connect for Desktop.
Overview
When connected, the sample waits for the client’s requests to perform any bond-deleting operation.
It supports up to two simultaneous client connections.
User interface
- LED 1:
Blinks, toggling on/off every second, when the main loop is running and the device is advertising.
- LED 2:
Lit when connected.
- LED 0:
Blinks, toggling on/off every second, when the main loop is running and the device is advertising.
- LED 1:
Lit when connected.
Building and running
This sample can be found under samples/bluetooth/peripheral_bms in the nRF Connect SDK folder structure.
To build the sample, follow the instructions in Building an application for your preferred building environment. See also Programming an application for programming steps and Testing and optimization for general information about testing and debugging in the nRF Connect SDK.
Note
When building repository applications in the SDK repositories, building with sysbuild is enabled by default.
If you work with out-of-tree freestanding applications, you need to manually pass the --sysbuild parameter to every build command or configure west to always use it.
Note
When using the nRF54H20 DK Engineering B (from v0.8.0 to 0.8.2), you must build samples and applications using the board revision 0.8.0 with the <board>@<revision> syntax.
For example, nrf54h20dk@0.8.0/nrf54h20/cpuapp when building for the application core, or nrf54h20dk@0.8.0/nrf54h20/cpurad when building for the radio core.
Testing
After programming the sample to your development kit, complete the following steps to test it:
Connect to the kit that runs this sample with a terminal emulator (for example, nRF Connect Serial Terminal). See Testing and optimization for the required settings and steps.
Reset the kit.
Start nRF Connect for Desktop.
Open the Bluetooth Low Energy app and select the connected device that is used for communication.
Connect to the device from the app. The device is advertising as “Nordic_BMS”.
Bind with the device:
Click the Settings button for the device in the app.
Select Pair.
Select Keyboard and display in the IO capabilities setting.
Select Perform Bonding.
Click Pair.
Check the logs to verify that the connection security is updated.
Disconnect the device in nRF Connect.
Reconnect again and verify that the connection security is updated automatically.
Verify that the Feature Characteristic of the Bond Management Service displays
10 08 02. This means that the following features are supported:Deletion of the bonds for the current connection of the requesting device.
Deletion of all bonds on the Server with the Authorization Code.
Deletion of all bonds on the Server except the ones of the requesting device with the Authorization Code.
Write
03to the Bond Management Service Control Point Characteristic.03is the command to delete the current bond.Disconnect the device to trigger the bond deletion procedures.
Reconnect the devices and verify that the connection security is not updated.
Bond both devices again.
Write
06 41 42 43 44to the Bond Management Service Control Point Characteristic.06is the command to delete all bonds on the Server, followed by the authorization code “ABCD”.Disconnect the device to trigger the bond deletion procedures.
Reconnect the devices again and verify that the connection security is not updated.
Dependencies
This sample uses the following nRF Connect SDK libraries:
In addition, it uses the following Zephyr libraries:
include/zephyr/types.hlib/libc/minimal/include/errno.hinclude/sys/printk.hAPI:
include/bluetooth/bluetooth.hinclude/bluetooth/conn.hinclude/bluetooth/uuid.hinclude/bluetooth/gatt.h