NCS Chat example UART

[Sergnrf]

Hi Team,
NCS v2.3.0
nrf52840


I use Chat example, when I look at what comes to uart, I see messages that I don’t need, as shown below

*** Booting Zephyr OS build v3.2.99-ncs2 ***

Initializing...
I: 8 Sectors of 4096 bytes
I: alloc wra: 2, 5b8
I: data wra: 2, 518
[m

[1;Bluetooth initialized
Mesh initialized
32muart:~$ [m

tell me please how can I turn them off, I want only received messages from other nodes to go to my uart.

Thank you.

[Hieu]

Hi Sergnrf,

Let me feedback for each line that you want to turn off.

*** Booting Zephyr OS build v3.2.99-ncs2 ***

This is the boot banner. You can turn it off via CONFIG_BOOT_BANNER.

Initializing...

This is just a printk() done by the application itself in main.c. You can remove it.

I: 8 Sectors of 4096 bytes
I: alloc wra: 2, 5b8
I: data wra: 2, 518

This is log done by the NVS module. You have a few options:

• Turn off logging completely (CONFIG_LOG)
  • I don't recommend completely disable logging unless you are sure of it. Future troubleshooting might become much more difficult.
• Turn down logging level of the NVS module (CONFIG_NVS_LOG_LEVEL_CHOICE)
  
  • Note that the Kconfig is a choice type. That means you choose an options by setting one of the choice to y
    For example: CONFIG_NVS_LOG_LEVEL_ERR=y.
• Disable logging backend UART or SHELL, and use a different backend instead.
  
  • Log backend shell also has to be turned off, because the Mesh Chat example uses Shell for the CLI.
  • For example:
    

    CONFIG_LOG_BACKEND_UART=n
    CONFIG_SHELL_LOG_BACKEND=n
    CONFIG_LOG_BACKEND_RTT=y

  • References:
    • CONFIG_SHELL_LOG_BACKEND
    • CONFIG_LOG_BACKEND_UART
    • CONFIG_LOG_BACKEND_RTT
  • Note that the new log backend's dependencies have to be met.

Bluetooth initialized
Mesh initialized

Again, printk() in main.c.

Hieu

[Sergnrf]

Thank you, in general, it helped, there was a small artifact that I can’t find where it is displayed

.[m.....[1;32muart:~$ .[m

[Hieu]

I didn't think you want even that off. That is the Shell prompt. It is a part of the CLI which would be helpful to differentiate input and output.

The ".[m.....[1;32m" and ".[m" is the ANSI escape sequences to format the "uart:~$" prompt. 

To disable coloring, you can turn CONFIG_SHELL_VT100_COLORS off.

If you want to disable the prompt itself, set CONFIG_SHELL_PROMPT_UART to "".

CONFIG_SHELL_VT100_COLORS=n
CONFIG_SHELL_PROMPT_UART=""

If you are sending command over UART to the device, the Shell by default also echo back what you sent, so that you can see it on your terminal. That echo can also be turned off with CONFIG_SHELL_ECHO_STATUS.

[Sergnrf]

Thank you, it helped.
I need to remove everything but the message itself.
.[J  three extra characters left, they stand in front of the message.

[Hieu]

That's odd. I have not figured out how to get my terminal program to show the escape sequences, so I am not certain what this could be.

Could you give more log where this ".[J" is included?

If you could share how to configure a terminal program to show these characters, that will help me debug faster as well.

I am on sick leave now, but I should return in a few days.

[Sergnrf]

I use COM Port Toolkit. 

Issue is closed, uart_tx helped.

Thank you