Multi-Image DFU project structure

RE: Multi-Image DFU project structure

variant — Fri, 10 Mar 2023 15:18:40 GMT

Robert, If you haven't already seen this link, perhaps this could be useful to you.

RE: Multi-Image DFU project structure

Øivind — Mon, 13 Feb 2023 15:14:39 GMT

Hi, sorry for not getting back to you earlier

It is possible to send over the binary for each core separately, app_update.bin for the application core and net_core_app_update.bin for the network core.
However, this still requires an MCUboot build that supports updating both cores, which is the core issue. As I said earlier, the issue is in the build system, not in MCUboot's capabilities.

You mentioned earlier that you could perhaps modify hci_rpmsg to fit your needs, and if that is sufficient then you should not encounter any issues with simultaneous or non-simultaneous updates of the cores.

RE: Multi-Image DFU project structure

Robert de Brum — Thu, 09 Feb 2023 22:34:50 GMT

Could I get an update on this?

RE: Multi-Image DFU project structure

Robert de Brum — Mon, 16 Jan 2023 22:12:43 GMT

I just entered a new ticket here: Encrypted DFU nrf5340 in NCS with case ID 301424.

Back on the same topic of FOTA DFU for both the network and application core:

I am able to send over a DFU binary, and update the application core via BLE FOTA for my custom project that contains source code for both the application and network core. However, this of course does not update the network core.

Is it possible to generate and send over the binary package required to update just the network core? Essentially, my customer would be satisfied with performing a DFU of the network core and application core separately with two different binaries instead of simultaneously.

RE: Multi-Image DFU project structure

Øivind — Fri, 13 Jan 2023 13:12:31 GMT

Great!

Yes, starting a new thread for that is best, as it becomes easier to find specific answers for other users.

RE: Multi-Image DFU project structure

Robert de Brum — Wed, 11 Jan 2023 18:10:33 GMT

Thanks again for the response. I think for me and my customer's sake, we can proceed with simply adding DFU of the application core only for now. I have that working with the nrfconnect app and sending over a .bin file.

My next question is going to be slightly off topic, but I have not been able to find a concise answer through my research and DevZone reading: Is encrypted DFU supported in NCS yet? How could I achieve this effect (we will need higher security than just signing the payload) for the nrf5340?

Let me know if I should start a new thread. I assume you might be able to give me a quick and short answer if it is/not supported.

Thanks again for your time and support. Much appreciated!

RE: Multi-Image DFU project structure

Øivind — Wed, 11 Jan 2023 14:56:31 GMT

The issue is the order that the build system builds images and how early the build system needs to be aware of the child image. We are in the early stages of supporting sysbuild as a build system, which will hopefully make this easier.

Yes, if you change the hci_rpmsg sample to fit your needs and keep the modified version at the original location, then I believe you should be able to include it and generate dfu files for it properly.

RE: Multi-Image DFU project structure

Robert de Brum — Tue, 10 Jan 2023 17:23:16 GMT

Thank you very much for this information.

Could you comment on the status of this task? Would it begin development or be in planning for release soon?

I think I understand what you are mentioning as a workaround, and I will look into that. Correct me here if I am wrong, but perhaps a "workspace" project would be appropriate, so that I can have a specific instance of the SDK to meddle with and not hamper any other projects?

Notably, I would only mess with the hci_rpmsg sample hidden within the SDK, but please let me know if this approach sounds appropriate.

RE: Multi-Image DFU project structure

Øivind — Tue, 10 Jan 2023 12:32:44 GMT

Hi,

Unfortunately, using a custom image on the network core is not currently supported with multi-image DFU.

The only workaround I am aware of involves modifying nrf/samples/CMakeLists.txt to add your netcore image, in the same way that netcore images like hci_rpmsg are added.