Zigbee Task halts on Leave Request

[sjf]

Hi,

We have been working with an end device based on nRF52840 with nRF5_SDK_for_Thread_and_Zigbee_v4.0.0_dc7186b and FreeRtos

This device has some bindings already set to the coordinator.

When it receives a Leave Request from coordinator, the Zigbee Stack gets stucked on zb_address_reset() function. Because of that, the Zigbee task remains blocked for the rest of the time.

Which should be the reason to halt at this point and how this could be avoided?

Regards,

Santiago

[Marte Myrvold]

Hi Santiago,

I just got a response from the Zigbee team. They were able to reproduce the problem, with both nRF5 SDK T&Z and with NCS, so it seems the problem is with the Zigbee stack (ZBOSS). The problem has been reported to DSR in ZBOSS Open Initiative (ZOI).

Best regards,

Marte

[sjf]

Hi Marte,

Thanks for your response. Is there any workaround?

Regards,

[Marte Myrvold]

Hi Santiago,

I don't know of any workaround yet, but our Zigbee team is looking into it to try and see if there's an obvious fix besides waiting for a response from DSR. However, I can't give an estimate on when this will be done, as it might take some time. I'll let you know as soon as I know more.

Best regards,

Marte

[Marte Myrvold]

Hi Santiago,

The Zigbee team is still waiting for a response from DSR, but they have proposed a workaround in the meantime:

Place the following lines inside the zboss_signal_handler switch-case structure:

       case ZB_ZDO_SIGNAL_SKIP_STARTUP:
               /* WORKAROUND for the ZOI-297: unlock the device's address on ZEDs to fix assertion upon leave request. */
               {
                       zb_address_ieee_ref_t addr_ref;
                       /* Unlock our address: it will be locked at rejoin confirm */
                       if (zb_address_by_short(ZB_PIBCACHE_NETWORK_ADDRESS(), ZB_FALSE, ZB_FALSE, &addr_ref) == RET_OK) {
                               zb_address_unlock(addr_ref);
                       }
               }

The Zigbee team were able to do many leave requests and resets in a row without failure with this workaround.

Please let me know whether this workaround solves your issue or not. I'll let you know if we hear anything from DSR.

Best regards,

Marte

[sjf]

Hi Marte, we're still facing this issue even with the new code you provided.

Please find attached an image with the Call Stack content.

Device (router role ) was removed from the network.

When it starts, it automatically joins to the network and periodically prints:

app: Parent is unreachable
 app: UNKNOWN SIGNAL = 17

When we press a button to order it to leave network, it sends the leave request:

      /* Set dst_addr == local address for local leave */
      p_req_param->dst_addr = ZB_PIBCACHE_NETWORK_ADDRESS();
      p_req_param->rejoin   = ZB_FALSE;
      UNUSED_RETURN_VALUE(zdo_mgmt_leave_req(bufid, zbm_send_leave_nwk_cb));

And the callback is triggered successfully. But then the funcntion zb_nrf52_abort() is called due to an assert....

Regards,