Zigbee Task halts on Leave Request

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Tue, 02 Nov 2021 09:45:02 GMT

Hi Santiago,

This will be fixed in an upcoming release of nRF5 SDK for Thread and Zigbee, which will include multiple bugfixes for ZBOSS.

Best regards,

Marte

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Tue, 05 Oct 2021 12:23:18 GMT

Hi Santiago,

Could you try the workaround suggested in this comment?

Best regards,

Marte

RE: Zigbee Task halts on Leave Request

sjf — Sat, 11 Sep 2021 12:50:45 GMT

Hi Marte,

We create some bindings from this device to coordinator at different clusters the first time. Once we remotely request to leave the network, this issue happens every time.

Our firmware is based on FreeRTOS and SoftDevice.

Regards

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Fri, 10 Sep 2021 07:48:17 GMT

Hi Santiago,

The assert is caused by an attempt to delete an entry with short_address for an address that has not been fully unlocked.

How difficult is this to reproduce? Can you reproduce it with an example without FreeRTOS and SoftDevice?

Could you also provide or describe a scenario for which the device has failed? Please also provide a sniffer log of this happening.

Best regards,

Marte

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Wed, 08 Sep 2021 09:07:53 GMT

Hi Santiago,

I have forwarded this to our developers, and I will come back to you when I hear from them.

Best regards,

Marte

RE: Zigbee Task halts on Leave Request

sjf — Mon, 06 Sep 2021 15:08:27 GMT

Hi Marte, we are still facing this issue both on end devices and routers.

Please find attached an image about an assert error on zb_address_reset() function for end devices.

Regards,

devzone.nordicsemi.com/.../network_5F00_leave_5F00_issue.zip

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Wed, 21 Apr 2021 09:02:30 GMT

Hi,

The workaround provided was for end-devices. In order to prevent compiling-in the workaround for non-end-devices you can use something like this:

case ZB_ZDO_SIGNAL_SKIP_STARTUP:
#ifdef ZB_ED_ROLE
            /* 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);
            }
#endif /* defined ZB_ED_ROLE */

The Zigbee team wants to know if there are any other issues with the router device when the workaround is not compiled in?

Best regards,

Marte

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Fri, 16 Apr 2021 14:06:10 GMT

Hi,

Unfortunately, I have not heard back from the Zigbee team yet. I will ping them to see if there are any updates.

Best regards,

Marte

RE: Zigbee Task halts on Leave Request

sjf — Fri, 09 Apr 2021 13:10:15 GMT

Hi, is there any update on this?

Regards

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Wed, 31 Mar 2021 13:36:24 GMT

Hi Santiago,

I will ask our Zigbee team about this. Due to Easter we are short staffed, and I will not get a response from them until next week.

Best regards,

Marte

RE: Zigbee Task halts on Leave Request

sjf — Mon, 29 Mar 2021 15:31:32 GMT

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,

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Fri, 13 Nov 2020 12:30:36 GMT

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

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Mon, 09 Nov 2020 13:42:48 GMT

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

RE: Zigbee Task halts on Leave Request

sjf — Mon, 09 Nov 2020 13:09:24 GMT

Hi Marte,

Thanks for your response. Is there any workaround?

Regards,

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Mon, 09 Nov 2020 07:28:18 GMT

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

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Thu, 05 Nov 2020 10:03:35 GMT

H Santiago,

The end device sends a leave command in your sniffer log, so it does leave, and therefore ZB_ZDO_SIGNAL_LEAVE is called. This signal is generated when the device itself has left the network by sending leave command. ZB_ZDO_SIGNAL_LEAVE is called even if the leave request is from the coordinator. You can test this yourself by using the CLI Agent example and issuing the 'zdo mgmt_leave' command, and you will see that "Network left" is printed.

Can you please debug your code using breakpoints so that you can see what's happening in your program? You can put the breakpoints at the if statements in the code above, as well as at App_Zigbee_Status() and Zigbee_Fsm().

What is zigbee.state, and what does the functions App_Zigbee_Status() and Zigbee_Fsm() do?

Best regards,

Marte

RE: Zigbee Task halts on Leave Request

sjf — Wed, 04 Nov 2020 17:31:55 GMT

ZB_ZDO_SIGNAL_LEAVE is never called. In fact, the description of this signal says that is called when the device leaves the network by sending leave command.

Find code below:

case ZB_ZDO_SIGNAL_LEAVE:
        /* This signal is generated when the device itself has left the network by sending leave command.
          *
          * Note: this signal will be generated if the device tries to join legacy Zigbee network and the TCLK
          *       exchange cannot be completed. In such situation, the ZB_BDB_NETWORK_STEERING signal will be generated
          *       afterwards, so this case may be left unimplemented.
          */
        if (status == RET_OK)
        {
          zb_zdo_signal_leave_params_t * p_leave_params = ZB_ZDO_SIGNAL_GET_PARAMS(p_sg_p, zb_zdo_signal_leave_params_t);
          ZIGBEE_LOG_INFO("Network left (leave type: %d)", p_leave_params->leave_type);

          if(ZIGBEE_STATE_JOINING != zigbee.state)
          {
            App_Zigbee_Status(ZIGBEE_STATUS_DISCONNECTED);
            Zigbee_Fsm(ZIGBEE_STATE_DISCONNECTED);
          }
        }
        else
        {
          ZIGBEE_LOG_ERROR("Unable to leave network (status: %d)", status);
        }
 

      break;

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Wed, 04 Nov 2020 15:54:03 GMT

Hi Santiago,

What does your code look like? After ZB_ZDO_SIGNAL_LEAVE is called.

Best regards,

Marte

RE: Zigbee Task halts on Leave Request

sjf — Wed, 04 Nov 2020 15:09:38 GMT

Hi Marte,

There is no signal triggered. It just halts

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Wed, 04 Nov 2020 14:29:23 GMT

Hi Santiago,

I have forwarded your problem and will get back to you as soon as I get a response.

In the meantime, what does it look like in your signal handler when the leave signal is received?

Best regards,

Marte

RE: Zigbee Task halts on Leave Request

sjf — Wed, 04 Nov 2020 11:43:15 GMT

Hi Marte,

It is invoked internally by the Zigbee Task. We do not call it at all.

Consider that there are some bindings set on this device as extra information.

Please, we need to get a response as soon as possible from you/Zigbee team.

Regards,

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Wed, 04 Nov 2020 07:40:56 GMT

Hi Santiago,

Where is zb_address_reset() called, and what is it used for in your project?

Best regards,

Marte

RE: Zigbee Task halts on Leave Request

sjf — Fri, 30 Oct 2020 15:11:54 GMT

Hi Marte,

Find IDE screenshot attached.

Regards

RE: Zigbee Task halts on Leave Request

Marte Myrvold — Wed, 28 Oct 2020 13:36:07 GMT

Hi,

How are you debugging the example? How did you figure out it gets stuck at zb_address_reset()?

Could you please show me your callstack?

Best regards,

Marte

RE: Zigbee Task halts on Leave Request

sjf — Wed, 28 Oct 2020 12:35:24 GMT

Also, when leave is initiated from the device that has to leave the network there is no issue. It just works fine