SILICON LABS SDK 7.2.6.0 EmberZNet Zigbee Platform User Guide

SILICON LABS SDK 7.2.6.0 EmberZNet Zigbee Platform

Product Information

Specifications

• Zigbee EmberZNet SDK Version: 7.2.6.0
• Gecko SDK Suite Version: 4.2, Released on July 3, 2024
• Vendor: Silicon Labs
• Compatible Compilers: GCC (The GNU Compiler Collection) version 10.3-2021.10

Product Usage Instructions

Key Features
The Silicon Labs Zigbee platform is the most integrated,  complete, and feature-rich Zigbee solution available.

Using the EmberZNet SDK
The EmberZNet SDK contains Silicon Labs’ implementation of theZigbee stack specification. To get started:

1. Download the SDK from the official website.
2. Refer to the release notes for compatibility and use notices.
3. Ensure you have the compatible compiler (GCC version 10.3-2021.10).
4. Follow the instructions provided in the “Using This Release” guide if you are new to the Zigbee EmberZNet SDK.

Zigbee EmberZNet SDK 7.2.6.0 GA
Gecko SDK Suite 4.2
July 3, 2024

Silicon Labs is the vendor of choice for OEMs developing Zigbee networking into their products. The Silicon Labs Zigbee platform is the most integrated, complete, and fea-ture-rich Zigbee solution available.
Silicon Labs EmberZNet SDK contains Silicon Labs’ implementation of the Zigbee stack specification.

These release notes cover SDK version(s):

• 7.2.6.0 released July 3, 2024
• 7.2.5.0 released January 24, 2024
• 7.2.4.0 released August 16, 2023
• 7.2.3.0 released May 3, 2023
• 7.2.2.0 released March 8, 2023
• 7.2.1.0 released February 1, 2023
• 7.2.0.0 released December 14, 2022

KEY FEATURES

Zigbee
Secure key storage support for MG2x parts support Secure Vault-High

• MG24+Si4468 Dual-PHY Zigbee Smart Energy support
• MG12 Dual-Band 2.4GHz + SubGHz ZigbeeSmart Energy support
• MGM240S SiP Module Support
• Zigbee on Host (ZigbeeD) support for 32 bit and 64 bit x86 architecture – experimental

Multiprotocol

• Dynamic Multiprotocol Bluetooth and multi-PAN 802.15.4 in RCP mode
• Dynamic Multiprotocol Bluetooth and ZigbeeNCP – experimental
• Manufacturing Library (MfgLib) support for concurrent Multiprotocol RCP
• Zigbee + OpenThread Concurrent Listeningon MG24 parts – experimental

Compatibility and Use Notices

For information about security updates and notices, see the Security chapter of the Gecko Platform Release notes installed with this SDK or on the TECH DOCS tab on https://www.silabs.com/developers/zigbee-emberznet Silicon Labs also strongly recommends that you subscribe to Security Advisories for up-to-date information. For instructions, or if you are new to the Zigbee EmberZNet SDK, see Using This Release.

Compatible Compilers:
IAR Embedded Workbench for ARM (IAR-EWARM) version 9.20.4.

• Using wine to build with the IarBuild.exe command line utility or IAR Embedded Workbench GUI on macOS or Linux could result in incorrect files being used due to collisions in wine’s hashing algorithm for generating short file names.
• Customers on macOS or Linux are advised not to build with IAR outside of Simplicity Studio. Customers who do should carefully verify that the correct files are being used.

New Items

New Features
New in release 7.2.0.0

Zigbee Security
Support is available for storing encryption keys securely on EFR32MG2x parts that support the Secure Vault-High feature. Refer to AN1271: Secure Key Storage for information about securely storing security keys. Applications that wish to store security keys in secure storage must be used for new deployments, as OTA upgrade for existing devices is currently unsupported in this release.

