Bluetooth: Throughput

The Bluetooth® Throughput sample uses the GATT Throughput Service to measure Bluetooth Low Energy throughput performance. You can use it to determine the maximum throughput, or to experiment with different connection parameters and check their impact on the throughput.

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/ns nrf5340dk/nrf5340/cpuapp

nRF52 DK

PCA10040

nrf52dk

nrf52dk/nrf52832

nRF52840 DK

PCA10056

nrf52840dk

nrf52840dk/nrf52840

When built for a board target with the */ns variant, the sample is configured to compile and run as a non-secure application with Cortex-M Security Extensions enabled. Therefore, it automatically includes Trusted Firmware-M that prepares the required peripherals and secure services to be available for the application.

You can use any two of the development kits listed above and mix different development kits.

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 connection to a computer with a serial terminal that supports VT100/ANSI escape characters for each of the development kits.

Overview

The sample transmits data between two development kits, the tester and the peer, and measures the throughput performance. It uses the GATT Throughput Service for this. To run the tests, connect to the kit using the serial port and send shell commands. Zephyr’s Shell module is used to handle the commands.

The sample demonstrates the interaction of the following connection parameters:

ATT_MTU size

In Bluetooth Low Energy, the default Maximum Transmission Unit (MTU) is 23 bytes. When increasing this value, longer ATT payloads can be achieved, increasing the ATT throughput.

Note

To configure the ATT_MTU size, use menuconfig and compile and program the sample again.

Data length

In Bluetooth Low Energy, the default data length for a radio packet is 27 bytes. Data length extension allows to use larger radio packets, so that more data can be sent in one packet, increasing the throughput.

Connection interval

The connection interval defines how often the devices must listen to the radio. When increasing this value, more packets may be sent in one interval, but if a packet is lost, the wait until the retransmission is longer.

Physical layer (PHY) data rate

Starting with Bluetooth 5, the over-the-air data rate in Bluetooth Low Energy can exceed 1 Ms/s (mega symbols per second), which allows for faster transmission. In addition, you can use coded PHY (available on select nRF SoCs) for long-range transmission.

By default, the following connection parameter values are used:

Default parameter values

Parameter

Value

ATT_MTU size

498 bytes

Data length

251 bytes

Connection interval

320 units (400 ms)

PHY data rate

2 Ms/s

Changing connection parameter values

To experiment with different connection parameter values, reconfigure the values using the Shell interface before running a test.

You can adjust the following parameters:

  • PHY

  • LE Data Length

  • LE Connection interval

Note

In a Bluetooth Low Energy connection, the different devices negotiate the connection parameters that are used. If the configuration parameters for the devices differ, they agree on the lowest common denominator.

By default, the sample uses the fastest connection parameters. You can change them to different valid values without a need to program both kits again.

When you have set the LE Connection Interval to high values and need to change the PHY or the Data Length in the next test, the PHY Update or Data Length Update procedure can take several seconds.

User interface

Button 1:

Set the board into a central (tester) role.

Button 2:

Set the board into a peripheral (peer) role.

Building and running

This sample can be found under samples/bluetooth/throughput in the nRF Connect SDK folder structure.

When built as firmware image for a board target with the */ns variant, the sample has Cortex-M Security Extensions (CMSE) enabled and separates the firmware between Non-Secure Processing Environment (NSPE) and Secure Processing Environment (SPE). Because of this, it automatically includes the Trusted Firmware-M (TF-M). To read more about CMSE, see Processing environments.

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

Programming the nRF54H20 SoC can sometimes fail due to conflicts in the resource configuration. This can happen if, for example, an application programmed to the nRF54H20 SoC configured the UICRs for one or more cores in a way that is incompatible with the configuration required by the application you are trying to program on the SoC.

To fix this error and erase the UICR for the application core, run the following command:

nrfutil device recover --core Application

If your sample also uses the radio core, you must also erase the UICRs for the radio core. To erase the UICR for the radio core, run the following command:

nrfutil device recover --core Network

For more information on the command, run:

nrfutil device recover --help

You can then run west flash to program your application.

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 both kits, complete following steps to test it:

  1. Connect to both kits with a terminal emulator that supports VT100/ANSI escape characters (for example, nRF Connect Serial Terminal). See Testing and optimization for the required settings and steps.

  2. Reset both kits.

  3. Press Button 1 on the first development kit or type central in the terminal connected to the first kit to set it into the central (tester) role.

  4. Press Button 2 on the second development kit or type peripheral in the terminal connected to the second kit to set it into the peripheral (peer) role.

  5. Observe that the kits establish a connection. The tester outputs the following information:

    Type 'config' to change the configuration parameters.
