tools/fw-update/README.md

21         metadatafile     Path of metadata JSON file
27 - Providing the metadata JSON file is a must
31   metadata json
36 in an input metadata file (see the section 'Mapping fields to DSP0267') that's
39 metadata JSON files can be reused. The key names used in the metadata JSON
40 _match with the proprerty names_ used in DSP0267. There is an example metadata
41 json file included - metadata-example.json, which has example entries for
58 - PackageHeaderIdentifier: Supported, must be specified in metadata file
59 - PackageHeaderFormatRevision: Supported, must be specified in metadata file
61 - PackageReleaseDateTime: Supported, this is an optional field in the metadata
63   'T' for full ISO-8601 compliance). If not specified in the metadata file,
70 - PackageVersionString: Supported, must be specified in metadata file
83   - DeviceUpdateOptionFlags: Supported, must be specified in metadata file
89   - ApplicableComponents: Supported, must be specified in metadata file
92   - ComponentImageSetVersionString: Supported, must be specified in metadata
107     - DescriptorType: Supported, must be specified in metadata file
109     - DescriptorData: Supported, must be specified in metadata file as a hex
116       metadata file
117     - VendorDefinedDescriptorData: Supported, must be specified in metadata file
134   - ComponentClassification: Supported, must be specified in metadata file
135   - ComponentIdentifier: Supported, must be specified in metadata file
137     value in metadata file if ComponentOptions bit 1 is selected. If the
140   - ComponentOptions: Supported, must be specified in metadata file
143   - RequestedComponentActivationMethod: Supported, must be specified in metadata
152   - ComponentVersionString: Supported, must be specified in metadata file