Enable mcumgr features on NRF5340 DK board while Bluetooth HCI_USB program is running

[Utsav R Shah]

Hello community,

I am trying for multiple firmware updates for my NRF5340 DK board. 

What I am doing is I have build and flashed the SMP server sample program found /zephyr/samples/subsys/mgmt/mcumgr/smp_svr

After flashing this application, I can see my board recognised as a ttyACM0 device while I perform ls /dev.

Using the mcumgr tool I am also able to flash the Bluetooth HCI_USB sample program and after confirming the image and resetting the board, the board now acts as a bluetooth controller. I can verify this using the bluetoothctl command.

Now If I want to do a firmware upgrade, I dont have any way in the HCI_USB application to go back to smp server application. How can I perform multiple firmware updates using mcumgr?

Can virtual com port concept be useful here? If yes then I would like to have a detailed tutorial for this .

[Hieu]

Hello Utsav,

In a different DevZone case, I was able to emulate two UART COM on the same USB peripheral simply by setting one more cdc_acm_uart node under the usbd node. 

		usbd: zephyr_udc0: usbd@40027000 {
			compatible = "nordic,nrf-usbd";
			reg = < 0x40027000 0x1000 >;
			interrupts = < 0x27 0x1 >;
			num-bidir-endpoints = < 0x1 >;
			num-in-endpoints = < 0x7 >;
			num-out-endpoints = < 0x7 >;
			num-isoin-endpoints = < 0x1 >;
			num-isoout-endpoints = < 0x1 >;
			status = "okay";
			cdc_acm_uart: cdc_acm_uart {
				compatible = "zephyr,cdc-acm-uart";
			};
			cdc_acm_uart0: cdc_acm_uart0 {
				compatible = "zephyr,cdc-acm-uart";
				label = "CDC_ACM_0";
			};

Once that second virtual COM port is setup, you can select it for MCUmgr by overlaying the chosen property as such:

/{
	chosen {
		zephyr,uart-mcumgr = &new_usb_uart_com;
	};
}

Please note that it is the Christmas - New Year holiday season here. We are thus severely understaffed, and there would be delays in responses. Our apologies for the inconveniences. 

Hieu

[Utsav R Shah]

Hello Hieu  thanks for your response. I understand Christmas season is here and most of  the people would be on vacations. I really appreciate your response. 

In the Bluetooth HCI_USB project I have done the following changes : 

I have tried modifying the overlay file and here are the results : 

The contents of my overlay file are as follows: 

/ {
chosen {
zephyr,code-partition = &slot0_partition;
zephyr,out-usb = &cdc_acm1;
zephyr,uart-mcumgr = &cdc_acm0;
};
};

&zephyr_udc0 {
cdc_acm0: cdc_acm0 {
compatible = "zephyr,cdc-acm-uart";
};
cdc_acm1: cdc_acm1 {
compatible = "zephyr,cdc-acm-uart";
};
};

&uart0 {
status = "okay";
};

The contents of my prj.conf file are as follows:

CONFIG_STDOUT_CONSOLE=y
CONFIG_GPIO=y
CONFIG_SERIAL=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_USB_DEVICE_INITIALIZE_AT_BOOT=n

CONFIG_BT=y
CONFIG_BT_HCI_RAW=y

CONFIG_USB_DEVICE_STACK=y
CONFIG_USB_DEVICE_PID=0x000B
CONFIG_USB_DEVICE_BLUETOOTH=y
CONFIG_USB_DEVICE_BLUETOOTH_VS_H4=n

# Workaround: Unable to allocate command buffer when using K_NO_WAIT since
# Host number of completed commands does not follow normal flow control.
CONFIG_BT_BUF_CMD_TX_COUNT=10

#This flag is enabled to make the mcuboot features for DFU available
CONFIG_BOOTLOADER_MCUBOOT=y

#Commands to add composite USB feature to HCI_USB program
#Composite USB configuration ----------------
CONFIG_USB_COMPOSITE_DEVICE=y
#CONFIG_USB_CDC_ACM=y

# Enable MCUmgr and dependencies.
CONFIG_NET_BUF=y
CONFIG_ZCBOR=y
CONFIG_CRC=y
CONFIG_MCUMGR=y
CONFIG_STREAM_FLASH=y
CONFIG_FLASH_MAP=y

# Some command handlers require a large stack.
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2304
CONFIG_MAIN_STACK_SIZE=2048

# Enable flash operations.
CONFIG_FLASH=y

# Required by the `taskstat` command.
CONFIG_THREAD_MONITOR=y

# Support for taskstat command
CONFIG_MCUMGR_GRP_OS_TASKSTAT=y

# Enable statistics and statistic names.
CONFIG_STATS=y
CONFIG_STATS_NAMES=y

# Enable most core commands.
CONFIG_FLASH=y
CONFIG_IMG_MANAGER=y
CONFIG_MCUMGR_GRP_IMG=y
CONFIG_MCUMGR_GRP_OS=y
CONFIG_MCUMGR_GRP_STAT=y

# Enable logging
CONFIG_LOG=y
CONFIG_MCUBOOT_UTIL_LOG_LEVEL_WRN=y

# Disable debug logging
CONFIG_LOG_MAX_LEVEL=3

# Enable USB subsystem
CONFIG_USB_DEVICE_STACK=y
CONFIG_SERIAL=y
CONFIG_UART_LINE_CTRL=y
CONFIG_USB_DEVICE_INITIALIZE_AT_BOOT=n
CONFIG_CONSOLE=y
# USB backend is serial device
CONFIG_MCUMGR_TRANSPORT_UART=y
CONFIG_BASE64=y

Then I have build the project using the following command : 

west build -b nrf5340dk_nrf5340_cpuapp --pristine -- -DOVERLAY_CONFIG=overlay-cdc.conf -DDTC_OVERLAY_FILE=nrf5340_cpuapp.overlay -DCONFIG_MCUBOOT_SIGNATURE_KEY_FILE=\"/home/mutsl04176/ncs/v2.4.2/bootloader/mcuboot/root-rsa-2048.pem\"

After successful build, I flashed the program into the NRF5340 DK board and plugged in the other USB.

You can see from the screenshot below that I get two virtual ports as ACM0 and ACM1 :

But at the same time, the board is not visible as a Bluetooth controller under bluetoothctl . Only the default Bluetooth controller (of the laptop) is visible.

How do I solve this? 

Any other modifications that needs to be made? If yes then please let me know in which file and what needs to be done. 

Thanks!

[Sigurd Hellesvik]

Utsav R Shah said:

I get two ACM ports while checking the ls /dev. But only the default bluetooth controller of the laptop comes up. I should be able to see 2 bluetooth controllers instead but that's still not happening :

From HCI UART docs, did you run the following?

sudo btattach -B /dev/ttyACMX -S 1000000

Are you able to use mcumgr with the sample?

[Utsav R Shah]

I ran the command and while the command is running, I can get the device to detect as a bluetooth controller as well as show up as a ttyACMx device . You can check the screenshot below : 

But I am not able to use mcumgr with the sample. While trying to upload an image through mcumgr, the progress bar is stuck and it does not upload.

This is the following command I am using to upload an image using mcumgr : 

sudo ./mcumgr image upload app_update.bin --conntype=serial --connstring=/dev/ttyACM0

As you can see it does not upload the image.

[Sigurd Hellesvik]

Utsav R Shah said:

sudo ./mcumgr image upload app_update.bin --conntype=serial --connstring=/dev/ttyACM0

Did you try any other ACM for this?

Try mcumgr first before attaching HCI, and then after.

[Utsav R Shah]

I tried the command with both ACM0 and ACM1 as options.

I tried the command before attaching the HCI as well but it shows no progress.

[Sigurd Hellesvik]

In case it has not been asked before:

Are you able to run mcumgr on the application before adding HCI?

[Utsav R Shah]

Yes I am able to run mcumgr if I enable the SMP server configuration in Bluetooth HCI program. I can also upload a program.

[Sigurd Hellesvik]

Utsav R Shah said:

I am able to run mcumgr if I enable the SMP server configuration in Bluetooth HCI program.

Nice! Does that mean everything works now?

[Utsav R Shah]

I am able to upload a sample program using mcumgr when I enable SMP server configuration in HCI_USB program. But in that instance it does not detect at a bluetooth device.

[Sigurd Hellesvik]

Copying boards/nrf52840dk_nrf52840.conf/overlay to boards/nrf5340dk_nrf5340_cpuapp.conf/overlay in my sample, I get this:

Try to follow the steps that I follow. Does it look the same to you?
Let me know about anything that is different on your end.

[Utsav R Shah]

Hello Sigurd Hellesvik  apologies for the extreme delay in answering . I kind of solved the issue of enabling the controller board as a bluetooth controller as well as enable it to listen to mcumgr specific comamnds. 

Instead of HCI_USB I had used HCI_UART sample program. I had enabled all mcugmr featues in the prj.conf file.

In the overlay file I had specified two ACM ports - First one to be used for MCUMGR specifiec commands and the other to be used to attach the nrf board as a bluetooth HCI controller.