DFU on nRF Connect SDK by Random Flash Write

RE: DFU on nRF Connect SDK by Random Flash Write

loquat — Thu, 07 Sep 2023 06:58:18 GMT

I see. I will try.

Thank you

RE: DFU on nRF Connect SDK by Random Flash Write

Vidar Berg — Thu, 07 Sep 2023 06:53:57 GMT

You can read about the DFU target library here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.2/nrf/libraries/dfu/dfu_target.html. But for your case, I think it would be easiest to start with the smp_srv sample (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/README.html#smp-svr-sample) and see how it uses mcuboot.c and flash_img.c to place the update binary in slot 1.

RE: DFU on nRF Connect SDK by Random Flash Write

loquat — Wed, 06 Sep 2023 14:16:36 GMT

I believe the dfu_target_xxx API does a lot more than writing the image to FLASH.
It may be possible to write a DFU image to FLASH using the FLASH API, but I don't know the process to prepare the DFU.

By the way, we have independently incorporated and operated the same functionality into the nRF5 SDK.
We want to use this functionality that we implemented in the nRF5 SDK in the nRF Connect SDK as well.

RE: DFU on nRF Connect SDK by Random Flash Write

Vidar Berg — Wed, 06 Sep 2023 11:45:46 GMT

Hi,

It should be fine to not store the data sequentially as long as it all gets stored in the end. But you will probably need to use the regular flash API, and not the Stream Flash API used by dfu_target_write(). There aren't any DFU examples that do non-sequential writes as far as I can tell.