Configuring ZBOSS traces in nRF Connect SDK

The ZBOSS Zigbee stack (ZBOSS stack) comes included in the nRF Connect SDK in a set of precompiled libraries, which can complicate the debugging process. To help with that, the ZBOSS stack can be configured to print trace logs that allow you to trace the stack behavior. This page describes how to enable and configure ZBOSS trace logs.

Trace logs are printed in binary form and require access to stack source files to be decoded into log messages. Enabling trace logs can help with the debugging process even if you cannot decode them (due to lack of access to stack source files). This is because of the information they can provide about the stack behavior whenever an issue is found or reproduced.

If any issues are found with the ZBOSS stack, trace logs can be enabled to collect this information while reproducing the issue. A ticket can then be created in DevZone with the log file attached for assistance with the debugging process, and for decoding trace log files.

Note

ZBOSS trace logs are meant to be used for debugging ZBOSS based applications. These libraries are not certified and should not be used for production firmware or end products.

Requirements

To collect and view the log files, you will need the following:

  • Software that allows for reading serial ports. For example, if you are using Windows you can use PuTTY.

  • Correct COM port.

    • For traces using the UART, the JLink COM port is used. The development kit is assigned to a COM port (Windows) or a ttyACM device (Linux), which is visible in the system’s Device Manager.

    • For traces using USB, a virtual COM port (a serial port emulated over USB) is used. You can set CONFIG_USB_DEVICE_PRODUCT to help identify the COM port in the system’s Device Manager.

  • An additional USB cable if trace logs through USB are enabled (see Trace logs using native USB).

Switch to ZBOSS libraries with compiled-in trace logs

Set the Kconfig option CONFIG_ZIGBEE_ENABLE_TRACES to switch to ZBOSS libraries with compiled-in trace logs.

The ZBOSS stack comes in a precompiled form and trace logs are not compiled-in by default. An additional set of ZBOSS libraries are available in nrfxlib, which does have trace logs compiled-in.

Select which ZBOSS trace logs to print

Complete the following steps:

  1. Select from which subsystems you would like to receive logs by configuring the ZBOSS trace mask with the Kconfig option CONFIG_ZBOSS_TRACE_MASK. Trace masks can be created by adding up masks of subsystems to receive the trace logs from. For available subsystems, see nrfxlib/zboss/production/include/zb_trace.h.

  2. Select the level of logs you want to receive. Configure ZBOSS trace level by selecting one of the following levels:

If you do not want to receive trace logs, turn them off by setting the Kconfig option CONFIG_ZBOSS_TRACE_LOG_LEVEL_OFF.

Each of the following levels on the list also includes the previous one. See Stack logs to read more about trace logs.

Configure how to print ZBOSS trace logs

The ZBOSS OSIF serial abstract offers a few backends to choose from for printing ZBOSS trace logs. It is recommended to use the Zigbee serial logger, as it is the most efficient. To enable it, set the Kconfig option CONFIG_ZBOSS_TRACE_BINARY_LOGGING.

Optional: Increasing the size of the ring buffer

You can increase size of the ring buffer that temporarily stores the trace logs. To do this, use CONFIG_ZBOSS_TRACE_LOGGER_BUFFER_SIZE to assign a value for size of the buffer. This can prevent losing some of the logs in demanding scenarios such as high network traffic, multiple devices being configured or joined, and so on. See Zigbee serial logger for more information.

Trace logs using UART (default)

When CONFIG_ZBOSS_TRACE_BINARY_LOGGING is selected, trace logs are printed using the UART by default. To configure trace logs using the UART, complete the following steps:

  1. Set the CONFIG_ZBOSS_TRACE_UART_LOGGING Kconfig option.

  2. Optionally, configure which UART device you want to use with the Kconfig option CONFIG_ZBOSS_TRACE_LOGGER_DEVICE_NAME. The default UART_1 will be used if no other UART device is configured.

  3. Configure the UART device that you want to use to be connected to the onboard JLink instead of UART_0, by extending the DTS overlay file for the selected board with the following:

    &uart1 {
   tx-pin = <6>;
   rx-pin = <8>;
   rts-pin = <5>;
   cts-pin = <7>;
};

&uart0 {
   rx-pin = <33>;
   tx-pin = <34>;
   /delete-property/ rts-pin;
   /delete-property/ cts-pin;
};

    Note

    By connecting the UART device to the on-board JLink, trace logs can be read directly from the JLink COM port. As a consequence, the UART device used by the logger is disconnected and application logs cannot be accessed from the JLink COM port.

Optional: Increasing the UART throughput

You can also increase the UART throughput by changing the baudrate. Some of the trace logs will be dropped if the throughput is too low. By default, the UART baudrate is set to 115200. To increase the baudrate to 1000000, add the current-speed = <1000000>; property to the uart1 node in the DTS overlay file. This can be done like the following:

&uart1 {
   current-speed = <1000000>;
   tx-pin = <6>;
   rx-pin = <8>;
   rts-pin = <5>;
   cts-pin = <7>;
};

Trace logs using native USB

Trace logs can also be configured to use a native USB. This is useful because trace logs will be printed through a separate virtual COM port so that the console logs can still be read through the JLink COM port. For applications that relay on the UART connection through the JLink COM port, for example the Network co-processor (NCP) sample, trace logs can only be configured through USB (COM port emulated over USB). See the Zigbee NCP sample page for how to configure trace logs for USB in this case.

Note

Before proceeding with the following steps, first check if your Zigbee application already has USB enabled or is currently using a USB. If your application is already using a virtual COM port via native USB, use a device name that is different than the default CDC_ACM_0 to create new virtual COM port for printing trace logs. For example, if CDC_ACM_0 is already present, then create a virtual COM port named CDC_ACM_1, and so on. Additionally, the Kconfig option CONFIG_USB_COMPOSITE_DEVICE must be set if there are multiple virtual COM ports configured.

See the Zigbee NCP sample page as an example where one virtual COM port instance is already configured, and another must be created.

To configure trace logs using native USB, complete the following steps:

  1. Set the Kconfig option CONFIG_ZBOSS_TRACE_USB_CDC_LOGGING. This also enables the necessary USB Kconfig options.

  2. Configure which USB device to use with the Kconfig option CONFIG_ZBOSS_TRACE_LOGGER_DEVICE_NAME. This is optional, as the default CDC_ACM_0 will be used if no other USB device is configured.

  3. Create a virtual COM port that will be used for printing ZBOSS trace logs by extending the DTS overlay file for the selected board with the following:

    &zephyr_udc0 {
   cdc_acm_uart0: cdc_acm_uart0 {
      compatible = "zephyr,cdc-acm-uart";
      label = "CDC_ACM_0";
   };
};

    Note

    For the ZBOSS trace logs to be printed correctly through the USB, it is recommended to avoid using the USB autosuspend.