Can I update the user data through dfu protocal?

[ZHENGXIANG]

Hi,

I have read the dfu protocal and found that there are three types of dfu transfer which are identified by a firmware ID. Now I want to add a new part to update the user data. Do you have any examples which extend the dfu protocal?

PS: I use nrf52832 and mesh SDK v3.0.0

Thanks for your prompt response!

Sincerely,

Jin.

[Vidar Berg]

Hi Jin,

I do not know of any examples that extend DFU to include other image types, unfortunately. But would it be an option to add the user data in your application image? I believe that might be the simplest approach for this. You can make the new app can copy the data to your app data region if necessary.

Best regards,

Vidar

[ZHENGXIANG]

His Vidar,

OK, I will try it. Moreover, in the dfu file (in zip format), there are three files, manifest, dat and bin. I have successfully tried dfu by using the mesh nrfutil tool. Now I want to do wireless mesh dfu, which means I should know which file is sent to the nrf52832. Is it right that manifest and dat  are used for nrftil tool and only bin is sent to the nrf52832?

By the way, do you know any method to see the log when dfu is running? When I connect the Jlink and the USB serial in the same time, I cannot start dfu in PC.

Thanks for your prompt response!

Sincerely,

Jin.

[Vidar Berg]

Hi Jin,

The *.dat file is the init command which contains additional information about the update, and the *.bin file contains the FW image. The manifest file is optional and may be parsed by the DFU controller to determine the content of a DFU package. It's not sent to the 52832, as you said.

ZHENGXIANG said:

By the way, do you know any method to see the log when dfu is running?

 Which node is it that you want to get logs from, the DFU target or source? Logging must be done over RTT if it is the latter because the only available UART instance is used for the DFU process.