Zigbee and Thread Wireless Knowledge Base

Zigbee & Thread Knowledge Base

Publish

Steps to Zigbee Certification for Wireless Mesh Products

ADKates | 07/205/2017 | 02:35 PM
Zigbee Alliance Product Certification

Silicon Labs provides a Zigbee Alliance Certified stack, but the Zigbee Alliance also provides a path for product certification as a Zigbee Compliant Platform or Zigbee Certified Product.

We're sharing details here of the Zigbee certification process provided by the Zigbee Alliance for your information and convenience. The Zigbee Alliance my change these details at any time. If you have questions about Zigbee certification or the certification process, we recommend contacting the Zigbee Alliance directly at certification@zigbee.org.

Certification: Getting Started

Steps to Certification

The first step of the certification process is to submit your product to an authorized test service provider. A list of authorized providers can be found on the Zigbee Alliance website here.The provider will send a test report directly to us when testing is complete – no need to forward it yourself.

The second step in the process is to submit an application online via the Zigbee Alliance Certification Web Tool.

If you don’t already have a Zigbee Alliance user account (separate from your Workspace account), you can sign up as a new user by clicking the “Sign Up” link. When requesting a new account, be sure to sign up with a company e-mail address (not Gmail, Yahoo, 163.com, or other free e-mail domains).

For detailed instructions on creating and submitting an application in the Certification Tool, a user information guide is available here.

After you complete and submit your application, the Zigbee Alliance will review it and send you either an approval notice or feedback via e-mail.

Tips and Pointers

Have all documents ready:

To ensure prompt processing of your application, remember to upload all required documents before clicking the “Submit” button.

All applications should include completed Declaration of Conformity (DoC) and Protocol Implementation Conformance Statement (PICS) documents

Ensure consistency across all documents submitted:

A common mistake we see is inconsistent information across the web application, DoC, PICS, and test report – save on processing time by double-checking these entries!

Ensure that all hardware/software version fields match the versions declared in the test report.

Make sure that the compliant platform declared in the application is consistent with the DoC and test report (or the original certified application, for Certification by Similarity requests).

Tips for completing the DoC:

The latest DoC template can be found on Workspace here.

Remember to have both signature blocks (applicant and test house) signed and dated.

Tips for completing the PICS:

Each Zigbee standard has its own PICS document, available with its respective specification document package in the Zigbee Alliance Member’s Area (Workspace).

Instructions for completing PICS documents are found at the beginning of each document template.

For Zigbee (3.0) applications, multiple PICS documents are required (base device behavior + individual cluster PICS) – these may be uploaded to the Certification Tool in a single ZIP archive.

Make sure that all mandatory PICS items are supported!

Tips for the Zigbee Test Tool (in-house pre-testing):

Tips for PICS and ZTT (right panel: PICS):

Before starting, clear the previous loaded ZTT PICS (right panel: Clear).

In order to generate a PICS file, the ZTT Tool format uses the PICS GUI (right panel: PICS).

Do not forget to save from time to time (right panel: Save).

If you need to share the PICS with a third party (right panel: Export PICS).

If somebody made the test plan for you (right panel: load PICS).

Finally, a list of test cases is almost ready for your device, let’s build the test plan (right panel: Build Test List).

Tips for PIXIT: There are plenty of options in this panel (right panel: PIXIT).

Tips for if the unit is not joining the Network:

Under “Common” expander be sure that the “Channel” has the proper value (this is applicable when the ZTT is forming the NWK)

Under “Common” expander be sure that the NWK PANID has the correct value.

Under “Common” expander be sure that the DUT MAC has the correct value.

Tips if the DUT is not responding application unicast messages:

Under “Common” expander be sure that the “DUT End Point” has the correct value.

Tips for if you want to test a cluster or a custom test case:

When the DUT is a ZC, start the DUT and run the test case “Test Cases: BDB->CS-NFS-TC-05B” (you can stop the ZTT just after the ZTT has joined the DUT NWK).

