EFR32 Migration Guide for Proprietary Applications#

This section replaces AN1244: EFR32 Migration Guide for Proprietary Applications. Further updates to this application note will be provided here.

This application note presents a high-level collection of elements that differentiate Wireless MCU EFR32 generations from each other, as well as more detailed descriptions of features exclusive to the newest EFR32 generations. This information is designed to support those considering migrating proprietary applications from one EFR32 generation to another.

Proprietary is supported on all EFR32FG devices. For others, check the device's data sheet under Ordering Information > Protocol Stack to see if Proprietary is supported. In Proprietary SDK version 2.7.n, Connect is not supported on EFR32xG22.

Introduction#

This application note uses the following terms to classify devices in accordance with the EFR32 device datasheets:

  • Device Configuration: EFR32xG1, EFR32xGx1, EFR32xGx2, EFR32xGx3, EFR32xGx4, and EFR32xGx5 devices

  • Series: EFR32xG1x (including EFR32xG1 devices) and EFR32xG2x devices

  • Device Family: EFR32MGxx, EFR32BGxx, EFR32FGxx, and EFR32ZGxx devices

Device generations are defined as the combinations of the device configuration and series. The complete list of EFR32 device generations is: EFR32xG1, EFR32xG12, EFR32xG13, EFR32xG14, EFR32xG21, EFR32xG22, EFR32xG23, EFR32xG24, and EFR32xG25.

For more information on the existing combinations of EFR32 generations and families, visit silabs.com.

This application note discusses differences among the Series 1 and Series 2 EFR32 Wireless MCU generations that are relevant to proprietary wireless applications. "Proprietary" refers to applications based on RAIL (Radio Abstraction Interface Layer) or Connect, and typically implementing a custom radio configuration not defined by any wireless protocol standard. The target audience for this perspective consists of developers who are migrating existing EFR32 proprietary wireless applications to alternative EFR32 devices. This insight is also of interest to developers of new EFR32 proprietary solutions. However, this document is not intended to guide the migration of existing proprietary applications from non-EFR32 Silicon Labs wireless devices (EZRadioPRO, Si10xx, EZR32xG, and so on).

For developers migrating from EFR32 Series 1 to Series 2, AN918.2: Series 1 to Wireless Gecko Series 2 Compatibility and Migration Guide offers essential and extensive guidance for this endeavor from a platform perspective. Proprietary wireless applications (on any EFR32 device) additionally rely on RAIL or Connect as well as the Radio Configurator (a tool within Simplicity Studio) to manage and initially configure the integrated radio transceiver.

At a high level, RAIL and the Radio Configurator abstract away most differences that exist between EFR32 devices. The Connect stack and application framework leverage RAIL implicitly, and as such also benefit from (and further extend) abstraction to the application from most variation across potential target EFR32 devices. However, some device capabilities vary enough - or some features are unique enough - that they cannot simply be normalized "under the hood" of RAIL and/or the Radio Configurator. In these cases, customers must consider the impact of these generation-specific differences when planning a migration path for EFR32 proprietary wireless applications. Often, these distinguishing characteristics may in fact be enhancements that invite the porting of existing proprietary applications to new, more capable, EFR32 devices. More information on these differences relevant to proprietary wireless applications is presented in the following sections:

Note: This application note focuses on device-specific variations and where to find information on how RAIL accommodates them. As stated above, Connect abstracts most of these differences away. In the few cases where it is appropriate, they will be highlighted in this document.