Lines Matching refs:node
34 Target node
35 Target node is the receiver and user of the transferred firmware images. All its functionality is
41 node in the Upload Firmware procedure, then it distributes the uploaded image to other Target
66 :ref:`bluetooth_mesh_dfu_cli` on the Initiator node and calling its API directly.
84 image and all its metadata to the Distributor node inside the mesh network. The Distributor
107 All updatable parts of a mesh node's firmware should be represented as a firmware image. Each Target
108 node holds a list of firmware images, each of which should be independently updatable and
115 The firmware ID is used to identify a firmware image. The Initiator node may ask the Target nodes
118 enough information for an Initiator node with knowledge of the format to determine the type of
123 The firmware metadata is used by the Target node to determine whether it should accept an
125 vendor specific, and should contain all information the Target node needs to verify the image, as
126 well as any preparation the Target node has to make before the image is applied. Typical metadata
127 information can be image signatures, changes to the node's Composition Data and the format of the
128 BLOB. The Target node may perform a metadata check before accepting incoming transfers to
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
161 | New number of elements | 2 B | Number of elements on the node |
182 versions of the firmware. This allows Initiators to perform updates for any node in the mesh
198 A new image may have the Composition Data Page 0 different from the one allocated on a Target node.
199 This may have an effect on the provisioning data of the node and how the Distributor finalizes the
219 When the Target node receives the Firmware Update Firmware Metadata Check message, the Firmware
238 :ref:`bluetooth_mesh_dfu_cli`. The Target node implements all handling of these procedures in the
279 Target node. The Initiator may send one or more Firmware Distribution Receivers Add messages to
304 node's Firmware Update Server model, along with the other BLOB transfer parameters, the Target
305 node firmware image index and the firmware image metadata. Each Target node performs a metadata
308 the Bluetooth Mesh state of the node.
316 If the distribution procedure completed with at least one Target node reporting that the image has
344 #. The Target node's application performs any preparations needed before applying the transfer, such
346 #. The Target node's application swaps the current firmware with the new image and updates its
349 each Target node, and scans through the list to make sure that the new firmware ID has replaced
353 During the metadata check in the distribution procedure, the Target node may have reported that