SWRA671 June 2020 CC1312R , CC1312R , CC1314R10 , CC1314R10 , CC1352P , CC1352P , CC1352R , CC1352R , CC1354P10 , CC1354P10 , CC1354R10 , CC1354R10 , CC2652P , CC2652P , CC2652R , CC2652R , CC2652R7 , CC2652R7 , CC2652RB , CC2652RB , CC2652RSIP , CC2652RSIP
The CC2652R device from Texas Instruments is the ideal System-on-Chip (SoC) from high-performance ZigBee applications, addressing many product specifications from a low-power standpoint. The CC2652R combines a powerful 48 MHz Arm Cortex-M4F CPU with up to 80KB of RAM and 352KB of on-chip flash. With a dedicated Radio Controller handling low-level RF protocol commands stored in ROM, it can handle complex network stacks ensuring ultra-low power and great flexibility.
In the world of IoT, battery life is tremendously valued by customers, cutting down on the bill of materials and battery replacement costs, while enabling easy maintenance and product convenience. Therefore, current consumption of devices inside a connected network must have their current consumption tightly controlled. The CC2652R is designed with the lowest power performance in sleep mode, active mode, and during sensor and data processing.
When range is an important consideration for an application, Texas Instruments offers the CC1352P device, which contains a +20 dBm integrated high-power amplifier with a best-in-class efficiency for long range applications. The CC1352P is a multiprotocol Sub-1 and 2.4-GHz with the same powerful system, offering the ability for a high-performance, long range ZigBee device.
This application report references examples from Z-Stack 3.6.0, which is based on the ZigBee 3.0 profile. Z-Stack comes packaged as part of the SimpleLink CC13X2/CC26X2 SDK, which is designed for simplified development within one environment using industry standard APIs, TI Drivers, and TI RTOS to provide a robust foundation for application development. The SDK version used in this report’s test is v3.4.0.
There are different logical device types within a ZigBee Mesh Network: Coordinator, Router, and End Device. This application report focuses on the coordinator, for which there can only be one per network. The coordinator is responsible for forming and starting the network as well as managing the Trust Center (TC). If the coordinator were to fail, new devices would be prevented from joining the existing network since there would be no means of opening the network for joining, or exchanging network and application keys. Therefore, there is a need to back up the information contained in the coordinator and transfer it to a new device so that the new device can resume the role as coordinator. By being able to “clone” the device, the established network can continue as is, and new devices are able to successfully join. Section 4 discusses the TC and required Non-Volatile Memory (NVM) regions to be cloned. Afterwards, the setup and process to clone a Zigbee Coordinator (ZC) is discussed in Section 7 and Section 8 respectively.
NOTE
This application report is also applicable to Zigbee Network Processors (ZNPs)