Lines Matching refs:procedure

41    node in the Upload Firmware procedure, then it distributes the uploaded image to other Target
185    according to the Firmware Check Over HTTPS procedure defined by the specification. The firmware
250 The Upload Firmware procedure uses the :ref:`bluetooth_mesh_blob` to transfer the firmware image
251 from the Initiator to the Distributor. The Upload Firmware procedure works in two steps:
290 may initiate the distribution procedure. The BLOB transfer parameters for the distribution are
316 If the distribution procedure completed with at least one Target node reporting that the image has
317 been received and verified, the distribution procedure is considered successful.
320    The firmware distribution procedure only fails if *all* Target nodes are lost. It is up to the
336 procedure on all Target nodes that successfully received and verified the firmware image. The Apply
337 Firmware on Target Node procedure takes no parameters, and to avoid ambiguity, it should be
338 performed before a new transfer is initiated. The Apply Firmware on Target Node procedure consists
353    During the metadata check in the distribution procedure, the Target node may have reported that
362 Distributor starts the cancelling procedure by sending a cancelling message to all Target nodes. The
364 request has timed out, the distribution procedure is cancelled. After this the distribution
365 procedure can be started again from the ``Firmware distribution`` section.