Smart Energy
Simultaneous Dual-PHY Smart Energy support is now available on EFR32xG24+Si4468 parts.
Zigbee Smart Energy Dual-Band 2.4GHz and Sub-GHz support for end devices is now available on EFR32xG12 parts.

DMP NCP
Dynamic Multiprotocol Zigbee-NCP + Bluetooth-NCP support is now available.

New Applications

• None

New Components
New in release 7.2.0.0
Zigbee Security Manager Components

Zigbee Security Manager
The Zigbee Security Manager component is a common component that provides an interface for the user to manage security keys and crypto routines. This component is tailored to Zigbee-specific keys and crypto routines.

Security Manager
The Security Manager component is a stack-agnostic component that provides an interface to manage keys in PSA storage. These may be wrapped keys if the device supports the Secure Vault-High feature. The Security Manager component also provides an interface to certain crypto routines. The Zigbee Secure Key Storage component utilizes the Security Manager component.

Classic Key Storage
The Zigbee Classic Key Storage component handles the storing and fetching of security keys in NVM3 tokens. NVM3-stored keys are saved in-the-clear in flash, which means that keys can be read when flash is read from the device. This storage method is the way Zigbee applications have previously stored keys on the device.

Secure Key Storage

The Zigbee Secure Key Storage component handles storing keys using PSA APIs. For devices that support the Secure Vault-High feature, keys are wrapped in secure storage and cannot be gleaned by reading flash from the device.
The Security Manager component is used by the Zigbee Secure Key Storage component to execute certain crypto routines, like AES encryption and decryption.
Users wishing to have the application store keys securely must do so on fresh deployments only. There is currently no support for deployed devices to upgrade their key storage and move security keys from tokens into secure key storage. This upgrade functionality is planned for a future release.

Devices that include the Secure Vault High feature may still store security keys classically (for example in tokens) by including the Classic Key Storage component instead. SDK 7.2.0.0-based applications that include OTA upgrade functionality for these Secure Vault-High devices running pre-SDK 7.2.0.0 code are currently limited to using the Classic Key Storage component.

Secure Vault-High devices may not downgrade from an image that stored keys in secure storage to an image that stores keys back into tokens.

Other Components

Watchdog Refresh
The watchdog refresh component resets the watchdog timer periodically (value is configurable and holds a default of 1 second). Note that in order to accomplish this, the part needs to get into EM0 energy mode. This component is included by default when there is an RTOS and watchdog is used in the code. Refreshing of the watchdog timer can be disabled using the configuration option in the compo-nent.

Green Power Adapter
The zigbee_green_power_adapter component supports use of green power server or client component in a custom framework. This component includes a set of minimum required source files from the application framework and it provides a number of subroutines to be used to integrate the custom framework.

New APIs

• New in release 7.2.1.0
• Renamed sl_set_passive_ack_config() to sl_zigbee_set_passive_ack_config()
• Renamed emAfOverrideAppendSourceRouteCallback() to emberAfOverrideAppendSourceRouteCallback()
• Reinstated emberChildId() after removal in 7.2.0.0
• Reinstated emberChildIndex() after removal in 7.2.0.0
• New in release 7.2.0.0

Zigbee Security Manager Component
The Zigbee Security Manager component provides several APIs, which are implemented by either the Zigbee Classic Key Storage or Zigbee Secure Key Storage component. They provide functionality that includes importing and exporting keys stored by the component, retrieving key metadata, loading keys to use in an operation, and performing cryptographic operations with a loaded key. A full list of these new APIs is available in Zigbee Stack API documentation at https://docs.silabs.com  A subset of those APIs are listed here.

• void sl_zb_sec_man_init_context(sl_zb_sec_man_context_t* context)
• sl_status_t sl_zb_sec_man_import_key(sl_zb_sec_man_context_t context, sl_zb_sec_man_key_t plaintext_key)
• sl_status_t sl_zb_sec_man_export_key(sl_zb_sec_man_context_t context, sl_zb_sec_man_key_t plaintext_key)
• sl_status_t sl_zb_sec_man_hmac_aes_mmo(const uint8_t input, const uint8_t data_length, uint8_t output)
• sl_status_t sl_zb_sec_man_aes_ccm(uint8_t nonce, bool encrypt, const uint8_t input, uint8_t encryption_start_index, uint8_t length, uint8_t* output)

