NCS v.1.6.1 migration issue for shell

[Dmitry Kr]

Dear Nordic, 

could you please suggest what should be done to make USB console & shell options work? What should be checked? 

It was quite fine on nCS v1.5.1, and completely breaks after migration. 

Should note both console & shell & log works on RTT completely, and only console works on USB.

Also, shell over NUS still works fine. 

Current settings are:

#
# Console settings
#
CONFIG_CONSOLE=y
CONFIG_STDOUT_CONSOLE=y

#
# RTT settings
#

# Enable RTT
CONFIG_USE_SEGGER_RTT=y
CONFIG_SEGGER_RTT_MODE_NO_BLOCK_SKIP=y

# enable LOG on RTT
CONFIG_LOG=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_OVERRIDE_LEVEL=0
CONFIG_LOG_MAX_LEVEL=4
# CONFIG_LOG_PRINTK is not set
CONFIG_LOG_MODE_OVERFLOW=y
CONFIG_LOG_PROCESS_THREAD=y
CONFIG_LOG_PROCESS_THREAD_SLEEP_MS=1000

# console output on RTT
CONFIG_RTT_CONSOLE=y

#
# USB settings, shell and console
#

# enable USB
CONFIG_USB=y
CONFIG_USB_DEVICE_STACK=y
CONFIG_USB_DEVICE_PRODUCT="VND"
CONFIG_USB_COMPOSITE_DEVICE=y
CONFIG_USB_SELF_POWERED=y
CONFIG_USB_MAX_POWER=50

# enable CDC ACM ports
CONFIG_SERIAL=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_UART_LINE_CTRL=y
CONFIG_USB_CDC_ACM=y
CONFIG_USB_CDC_ACM_DEVICE_NAME="CDC_ACM"
CONFIG_USB_CDC_ACM_DEVICE_COUNT=2

# enable USB shell on CDC #0
CONFIG_SHELL=y
CONFIG_SHELL_BACKENDS=y
CONFIG_SHELL_BACKEND_SERIAL=y
CONFIG_UART_SHELL_ON_DEV_NAME="CDC_ACM_0"
CONFIG_SHELL_PROMPT_UART="usb:~$ "
CONFIG_SHELL_LOG_BACKEND=n

[Øyvind]

Hello, 

Can you provide some more information? What application are you running? Are you using customer HW or a development kit? 

Thanks. 

Kind regards,
Øyvind

[Dmitry Kr]

Dear Oywind, 

We're running our own target board, it has USB only connectivity.

Please note: it works well on previous nCS releases, and nothing (initially) has been changed when moving to nCS 1.6.1, when the issue appears.

Now we can use actually only RTT shell and it is not useful for field testing / algorithm tuning of the application solution.

[Øyvind]

Hi, I've discussed the issue with our developers, and a similar question was asked in the Zephyr Slack community. Could you please try adding the following to your config:

CONFIG_SHELL_BACKEND_SERIAL_INIT_PRIORITY=51

Kind regards,

Øyvind

[Dmitry Kr]

Hi Oyvind, 

Many thanks, it works.