Lines Matching refs:Target
34 Target node
35 Target node is the receiver and user of the transferred firmware images. All its functionality is
37 Target nodes, and they will all be updated concurrently.
40 The Distributor role serves two purposes in the DFU process. First, it's acting as the Target
41 node in the Upload Firmware procedure, then it distributes the uploaded image to other Target
43 relies on an Initiator to give it a list of Target nodes and transfer parameters. The Distributor
47 image to the Target nodes.
53 Target nodes and their firmware, and will control (and initiate) all firmware updates. The
92 Before starting the Distribution stage, the Initiator may optionally check if Target nodes can
97 Before the firmware image can be distributed, the Initiator transfers the list of Target nodes
100 mesh network perform other duties. Once the firmware image has been transferred to the Target
107 All updatable parts of a mesh node's firmware should be represented as a firmware image. Each Target
115 The firmware ID is used to identify a firmware image. The Initiator node may ask the Target nodes
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
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
198 A new image may have the Composition Data Page 0 different from the one allocated on a Target node.
220 When the Target node receives the Firmware Update Firmware Metadata Check message, the Firmware
239 :ref:`bluetooth_mesh_dfu_cli`. The Target node implements all handling of these procedures in the
276 Before the Distributor can start distributing the firmware image, it needs a list of Target nodes to
277 send the image to. The Initiator gets the full list of Target nodes either by querying the potential
280 Target node. The Initiator may send one or more Firmware Distribution Receivers Add messages to
290 Once the Distributor has stored a firmware image and received a list of Target nodes, the Initiator
293 Distributor should request that the firmware is applied on the Target nodes or not. The Distributor
294 stores the transfer parameters and starts distributing the firmware image to its list of Target
301 subsystem to communicate with all Target nodes. The firmware distribution is performed with the
304 1. The Distributor's Firmware Update Client model generates a BLOB ID and sends it to each Target
305 node's Firmware Update Server model, along with the other BLOB transfer parameters, the Target
306 node firmware image index and the firmware image metadata. Each Target node performs a metadata
310 #. The Distributor's BLOB Transfer Client model transfers the firmware image to all Target nodes.
311 #. Once the BLOB transfer has been received, the Target nodes' applications verify that the firmware
314 #. The Distributor's Firmware Update Client model queries all Target nodes to ensure that they've
317 If the distribution procedure completed with at least one Target node reporting that the image has
321 The firmware distribution procedure only fails if *all* Target nodes are lost. It is up to the
322 Initiator to request a list of failed Target nodes from the Distributor and initiate additional
323 attempts to update the lost Target nodes after the current attempt is finished.
329 the Distributor will stop sending any messages to Target nodes. When the firmware distribution is
336 If the Initiator requested it, the Distributor can initiate the Apply Firmware on Target Node
337 procedure on all Target nodes that successfully received and verified the firmware image. The Apply
338 Firmware on Target Node procedure takes no parameters, and to avoid ambiguity, it should be
339 performed before a new transfer is initiated. The Apply Firmware on Target Node procedure consists
342 1. The Distributor's Firmware Update Client model instructs all Target nodes that have verified the
343 firmware image to apply it. The Target nodes' Firmware Update Server models respond with a status
345 #. The Target node's application performs any preparations needed before applying the transfer, such
347 #. The Target node's application swaps the current firmware with the new image and updates its
350 each Target node, and scans through the list to make sure that the new firmware ID has replaced
354 During the metadata check in the distribution procedure, the Target node may have reported that
363 Distributor starts the cancelling procedure by sending a cancelling message to all Target nodes. The
364 Distributor waits for the response from all Target nodes. Once all Target nodes have replied, or the