Miscellaneous
bool emberAfClusterEnableDisable(uint8_t endpoint, EmberAfClusterId clusterId, EmberAfClusterMask
mask, bool enable) allows enabling and disabling clusters at runtime, with bool emberAfIsClusterEnabled(uint8_t end-
point, EmberAfClusterId clusterId, EmberAfClusterMask mask) to check whether a cluster is enabled. These APIs require setting EMBER_AF_PLUGIN_ZCL_CLUSTER_ENABLE_DISABLE_RUN_TIME in the ZCL framework core plugin to true in
order to be compiled.

New CLI Commands
New in release 7.2.0.0
Added new CLI command for “bluetooth_on_demand_start” component, ‘plugin ble start’ and ‘plugin ble stop’ to request starting and stopping the Bluetooth stack when needed.

New Platform Support
New in release 7.2.4.0
BRD4195B and BRD4196B radio board support is now available.
New in release 7.2.0.0
MGM240S SiP Module support is now available.

New Documentation
All components have documentation available. If you have an issue seeing the documentation when you select the component in Project Configurator, you can find it on https://docs.silabs.com/

Improvements

Changed in release 7.2.5.0
MAC TX Unicast Retry Counter
In previous versions, the Counter Handler callback for MAC and APS layer EmberCounterTypes concerning packet RX and TX was not being passed the passing proper target node ID or data arguments, and API documentation concerning behavior of certain counters that used these parameters was unclear or misleading. While the signature of emberCounterHandler() has not changed, the way its parameters are populated have changed slightly. Changes around this API include the following:

• Comments around EmberCounterType enums in ember-types.h have been expanded for clarity.

• Node ID parameter to the Counter Handler for TX-related counters now check whether the destination address mode indicates a valid short ID before using it. (If not, no destination address is populated, and a placeholder value of EMBER_UNKNOWN_NODE_ID is used instead.)

• Node ID parameter to the Counter Handler for RX-related counters now reflect the source node ID, not the destination node ID.

• Retry count is not passed as the data parameter for EMBER_COUNTER_MAC_TXUNICAST SUCCESS/FAILED counters as described in ember-types.h in previous versions, but this was never properly populated in previously released versions, so its value in previous releases would always have been 0. This behavior has been clarified in the description of those Em-berCounterTypes. (However, retry count for APS layer retries continues to be populated in the data parameter for
  EMBER_COUNTER_APS_TX_UNICAST_SUCCESS/FAILED counter types, consistent with prior releases.)

• All counters that populate the Node ID or data parameter for the callback have been audited to ensure they pass the expected address (or EMBER_UNKNOWN_NODE_ID if a Node ID was expected but not able to be obtained from the packet), or data as described in revised ember-types.h documentation.

• Counter handler for EMBER_COUNTER_MAC_TX_UNICAST_RETRY now correctly reflects the MAC layer destination node ID and number of retries in its Destination Node ID and data parameters.

• Counter handler for EMBER_COUNTER_PHY_CCA_FAIL_COUNT now provides destination node ID information through the Node ID parameter about the intended MAC layer target of the message that failed transmission.

Intended Behavior Clarification for CSL
Users are reminded that zigbee unsynchronized CSL transmissions are subject to protocol preemption at the radio scheduler. In the SleepyToSleepy applications, BLE can and will preempt a zigbee CSL transmission, which will terminate the transmission. Scheduler preemption is more common for unsynchronized CSL, given that a potentially lengthy wake up frame sequence may be used. Users wishing to adjust transmission priorities may use the DMP Tuning and Testing component to do so. Users may also consult UG305: Dynamic

