Dynamic multiprotocol examples

This information applies to the following SoCs: nRF52833 and nRF52840.

This information applies to the following SoftDevice: S140

In the dynamic multiprotocol method, radio hardware is time-sliced between all protocols. This solution allows for maintaining established connections in a few protocols at the same time. For more information about dynamic multiprotocol support, see Dynamic multiprotocol.

Warning

There is an issue in the nRF5 SDK for Thread and Zigbee v4.1.0 that causes higher-than-usual sleep power consumption for all multiprotocol examples when using nRF52840. See workaround on DevZone.

The following examples are available:

• BLE UART and Thread MTD CoAP Client Examples
• BLE Proximity and Thread CoAP Server Example
• BLE Eddystone and Thread CoAP Server Example
• BLE HRS and Thread CoAP Server with FreeRTOS Example
• BLE and Thread Template Example
• BLE Scanner and Thread SED Example

You can also transform any BLE peripheral example available in nRF5 SDK v16.0.0 into a BLE-Thread dynamic multiprotocol example. See Adding dynamic multiprotocol Thread support to BLE examples.

Device support breakdown

Not all Thread dynamic multiprotocol examples support all nRF52840 and nRF52833 devices. See the following table for an overview.

Example	PCA10056 (nRF52840)	PCA10059 (nRF52840 dongle)	PCA10100 (nRF52833)	PCA10112 (nRF52840)
BLE UART and Thread MTD CoAP Client Examples	X		X
BLE Proximity and Thread CoAP Server Example	X
BLE Eddystone and Thread CoAP Server Example	X		X*
BLE HRS and Thread CoAP Server with FreeRTOS Example	X
BLE and Thread Template Example	X		X*
BLE Scanner and Thread SED Example	X		X

Note

• BLE Eddystone and Thread CoAP Server Example and BLE and Thread Template Example do not support the SES compiler.
• nRF21540 on PCA10112 is not supported by SoftDevice, and for this reason PCA10112 does not support multiprotocol examples.