Issues with MCUmgr over serial with nRF52 devkit/J-Link

RE: Issues with MCUmgr over serial with nRF52 devkit/J-Link

FARLY7 — Wed, 13 Jul 2022 07:55:08 GMT

Hi, late reply. But my speed related issue was actually related to this bug in Mcumgr: https://github.com/apache/mynewt-newtmgr/issues/185.

Applying the provided patch, I was able to reduce the upload times down from 3.5mins to a more respectable 44s @ 115,200 baud:

Original at 115,200 baud:
247.23 KiB / 247.23 KiB [===============================] 100.00% 1.14 KiB/s 3m37swith patch:
247.23 KiB / 247.23 KiB [===============================] 100.00% 5.56 KiB/s 44sFor me, this issue was only occurring while using Serial Recovery mode of MCUBoot, it was not occurring when updating the image using application-level SMP server. I guess this has something to do with the flash alignment of the primary slot vs secondary slot. In Serial Recovery mode, Mcumgr was writing directly to primary slot, where as application-level updates the update is written to the secondary slot.

Another interesting point for those running macOS. The serial_posix.go file in the Tarm serial library used by Mcumgr CLI tool limits the baud rate to 115,200, which is a standard POSIX limit. We also created a patch that removed the use of constants to define the baud rate and instead use the absolute baud rate value. This allowed us to run baud rates beyond 115,200. The highest we tested was 921,600 baud, bringing the upload times further down to 11s! A massive improvement from 3.5mins.

With patch at 921,600 baud:
247.03 KiB / 247.03 KiB [===============================] 100.00% 21.89 KiB/s 11s

RE: Issues with MCUmgr over serial with nRF52 devkit/J-Link

rerickson — Tue, 08 Mar 2022 17:28:21 GMT

[quote userid="99317" url="~/f/nordic-q-a/84174/issues-with-mcumgr-over-serial-with-nrf52-devkit-j-link/356964#356964"] Do you know how to increase the upload speed?[/quote]

In the past upping the MTU will increase the update speed:

CONFIG_MCUMGR=y

CONFIG_MCUMGR_SMP_SHELL=y

CONFIG_MCUMGR_SMP_SHELL_MTU=2048

CONFIG_MCUMGR_BUF_SIZE=2050

CONFIG_MGMT_CBORATTR_MAX_SIZE=2048

CONFIG_FS_MGMT_UL_CHUNK_SIZE=2048

RE: Issues with MCUmgr over serial with nRF52 devkit/J-Link

FARLY7 — Tue, 08 Mar 2022 16:03:24 GMT

No problem Hakon, I will check this tomorrow and get back to you.

One other question perhaps you can help with: Do you know how to increase the upload speed? It’s taking me 3.5mins to upload one ~256KB image. I am using serial recovery mode in MCUBoot if that makes any difference.

What kind of upload speed/times do you see?

I think I read somewhere else that there is a hard coded delay of 20ms between each packet in mcumgr tool, but I’ve not investigated this.

RE: Issues with MCUmgr over serial with nRF52 devkit/J-Link

Håkon Alseth — Tue, 08 Mar 2022 11:30:16 GMT

Hi,

[quote user="FARLY7"]I just tried the suggestion from your answer in the other issue thread, and this worked.[/quote]

This is interesting!

Was the CONFIG_HEAP_MEM_POOL_SIZE set to non-zero value prior to adjusting it?

Kind regards,

Håkon

RE: Issues with MCUmgr over serial with nRF52 devkit/J-Link

FARLY7 — Tue, 08 Mar 2022 10:10:38 GMT

Hi Hakon,

I just tried the suggestion from your answer in the other issue thread, and this worked.

I will also test the smp_svr example again like you did. A little bit more investigation is required on my side to clarify where the issue is and how it is fixed.

Thanks,

Sean

RE: Issues with MCUmgr over serial with nRF52 devkit/J-Link

Håkon Alseth — Tue, 08 Mar 2022 09:52:32 GMT

Hi,

[quote user="FARLY7"]I saw your post on this similar issue, I will try your suggestion here and see if it works.[/quote]

That is specifically for the nrf9160dk_nrf9160_ns target.

I have seen similar issues in the past myself and disabling the MSD has usually been the fix.

I just tested ncs v1.8.0 and ncs v1.9.0, with board nrf52dk_nrf52832, stock smp_svr (w/overlay-serial.conf):

$ mcumgr --conntype serial --connstring /dev/ttyACM0 image upload zephyr/app_update.bin
 48.14 KiB / 48.14 KiB [====================================================================================] 100.00% 3.46 KiB/s 13s
Done

image list shows:

Images:
 image=0 slot=0
    version: 0.0.0
    bootable: true
    flags: active confirmed
    hash: ed10f5869785d67af2fa7d416016a6836c78c6254cd330b4446ba21b316ac2e4
 image=0 slot=1
    version: 0.0.0
    bootable: true
    flags: 
    hash: 1ffb1291735140f39b1ba1f920b14e07e26136abde2d92109ddacbd047d509a7
Split status: N/A (0)

Do you see the same behavior on other PCs as well?

Kind regards,

Håkon

RE: Issues with MCUmgr over serial with nRF52 devkit/J-Link

FARLY7 — Tue, 08 Mar 2022 08:46:50 GMT

Yes, I have done this already. This is one of the first things I do with a new devkit.

I have also tried different MTU sizes in the mcumgr connection parameters, but no luck.

I saw your post on this similar issue, I will try your suggestion here and see if it works.

RE: Issues with MCUmgr over serial with nRF52 devkit/J-Link

Håkon Alseth — Tue, 08 Mar 2022 08:29:01 GMT

Hi,

If you have issues with the usb-serial bridge in the debugger, it might be beneficial to disable the mass storage device in the debugger itself.

This is done by opening J-Link Commander (JLinkExe on mac/linux) and writing:

msddisable

Remember to power cycle the board afterwards before testing again.

Kind regards,

Håkon

RE: Issues with MCUmgr over serial with nRF52 devkit/J-Link

FARLY7 — Mon, 07 Mar 2022 13:25:36 GMT

Hi Hakon,

Sorry for the delay in response.

Yes this is using the smp_svr example. I think you should be able to easily recreate it just by flashing the smp_svr example to the nRF52 devkit and attempting to upload an image over the USB serial port.

Thanks,

Sean

RE: Issues with MCUmgr over serial with nRF52 devkit/J-Link

Håkon Alseth — Fri, 28 Jan 2022 14:45:46 GMT

Hi,

Are you seeing this issue when using the smp_svr example? Could you share the configuration that you're using so I can try to recreate the issue on my side?

Kind regards,

Håkon