RE: Zehpyr Shell + Logging on RTT

Dmitry Kr — Tue, 05 Jul 2022 09:14:25 GMT

Dear Nordic,

there is some misunderstanding in terms: RTT Viewer operates by Terminals, not RTT channels. Altougth RTT channel for logger (RTT #1) is created and operates well, there is no ready-to-use software to view the logging output and use shell simultaneosly.

We could use SEGGER RTT Logger, but it only saves logs to file - no option to view logs online.

Still, there is ability to select particular terminal mark or out to particular terminal using SEGGER_RTT_TerminalOut() funciton. So, do we have a solution to distinquish logs and shell interface between logical terminals easier than writing our own log backend?

RE: Zehpyr Shell + Logging on RTT

Dmitry Kr — Tue, 05 Jul 2022 07:56:33 GMT

Have seen following:

Log and shell through RTT backend don't play nicely

Using the Zigbee shell through Segger RTT backend

We have the following on prj.conf:

# 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_BACKEND_RTT_BUFFER=1

CONFIG_LOG_OVERRIDE_LEVEL=0

CONFIG_LOG_MAX_LEVEL=4

# CONFIG_LOG_PRINTK=n

CONFIG_LOG_MODE_OVERFLOW=y

CONFIG_LOG_PROCESS_THREAD=y

CONFIG_LOG_PROCESS_THREAD_SLEEP_MS=100

CONFIG_LOG_BUFFER_SIZE=16384

CONFIG_LOG_PROCESS_THREAD_STACK_SIZE=16384

# console output on RTT

CONFIG_RTT_CONSOLE=y

CONFIG_SHELL=y

CONFIG_SHELL_BACKENDS=y

CONFIG_SHELL_BACKEND_RTT=y

CONFIG_SHELL_PROMPT_RTT="rtt:~$ "