CC2530: Z stack NV RESTORE

You need to call "zgWriteStartupOptions(ZG_STARTUP_SET, ZCD_STARTOPT_DEFAULT_NETWORK_STATE);" and do reset.

NO actually In my application I don't want that Node should forget its parent coordinator ever

and it has behaved exactly like that but on one special scenario during Power on Reset I have noticed that node again started sending beacon request, ( Although once it is associated it should not send again beacon request )

But it happened only once

In the ZDO_init_Device Function < ZdApp.c>

----------------------------------------------------------------------------------------------------------------------------------------------------------

This is my user logic that one one special event I am using this logic  

if( osal_nv_item_init( BOOT_CHECK_NV_ID, sizeof(NodeP_mode), &NodeP_mode )== ZSUCCESS)   //0x7D0 'BOOT_CHECK_NV_ID'

 {

     osal_nv_read( BOOT_CHECK_NV_ID, 0, sizeof(NodeP_mode), &NodeP_mode );

 }

 if( NodeP_mode == START_AS_FRESH )                                                //0x21 'START_AS_FRESH'

 {

   networkStateNV = ZDO_INITDEV_NEW_NETWORK_STATE;

 }

 else

 {

   // Determine if NV should be restored

   networkStateNV = ZDApp_ReadNetworkRestoreState();

 }

 if ( networkStateNV == ZDO_INITDEV_RESTORED_NETWORK_STATE )

 {

   networkStateNV = ZDApp_RestoreNetworkState();

 }

 else

 {

   // Wipe out the network state in NV

   NLME_InitNV();

   NLME_SetDefaultNV();

   // clear NWK key values

   ZDSecMgrClearNVKeyValues();

 }

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Node - Router device

Cooridnator - ZNP

My doubt is is it happening because of that osal related if else condition failure ?

or any other event can also lead to the node to start it as Fresh node 

Maybe I misunderstand your question in my first reply but I don't think there is a chance that Node will forget its parent. If you have this issue, I suggest you to use Ubiqua Packet Analyzer to check over the air messages.

I have checked through TI Packet sniffer
as Ubiqua Packet analyzer trail version was there in My PC ( which works only for 21 Days )

The node was getting announced with its parent coordinator and many times I have done Power oN reset for the nodes it is working as expected
like getting device announce directly,
One time I have viewed from Ti Packet sniffer that node was sending Beacon request instead of directly joining to its parent coordinator

that's why I though of asking it why or HOW it can happen ?

ZED should send rejoin request to try to rejoin. If there is no rejoin response, it shall send beacon requests to scan channels and try to join again.

Is is the case only with ZED

As I am using ZRD - ZigBee Router Devices

ZR doesn't have a parent node so it won't send rejoin request.

Yes even same i am also thinking then what could be the other possible reason that it started sending beacon request again
and also it didn't get connected/associated with the coordinator even though it was kept very near by to ccordinator

The only possibility that ZR send beacon requests is its not in any Zigbee network.

Then in my case

The ZigBee router device was associated with coordinator

Only thing is that after multiple power on reset tested for more than two days

For one time the device announce not happened then i connected packet sniffer and saw that particular ZigBee router device was sending beacon request and i got surprised

I suggest you to use sniffer to keep full tracking from the beginning of your test so you can know what exactly happens.

Hi Yikai

is it possible in this case that ongoing node which is in the network and which has not been powered down, can start sending beacon request

if yes which event will cause this to happen ?

I couldn't understand your question. Can you elaborate?

I have a steup

for 3 nodes and one coordinator

All the three nodes are communicating perfectly and after a while say 30 minute or later, One of these nodes started sending beacon request again ?

I have not done any power off and on for the full set up

You have to setup a sniffer to know why this happens.