What Kconfig (prj.conf) options should I use for enabling logging via RTT only (no UART).

RE: What Kconfig (prj.conf) options should I use for enabling logging via RTT only (no UART).

nik2k — Fri, 28 Jun 2024 16:01:19 GMT

Hi Vidar, that clears quite a few things up for me. In the meantime I have done a bit of digging myself with your help. Thanks. You may close the issue.

RE: What Kconfig (prj.conf) options should I use for enabling logging via RTT only (no UART).

Vidar Berg — Thu, 27 Jun 2024 10:15:08 GMT

Both the logger module and the console will redirect data to the serial terminal if UART backends are enabled. If you want to disable logging and printk/printf output to the console (RTT or UART), you can disable the following symbols: CONFIG_CONSOLE=n,
CONFIG_LOG=n
CONFIG_SERIAL=n

Note: you will get a Kconfig warning if you try to select CONFIG_RTT_CONSOLE in your project configiuration file while the console is disabled.

RE: What Kconfig (prj.conf) options should I use for enabling logging via RTT only (no UART).

nik2k — Wed, 26 Jun 2024 14:25:51 GMT

Hi Vidar, thanks for you time, and sorry for the delayed response. What about CONFIG_CONSOLE? Should I remove it ? I'm also a little shaky on whether to keep CONFIG_RTT_CONSOLE and CONFIG_LOG_BACKEND_RTT, or both?

RE: What Kconfig (prj.conf) options should I use for enabling logging via RTT only (no UART).

Vidar Berg — Mon, 24 Jun 2024 12:04:47 GMT

Hi,

It should be sufficient to set CONFIG_SERIAL to '=n'. This will disable the UART serial drivers. To ensure the UART drivers can't be enabled, you can disable the uart0 node in your device tree, either in your board file or with a board overlay.

When the UART console is enabled, printk()/printf() input will be relayed over UART, provided that CONFIG_SERIAL is enabled. Similar to how the LOG_* macros work when logging over UART is enabled.

&uart0 {
	status = "disabled";
};

Best regards,

Vidar