Home 1.2.1 - CC2530
Hi,
I am trying to copy the Coordinator NV items in order to restore a Coordinator upon hardware failure.
I am able to start the ZC, osal_nv_write a predefined PANID to NV Ram and SystemReset(). Then start as normal and the ZC starts on the predefined PANID. Great!
The problem lies with trying to stop the ZC incrementing the PANID by 1 when starting and finding Routers around on the PANID in NV Ram.
From reading the datasheets and forum's it's simply a matter of backing up the zgItemTable but that is not possible. I do not have much backup storage space available off the CC2530 and so I need to keep the storage space requirements as low as possible. I am not using bindings or security, do not need to be ZigBee compliant and do not need the ZC to come on-line seamlessly so do not need to worry about the Association Table.
So in an attempt to come up with the absolute minimum list of back-up requirements I am systematically going through the list in ZComDef.h.
The Question: I am reading ZCD_NV_PANID but it returns 0xFFFF even after a successful ZED join. Where does Z-Stack save the PANID during runtime? I would expect it writes to ZCD_NV_PANID after forming the network but it seems not to.
As an alternative, is there a way to stop the ZC sending out a beacon (and therefore avoid the PANID +1) if it needs to start on the same network as other routers? I guess not due to the ZigBee protocol.
Many thanks,
Andy