• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 55 subscribers
  • Views 236 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2652P7: ZDO_NetworkDiscoveryConfirmCB not triggered in noisy environment

Shuyang Zhong
Expert 5115 points

Part Number: CC2652P7

A customer found that in a noisy environment which multiple coordinator exists, there is a chance that ZDO_NetworkDiscoveryConfirmCB() is not triggered after end device sending Zstackapi_bdbStartCommissioningReq().

End device is stuck in ZDO_beaconNotifyIndCB() and could not exit and go to ZDO_NetworkDiscoveryConfirmCB().

The questions are:

1. What is the cause of this behavior and how to avoid it?

2. The customer wants to use NLME_NwkDiscTerm() to terminate the scanning when it happens, it is recommended to do so? If not, is there another API to manually terminate the scanning?

Best regards,

Shuyang

  • 0
    TI__Guru**** 223757 points

    Hi Shuyang,

    Please help clarify this issue. 

    • What SDK version are they evaluating? 
    • How often does this behavior occur?
    • How many coordinators/routers are sending Beacons in response to the ZED Beacon Request?  How many of these are open for joining?
    • How many channels does the ZED scan?
    • Does the application continue processing or is it stuck in a loop and unable to continue/restart?

    NLME_NwkDiscTerm cleans up the NWK layer after a call to NLME_NwkDiscReq2 and is not tested for this purpose.  I suggest using SysCtrlSystemReset as a possible workaround if the device is certainly stuck inside of the network discovery process and is unable to exit independently.

    Regards,
    Ryan