Lines Matching full:new
93 accept the new firmware. Nodes that do not respond, or respond that they can't receive the new
102 their status and new firmware IDs.
143 | New firmware version | 8 B | 1 B: Major version |
148 | New firmware size | 3 B | Size in bytes for a new firmware |
150 | New firmware core type | 1 B | Bit field: |
159 | | | in the New firmware core type field. |
161 | New number of elements | 2 B | Number of elements on the node |
164 | | | in the New firmware core type field. |
167 | data for new firmware | (Optional) | application to execute some |
181 be found. The URI points to an online resource the Initiator can interact with to get new
198 A new image may have the Composition Data Page 0 different from the one allocated on a Target node.
200 DFU. Depending on the availability of the Remote Provisioning Server model on the old and new image,
201 the device may either boot up unprovisioned after applying the new firmware or require to be
205 The device stays provisioned after the new firmware is programmed. This effect is chosen if the
206 composition data of the new firmware doesn't change.
209 provisioning. The new composition data takes place only after re-provisioning.
212 provisioning. In this case, the device stays provisioned and the new composition data takes place
215 This effect is chosen if the composition data in the new firmware changes, the device doesn't
216 support the remote provisioning, and the new composition data takes effect after applying the
224 prepare the Composition Data Page and Models Metadata Page contents before applying the new
338 performed before a new transfer is initiated. The Apply Firmware on Target Node procedure consists
346 #. The Target node's application swaps the current firmware with the new image and updates its
347 firmware image list with the new firmware ID.
349 each Target node, and scans through the list to make sure that the new firmware ID has replaced