Bluetooth: Peripheral Heart Rate Monitor with Coded PHY

The Peripheral Heart Rate Monitor with Coded PHY offers similar functionality to the Heart-rate Monitor (Peripheral) sample from Zephyr. However, this sample supports LE Coded PHY.

Requirements

The sample supports the following development kits:

Hardware platforms

PCA

Board name

Board target

nRF54L15 DK

PCA10156

nrf54l15dk

nrf54l15dk/nrf54l15/cpuapp

nRF54H20 DK

PCA10175

nrf54h20dk

nrf54h20dk/nrf54h20/cpuapp

nRF5340 DK

PCA10095

nrf5340dk

nrf5340dk/nrf5340/cpuapp

nRF52840 DK

PCA10056

nrf52840dk

nrf52840dk/nrf52840

Note

If you use nRF5340 DK, the additional configuration of the network core will be taken from the child_image directory. For more details, see Image-specific variables.

The sample also requires a device running a Heart Rate Server with LE Coded PHY support to connect to. For example, another development kit running the Bluetooth: Central Heart Rate Monitor with Coded PHY sample.

Overview

The sample demonstrates a basic Bluetooth® Low Energy Peripheral role functionality that exposes the Heart Rate GATT Service with LE Coded PHY support, which is not available in Zephyr Bluetooth LE Controller (See Controller for more information). Once it connects to a Central device, it generates dummy heart rate values. You can use it together with the Bluetooth: Central Heart Rate Monitor with Coded PHY sample.

User interface

The user interface of the sample depends on the hardware platform you are using.

LED 1:

Blinks, toggling on/off every second, when the main loop is running and the device is advertising.

LED 2:

Lit when the development kit is connected.

Building and running

This sample can be found under samples/bluetooth/peripheral_hr_coded 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.

Testing

After programming the sample to your development kit, you can test it by connecting to another development kit that runs the Bluetooth: Central Heart Rate Monitor with Coded PHY.

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

  2. Reset the kit.

  3. Program the other kit with the Bluetooth: Central Heart Rate Monitor with Coded PHY sample.

  4. Wait until the Coded advertiser is detected by the Central. In the terminal window, check for information similar to the following:

    Connected: xx.xx.xx.xx.xx.xx (random), tx_phy 4, rx_phy 4

  5. In the terminal window, observe that notifications are enabled:

    <inf> hrs: HRS notifications enabled

Dependencies

This sample uses the following nRF Connect SDK library:

This sample uses the following Zephyr libraries:

  • include/zephyr/types.h

  • include/errno.h

  • include/zephyr.h

  • include/sys/printk.h

  • include/sys/byteorder.h

  • Kernel Services:

    • include/kernel.h

  • API:

  • include/bluetooth/bluetooth.h

  • include/bluetooth/conn.h

  • include/bluetooth/uuid.h

  • include/bluetooth/gatt.h

  • include/bluetooth/services/bas.h

  • include/bluetooth/services/hrs.h