SWRA671 June   2020 CC1312R , CC1312R , CC1352P , CC1352P , CC1352R , CC1352R , CC2652P , CC2652P , CC2652R , CC2652R , CC2652R7 , CC2652R7 , CC2652RB , CC2652RB , CC2652RSIP , CC2652RSIP

 

  1.   Cloning Z-Stack Network Properties Using the SimpleLink Wireless MCU Family
    1.     Trademarks
    2. 1  Introduction
    3. 2  Abbreviations and Acronyms
    4. 3  Tool Versions
      1. 3.1 Command Line Interface (CLI)
      2. 3.2 MAC OS Application
      3. 3.3 Windows Executable
    5. 4  Trust Center and Non-Volatile Memory
    6. 5  Multi-Page NVM
    7. 6  MT Interface
    8. 7  Zigbee Coordinator Setup Procedure
    9. 8  Zigbee Coordinator Cloning Procedure
      1. 8.1 Cloning: Method One
      2. 8.2 Cloning: Method Two
    10. 9  Zigbee Coordinator Cloning Procedure Example
    11. 10 Other Application Considerations
    12. 11 Summary
    13. 12 References
  2.   A TI Zigbee Network Properties Cloning Tool Guide
    1.     A.1 Tool Layout
    2.     A.2 Configuration File
    3.     A.3 Content File
    4.     A.4 Application Selection
    5.     A.5 COM Ports
    6.     A.6 Read Settings
    7.     A.7 Write Settings
    8.     A.8 Output Settings
    9.     A.9 Save/Load Settings
    10.     A.10 Help
  3.   B Establishing a Serial Connection
    1.     B.1 Serial Connections
    2.     B.2 Detecting COM Ports

10 Other Application Considerations

With this procedure it is possible to be able to clone any ZC device that is operating in a network. This application report and the associated resources are for demonstrative purposes. The implementations discussed are left to the user to apply in the case a more secure system is desired.

Nothing is preventing illicit NV memory reads from unwanted sources. Thus, when discussing security in ZC cloning it is important to take precautions. One possible way to accomplish this is to have a password protected device. In order to be able to read certain memory regions of the device then the user must enter said password. Refer to Understanding Security Features for SimpleLink™ Zigbee CC13x2 and CC26x2 Wireless MCUs for both device and OTA Zigbee considerations.

Another implementation is backing up the coordinator every time a new device joins the network. This can be done by sending a message to the host processor when there is a device announcement to let the host know to kick off the backup. The reason this is important is for the circumstances when the issue with the coordinator is in the memory itself. Therefore, if the memory gets corrupted, the contents of the TC would still be saved up to the point of the last time a device joined the network and updated key information. The tool provided only gives base functionally of cloning a ZC device at a time of interest.