This information applies to the nRF52840 SoC only.
The following examples demonstrate different features of a Zigbee stack running on the nRF52840 SoC.
You can also transform any BLE peripheral example available in nRF5 SDK v15.0.0 into a BLE-Zigbee dynamic multiprotocol example. See Adding dynamic multiprotocol Zigbee support to BLE examples.
- Note
- Zigbee examples do not use the SoftDevice, with the exception of multiprotocol examples.
-
All Zigbee examples use the following parameters:
Radio Channel: 16
Network Master Key (Touchlink examples): ab:cd:ef:01:23:45:67:89:00:00:00:00:00:00:00:00
In an end product, constant master key must NOT be used. Use the commissioning procedure to obtain network credentials.
Testing
You can find the source code and the project file of the examples in the following folder: <InstallFolder>\examples\zigbee\experimental
Use the following steps to test the Zigbee examples:
- Build the example according to the instructions in Building examples.
- Use nrfjprog (from nRF5x Command Line Tools v9.2.0 or newer) to program the .hex file that was created in the
_build
folder to the board.
- Use an UART viewer to see the log messages produced by the application. All Zigbee examples uses 1 000 000 baud rate.
Zigbee BSP LED reference
All Zigbee examples use the same LED assignments:
- LED 1 and LED 2 (BSP_LED_0 and BSP_LED_1) - are used only inside multiprotocol examples in order to indicate BLE status:
- Blinking - BLE advertising
- Continuously on - Connected over BLE
- LED 3 (BSP_LED_2) - network connection state:
- Disabled – Node is disconnected or is currently connecting to a Zigbee mesh network.
- Solid – Node is connected to a Zigbee mesh network.
- LED 4 (BSP_LED_3) – user application LED.