https://test-devzone.nordicsemi.com/f/nordic-q-a/88339/rtt-logging-in-ncs-messages-lostHello, I am trying to get reliable log output using the Nordic Connect SDK (NCS) over RTT. When I use Minimal mode, the following config: CONFIG_LOG_MODE_MINIMAL=y CONFIG_SEGGER_RTT_MODE_BLOCK_IF_FIFO_FULL=y I get the following output at startupen-USTelligent Community 13 Non-ProductionMon, 30 May 2022 13:23:34 GMThttps://test-devzone.nordicsemi.com/thread/370007?ContentTypeID=1Mon, 30 May 2022 13:23:34 GMT137ad170-7792-4731-bb38-c0d22fbe4515:54238d02-38a9-4beb-9948-9e4f7b049ebauser7377<p>Hi,</p> <p>Even if you use&nbsp;CONFIG_LOG_BLOCK_IN_THREAD=y there is a timeout which is 1000 (ms) by default, specified by CONFIG_LOG_BLOCK_IN_THREAD_TIMEOUT_MS. If you set this to -1, the logger will block forever if needed.</p><div style="clear:both;"></div>https://test-devzone.nordicsemi.com/thread/369737?ContentTypeID=1Fri, 27 May 2022 08:57:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d6079244-839e-4634-b605-2bae86bcb7acuser15175<p>Yes, okay, that works. Interestingly then the following config is not needed, maybe because the initial output all fits into the RTT buffer? I would conclude then that there must be a bug with blocking when the RTT buffer is full.</p> <p>#CONFIG_LOG_BLOCK_IN_THREAD=y<br />#CONFIG_LOG_BUFFER_SIZE=4096<br />#CONFIG_SEGGER_RTT_MODE_BLOCK_IF_FIFO_FULL=y</p><div style="clear:both;"></div>https://test-devzone.nordicsemi.com/thread/369718?ContentTypeID=1Fri, 27 May 2022 07:15:42 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2afa6128-44f2-418d-99de-af941c7de3b4user7377<p>Hi,</p> <p>Can you try to increase the RTT buffer size as well, using (say)&nbsp;<code>CONFIG_SEGGER_RTT_BUFFER_SIZE_UP=4096</code>?</p><div style="clear:both;"></div>