TI Z-Stack 4.10.00 Release Notes
Table of Contents
Introduction
Z-Stack 3.x is a component of the SimpleLink™ CC13x2 / CC26x2 Software Development Kit. This component enables development of Zigbee® 3.0 specification based products. Z-Stack is TI’s complete solution for developing certified Zigbee 3.0 solution on CC13x2 and CC26x2 platforms. Z-Stack contained in this release is based on Zigbee 3.0 specification with the added benefit of running on top of TI-RTOS.
Key features of Z-Stack 4.10.00 :
- Zigbee certified stack - Zigbee Pro 2017 (R22) and Green Power Proxy v1.1.1 (Z-Stack Core v1.0.0.0)
- Zigbee Cluster Library (ZCL) 7 integration
- Standalone Home Automation sample applications to jump start development
- Generic example application to start creating custom Zigbee 3.0 certifiable products
- Green Power Device (GPD) and Sink (GPS) examples for battery-less devices
- Integrated User Interface or Zigbee network processor (ZNP) dual-device configurations
- Secure Over-the-Air Download (OAD) firmware upgrade support and Over-the-Air Update (OTA) examples for updating Zigbee device firmware wirelessly
- Dynamic Multiprotocol Manager (DMM) Integration - BLE + Zigbee coexistence examples included in the SDK
- Full integration with TI-RTOS for real-time scheduling, automatic power management and utilizing peripheral device drivers
- Free code development option with Code Composer Studio™ (CCS)
Additional information about TI’s Zigbee solution can be found at www.ti.com/zigbee
Z-Stack Documentation
The SimpleLink CC13x2 and CC26x2 Software Development Kit(SDK) allows easier product development by combining TI-RTOS and the Zigbee protocol stack in one unified SDK. All Z-Stack sample applications are based off the TI-RTOS Kernel. Key documents needed for Zigbee application development include:
- Z-Stack Quick Start Guide
- TI Z-Stack User’s Guide
- Z-Stack Application APIs
- Z-Stack Migration Guides
- Z-Stack Monitor and Test API
- Z-Stack ZCL APIs
Installation and Usage
- To build the sample applications with this SDK a supported IDE must be installed (refer to Dependencies below)
- Install the simplelink_cc13x2_26x2_sdk_4_10_00_xx installer package on a supported host operating system build machine with Administrator privileges
- The default install path for Windows is C:\ti\simplelink_cc13x2_26x2_sdk_4_10_00_xx
- Changing the default install path and/or drive letter may require updating project variables. Do not use a space in the install path
- It is recommended to make a backup of the installation in order to revert modifications to the SDK
What’s New
| ID | Summary |
|---|---|
| None | None |
Fixed Issues
| ID | Summary |
|---|---|
| ZIGBEE-709 | NWK Route Requests sent with NWK DestAddr to all RxOnIdle devices instead of only Routing devices |
| ZIGBEE-704 | Touchlink Initiator not scanning secondary channels if network already formed |
| ZIGBEE-699 | Parent Annce / Parent Annce Rsp payload can exceed max packet size |
| ZIGBEE-688 | Zigbee Extended PAN ID in SysConfig is reversed |
| ZIGBEE-685 | In rare cases, sleepy ZEDs that send multiple Association Reqs during initial join can be sent a Leave Req |
| ZIGBEE-683 | ZCL Req/Rsp sequence numbers between OTA Server/Client do not match |
| ZIGBEE-681 | MTO Routing does not send Route Records for all relayed ZED unicast data frames |
| ZIGBEE-680 | Joining device broadcasts MgmtPermitJoining_req even if no TCLK was not received |
| ZIGBEE-676 | SysConfig does not allow configuration of TX power and PA |
| ZIGBEE-675 | Defining POLL RATE as 0 in SysConfig does not allow ZED to stay in network |
| ZIGBEE-673 | ZC crashes during TCLK exchange when more than 16 joiners connect with Install Codes |
| ZIGBEE-672 | Unnecessary route requests due to route replies not updating neighbor table entries |
| ZIGBEE-670 | Zigbee devices do not rejoin network if using install codes |
| ZIGBEE-668 | Zigbee Default Network Key in SysConfig is reversed |
| ZIGBEE-655 | ZCL OTA sends UNSUP_CLUSTER_COMMAND instead of MALFORMED_COMMAND status code |
| ZIGBEE-648 | Incorrect extAddr is used in bdb_TCAddJoiningDevice() |
| ZIGBEE-647 | Preconfigured PAN ID may not be selected correctly if multiple networks are open |
| ZIGBEE-607 | Using Custom Board in SysConfig may cause unexpected build and runtime behavior |
Known Issues
| ID | Summary |
|---|---|
| ZIGBEE-698 | Inclusion of FEATURE_NVEXID causes compile errors, MT_SysNv* APIs need to be updated |
| ZIGBEE-687 | OTA Client does not send default response for a non-success status Upgrade End Request |
Upgrade and Compatibility Information
The Z-Stack 4.10.00 only supports Revision E SimpleLink CC13x2 and CC26x2 devices. No support for previous silicon revisions or LaunchPad™ development kits using earlier silicon revisions. If you’re unsure of the revision number of your device, please see the Package Symbolization and Revision Identification section of the Errata Note.
Operating System Support
- Microsoft Windows® 7 SP1, Windows 8.1 or Windows 10
- Ubuntu 14.04 64-bit, Ubuntu 16.04 64-bit
- macOS Sierra
Dependencies
The Z-Stack sample applications were built & tested with the Integrated Development Environments (IDEs) and listed in the top-level SDK release notes.
Note: Earlier IDE/toolchain versions are not supported and compatibility with newer versions of supported IDEs is not assured.
Device Support
Development Board Support
Validation
The Z-Stack sample applications were built & tested with versions of the following Integrated Development Environments (IDEs) and tool chains listed in the top-level SDK release notes:
- Code Composer Studio using the TI C Compiler for Arm
- IAR Embedded Workbench for Arm
This release is for evaluation and development purposes only. End products being developed with this protocol stack version will require a future update prior to obtaining Zigbee and/or regulatory certification.
Versioning
This product follows a version format, M.mm.pp.bb, where:
- M is a 1 digit major number,
- mm is a 2 digit minor number,
- pp is a 2 digit patch number,
- bb is a 2 digit incrementing build counter.