Unable to install MCUMGR using GO

[siddharth_987]

Hi,

I am trying to install mcumgr using the following command on my Laptop which is running Linux Ubuntu 20.04.6 LTS.

"go get github.com/apache/mynewt-mcumgr-cli/mcumgr"

I need this to enable DFU for UART. Below is the error prompt that I am getting:

"package io/fs: unrecognized import path "io/fs" (import path does not begin with hostname)"

I am currently using nRF SDK 2.5.1 and the go version which is running on my laptop is 1.13.8 linux/amd64

[Håkon Alseth]

Hi,

 

Could you try this?

go install github.com/apache/mynewt-mcumgr-cli/mcumgr@latest

 

Kind regards,

Håkon

[siddharth_987]

Hi,

Thank you for your response I have successfully installed mcumgr and I have verified it by running "mcumgr" command on the terminal.

I am trying to put my nRF52840 in serial recovery mode for DFU over UART. But it is not happening. I am using the following configurations for child image

CONFIG_LOG=y

CONFIG_MCUBOOT_LOG_LEVEL_INF=y

CONFIG_MCUBOOT_SERIAL=y

CONFIG_BOOT_SERIAL_UART=y

CONFIG_UART_CONSOLE=n

CONFIG_SINGLE_APPLICATION_SLOT=y

CONFIG_MCUBOOT_INDICATION_LED=y

And i am using CONFIG_BOOTLOADER_MCUBOOT=y to enable MCUBOOT in my prj.conf.

I have kept the below code in mcuboot.overlay file as well:

/ {

aliases {

mcuboot-button0 = &button1;

mcuboot-led0 = &led1;

};

};

mcumgr conn add acm0 type="serial" connstring="dev=/dev/ttyACM0,baud=115200,mtu=512"

mcumgr -c acm0 image list

After using the above command I recevied this error: Error: NMP timeout

Also before this when i press and hold button 2 I didn't see the LED1 blinking. I have tried with button 1,3,4 as well.

All the above commands and procedure were followed as per the documentation and tutorials given in the links below:

https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/topic/exercise-1-dfu-over-uart/

https://webinars.nordicsemi.com/adding-device-firmware-update-5

[siddharth_987]

Hi,

SInce i am using Linux Ubuntu i don;t have access to nRF connect desktop, hence I am using the CLI terminal to do so.

nrfjprog -f nrf52 --program <path_to_hex_file> --sectorerase

i am using this command to flash from the terminal where my hex file is located but i am unable to do so. Here is the log:

Regards,

Siddharth Singh

[Håkon Alseth]

Run "nrfjprog --recover -f nrf52" first.

Kind regards,

Håkon

[siddharth_987]

Hi,

I can see the LED1 glowing after flashing the given hex file.

Regards,

Siddharth Singh

[Håkon Alseth]

Hi,

 

Thanks for confirming. Then it is highly likely a configuration issue in your project.

Check your configurations, and try to do what I did here:

Håkon Alseth said:

This is hello_world with CONFIG_BOOTLOADER_MCUBOOT=y, and with child_image/mcuboot.conf holding:

CONFIG_MCUBOOT_SERIAL=y
CONFIG_UART_CONSOLE=n
CONFIG_MCUBOOT_INDICATION_LED=y

 

Kind regards,

Håkon

[siddharth_987]

Hi,

Thank you for sharing the configurations. I will try to do the same with a new hello world project

Regards,

Siddharth Singh

[siddharth_987]

Hi,

While the DK is in serial recovery mode. I am trying to communicate using mcumgr.

When I run this command -> mcumgr -c testDK image list

This is the output log I am receiving:

Images:
 image=0 slot=0
    version: 0.0.0
    bootable: false
    flags:
    hash: dc8aec29620ddbc92361b7abfcecb44a115191e2c0ff4b1685d7d438e327f7ae
Split status: N/A (0)

I am expecting the "bootable" key to be true and "flags" to be "active confirmed", as mentioned in the giude : https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/topic/exercise-1-dfu-over-uart/

I have attached the screenshot of the log for your reference.

Regards,

Siddharth Singh

[Håkon Alseth]

Hi,

 

Serial recovery is a single-slot only operation, and it is a simplified form of upgrade, where it is actually targeted towards recovering a device.

As seen from the documentation of mcuboot, the metadata output matches yours:

https://docs.mcuboot.com/serial_recovery.html

 

I see this as a bug in our own course, and I'll report this internally.

 

When you add management modules, such as "5. Add DFU over UART to the application.", then the metadata will be valid.

 

Kind regards,

Håkon

[siddharth_987]

Hi,

Thank you for your prompt response. It's reassuring to hear that serial recovery is functioning normally. Our project requirement necessitates exploring DFU over UART to achieve firmware updates for the nRF52840 chip.

Essentially, we need to update the firmware for the nRF52840 chip from a non-Nordic chipset, with both connected via UART pins. The non-Nordic chip will hold the application binary/hex file, which will then be transferred to the nRF52840 over UART to perform the update.

To ensure robust functionality, we believe that implementing dual image slots is necessary. Therefore, we aim to integrate this functionality into our existing application.

Could you please provide insights or guidance on how to achieve this functionality?

Best Regards,

Siddharth Singh

[siddharth_987]

Hi,

 I am trying to do DFU using dual image slots. According to the steps mentioned in this document I have made the required changes in proj.conf and child image .conf file as shown in the attached image.

After running mcumgr -c acm0 image list command I can't see the image list log without adjusting th DK in serial recovery mode, it displays Error: NMP Timeout.

If I bring the DK into serial recovery mode by pressing button 2 while resetting the DK then only it will show the dual image list. As mentioned in the document in step 5.3 the device should display the image list log without entering in Serial recovery mode.

The document link is mentioned as follows:

https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/topic/exercise-1-dfu-over-uart/

Regards,

Siddharth Singh

[Håkon Alseth]

Hi,

 

You have both mcuboot recovery over uart enabled, as well as application aware DFU over uart now.

This is per chapter 5 in the link that you posted, ie. "5. Add DFU over UART to the application." and below.

 

You are not receiving any response. Is there any log output from your device?

Kind regards,

Håkon