Lines Matching refs:metadata
84 image and all its metadata to the Distributor node inside the mesh network. The Distributor
85 stores the firmware image and its metadata persistently, and awaits further instructions from the
122 Firmware metadata
123 The firmware metadata is used by the Target node to determine whether it should accept an
124 incoming firmware update, and what the effect of the update would be. The metadata format is
126 well as any preparation the Target node has to make before the image is applied. Typical metadata
128 BLOB. The Target node may perform a metadata check before accepting incoming transfers to
129 determine whether the transfer should be started. The firmware metadata can be discarded by the
130 Target node after the metadata check, as other nodes will never request the metadata from the
131 Target node. The firmware metadata is optional, and its maximum length is determined by
134 The Bluetooth Mesh DFU subsystem in Zephyr provides its own metadata format
137 :kconfig:option:`CONFIG_BT_MESH_DFU_METADATA` option. The format of the metadata is presented in
176 encryption in Bluetooth Mesh DFU metadata. The resulting hash is not secure since the key is
221 then process the metadata and provide the effect value. If the effect is
305 node firmware image index and the firmware image metadata. Each Target node performs a metadata
312 metadata.
353 During the metadata check in the distribution procedure, the Target node may have reported that