• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 410 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.

Issue of Address Management in ZStack

Fanzhong CHEN
Prodigy 40 points

Hi,

I'm trying to retrieve the 16-bit short address with a known 64-bit address, and trying to keep the retrieved address maping information on coordinate device.

For the first task, it can be accomplished sucessfully by calling ZDP_NwkAddrReq function and get the returned short address by parsing ZDO message.

I met problem at the second task:

In my understanding, zstack will automatically call the following function to save address information if the short address is retrieved sucessfully :    ZDO_UpdateAddrManager( pAddrRsp->nwkAddr, pAddrRsp->extAddr ) (which will call AddrMgrEntryUpdate( &addrEntry ) function indeed)

My finding is that the above scenario only works for one-hop network.   If the requested device is not the direct child of the coordinate, AddrMgrEntryUpdate always return FALSE, thus the address mapping information CAN NOT be saved.

Is it the desired behavior of  ZDO_UpdateAddrManager (and AddrMgrEntryUpdate) ?

Since the lack of document or source code, I have been stucked in the problem for quite a while.

Hope someone can help me out.

Thanks,

Fanzhong

  • 0
    Prodigy 40 points

    Hi TIers,

        Is it possible to expose some implementation details of AddrMgrEntryUpdate library function?

        I don't  need the full source code. I just want to know the condtions when AddrMgrEntryUpdate return FALSE, and the meaning of entry.index when AddrMgrEntryUpdate return FALSE.

     

    Thanks,

    Fanzhong