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. Introduction
    3. Abbreviations and Acronyms
    4. Tool Versions
      1. 3.1 Command Line Interface (CLI)
      2. 3.2 MAC OS Application
      3. 3.3 Windows Executable
    5. Trust Center and Non-Volatile Memory
    6. Multi-Page NVM
    7. MT Interface
    8. Zigbee Coordinator Setup Procedure
    9. Zigbee Coordinator Cloning Procedure
      1. 8.1 Cloning: Method One
      2. 8.2 Cloning: Method Two
    10. 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

Multi-Page NVM

Z-Stack 3.5.0 and onward has a multi-page NVM that grants users of the TI Z-Stack more flexibility in the amount of devices used within the network and the space required to store that information. Previously the NVM size used to be two pages (one for storage and one for compaction) while using the NVOCTP driver. Now, the NVM has been extended to five pages (four for storage and one for compaction) with the NVOCMP driver. With this transition came moving all tables out of ‘ZCD_NV_EX_LEGACY’ and creating new item IDs for each table/list. The TI Zigbee Network Properties Cloning Tool was created with the new implementation of NVM layout. If a device is running a project from Z-Stack 3.4.0 or earlier then the predefined symbol ‘ZSTACK_NVOCMP_MIGRATION’ must be defined in the new (Z-Stack 3.5.0 or newer) project in order to compensate for the changes involved with upgrading from the NVOCTP to the NVOCMP driver and to retain the NV memory sections as-is. For more details on this topic, see the Non_Volatile Memory Items section within ‘Z-Stack Overview’ in the TI Z-Stack User’s Guide.