Lines Matching +full:update +full:- +full:2

3 Firmware Update Server
6 The Firmware Update Server model implements the Target node functionality of the
10 Together with the extended BLOB Transfer Server model, the Firmware Update Server model implements
17 The Firmware Update Server holds a list of all the updatable firmware images on the device. The full
24 firmware update capabilities could have three entries in the firmware image list, each with their
30 The Firmware Update Server model uses a BLOB Transfer Server model on the same element to transfer
31 the binary image. The interaction between the Firmware Update Server, BLOB Transfer Server and
36    :alt: Bluetooth Mesh Firmware Update Server transfer
38    Bluetooth Mesh Firmware Update Server transfer
43 The transfer check is an optional pre-transfer check the application can perform on incoming
44 firmware image metadata. The Firmware Update Server performs the transfer check by calling the
49 Distributor, and should indicate what effect the firmware update will have on the mesh state of the
55 ------------------------------------
63 firmware image will be represented by Models Metadata Page 128. Composition Data Pages 0, 1 and 2,
71 Metadata. The old Composition Data will then be loaded into Composition Data Pages 0, 1 and 2,
85 about which image is being updated, as well as the update metadata.
87 The Firmware Update Server :c:member:`start <bt_mesh_dfu_srv_cb.start>` callback must return a
93 After the setup stage, the Firmware Update Server prepares the BLOB Transfer Server for the incoming
97 At the end of the BLOB transfer, the Firmware Update Server calls its
112 Finally, if the image was verified, the Distributor may instruct the Firmware Update Server to apply