The information in this KBA has been supplanted by AN1118: Certifying Zigbee 3.0 Devices. Please refer to that document for details about the Zigbee certification process.
How to setup OTA Server and OTA Client on WSTK+4162 radio boards?
Answer
Here are some instruction about how to setup an OTA Server and OTA Client by WSTK+4162 radio boards. The intention of this article is to setup an OTA Server and OTA Client quickly. We are using the v6.7.4 EmberZnet stack to do the test.More information about OTA setup please refer to AN728OTAClientServerSetup.
In this testing, OTA Server works in NCP mode, we use WSTK+4162 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: bootloader-uart-xmodem.s37 and NCP firmware: ncp-uart-hw.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 “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:\SimplicityStudio\v4_workspace\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, create an application as OTA Client.
Create a Z3light sample, modify the Z3light.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 “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.
Set the “EEPROM Device Read-modify-write Support” to false.
EEPROM
OTA Simple Storage Module
Save your configuration (ISC) file.
Click Generate.
Build the OTAClient in Appbuilder.
Flash application bootloader(bootloader-storage-spiflash-single.s37) and Z3light.s37 (First Client Image) to another WSTK+4162 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 project.
You can find an Z3light.ota in your build directory. This is the Second Client Image for OTA.
Form network and do OTA Test.
Copy the Z3light.ota to Z3GatewayHost/build/exe/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 Z3light side
plugin network-steering start 0
After the Z3light 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?
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
Steps to Zigbee Certification for Wireless Mesh Products
The information in this KBA has been supplanted by AN1118: Certifying Zigbee 3.0 Devices. Please refer to that document for details about the Zigbee certification process.
AN1118: Certifying Zigbee 3.0 Devices
How to setup OTA Server and OTA Client on WSTK+4162 radio boards?
Question
How to setup OTA Server and OTA Client on WSTK+4162 radio boards?
Answer
Here are some instruction about how to setup an OTA Server and OTA Client by WSTK+4162 radio boards. The intention of this article is to setup an OTA Server and OTA Client quickly. We are using the v6.7.4 EmberZnet stack to do the test.More information about OTA setup please refer to AN728OTAClientServerSetup.
In this testing, OTA Server works in NCP mode, we use WSTK+4162 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.
Firstly, download standalone Bootloader: bootloader-uart-xmodem.s37 and NCP firmware: ncp-uart-hw.s37 to a WSTK kit.
Then create the Host: Z3GatewayHost as follows:
Secondly, create an application as OTA Client.
plugin network-steering start 0
What are the differences of IPv6 address in Thread network?