Lines Matching full:transfer

55 	/** @brief Transfer check callback.
57 	 *  The transfer check can be used to validate the incoming transfer
61 	 *  the effect of the transfer would be.
68 	 *  transfer and as a separate procedure.
85 	/** @brief Transfer start callback.
87 	 *  Called when the Firmware Update Server is ready to start a new DFU transfer.
89 	 *  during the DFU transfer.
95 	 *    transfer.
97 	 *    image, and there's no need to transfer it again. The Firmware Update model
98 	 *    will skip the transfer phase, and mark the image as verified.
118 	/** @brief Transfer end callback.
122 	 *  If the transfer is successful, the application should verify the
126 	 *  If the transfer fails, the Firmware Update Server will be available for new
131 	 *  @param success Whether the DFU transfer was successful.
136 	/** @brief Transfer recovery callback.
138 	 *  If the device reboots in the middle of a transfer, the Firmware Update Server
150 	 *          transfer.
156 	/** @brief Transfer apply callback.
158 	 *  Called after a transfer has been validated, and the updater sends an
177 	/** Underlying BLOB Transfer Server. */
189 		/* Effect of transfer, @see bt_mesh_dfu_effect. */
200 /** @brief Accept the received DFU transfer.
202  *  Should be called at the end of a successful DFU transfer.
204  *  If the DFU transfer completes successfully, the application should verify
212 /** @brief Reject the received DFU transfer.
214  *  Should be called at the end of a successful DFU transfer.
216  *  If the DFU transfer completes successfully, the application should verify
224 /** @brief Cancel the ongoing DFU transfer.
230 /** @brief Confirm that the received DFU transfer was applied.
238 /** @brief Check if the Firmware Update	Server is busy processing a transfer.
250  *  @return The current transfer progress in percent.