Multiprotocol User’s Guide for more information.
An issue has been fixed in CSL where a new wake up frame sequence that is received immediately following a previous payload frame would not be recorded correctly. This would result in a missed payload frame.
Changed in release 7.2.2.0

Miscellaneous
Improved the reportable change calculation in the Reporting component by supporting float datatype difference calculation. This is supported using the platform float libraries. If the reportable change calculation involves double or semi precision data types, a set of callbacks (emberAfGetDiffCallback and emberAfDetectReportChangedCallback) are introduced for the user to provide their arithmetic functions.
Updated application framework stack callback function signatures and added missing host framework callbacks. These updates are available at https://docs.silabs.com/
Updated the ezspPollHandler function with updated input arguments, that required updating the EZSP_PROTOCOL_VERSION to 0x0B.
Changed in release 7.2.1.0

Miscellaneous
Improved error handling in sl_zigbee_set_passive_ack_config().

Changed in release 7.2.0.0
Watchdog
Re-enabled the watchdog timer on Zigbee sample applications. We now pet the watchdog once per second in the app.c file for the corresponding project.

Sub-GHz Network Find
Added the CMSIS configuration for channel pages and masks for the sub gigahertz network find component.

Network Steering
Added a validation script for the Zigbee Network Steering component to confirm that the optimized scans option is also enabled if the ‘try all keys’ option is enabled* .
NCP – CPC
Documentation was updated to indicate that the NCP applications need CPC included in RTOS-based applications and must be used with a host application that supports CPC.

Green Power Sink
The GP sink table now stores the group ID for the group cast sink type (EMBER_GP_SINK_TYPE_GROUPCAST) in the respective token. The sink type enumeration was updated to remove the EMBER_GP_SINK_TYPE_SINK_GROUPLIST.

Miscellaneous
Documentation was updated to state that the last two bytes of the received packet in manufacturing mode is not to be interpreted as the FCS / CRC bytes.
Command structs with items of size greater than 4 bytes are now defined as integer arrays instead of integer pointers.

Fixed Issues

Fixed in release 7.2.6.0

context. Other ref. 1255315
1152512| Fixed a potential crash in low-mac-rail when modifying the event in ISR context. Other ref. 1290782

1169966

| Fixed crash issue because of missing NULL_BUFFER check in stack code when allocating new buffer with no resource available.

Other ref. 1255316

1222509

| Fixed an issue where the router/coordinator sends a leave & rejoin request to a non-child polling end device, but the MAC destination is 0xFFFF instead of matching the NWK destination address.

Other ref. 1255320

1225294

| The stack was keeping track of recently seen unicast packets at the NWK layer in an attempt to provide rudimentary duplicate protection. However, unicast messages were being added to this table before checking for successful decryption, which could result in improper duplicate filtering if a device with the same node ID as an existing neighbor used an NWK sequence number that collided with that of the neighbor in question. In resolving this issue, the use of a NWK unicast table for duplicate tracking by the stack was removed as security frame counter checks already provide more robust duplicate filtering without incurring the same risk.

Other ref. 1313461

1225435

| Fixed an issue that caused the radio to enter sleep incorrectly when receiving a broadcast message before the expected macack for a previous unicast.

Other ref. 1240369

1262368| Removed code for deprecated MAC command handling. Other ref. 1265496

1228380

| Fixed an issue where the stack’s NWK layer TX retry queue could get stuck due to a race condition on devices with sub-GHz MAC layer support (dual-band or dual-PHY devices), causing the Retry Queue Overflow counter to accumulate and no messages other than MAC Acks and Beacons to be transmitted until the device was reset.
1232359| Fixed the gppTunnelingDelay parameter calculation in green power client command processing. Other ref. 1254062

1241777

| When operating in a dual PHY configuration, the sub-GHz radio may occasionally time out during an SPI handshake with the EFR32, leading to an assert in phy.c.

Optional recovery code has been put in place to detect and recover from this scenario without asserting. This code can be enabled by setting the p2ForcedRecoveryEnabled boolean to true at runtime.

