The EmberZNet stacks automatically create OTA update files for your projects which have the OTA Client related plugins enabled. These plugins create a script which is run after the project compilation and linking has completed successfully.
However, you may find you want to manually create an OTA from existed *.gbl files, without rebuilding your project again. Also, because the files automatically generated are basic, you might discover the need to add additional features to your OTA files, such as signatures, certificates, image integrity, manufacturer specific data, etc.
The following steps will explain how to create an OTA file manually.
image-builder-windows.exe --create "Z3LightSoc.ota" --version 3 --manuf-id 0x1002 --image-type 0 --tag-id 0x0000 --tag-file Z3LightSoc.gbl
Full details of these options and further options can be found in the reference material found below.
--create "Z3LightSoc.ota" The file to be created by the Image-Builder software --version 3 The firmware version of the OTA file. This version is used by the OTA clusters to determine if a new file is available for a device. --manuf-id 0x1002 The Zigbee Alliance unique ID assigned to a company --image-type 0 Manufacture specific image information --tag-id 0x0000 --tag-file Z3LightSoc.gbl Tags are used to identify different parts of an OTA file, such as signature, certificates, etc. Tag 0x0000 is the identifier for the upgrade file.
image-builder-windows.exe –p Z3LightSoc.ota
For more information on Image-Builder, refer to the following reference materials: