CC2652R7: ZED Randomly leaves network

Hi Elarif,

Does bdb_isDeviceNonFactoryNew return bdbAttributes.bdbNodeIsOnANetwork as TRUE?  If not then the NV memory has been reset to a factory new setting.

Elarif Mohamed said:

• zstack_DevState -> zstack_DevState_HOLD
• bdbCommissioningMode -> BDB_COMMISSIONING_NWK_STEERING
• bdbCommissioningStatus -> BDB_COMMISSIONING_NO_NETWORK

Based on these values, it is likely that the bdb_nwkDiscoveryAttempt -> bdb_reportCommissioningState BDB_COMMISSIONING_STATE_JOINING case had failed.  The following code is from the SimpleLink v7.10 SDK and may vary for your version (there are very few changes from v6.40 so I doubt this makes a difference):

      case BDB_COMMISSIONING_STATE_JOINING:
        if(ZG_DEVICE_JOINING_TYPE)
        {
          //Prepare for the next state or commissioning mode to be excecuted
          OsalPortTimers_startTimer(bdb_TaskID,BDB_CHANGE_COMMISSIONING_STATE,50);

          if(didSuccess)
          {
            //Next state is TC link key exchange
            bdbCommissioningProcedureState.bdbCommissioningState = BDB_COMMISSIONING_STATE_TC_LINK_KEY_EXCHANGE;
            //Free the list of nwk discovered
            while(pBDBListNwk)
            {
              bdb_nwkDescFree(pBDBListNwk);
            }

            //No notification in this step
            return;
          }
          else
          {
            uint8_t temp = FALSE;

            bdbAttributes.bdbCommissioningStatus = BDB_COMMISSIONING_NO_NETWORK;
            bdbCommissioningModeMsg.bdbCommissioningMode = BDB_COMMISSIONING_NWK_STEERING;
            bdbCommissioningProcedureState.bdbCommissioningState = BDB_COMMISSIONING_STATE_START_RESUME;
            bdbAttributes.bdbCommissioningMode &= ~BDB_COMMISSIONING_MODE_NWK_STEERING;

            //Turn off the radio
            ZMacSetReq(ZMacRxOnIdle, &temp);
            //Set the device to FN, to start as new for subsequent attempts
            bdb_setFN();
            NLME_ResetRequest();
            ZDApp_ChangeState( DEV_HOLD );

            //Free the list of nwk discovered
            while(pBDBListNwk)
            {
              bdb_nwkDescFree(pBDBListNwk);
            }
          }
        }
      break;

You can also further debug the device directly to determine when bdbCommissioningStatus is set to BDB_COMMISSIONING_NO_NETWORK and what the call stacks and network status are at this point.  Are you able to replicate this behavior with a default project?  If not then please further clarify your application changes.  The ZED DoorLock example at least does not report attributes, and the changes implemented could be causing a memory leak which eventually corrupts the NV memory, or causes an unexpected factory reset.  If you know that the device has reset to factory new then you should further debug to try and break at bdb_setFN to determine why this is taking place.  Here are some other threads which you may consider:

https://e2e.ti.com/f/1/t/1274985 
https://e2e.ti.com/f/1/t/1288546 

Regards,
Ryan

Hi Ryan,

Thank you for that quick answer and these suggestions.

The v7.10 code you provided is indeed identical to the v6.40 .

My next actions wille be to Implement more instrumentation in my code to identify the complete state of the device when the problem occurs.

Plus, after reading the threads you mentioned :

• Add some stack modifications on my ZED regarding that DEV_END_DEVICE_UNAUTH behavior
• Upgrade my ZC firmware.

Based on the results, I may start looking for NV Corruption and/or try to program my ZED with a clean example after that.

I'll get back to you with my test results (few days are expected...) !

One more thought: if the ZED are battery powered, please make sure that the voltage level is not dropping below 2 V as this could cause flagrant NV memory writes.  See Non-Volatile Memory Low Voltage Detection for more details.  Otherwise, if the ZED are mains powered and power consumption is not an issue then please consider using a ZR project instead, at least as a test to determine if behavior is similar.

Regards,
Ryan

Hi Elarif,

FYI  

(+) SIMPLELINK-CC13X2-26X2-SDK: Firmware not stable since SDK 6.20.00.29 - Zigbee & Thread forum - Zigbee & Thread - TI E2E support forums

Best regards,

David