1254397

| Added mutex protection for App Framework event queue so App Framework event APIs can be called from multiple tasks.

Other ref. 1310479

1258636

| Fixed an issue where the optional optionsMask parameter for “net multi-phy- start” CLI command was being ignored and always treated as 0.

Other ref. 1260609

1259936| Fixed an issue that GP server did not drop frame invalid FC in rare cases. Other ref. 1262543

1266351

| Fixed an issue to improve multi-hop joining of the devices. Upon device announcement, the address pair is added to the address cache.

Other ref. 1270723

1269700| The initialization value for the green power security frame counters in non-volatile memory is set to 0. Other ref. 1273623

1270706

| Fixed an issue that prevented the Green Power cluster to send out ZCL default response for success case when Disable Default Response bit was not set.

Other ref. 1290781

1272280

| As per the SE1.4a specification, a Multi-MAC Joining End Device is required to rejoin on the same interface it has joined and no change of interface (switching from 2.4GHz to Sub-GHz or vice versa) is allowed during rejoining. The rejoin may be initiated as a result of parent loss, or a power recycle of the node. In both of these cases, the stack API emberFindAndRejoinNetworkWithReason is called internally to start the rejoin process, and this API needs the rejoin channel mask as an argument. This channel mask is acquired by the stack by calling function, emberUpdateMultiMacRejoinChannelMaskForSelectionOrJoiningDevice, that is implemented as source and as part of the application project.

A default implementation can be found in the ember-configuration.c as a WEAK function so that a user override is possible.

Other ref. 1272281

---|---

1276049

| If a dual-PHY NCP device were performing an Energy Scan on the sub-GHz band while the 2.4GHz radio was active, large bursts of incoming Beacon traffic in response to incoming Beacon Requests on the 2.4GHz radio channel could occupy lots of the stack’s buffer memory (allocated from the Heap segment) while the many sub-GHz channels were being scanned, which could lead to buffer shortages and EZSP Overflow conditions if the Heap size (which determines how many buffers are available to the system) was not sufficiently large. This Overflow condition could prevent the Scan Complete Handler from reaching the host application, causing the app’s scan state machine to be stuck forever. The Energy Scanning code for dual PHY devices now discards any Beacon packets received on the 2.4GHz radio during the scanning of a sub-GHz channel, thus preventing a large influx of beacons from creating the aforementioned problem.

Note that this does not prevent normal operation of the network on 2.4GHz, as Beacons are only used for potential PAN ID conflict detection when the device isn’t performing an Active Scan, and PAN ID conflicts can still be detected by other routers in the network during this time or by the coordinator once the Energy Scan has completed.

Other ref. 1296650

1258164

1276806

| Triggering a child removal operation for a sleepy end device child when an Association Response or Rejoin Response is still pending delivery for that child can result in two erasures for the same child entry, leaving the emberChildCount() off by -1. If this is the last child in the table to be removed, this can lead to an underflow of the child count, which inhibits any further join/rejoin attempts by any end devices until a reset or LeaveNetwork is performed.In certain releases, this may result in an assert failure (citing child.c).

Other ref. 1277341

1277012

| Fixed an issue where, if the child table was full and an existing child of the local device tried to rejoin, the rejoin was incorrectly rejected, causing the child entry to be removed and forcing the child to rejoin again to get reassociated with that parent.

Other ref. 1277346

1289413

| Fixed an issue where, if Fragmentation plugin miscalculated available payload for a unicast fragment, it could send more data to the NCP than would fit in a single packet after all stack overhead was accounted for, and this could lead to memory corruption in the NCP that triggered assert failures or other unexpected behavior.

Other ref. 1284463

1293923

| Fixed an issue where the network steering plugin could act as if the device was already on a network when it was not, being stuck in this invalid state until reset.

Other ref. 1294662

1296881

