MCUMGR remote firmware update

[AngusKu]

| Host |  <---- UART ----> | nRF52833 (central) |  <-- BLE--> | nRF52833 (Target) |

I have a requirement where I hope to update the central's firmware image through the Host.
However, I also want the Host to be able to update the firmware image of the target through the central.

As a beginner, I'm currently unsure how to proceed.

From what I understand, it seems possible to enable MCUMGR functionality on the Zephyr running on the central.
But I'm not sure how firmware updates can be performed between the central and target.

Which nordic zephyr examples can I refer to?
or suggestions regarding this design architecture?

[Vidar Berg]

Hello,

You can integrate the GATT DFU SMP Service Client on your GAP central as demonstrated by the Bluetooth: Central SMP Client sample. Unfortunately, there are not official samples that implements DFU support. You may have a look at this example for that: https://github.com/simon-iversen/ncs_samples/tree/master/central_smp_client_dfu 

Best regards,

Vidar

[AngusKu]

Thanks for information.

The target which needs to be updated by Central and the image is from Host.

Have any suggestions for it? For now, I am looking the smp_svr sample. 

I was thinking that I have to enable the mcumgr at central and traget both. And maybe I have to create a proprietary mgnt command at central for forwarding the image to target.

Could you please give me some comments for the thought or maybe it isn't a good idea.

[Vidar Berg]

What is the host in this case?

[AngusKu]

It will be the other nordic chip and connect to central by serial port (Uart)

For now, The host is that We ran a mcumgr command line tool on PC to send the central board and target board image.

Currently, we want to use the mcumgr on the PC to facilitate the development of the BLE firmware update feature between the central and target.

[Vidar Berg]

It sounds like a simpler approach would be to just update the central and peripheral separately from your PC. Auterm (https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/services/device_mgmt/mcumgr.html#toolslibraries) supports BLE on Windows, not just Linux, like mcumgr.

[AngusKu]

Since the host chip does not have BT functionality, it is connected to the central via a serial port. We thought we could use mcumgr for updates directly.

Currently, we are temporarily using the PC as the Host to facilitate our development.

The target and central are connected via BLE, and we plan for the central to handle the firmware updates for the target.

I was thinking to first transfer the target's firmware to the central's flash, and then have the central handle the firmware update for the target. Does this mean that the host chip, as well as the central and target, all need to be configured with mcumgr?

All programs on the host, central, and target are using Nordic's Zephyr project.

Could you provide any example programs for this architecture?

Is it reasonable to extend a mgnt ID to determine firmware updates as a solution?"

Since we are not very familiar with your SDK, could you please provide any recommendations regarding this requirement?

[Vidar Berg]

I think you can use this demo sample as a starting point: https://github.com/simon-iversen/ncs_samples/tree/master/central_smp_client_dfu