When the DUT is a ZR/ZED, start the DUT and run the test case “Test Cases: BDB->CS-NFS-TC-06”.

Now the ZTT is in the DUT NWK and you can run your custom test case.

Certification Reference Material from the Zigbee Alliance

Certification Resources for Members

Zigbee (3.0) Test Tool

Zigbee Green Power Test Harness

Certification Web Tool
How to setup OTA Server and OTA Client on WSTK+4151 radio boards?

Lesun | 07/186/2017 | 08:57 AM
Question

How to setup OTA Server and OTA Client on WSTK+4151 radio boards?
Answer

Here are some instruction about how to setup an OTA Server and OTA Client by WSTK+4151 radio boards. The intention of this article is to setup an OTA Server and OTA Client quickly. We are using the v5.10 EmberZnet stack to do the test. If you use later stack you will need configure the .hwconf for your project, which we won't discuss it here. More information about OTA setup please refer to AN728 OTAClientServerSetup.

In this testing, OTA Server works in NCP mode, we use WSTK+4151 radio board as NCP, and build the Host by Cygwin in Windows OS. The OTA file is storage at Host side. The OTA Client works in SOC mode, it downloads the OTA file to external SPI flash after detect a newer image in OTA Server.

OTA Server: NCP mode

Firstly, download standalone Bootloader: serial-uart-bootloader.s37 and NCP firmware: ncp-uart-rts-cts-use-with-serial-uart-btl-5.10.0.s37 to a WSTK kit.

Then create the Host: Z3GatewayHost as follows:

Create a Z3GatewayHost sample, then modify the Z3GatewayHost.isc file.

In “ZCL clusters” tab.

In the Cluster List pane on the bottom left, expand the General group. Check the Over-the-Air Bootloading Cluster server checkbox.

In “Pringting and CLI” tab.

In the Debug Printing section, check the “Enable Debug Printing” checkbox.

Expand the Cluster Debugging group.

Check the Compiled-in and Enabled at startup checkboxes for the Over-the-Air Bootloading cluster.

In the “HAL Configuration” tab,

Make sure the appropriate chip (EFR32-EZSP) is selected.

Under the Platform Configuration section, open the Host drop-down menu and select UNIX Host.

In the “Plugins” tab. Make sure the following OTA plugins are checked.

OTA Bootload Cluster Common Code

OTA Bootload Cluster Server

OTA Bootload Cluster Server Policy

OTA Bootload Cluster Storage Common Codes

OTA POSIX Filesystem Storage Module

Save your configuration (ISC) file.

Click Generate.

Build the Z3GatewayHost in Cygwin.

cd C:\SiliconLabs\SimplicityStudio\v4\developer\sdks\gecko_sdk_suite\v1.1\app\builder\Z3GatewayHost

make

Flash bootloader and NCP firmware to the WSTK kit.

Run Z3GatewayHost in Cygwin: ./build/exe/Z3GatewayHost.exe -p com37

OTA Client: SOC mode

Secondly, flash the Bootloader: app-bootloader-spiflash.s37 to the WSTK kit. Then create an application as OTA Client.

Create a blank project, rename the project as “OTAClient”, modify modify the OTAClient.isc file as follows.

In “ZCL clusters” tab.

In the Cluster List pane on the bottom left, expand the General group. Check the Over-the-Air Bootloading Cluster client checkbox.

In “Znet Stack” tab.

Select the “ZigBee Device Type” as Router. You can also select other Device Type.

In “Pringting and CLI” tab.

In the Debug Printing section, check the “Enable Debug Printing” checkbox.

Expand the Cluster Debugging group.

Check the Compiled-in and Enabled at startup checkboxes for the Over-the-Air Bootloading cluster.

In the “HAL Configuration” tab,

Make sure you select the right architecture.

Click the Bootloader drop-down menu and specify Application for EFR32MG1.

In the “Plugins” tab. Make sure the following OTA plugins are checked.

OTA Bootload Cluster Client