| Fixed an issue where the duty cycle aging data was being mistakenly cleared for all end device children instead of just the new device after a new end device joined on the sub-GHz band.

Other ref. 1309332

Fixed in release 7.2.5.0

sub ghz interface during network formation because of the previous network leave.
1198598,

1196698

| Fixed spurious frame pending bit set when there is no data pending

1215648

| Calling emberRemoveChild() during a secure rejoin attempt by an end device can potentially lead to an extra decrement of the Child Count, potentially leading to a Child Count of -1 (255), inhibiting end devices from joining/rejoining due to an indicated lack of capacity in the Beacon.
1215649| Child Table search functions within the stack are inconsistent in use of 0x0000 versus 0xFFFF for node ID return value representing invalid/empty entries, leading to problems checking for unused entries in APIs like emberRemoveChild().
1215650| Destination and PHY Index provided in EmberExtraCounterInfo struct as part of emberCounterHandler() may be incorrect for MAC TX Unicast counter types.
1215652| Outgoing Beacon packets should trigger EMBER_COUNTER_MAC_TX_BROADCAST instead of EMBER_COUNTER_MAC_TX_UNICAST.
---|---
1215653| Sending data poll when packet buffers have been depleted to near zero can lead to a bus fault.
1221878| Rejoining an end device a with previous NWK key after a key change caused the end device to mistakenly be put into the neighbor table and treated like a router instead of an end device child, interfering with proper message delivery.
1240390| ZDO Bind/Unbind Requests refused for access/permission reasons should return EMBER_ZDP_NOT_AUTHORIZED status rather than EMBER_ZDP_NOT_PERMITTED status as per Zigbee specifications.
1240620| Fixed an issue that caused the end device move state machine to stop attempts to rejoin the network under heavy traffic conditions.

Fixed in release 7.2.2.0

architectures.
754110| The reportable change calculation is updated to support float calculation using platform-dependent float library.
1026022| Fixed an issue that was affecting the UART baud rate when setting the CTUNE value on NCP from host using set the EZSP_CONFIG_CTUNE_VALUE command.
1026760| Fixed an issue that was letting the dual PHY-capable end devices to rejoin on 2.4 GHz interface after associating on sub gigahertz interface.
1030357| Fixed an issue with “plugin mfglib set-options” command returning an error in manufacturing mode by registering the callbacks for setting configuration values.
1063627| Updated emberAfRemoteSetBindingCallback() and added missing callback for the host architecture.
1079388| Fixed an issue where the EMBER_AF_PLUGIN_NETWORK_CREATOR_SECURITY_BDB_JOIN_USES_INSTALL_CODE_KEY option in the

Network Creator Security component is overwritten when the “plugin network- creator-security open-network” or “plugin network-creator-security open-with- key” CLI commands are invoked.

1087526| Fixed some Coverity issues.
1096375| Fixed an issue where the emberHmacAesHash API had been unavailable for application builds since EmberZNet 7.2.0.
1097258| Fixed an issue that affected Green Power Server test cases 4.5.2.2, 4.5.2.3, 4.4.3.1 and 4.4.2.8.
1099131| Fixed an issue that was preventing the server to send a termination message to a client if it received a malformed certificate during key establishment.
1103117| Fixed an issue that was causing the Green Power Server to remain uninitialized after a network leave and re-association of the Green Power Combo application.
1104793| Fixed an issue that was causing an assert failure for the scenario of ongoing data transactions on both the interfaces of dual PHY stack.
1106002| Fixed an issue that affected Green Power server test case 4.4.1.7 steps 1-2.

Fixed in release 7.2.1.0

