MCUMGR remote firmware update

RE: MCUMGR remote firmware update

Vidar Berg — Mon, 12 Aug 2024 06:39:03 GMT

Yes, it is recommended to enable HW byte counting to prevent data loss: https://github.com/nrfconnect/sdk-zephyr/blob/9e30235cce8e4b5df694d1f7689d7378ec8329cf/drivers/serial/Kconfig.nrfx_uart_instance#L52

RE: MCUMGR remote firmware update

AngusKu — Wed, 07 Aug 2024 23:47:13 GMT

It seems that the software counting has bugs.
Do you suggest that I use hardware counting by modifying the prj.conf file as shown below?

CONFIG_UART_0_NRF_HW_ASYNC_TIMER=1
CONFIG_UART_0_NRF_HW_ASYNC=y

Others have encountered the same issue and have discussed it here

A similar problem has also been raised on GitHub.
https://github.com/zephyrproject-rtos/zephyr/issues/49021
https://github.com/zephyrproject-rtos/zephyr/pull/24209

RE: MCUMGR remote firmware update

Vidar Berg — Fri, 05 Jul 2024 05:27:22 GMT

This setting allows you to use the Asynchronous API instead of the Interrupt-driven API in the mcumgr driver. The async UART driver provides better utilization of the DMA feature at the cost of increased memory usage. It can make the data reception more reliable when you don't use hardware flow control.

RE: MCUMGR remote firmware update

AngusKu — Thu, 04 Jul 2024 22:57:37 GMT

Thanks for sharing this information.

Due to our need for relay functionality,
I have been recently referencing the uart_mcumgr.c implementation in the Nordic Zephyr SDK.

I would like to ask under what circumstances one would choose the CONFIG_MCUMGR_SMP_UART_ASYNC option?"

RE: MCUMGR remote firmware update

Vidar Berg — Wed, 03 Jul 2024 07:33:12 GMT

You will get a image upload response for each chunk of data you send through the image upload request command: https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/services/device_mgmt/smp_groups/smp_group_1.html#image_upload_response.

RE: MCUMGR remote firmware update

AngusKu — Wed, 03 Jul 2024 03:14:29 GMT

I would like to ask a question about the DFU SMP service.

In dfu_smp.c ,
Why does bt_dfu_smp_command invokes bt_gatt_write_without_response ?

	/* Send request */
	ret = bt_gatt_write_without_response(dfu_smp->conn,
					     dfu_smp->handles.smp,
					     cmd_data,
					     cmd_size,
					     false);
	if (ret) {
		dfu_smp->cbs.rsp_part = NULL;
	}

How can we ensure that the SMP server receives every data packet sent by the Central during image upload?

RE: MCUMGR remote firmware update

AngusKu — Mon, 01 Jul 2024 06:15:47 GMT

Thanks for sharing.

RE: MCUMGR remote firmware update

Vidar Berg — Fri, 28 Jun 2024 13:11:33 GMT

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

RE: MCUMGR remote firmware update

AngusKu — Tue, 25 Jun 2024 12:01:45 GMT

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?

RE: MCUMGR remote firmware update

Vidar Berg — Tue, 25 Jun 2024 11:00:44 GMT

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.

RE: MCUMGR remote firmware update

AngusKu — Tue, 25 Jun 2024 10:11:57 GMT

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.

RE: MCUMGR remote firmware update

Vidar Berg — Tue, 25 Jun 2024 09:59:29 GMT

What is the host in this case?

RE: MCUMGR remote firmware update

AngusKu — Tue, 25 Jun 2024 09:31:28 GMT

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.

RE: MCUMGR remote firmware update

Vidar Berg — Tue, 25 Jun 2024 09:18:12 GMT

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