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

9 Zigbee Coordinator Cloning Procedure Example

This section provides a detailed example of the procedure outlined in Section 8. A sniffer log was used to ensure proper functionality. Before executing this example, a network was formed with a Zigbee Coordinator (ZC1), a CC135xR1 Launchpad running a modified version of the ZC light example project following the setup from Section 7. After the network was created, two ZRs joined the network.

  1. Identify the COM Ports for the devices: ZC1- COM20, ZC2- COM23
  2. Open the TI Zigbee Network Properties Cloning tool, and select the 'Clone' option then the designated ports from step 1. Afterwards, go to Tools -> Form Network. A network will be formed on ZC2 when the 'Clone' option is selected. If a network is formed the output should show a success, if not a failure message will be displayed.
    3. Figure 1. Formed Network Exampleformed-network-swra671.png
  3. Press the 'Start' button and observe the output display to verify what was read and written. If desired the content from both ZC1 and ZC2 can be compared by analyzing the differences between their read_content.txt file output after reading from each device separately. If the content from both files is the same then the procedure was successful.
    4. Figure 2. NV Content Read Exampleread-content-swra671.png
    This image shows an example of what was read from ZC1 (Top) and from ZC2 (Bottom). The contents of TCLK were shorted to only show the last two table entries. This is so because the TCLK table gets populated from the end of the table first.
  4. Remove ZC1 from the NWK.
  5. Power Cycle or Restart ZC2. After ZC2 is part of the already existing network it will send out periodic link statuses. Within the status should be the devices that had joined when ZC1 was the coordinator.
    6. Figure 3. Sniffer Log Capture Examplesniffer-capture-swra671.png
    This image is part of the sniffer log that was captured for this example. In link status (1), sent by the coordinator device ZC1 (0x0000), we can confirm that there were two devices who were part of the network. The green box shows ZC2 joining the network as ZC1 leaves signified by the opening and closing of the network. Link status (2), sent by the new coordinator ZC2, still shows the same devices as part of its network.
  6. The network should continue to operate as before.