source Id are added to the Green Power cluster command handlers.
651930| Removed legacy NCP callback emberAfPluginConcentratorBroadcastSentCallback().
621144| Added support for GPD switch on single-button devices such as BRD4183A.
648906| Reimplemented emberChildId().
659010| Reimplemented emberChildIndex().
727076| Fixed an issue that could result in diagnostics function to use incorrect Endpoint to update LQI, RSSI, and average MAC retry.
746260| Added support for Smart Energy KEEP-ALIVE cluster.
1026760| Fixed issue where End Device could rejoin using incorrect interface.
1031169| Fixed an issue where a paired GPD could be removed irrespective of presence in translation table.
1031241| Improved validation of reserved Green Power address.
1063525| Fixed an issue that could result in an invalid verify link key exchange to succeed even when Trust Center used an incorrect link key.
1067877| Fixed an issue whereby Scene information was incorrectly removed when adding a new Scene with the same GroupId and SceneId.
1068968| Improved handling of child table timeouts in emberGetChildData().
1069245| Improved device table plugin prototype emberAfTrustCenterJoinCallback() to fix compilation errors.
1074378| Fixed an issue that allowed dual-band End Devices to incorrectly join non-preferred channel yet not disallow re-joining PAN on channel.
1075748| Fixed an issue that caused an EEPROM compilation error when removing CLI.
1077176| Fixed an issue that could cause NCP to fail on startup due to inter- PAN MAC filter (0x36) as a result of an incorrect MAC filter table size.
1081511| Fixed an issue preventing the usage of correct type 4 (OOB) key for commissioning.
1082602| Fixed an issue that could cause packets that fail to decrypt during commissioning to be forwarded as commissioning notifications with authentication failed flag set.
1083200| Fixed an issue where Message Integrity Codes where not being copied back to host in emGpCalculateIncomingCommandMic().
1083835| Fixed sink table read command handling for the gpSharedKey type that fixed the GP Test Case failure 4.4.4.3.
1085137| Fixed an issue where the Sink could remove all entries for app mode 2 and matching EUI64s.
1087618| Fixed compilation issues due to missing Green Power Adaptor header files not being included in release.
1092779| Fixed issue that was preventing an End Device to process a ZDO Leave Request from a non-parent network node.
1091792| Improved error handling and return code of emberGetCurrentSecurityState().
1087567| The ncp sample application “ncp-uart-hw-dual-phy” is not supported by the development board BRD4155.
1089841| An issue that caused the emberFindAndRejoinNetworkWithReason to return busy status for an end device move procedure on sub gigahertz interface is fixed.
1094643| The function prototype for emGpOutgoingCommandEncrypt is removed from the green-power-server.h because it is only internal to the green-power- security.c file.
1097536| Fixed an issue that caused multi-MAC coordinator to use an incorrect MAC interface to send unsolicited rejoin response to its child during address conflict resolution. This issue caused ZCP Test Case 10.12 to fail on sub- gigahertz.

Fixed in release 7.2.0.0

