CC2530: How to clone a coordinator

Try to refer to sunmaysky.blogspot.com/.../how-to-clone-existing-z-stack.html

I'm using the same but I cannot read ZCD_NV_TCLK_TABLE_START(0x0101) using SYS_OSAL_NV_READ.

It shows INVALID_PARAMETER(0x2) error.

And what does the fourth step(4. Flash the same coordinator binary to the new coordinator.) of the blog mean?

What Z-Stack version do you use? For step 4, it mean to flash ZNP firmware into a new CC2530 which you would use later.

v2.7.1

If the new CC2530 is already flashed with ZNP firmware, then should I need to only write to the NV the previous configs to assign it as coordinator?

For Zigbee 3.0, you can refer to https://www.ti.com/lit/an/swra671/swra671.pdf to backup and restore ZNP/coordinator. And yes, you only need to write the previous configs to the NV of new ZNP to assign it as coordinator

Does this SDK supports cloning of CC2530?

and my one question still remains, why I could not read ZCD_NV_TCLK_TABLE_START(0x0101) using SYS_OSAL_NV_READ. It shows INVALID_PARAMETER(0x2) error.

ZCD_NV_TCLK_TABLE_START is define with 0x0111 in Zigbee 3.0 Z-Stack so you can try to use 0x0111 instead of 0x0101

There are some similar E2E threads on this topic:

https://e2e.ti.com/f/1/t/814208 
https://e2e.ti.com/f/1/t/684522 

I recall needing to define MT_SYS_KEY_MANAGEMENT in order to gain access to security key data.  You could also further debug your ZC to determine why INVALID_PARAMETER is returned.  NV ID locations are defined in the zcomdef file to better understand where ZCD_NV_TCLK_TABLE_START is.

Regards,
Ryan

Hello Ryan,

Could you please guide me on where(in which file) do I need to define MT_SYS_KEY_MANAGEMENT in order to read 0x003A and 0x003B from NV.

Also, how to restore the NV to its factory default values.

Hello YK,

Could you please brief me on how to enable Compiler option MT_SYS_KEY_MANAGEMENT on coordinator.

Which file do I need to modify?

Try to refer to the following screenshot and add it in ZNP project.

I suppose this screenshot is from IAR workbench. I have never used that tool. Can you please tell me how to do it? And what do you mean by ZNP project?

You should open ZNP project with IAR EW8051 and you can add it in project options.

What exactly is the ZNP project? Is it a file?

ZNP stands for Zigbee Network Processor and it’s one of Zigbee examples in Z-Stack. Don’t you run it on your CC2530 so it can work with ZTOOL?

There is no such MT_SYS_KEY_MANAGEMENT in the list. How to do it?

Click the edit box and type MT_SYS_KEY_MANAGEMENT in it.

I've mentioned the MT_SYS_KEY_MANAGEMENT. What do I need to do next? As of now I can read all the addresses mentioned in https://sunmaysky.blogspot.com/2016/01/how-to-clone-existing-z-stack.html except ZCD_NV_TCLK_TABLE_START(0x0111). When I try to read the length of 0x0111 using SYS_OSAL_NV_LENGTH, it shows length as zero. Why so? 

And FYI, now also I've read the locations 0x003A and 0x003B using ZB_READ_CONFIGURATION as SYS_OSAL_NV_READ still responds INVALID_PARAMETER.

Can you do screenshots to show me what you are doing?

After writing MT_SYS_KEY_MANAGEMENT, I've clicked OK and saved the file, then I restarted Z-Tool and now I'm able to  read 0x003A and 0x003B, but with ZB_READ_CONFIGURATION command. Also, the length of 0x0111 is shown to be zero. Below attached are the screenshots.

Please guide me to the next steps for cloning.

Do you rebuild ZNP with IAR and download built firmware into your Cc2530 to test with Z-tool. You should use SYS_OSAL_NV_READ to read 0x0111, not SYS_OSAL_NV_LENGTH.

The fact that you are using SAPI commands (ZB_READ_CONFIGURATION) means you are using a Z-Stack HA 1.2.2a solution, which varies from Z-Stack 3.0 in that ZCD_NV_TCLK_TABLE_START is defined at 0x0101 instead of 0x0111.  Otherwise, this nvId region should still be accessible with MT_SYS_KEY_MANAGEMENT defined.  Please confirm that you are re-programming your CC2530 with the updated firmware and further debug your MT_SYS.c file to find where/how ZInvalidParameter is being returned.

Regards,
Ryan