Is it possible to have the shell and mcumgr on the same uart interface

[raphaZahnd]

I'm limited in number of uart interfaces I can use and would therefore need to be able to have the shell and mcumgr using the same uart interface.

I have tried a few things and searched the internet but didn't find a good and working solution. The best would be to have the shell as default and than being able to switch to the mcumgr dynamically (through a shell command).

[nordicjm]

it is fully supported yes, https://github.com/zephyrproject-rtos/zephyr/blob/main/samples/subsys/mgmt/mcumgr/smp_svr/overlay-shell.conf enables it for the smp_svr sample but can be used in any application

[raphaZahnd]

Great thanks for the quick reply. It works after I commented out the following two configs:
#CONFIG_SHELL_BACKEND_SERIAL_API_ASYNC=y
#CONFIG_SHELL_BACKEND_SERIAL_INTERRUPT_DRIVEN=n

I also tried with the CONFIG_SHELL_LOG_BACKEND=y config of which the sample says that this isn't supported "mcumgr-cli application doesn't accepts log in the channel it uses" but it worked it just takes a little longer at the beginning of the upload image command where the Bits per second almost go to zero but than pick up normal speed again.

Unfortunately I would need the shell, console (logs) and the mcumgr on the same uart so CONFIG_SHELL_LOG_BACKEND=n is not really an option. I wonder if I'm just lucky that it worked with the LOG BACKEND enabled or if it is a valid use case. The good thing is that our application only logs very little so it shouldn't be interrupted too often.

[nordicjm]

Log backend is fine, that part there is in reference to an old bug whereby log output would interleave the output and make it unusable, so long as you are using deferred logging and printk via logging then it should work fine

[raphaZahnd]

Very well! Thanks @nordicjm.