server.c where the second input parameter of the invoked function emberAfContainsServer() had incorrectly referenced the cluster ID instead of the attribute ID.
ID #| Description
---|---
657626| OTA update with page request can now handle up to EMBER_AF_PLUGIN_EEPROM_PARTIAL_WORD_STORAGE_COUNT number of out-of-order write operations without an assert.
684653| Fixed an issue that caused network-steering start to add TC task without checking network state and steering state.
688985| Fixed issue where the joining device joined the network with wrong Extended Pan ID, which would result in a Pan ID conflict.
742167| Fixed an issue that caused the discrepancy of Sequence Number field in ZLL message pairs (request – response).
755880| Changed GBCS event IDs to have correct values from the spec.
756571| Fixed the issue that caused emberPacketHandoffIncoming to receive bad index for EMBER_ZIGBEE_PACKET_TYPE_NWK_DATA/EMBER_ZIGBEE_PACKET_TYPE_NWK_COMMAND packets
760759| An issue has been fixed where certain modules, such as MGM210, can be used to generate and build an application that uses LEDs and buttons, such as DynamicMultiprotocolLight. Apps that use these peripherals are not supported for modules that lack dedicated lines for using both buttons and LEDs.
763728| Handled the insufficient space case when reading attributes.
819117| Fixed an issue that caused parent not to check RX on idle bit when responding to a rejoin request from an unknown device
824361| Fixed typedef warnings when building “ncp-uart-hw” sample app with IAR.
825902| Resolved an issue where association, rejoin, and node ID updates may end up with a node being assigned an invalid address.
829607| Fixed an issue of end device configuration overriding the user- provided network address alias value to its own node ID when multicast and broadcast messages were originated by the application.
841499| Fixed an issue where a newly joined device can sometimes not get added to the child table if its IEEE address is not known.
842361| Fixed a parsing issue caused by incorrect min length array of OTA cluster commands.
844016| Fixed an issue that caused compilation errors on BRD4183C by excluding this board for some apps. *
850747| Watchdog is now enabled by default on all Zigbee EmberZNet sample applications.
1017165| Fixed an issue that caused Force Sleep & Wake Up component to depend CLI component
1021877| Fixed issue in DynamicMultiprotocolLight and DynamicMultiprotocolLightSed projects where scheduler was not properly being locked from the CLI task context when the number of CLI command arguments was less than 2.
1021884| Fixed an incorrect alignment for an indexed token in wwah-server- silabs component.
1024651| Fixed an issue where emberAfMessageSentCallback() was not called if child had been removed during the transmission.
1026622| Fixed an issue that caused missing last byte with packet-handoff when EMBER_MANGLE_PACKET is used.
1027200| Fixed an issue where the Key Establishment component sent NO_RESOURCES instead of the required BAD_MESSAGE when an initiator with unknown EUI64 attempted key establishment.
1030940| Fixed issue in which really high APS message frequency towards SED devices could result in unprocessed (re)join requests.
1042022| Fixed issue where the Key Establishment component didn’t check for minimum command request and command response length.
1058984| The templated callback for message_sent would be called multiple times for fragmented packets, instead of once after all fragments get sent. This was a change in behavior starting in Zigbee EmberZNet SDK 7.0 and has been addressed in SDK 7.2.0 and later. The templated callback is now only invoked once per fragmented transmission.
1060156| Fixed an issue where TC did not send NWK Key when other devices were scanning.
1061948| The issue of a lower ZCL sequence number for initiate key establishment command that follows a read attribute is fixed.
1066234| Fixed an issue that caused the key establishment state machine to get stuck if ConfirmKeyDataResponse is lost over the air.
1066947| Fixed issue where scan procedure in form-and-join code could corrupt memory used by other buffers. This manifests as either a bus fault, usage fault or a packet buffer assert.
1068035| Fixed a potential issue that caused a linking error when customer wants to use green power client or server only for their NCP application.
ID #| Description
---|---
1068055| The following ZCL Basic cluster optional attributes, which were missing from the XML definition file, have been added: 0x000C Manufacturer Version Details, 0x000D Serial Number, and 0x000E Product Label.
1069727| Fixed an uninitialized variable MISRA error in indirect queue.c file.
1077662| Fixed issue where the upgrade rule did not fire correctly for the Zigbee RTOS task stack size configuration. It is now specified in bytes instead of words.

Known Issues in the Current Release

Issues in bold were added since the previous release. If you have missed a release, recent release notes are available on https://www.si- labs.com/developers/zigbee-emberznet in the Tech Docs tab.

N/A

| The following apps/components are not supported in this release

·         NCP Sleepy

·         EM4 support

|

Features will be enabled in subsequent releases.

193492

| emberAfFillCommandGlobalServerToClientConfigureRe porting macro is broken. The filling of buffer creates incorrect command packet.| Use the “zcl global send-me-a-report” CLI command instead of the API.
278063| Smart Energy Tunneling plugins have conflicting treatment/usage of address table index.| No known workaround

289569

|

Network-creator component power level picklist doesn’t offer full range of supported values for EFR32

| Edit the range <-8..20> specified in the CMSIS comment for EMBER_AF_PLUGIN_NETWORK_CREATOR_RADIO_P

OWER in the