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

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

Sigurd Hellesvik — Wed, 19 Feb 2025 09:03:00 GMT

devzone.nordicsemi.com/.../2068.hci_5F00_uart_5F00_feat_5F00_cdc_5F00_feat_5F00_mcumgr_5F00_over_5F00_uart.zip

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

Aasim_ — Wed, 19 Feb 2025 06:28:06 GMT

[quote userid="106736" url="~/f/nordic-q-a/106938/enable-mcumgr-features-on-nrf5340-dk-board-while-bluetooth-hci_usb-program-is-running/463160"]hci_uart_feat_cdc_feat_mcumgr_over_uart.zip[/quote]

can you share this sample again its empty.

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

Sigurd Hellesvik — Wed, 10 Apr 2024 06:46:12 GMT

You are in good hands with Torbjørn, he is more experienced with USB than I am. In fact I asked him for assistance with this ticket.

But thanks for pointing out that ticket, I will keep an eye on it!

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

Utsav R Shah — Wed, 10 Apr 2024 06:28:49 GMT

Sigurd Hellesvik I had successfully used the HCI_UART program to open 2 virtual ports - once for attaching the bluetooth device to HCI and another for accepting MCUMGR specific commands. The two functionalities are working fine but there is an issue with the scanning while using the program. In my use case I have been using BlueZ which communicates via the Dbus for various bluetooth related commands. What I have observed during my testing is that after a certain time the bluetooth controller is unable to detect any advertising devices. I have to do a power reset for it to make it scan again only to get the same issue after sometime.

More details of this problem is being discussed on another thread posted by one my acquaintance :

NRF5340 HCI_USB & HCI_UART Stop Scanning

Let me know if you have anything on this that can be of help

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

Utsav R Shah — Thu, 25 Jan 2024 12:19:13 GMT

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.

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

Sigurd Hellesvik — Wed, 10 Jan 2024 15:04:29 GMT

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

devzone.nordicsemi.com/.../mcumgr_5F00_and_5F00_hci.mp4

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.

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

Utsav R Shah — Wed, 10 Jan 2024 13:47:27 GMT

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.

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

Sigurd Hellesvik — Wed, 10 Jan 2024 09:07:15 GMT

[quote user="Utsav R Shah"]I am able to run mcumgr if I enable the SMP server configuration in Bluetooth HCI program.[/quote]

Nice! Does that mean everything works now?

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

Utsav R Shah — Tue, 09 Jan 2024 12:25:44 GMT

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

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

Sigurd Hellesvik — Tue, 09 Jan 2024 09:20:12 GMT

In case it has not been asked before:

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

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

Utsav R Shah — Tue, 09 Jan 2024 09:01:41 GMT

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.

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

Sigurd Hellesvik — Tue, 09 Jan 2024 08:51:03 GMT

[quote user="Utsav R Shah"]sudo ./mcumgr image upload app_update.bin --conntype=serial --connstring=/dev/ttyACM0[/quote]

Did you try any other ACM for this?

Try mcumgr first before attaching HCI, and then after.

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

Utsav R Shah — Tue, 09 Jan 2024 07:58:15 GMT

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.

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

Sigurd Hellesvik — Tue, 09 Jan 2024 07:41:06 GMT

[quote user="Utsav R Shah"]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 :[/quote]

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?

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

Utsav R Shah — Tue, 09 Jan 2024 07:17:29 GMT

I tried the HCI_UART sample program with the following changes but the issue still remains.

Here are the contents of my prj.conf file :

CONFIG_CONSOLE=n
CONFIG_STDOUT_CONSOLE=n
CONFIG_UART_CONSOLE=n
CONFIG_GPIO=y
CONFIG_SERIAL=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_BT=y
CONFIG_BT_HCI_RAW=y
CONFIG_BT_HCI_RAW_H4=y
CONFIG_BT_HCI_RAW_H4_ENABLE=y
CONFIG_BT_BUF_ACL_RX_SIZE=255
CONFIG_BT_BUF_CMD_TX_SIZE=255
CONFIG_BT_BUF_EVT_DISCARDABLE_SIZE=255
CONFIG_BT_CTLR_ASSERT_HANDLER=y
CONFIG_BT_MAX_CONN=16
CONFIG_BT_TINYCRYPT_ECC=n
CONFIG_BT_CTLR_DTM_HCI=y

CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=512

# 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

###################################################################################################

CONFIG_USB_DEVICE_STACK=y
CONFIG_USB_DEVICE_PRODUCT="Zephyr HCI UART sample"
CONFIG_USB_CDC_ACM=y
CONFIG_USB_DEVICE_INITIALIZE_AT_BOOT=n

CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_MCUMGR=y
CONFIG_MCUMGR_TRANSPORT_UART=y
CONFIG_MCUMGR_GRP_IMG=y

# CONFIG_MCUMGR_TRANSPORT_UART dependencies
CONFIG_BASE64=y

# CONFIG_MCUMGR_GRP_IMG dependencies
CONFIG_FLASH=y
CONFIG_IMG_MANAGER=y

# CONFIG_IMG_MANAGER dependencies
CONFIG_STREAM_FLASH=y

# CONFIG_MCUMGR dependencies
CONFIG_NET_BUF=y
CONFIG_ZCBOR=y

