Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EZSP v14 (EZSP PROTOCOL VERSION 14) support in bellows? #632

Closed
Hedda opened this issue Jun 24, 2024 · 1 comment
Closed

EZSP v14 (EZSP PROTOCOL VERSION 14) support in bellows? #632

Hedda opened this issue Jun 24, 2024 · 1 comment

Comments

@Hedda
Copy link
Contributor

Hedda commented Jun 24, 2024

Feature request and issue tracker. Following puddly's work-in-progress pull request for initial EZSP v14 support -> #631

EZSP protocol version incremented to EZSP v14 in Zigbee EmberZNet v8.0.0.0 + also migrated from Gecko SDK to Simplicity SDK.

I understand EZSPv14 and migration to Simplicity SDK (Simplicity SDK 2024.6.0) could mean breaking changes? As per comment:

"Most EMBER_ constants have been renamed to SL_ZIGBEE_ and must be renamed in your manifests accordingly. This is a fairly large breaking change."

References:

Zigbee EmberZNet Version 8.0.0.0 SDK Release Notes Q2/2024 (June 2024)

  • Zigbee
    • Zigbee re-architecture to support stack and framework to be fully RTOS based
    • Memory management update
    • New clock manager component integrated in Zigbee applications
    • Support Sleepy NCP use case
    • Zigbee Green Power (ZGP / Zigbee GP) Revision 1.1.2
    • Removed support for Series 0/1 (making EFR32MG1x deprecated but till supported EmberZNet v7.4.x.x with bug-fixes only)
    • Added support for new platform xG26 (EFR32MG26)
    • Alpha : Added support for Series 3 (xG3x family, e.i. EFR32MG3x series)
    • Alpha: New application for Zigbee Unified Test Harness
  • Multiprotocol
    • Alpha: Support for OpenWRT on host processor of multiprotocol RCP solution
    • Alpha: Support for Concurrent Zigbee and Matter over OpenThread, with DMP BLE

New Components in release 8.0.0.0

• Inter Process Communication
Added a new component named “zigbee_ipc”.
This component adds support for interprocess communication on a Zigbee RTOS device.
• Byte utilities
Added a new utility component named “byte_utilities” outside Zigbee protocol for data store and fetch routines.
As part of that, moved the header file byte-utilities.h from protocol/zigbee/stack/include/ to util/plugin/byte_utilities.
Since this is not specific to Zigbee, the API has been renamed, from sl_zigbee_reverse_mem_copy() to sl_util_reverse_mem_copy().
• Separated a new component "Zigbee System Common (App Framework Task)" from Zigbee System Common, to better allow for apps that do not bring in the full ZCL and app framework but still use the app framework's RTOS task.
• RTOS Configurations

New APIs in release 8.0.0.0

• A new event initialization function sl_zigbee_af_isr_event_init is added for the events that can be activated in ISR.
Note that with this release the APIs have been renamed. For details, see the Zigbee v8.0.0 section of https://docs.silabs.com/.

New Application in release 8.0.0.0

• Zigbee Unified Test Harness SoC application is introduced as a new application in this release.
• Added a new ZigbeeMinimalRtos app to Zigbee offerings. This is a test application with a bare minimum RTOS based Zigbee stack. This application is non-compliant since it does not have all the necessary component and configurations of a fully functional Zigbee application.
• A new configuration for the SPI based NCP as a sleepy NCP is introduced in this release. This serves the use case of a host-SPI NCP configuration to be used as a sleepy node in the network. The host controls the sleep and wake up of the SPI NCP. See AN711: SPI Host Interfacing Guide for Zigbee for more details.

New Platform Support in release 8.0.0.0

• New hardware xG26 and xG22E.
• new platform component, Clock Manager, is integrated into all Zigbee sample applications for clock configuration.

New in Gecko Platform Version 5.0.0.0

  • Migration to Simplicity SDK Suite
  • Removed support for Series 0/1
  • Peripherals
  • New API names introduced for low-level drivers (with compatibility layer for old names)
  • Services
    • Memory Manager, APIs to manage embedded dynamic memory allocations
    • Clock Manager, for clock tree initialization
    • Event System, for inter-process communication
    • Interrupt manager, APIs to manage embedded interrupts
    • APIs for accessing value of tokens added to Token Manager
  • CPC
    • Small improvement and bug fixes
  • Security
    • Mbed TLS upgraded (to version 3.5.0)
  • RAIL 5.0.0
    • Added support for collision detection feature on the EFR32xG25 parts
    • Added support for additional Coex TX and RX metrics events to RAIL coexistence utility
    • Updated some RAIL APIs to better prepare for future API changes while retaining backwards compile-time compatibility
  • Other Components
    • Compilers upgraded (to GCC 12.2.1 and IAR 9.40.1)

image

Note! EmberZNet 8.0.0.0 and Gecko Platform remove support for EFR32 Series 0/1 (e.i. EFR32MGx and EFR32MG1x) so need to use separate SDKs for Series 0 & 1 and Series 2 & 3 Starting in Q2 2024 (June 2024) as the new Gecko Platfoprm and SDK are designed specifically for our EFR32 Series 2 and upcoming Series 3 devices only.

"Meanwhile, our Gecko Software Development Kit (GSDK) will continue to be available for users of our Series 0 and Series 1 devices. The Gecko SDK will continue to support all Series 0 and 1 devices with no change to the long-term support, maintenance, quality, and responsiveness provided under our software policy.The new SDK will branch from Gecko SDK and begin to offer new features that help developers take advantage of the advanced capabilities of our Series 2 and 3 products."

@puddly
Copy link
Contributor

puddly commented Jul 23, 2024

#631

@puddly puddly closed this as completed Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants