zigbee porting on a new microcontroller/RF chip
May 19, 2017
Product
zigbee porting is the integration of the zigbee network and application layer stack from one microcontroller/RF chip combination to another. zigbee po...
zigbee porting is the integration of the zigbee network and application layer stack from one microcontroller/RF chip combination to another. zigbee porting on a new microcontroller is possible if it is compatible with IEEE 802.15.4 standard and supporting minimum required footprint (i.e. SRAM). Following standard Open System Interconnect (OSI) reference model, the zigbee protocol stack is structured in layers. The first two layers, physical (PHY) and media access (MAC) are defined by the IEEE 802.15.4 standard and layers above them are defined by the zigbee alliance.
[Figure 1 | zigbee Architecture]
Due to the differences in microcontroller and RF chips, i.e. MAC implementation, platform-dependent modules (power management, OS, security, timer resolution, memory management), each microcontroller/RF chip combination requires its own zigbee stack. This means a zigbee stack from one microcontroller/RF chip combination will not work directly on a new combination and will require zigbee porting.
zigbee porting approaches
zigbee porting on new microcontroller/RF chips mainly covers two major tasks.
- Mapping zigbee network layer calls with IEEE 802.15.4 MAC calls (i.e. MCPS, NLDE, MLME, NLME). This is the most challenging part of zigbee porting and requires proper planning.
- Mapping zigbee platform dependent modules with new platform.
Considering the challenges involved in zigbee porting, two most followed industry wide approaches are covered as below.
1. Do not touch zigbee stack and modify MAC calls
This approach requires changes in MAC?s MCPS/MLME implementation as per zigbee network NLDE/NLME design. Figure 2 provides an overview of this approach.
[Figure 2 | zigbee Porting Approach 1]
Advantages and disadvantages of this approach are covered below.
Advantages:
- Fewer chances of failure in zigbee certification testing
- Zigbee stack remains unmodified
- Save overall porting effort and time
- Porting can be done without prior zigbee stack experience
Disadvantages:
- Changes required in MAC layer call sequence and design
- Porting not possible without prior MAC stack experience
2. Do not touch MAC stack and modify zigbee network layer calls
This approach requires changes in zigbee nework NLDE/NLME implementation as per MAC MCPS/MLME design. Figure 3 provides an overview of this approach.
[Figure 3 | ZigBee Porting Approach 2]
Advantages and disadvantages of this approach are covered below.
Advantages:
- MAC/PHY layer stack remains unmodified
- Porting can be completed without MAC/PHY source code
Disadvantages:
- High chances of failure in zigbee certification testing
- Changes required in zigbee network and application layer stack
- Overall porting time gets increased
- Porting not possible without prior zigbee stack experience
zigbee certification is part of zigbee porting validation. All zigbee base products required to pass zigbee certification tests to ensure its conformance to zigbee standards and interoperability between different zigbee base devices.
Today, zigbee plays key a role in IoT solutions. Its applications include domains such as healthcare, consumer electronics, home automation, industrial control, and many more. In recent VOLANSYS case studies, it has offered zigbee based solutions to multiple clients cross varied industries.