# Required for CONFIG_IMG_MANAGER
CONFIG_FLASH_MAP=y

And here is the content of my overlay file :

/ {
	chosen {
		zephyr,uart-mcumgr = &cdc_acm_uart1;
		zephyr,bt-mon-uart = &cdc_acm_uart0;
		zephyr,bt-c2h-uart = &cdc_acm_uart0;
	};
};

&zephyr_udc0 {
	cdc_acm_uart0: cdc_acm_uart0 {
		compatible = "zephyr,cdc-acm-uart";
	};
	cdc_acm_uart1: cdc_acm_uart1 {
		compatible = "zephyr,cdc-acm-uart";
	};
};

I build my program with this overlay file added by using the following command :

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

After this I flashed the merged.hex file. But the issue still remains the same.

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 :

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

Sigurd Hellesvik — Mon, 08 Jan 2024 13:39:10 GMT

I was able to use both HCI and mcumgr work at the same time on the nRF52840DK by configuring the hci_uart sample.

Here is the result:

devzone.nordicsemi.com/.../hci_5F00_uart_5F00_feat_5F00_cdc_5F00_feat_5F00_mcumgr_5F00_over_5F00_uart.zip

devzone.nordicsemi.com/.../hci_5F00_uart_5F00_feat_5F00_cdc_5F00_feat_5F00_mcumgr_5F00_over_5F00_uart.diff

Changes should be similar for the nRF5340.

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

Sigurd Hellesvik — Wed, 03 Jan 2024 15:15:57 GMT

Now you got the configuration I was talking about yes.
Seems like we got another error at our hands since it does not work here.

I am currently stuck out of office due to a snowstorm, meaning I can not use my linux computer at work. So I will try to find a colleague with Linux who can try to reproduce the issue you have now.

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

Utsav R Shah — Tue, 02 Jan 2024 13:38:25 GMT

Yes I now kind of understand what you are saying and I have modified my overlay file accordingly. Please have a look :

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

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

&uart0 {
	status = "okay";
};

Now the code compiles successfully and I was able to flash it. But the problem still remains the same. I am not able to see the device as a bluetooth controller. But when I check the device list, I can see the 3 ACM ports that are created. Only the default bluetooth controller of my laptop is visible.

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

Sigurd Hellesvik — Tue, 02 Jan 2024 13:03:15 GMT

I will try to continue to explain a bit further. In your code you got:

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

And the example got:

	cdc_acm_uart: cdc_acm_uart {
		compatible = "zephyr,cdc-acm-uart";
	};

Your node is named cdc_acm0, and the sample node is named cdc_acm_uart.
It is the name of the node which you point to in the "chosen" part of the DTS.

The error message is because you use cdc_acm_uart for your chosen node. But cdc_acm_uart does not exist for your code. Instead the CDC node in your code is named cdc_acm0

Does that make sense?

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

Utsav R Shah — Tue, 02 Jan 2024 12:46:43 GMT

I'm actually confused now on how to do this. Since I am completely new to this, I actually need some direct hand holding for this. Any chance I can connect with someone directly from the community or with you?

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

Sigurd Hellesvik — Tue, 02 Jan 2024 12:29:48 GMT

And then we can have a look at where the sample I mentioned sets up cdc_acm:

zephyr_udc0: &usbd {
	compatible = "nordic,nrf-usbd";
	status = "okay";

	cdc_acm_uart: cdc_acm_uart {
		compatible = "zephyr,cdc-acm-uart";
	};
};

You see how they defined cdc_acm_uart?
cdc_acm_uart is just the name set in the example. Which name did you give the same type of node in your dts?

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

Utsav R Shah — Tue, 02 Jan 2024 12:17:44 GMT

Sigurd Hellesvik Thank you so much for taking the time to understand my problem. That is really appreciable.

Looking at the zephyr.dts file present in build/zephyr directory, I could find this code snippet that I have attached. I think this may be how cdc_acm is defined

usbd: zephyr_udc0: usbd@36000 {
				compatible = "nordic,nrf-usbd";
				reg = < 0x36000 0x1000 >;
				interrupts = < 0x36 0x1 >;
				num-bidir-endpoints = < 0x1 >;
				num-in-endpoints = < 0x7 >;
				num-out-endpoints = < 0x7 >;
				num-isoin-endpoints = < 0x1 >;
				num-isoout-endpoints = < 0x1 >;
				status = "okay";
				cdc_acm0: cdc_acm0 {
					compatible = "zephyr,cdc-acm-uart";
				};
				cdc_acm1: cdc_acm1 {
					compatible = "zephyr,cdc-acm-uart";
				};
			};

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

Sigurd Hellesvik — Tue, 02 Jan 2024 12:12:26 GMT

I suggest that you loom through that file yourself and look for cdc.
I hope not only to help you with this specific, but also to help you learn how to debug this kind of issue yourself.

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

Utsav R Shah — Tue, 02 Jan 2024 12:02:20 GMT

I have given the contents of the dts file in the reply above, you can check that

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

Sigurd Hellesvik — Tue, 02 Jan 2024 11:53:59 GMT

I think the easiest way to find this is to look at build/zephyr/zephyr.dts for the previous working build