TI Z-Stack 3.4.0 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 3.4.0 :
- 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_3_20_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_3_20_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 |
|---|---|
| ZIGBEE-452 | End Device poll rate management module |
| ZIGBEE-133 | Add Secure BIM/Secure Boot support for Zigbee OTA Client Projects |
| ZIGBEE-63 | Change event_loop functions to use uint32_t event bitmask |
Fixed Issues
| ID | Summary |
|---|---|
| ZIGBEE-454 | Warning device warning timeout expiration does not update warning LED state |
| ZIGBEE-428 | Device locks up if BTN-2 is held too long during start-up |
| ZIGBEE-407 | Touchlink ZR Initiator ZED Target: No Device Information Response sent from ZR |
| ZIGBEE-406 | Touchlink ZED Initiator ZR Target: Rejoin Poll Rate used for ZED polling |
| ZIGBEE-405 | Touchlink ZR Initiator ZR Target: Identify Query Response never sent |
| ZIGBEE-403 | Unreferenced initiatorReJoinNwk function for ZED Touchlink Initiator |
| ZIGBEE-402 | Green Power Proxy not tunneling GPDFs under certain conditions |
| ZIGBEE-401 | ZNP (syscfg) configures ZNP ZEDs as non-sleepy by default |
| ZIGBEE-384 | Issue with reporting multiple attributes at once with BDB Reporting |
| ZIGBEE-352 | Thermostat LED behavior does not match README |
| ZIGBEE-349 | Default temp value of gpd_temperaturesensor should match zc/zr/zed_temperaturesensor |
| ZIGBEE-348 | OTA client unable to return to factory new image on external flash |
| ZIGBEE-324 | doorlock/doorlockcontroller PIN is not reset when device is factory new reset |
| ZIGBEE-318 | IEEE address is restored from NV even if device was factory reset |
| ZIGBEE-317 | UTIL_GET_NV_INFO does not display PAN ID from NV correctly |
| ZIGBEE-310 | Sample application Serial UI and HW Buttons should share BDB commissioning modes mask |
| ZIGBEE-244 | Commissioning GPD causes NV failure for GPS when ZCL_GROUPS is enabled |
| ZIGBEE-242 | Allow NV_RESTORE to be disabled OOB in gpd_sw (required for batteryless mode) |
| ZIGBEE-195 | Broadcast MAC Data Req on CH 11 after failure to associate |
| ZIGBEE-155 | ZED may attempt polling more than MAX_POLL_FAILURE_RETRIES under certain conditions |
Known Issues
| ID | Summary |
|---|---|
| ZIGBEE-453 | Green Power Device: ApiMac_mcpsDataReq_t txOptions.usePowerAndChannel setting is ineffective |
Upgrade and Compatibility Information
The Z-Stack 3.4.0 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.