OTA firmware update images must conform to the Matter OTA Software Image file format, which includes:
- A file identifier that uniquely identifies the file as being a Matter firmware update file
- The size of the file
- The header size
- A Tag-length-value (TLV)-encoded header containing information about the
- software version
- The payload
The Matter SDK provides a tool to create and inspect
Matter OTA images
Some build systems can create Matter OTA images
automatically, so check your SoC documentation.
Create an OTA image
ota_image_tool.py to create the image:
$ ./ota_image_tool.py create \ -v hexVendorId \ -p hexProductId \ -vn versionNumber \ -vs "versionString" \ -da "hash-function \ path_to_binary \ path_to_ota_file
To verify the metadata set and the header of the file, run the script with the
$ ./ota_image_tool.py show path_to_ota_file
Magic: 1beef11e Total Size: 90 Header Size: 62 Header TLV:  Vendor Id: XXXX (0xXX)  Product Id: XXX (0xXX)  Version: 101 (0x65)  Version String: 1.0.1  Payload Size: 12 (0xc)  Digest Type: 1 (0x1)  Digest: a948904f2f0f429b8f8197694b30184b0d2ed1c3cd2a1ec0fb85d299a193a447
Upload the OTA image
To upload the image to the Google Home Developer Console:
Go to Matter > OTA.
Click Manage next to the device in the Devices list.
In the OTA Configuration page, click the Images tab.
Click New Image.
Give the image a name and click Attach Image to select and upload the image file.
Once the image is successfully validated, click Save.
When the confirmation dialog appears, click Save to make the image available to your devices, or click Cancel to cancel the submission.
The OTA image is available for distribution shortly after uploading.