Lines Matching +full:re +full:- +full:sending
88 time-consuming Distribution stage. Once the firmware has been uploaded to the Distributor, the
140 +------------------------+--------------+----------------------------------------+
147 +------------------------+--------------+----------------------------------------+
149 +------------------------+--------------+----------------------------------------+
155 +------------------------+--------------+----------------------------------------+
156 | Hash of incoming | 4 B | Lower 4 octets of AES-CMAC |
157 | composition data | (Optional) | (app-specific-key, composition data). |
160 +------------------------+--------------+----------------------------------------+
165 +------------------------+--------------+----------------------------------------+
166 | Application-specific | <variable> | Application-specific data to allow |
168 | | | vendor-specific behaviors using |
171 +------------------------+--------------+----------------------------------------+
175 The AES-CMAC algorithm serves as a hashing function with a fixed key and is not used for
191 The out-of-band distribution mechanism is not supported.
196 ---------------
202 re-provisioned. The complete list of available options is defined in :c:enum:`bt_mesh_dfu_effect`:
209 provisioning. The new composition data takes place only after re-provisioning.
213 after re-provisioning using the Remote Provisioning models.
297 ---------------------
306 check and prepares their BLOB Transfer Server model for the transfer, before sending a status
325 ---------------------------
328 the Distributor will stop sending any messages to Target nodes. When the firmware distribution is
329 resumed, the Distributor will continue sending the firmware from the last successfully transferred
362 Distributor starts the cancelling procedure by sending a cancelling message to all Target nodes. The