This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Router stops sending Link Status messages

Other Parts Discussed in Thread: Z-STACK

 

Hi,

I'm using ZStack-CC2530-2.5.0 running as Zigbee PRO with security enabled.

Network consists of coordinator and 10 routers. All devices are mains powered and their receivers are always on.

Upon successfully joining network, each router sends ZB  "device announce" and broadcasts 2 messages (used for application level device announce).

The problem is that in some moment some of the routers stops sending "Link Status" messages and is unable to receive and rebroadcast MTORR messages (ZDO_ConcentratorIndicationCB() routine is never called although coordinator is sending MTORR messages and device is within range). Coordinator can send them uni-cast messages and the reply is successfully returned but MTORR and Link Status fails.

Regular functionality is restored only after router restarts.

 

Does anybody have any idea what could be a problem?

 

Thanks in advance!

 

 

  • It sounds like you have added code that causes a memory leak - your problem is not repeatable using the sample applications out-of-the-box. Please review the code that you've added and make sure there is a matching free (osal_mem_free or osal_msg_free) for all of the allocations that you've added.

  • Hi Dejan,

       I want to use  ZStack-CC2530-2.5.0 with  security enabled. I set zgPreConfigkeys equal to TURE , and set SECURE  to 1.

       Network consists of coordinator and 1 routers , but the coordinator  can't receive the data sent by the router. The router has joined the network.

      Is there any other place in the z-stack  need to be changed if I want to enable security?

      Thank you.

  • Hi Harry,

    Thank you for the quick response.

    I agree with You that this looks like some memory leak. Unfortunately I did not manage to locate the critical space. The strange thing is that this occurs in moments of heavy broadcast traffic and right after device rebroadcasts "DeviceAnnce" message, which is sent from new joined device.

    I will review code again.

     

    Thanks,

    Dejan.