Zboss "crash" in zb_schedule_alarm()

[0xGael]

Hello,

I'm using the zboss stack to implement a zigbee end device on nrf5340.

My device is able to connect to a zigbee network and to notify sensor events on zigbee but after a random time a crash happens on the stack side :

I'm quite stuck to debug this issue.

it seems that the stack stops because of an error executing zb_schedule_alarm() but I have no more clues.

How do you debug such issue ?

Environment :

* nRF5340

* NRF_SDK_VERSION=v1.0.1
  NRF_SDK_NAME=ncs-zigbee-r22
  NRF_MAIN_SDK_VERSION=v2.9.0

Regards,

Gaël

[Sigurd]

Hi!

Are you able to get some logs of the crash? 

See this page for log configuration: https://docs.nordicsemi.com/bundle/addon-zigbee-r22-latest/page/configuring.html#default_zigbee_application_logging

[0xGael]

Hello Sigurd,

this was my next step, to put in place the zboss log.

What I don't understand is how we use them. I should record a file with the binary data send over uart/USB CDC and send you the file, right ?

Considering the issue happens in zb_zdo_pim_start_turbo_poll_packets and zb_nwk_ed_timeout_req_frame_confirm(), which mask shall I enable ? 0x00000040 (Zigbee Device Object) and 0x00000008 (Network layer) ?

I get back to you when I have some logs

[0xGael]

Hello Sigurd,

sorry for the delay I had other tasks to do.

I figured out to make the trace work with this configuration :

CONFIG_ZIGBEE_ENABLE_TRACES=y

CONFIG_ZBOSS_TRACE_USB_CDC_LOGGING=y

CONFIG_ZBOSS_TRACE_BINARY_LOGGING=y

CONFIG_ZBOSS_TRACE_LOG_LEVEL_INF=y

CONFIG_ZBOSS_TRACE_MASK=0x00000C5F

But I didn't success to log HEXDUMP traces

Here is my log file for the following crash :

zboss_trace_20251202_164336.bin

[0xGael]

Hello Sigurd have you been able to decode the trace ?

[0xGael]

Hello,

any news ? Do you need other informations ?