SDK UART coexistence example

You can test this example on the following devices: nRF52840, nRF52833, and nRF52832.

This example is not compatible with the nRF52810, nRF52820, and nRF52840 dongle devices.

This example demonstrates how nRF5 SDK for Mesh and nRF5 SDK examples can be used together at the same time. It is built around two examples and has two parts:

• The Bluetooth mesh part of this example implements the light switch client example from the nRF5 SDK for Mesh.
• The BLE part of the example implements the UART/Serial Port Emulation over BLE example from the nRF5 SDK, except for the following changes:
  • The BSP events SLEEP, DISCONNECT and WHITELIST_OFF are ignored. This makes the board buttons only control the Bluetooth mesh part of the application.
  • The advertising interval is increased to allow more time for the Bluetooth mesh stack.
  • The light switch servers can be controlled over BLE UART by sending the light switch client button number to be simulated.
  • The example is not configured to enter the system-off mode, like in its nRF5 SDK version.

As the result of running this example, you'll be able to use the Bluetooth mesh network in which this example can replace the light switch client example.

Before you start testing this coexistence example, see the following pages:

• Integrating Bluetooth mesh into nRF5 SDK examples
• Light switch example and Light switch client details and Bluetooth mesh APIs

---

Hardware requirements

You need the same amount of development kits as for testing the light switch client example.

Additionally, you need one development kit for the static provisioner example. For details, see software requirements.

See Compatibility for information about the compatible development kits.

Note

While this example is compatible with nRF52840 and nRF52833 development kits, the nRF5 SDK for Mesh only provides SES files for nRF52832.

---

Software requirements

This example does not support PB-GATT for provisioning. For this purpose, use the static provisioner example: <InstallFolder>/examples/provisioner. See the provisioner example page for more information.

---

Setup

You can find the source code of the SDK UART coexistence example in the following nRF5 SDK for Mesh folder: <InstallFolder>/examples/sdk_coexist/ble_app_uart_coexist

The source code of the light switch client example is located at the following path: <InstallFolder>/examples/light_switch/client

---

Testing the example

Complete the following steps to program the SDK UART coexistence example and the light switch example devices:

1. Copy the ble_app_uart_coexist folder into the examples/ble_peripheral folder at your nRF5 SDK installation path.
2. Open the Segger Embedded Studio project at ble_app_uart_coexist/pca10040/s132/ses/ble_app_uart_pca10040_s132.emProject.
3. Add MESH_ROOT to your Segger Embedded Studio global macro list:
   1. From the SES menu bar, click Tools > Options....
   2. In the left column, click Building.
   3. In right column, double click Global macros.
   4. Add your Bluetooth mesh root directory in a new line: MESH_ROOT=<path to your Bluetooth mesh SDK installation>.
4. Program the light switch example devices as described in the Light switch example, including the servers and the static provisioner, with the following exceptions:
   • Replace the light switch client with examples/ble_peripheral/ble_app_proximity_coexist/pca10040/s132/ses/Output/Release/Exe/ble_app_proximity_pca10040_s132.hex.
   • Do not use the nRF Mesh mobile application for provisioning. Only use the static provisioner.

You can now run the two coexisting examples in parallel or in sequence:

• Run the light switch client example as described in light switch example documentation.
• Run the UART/Serial Port Emulation over BLE example as described in the nRF5 SDK documentation.
  • Write the hexadecimal ASCII codes equivalent to one of the digits (1, 2, 3, or 4) in the UART RX characteristic to simulate a button press.