Unselect the “Set Image Attribute (35x SOC only)”

OTA Bootload Cluster Client Policy

Check the Perform EBL Verification (SOC Only) checkbox.

In the Firmware Version text entry box, set the value to 1.

OTA Bootload Cluster Common Code

OTA Bootload Cluster Storage Common Code

OTA Cluster Platform Bootloader

OTA Simple Storage EEPROM Driver

Check the “SOC Bootloading Support” checkbox.

Modify the “OTA Storage End Offset” from 204800 to 524288. Make sure it has enough space to storage OTA file.

Unselect the “EEPROM Device Red-modify-write Support”.

EEPROM

OTA Simple Storage Module

Save your configuration (ISC) file.

Click Generate.

Build the OTAClient in Appbuilder.

Flash application bootloader and OTAClient.s37 (First Client Image) to another WSTK+4151 kit.

Using the OTAClient.isc file to build the Second Client Image

Modify the Firmware Version in “OTA Bootload Cluster Client Policy” plugin,

In the Firmware Version text entry box, set the value to 2.

Click Generate.

Build the OTAClient in Appbuilder.

You can find an OTAClient.ota in your build directory. This is the Second Client Image for OTA.

Form network and do OTA Test.

Copy the OTAClient.ota to Z3GatewayHost/ota-files/ folder in Cygwin

Lunch the Z3GatewayHost: ./build/exe/Z3GatewayHost.exe -p com37

Form network and pjoin at Z3GatewayHost side

plugin network-creator start 1

plugin network-creator-security open-network

Join the network at OTAClient side

Network join <Channel> <TxPower> <PANID>

After the Client join the network, it will discovery OTA Server and query the New Image for download.
What are the differences of IPv6 address in Thread network?

Lesun | 07/186/2017 | 08:20 AM
Question
What are the differences of IPv6 address in Thread network?
Answer
When a device joined a Thread network, we can type CLI command "info" in console to get the following info of this node.

network status: 0x03 eui64: >000B57FFFE315B35 network id: br-2BCB node type: 0x02 extended pan id: >34F48C11FEC2D244 pan id: 0xED1B channel: 24 radio tx power: 4 dBm ula prefix: fd44:d2c2:fe11::/64 local ip 0: fd44:d2c2:fe11:0:9624:c64:2d70:45 local ip 1: fe80::cc82:af87:fe43:5177 local ip 2: 2001:db8:385:9318:55af:f90b:971b:b154

What are the differences of these three local IP addresses?

* IP 0 contains the mesh-local 64 address of the node.
* IP 1 contains the link-local 64 address of the node.
* IP 2 and greater will return any global unicast addresses (GUAs) of this node.

Mesh-Local is for sending a message anywhere on the entire mesh.Thread uses mesh-local addresses to reach Thread interfaces within the same Thread Network Partition.

Link-Local is nodes within a single hop. Thread uses link-local addresses to reach Thread interfaces within range of a single radio transmission. Thread devices use link-local addresses to discover neighbors, configure links, and exchange routing information. A Thread device MUST assign a link-local IPv6 address where the interface identifier is set to the MAC Extended Address with the universal/local bit inverted.

Global Unicast Address is assigned by the Border Router so this is generally used from outside the mesh. Thread interfaces MAY assign additional IPv6 unicast addresses for valid prefixes assigned to the Thread Network. Such addresses can be used to enable communication with devices outside the Thread Network Partition.

This is briefly explained in network-management.h and please refer to Thread specification for more information.

Zigbee & Thread Knowledge Base

Zigbee & Thread Knowledge Base

Steps to Zigbee Certification for Wireless Mesh Products

Zigbee Alliance Product Certification

Certification: Getting Started

Tips and Pointers

Certification Reference Material from the Zigbee Alliance

How to setup OTA Server and OTA Client on WSTK+4151 radio boards?

Question

Answer

What are the differences of IPv6 address in Thread network?

Question

Answer

Tags

Top Authors

Archives