You can use the Tab key to autocomplete your input.
Type 'run' when you are ready to run the test.

  6. Type config print in the terminal to print the current configuration. Type config in the terminal to configure the test parameters to your choice. Use the Tab key for auto-completion and to view the options available for a parameter.

  7. Type run in the terminal to start the test.

  8. Observe the output while the tester sends data to the peer. At the end of the test, both tester and peer display the results of the test.

  9. Repeat the test after changing the parameters. Observe how the throughput changes for different sets of parameters.

Sample output

The result should look similar to the following output.

For the tester:

*** Booting Zephyr OS build v3.0.99-ncs1  ***
Starting Bluetooth Throughput example
I: SoftDevice Controller build revision:
I: 33 78 2a 18 20 f5 61 61 |3x*. .aa
I: a6 8b 77 60 62 83 39 2a |..w`b.9*
I: 7c f1 14 e4             ||...


: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 51.10872 Build 1643454488
I: Identity: D7:D6:AD:A2:50:62 (random)
I: HCI: version 5.3 (0x0c) revision 0x1136, manufacturer 0x0059
I: LMP: version 5.3 (0x0c) subver 0x1136
Bluetooth initialized

Press button 1 or type "central" on the central board.
Press button 2 or type "peripheral" on the peripheral board.
uart:~$
Central. Starting scanning
Filters matched. Address: DC:D6:E5:EE:75:9A (random) connectable: 1
Connected as central
Conn. interval is 320 units
Service discovery completed
MTU exchange pending
MTU exchange successful

Type 'config' to change the configuration parameters.
You can use the Tab key to autocomplete your input.
Type 'run' when you are ready to run the test.
run

==== Starting throughput test ====
PHY update pending
LE PHY updated: TX PHY LE 2M, RX PHY LE 2M
LE Data length update pending
LE data len updated: TX (len: 251 time: 2120) RX (len: 251 time: 2120)
The test is in progress and will require around 20 seconds to complete.
Done
[local] sent 1242945 bytes (1213 KB) in 7292 ms at 1363 kbps
[peer] received 1242945 bytes (1213 KB) in 2511 GATT writes at 1415583 bps

Type 'config' to change the configuration parameters.
You can use the Tab key to autocomplete your input.
Type 'run' when you are ready to run the test.

For the peer:

*** Booting Zephyr OS build v3.0.99-ncs1  ***
Starting Bluetooth Throughput example
I: SoftDevice Controller build revision:
I: 33 78 2a 18 20 f5 61 61 |3x*. .aa
I: a6 8b 77 60 62 83 39 2a |..w`b.9*
I: 7c f1 14 e4             ||...


: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 51.10872 Build 1643454488
I: Identity: DC:D6:E5:EE:75:9A (random)
I: HCI: version 5.3 (0x0c) revision 0x1136, manufacturer 0x0059
I: LMP: version 5.3 (0x0c) subver 0x1136
Bluetooth initialized

Press button 1 or type "central" on the central board.
Press button 2 or type "peripheral" on the peripheral board.
uart:~$
Peripheral. Starting advertising
Connected as peripheral
Conn. interval is 320 units
LE PHY updated: TX PHY LE 2M, RX PHY LE 2M

=============================================================================
=============================================================================
=============================================================================
=============================================================================
=============================================================================
=============================================================================
=============================================================================
===========================================================
[local] received 1242945 bytes (1213 KB) in 2511 GATT writes at 1415583 bps

Dependencies

This sample uses the following nRF Connect SDK libraries:

In addition, it uses the following Zephyr libraries:

  • include/console.h

  • Kernel Services:

    • include/kernel.h

  • include/sys/printk.h

  • include/zephyr/types.h

  • API:

    • include/bluetooth/bluetooth.h

    • include/bluetooth/conn.h

    • include/bluetooth/gatt.h

    • include/bluetooth/hci.h

    • include/bluetooth/uuid.h

  • Shell:

    • include/shell/shell.h

The sample also uses the following secure firmware component:

References

For more information about the connection parameters that are used in this sample, see the following chapters in the Bluetooth Core Specification:

  • Vol 3, Part F, 3.2.8 Exchanging MTU Size

  • Vol 6, Part B, 5.1.1 Connection Update Procedure

  • Vol 6, Part B, 5.1.9 Data Length Update Procedure

  • Vol 6, Part B, 5.1.10 PHY Update Procedure