https://devzone.nordicsemi.com/f/nordic-q-a/24597/sdk-14-rtt-logging-issueHi, The followings are more like an observation rather than a question.. We just upgraded to SDK 14, and realized that some of the RTT logs were mysteriously disappeared. We tried with and without NRF_LOG_DEFERRED, played with buffer sizes, buten-USTelligent Community 13Wed, 23 Aug 2017 12:22:44 GMThttps://devzone.nordicsemi.com/thread/96849?ContentTypeID=1Wed, 23 Aug 2017 12:22:44 GMT137ad170-7792-4731-bb38-c0d22fbe4515:707fbadc-b7a4-4b28-b44b-00db88a68041Adam Sillye<p>Thank you, this was exactly what we looking for... Adam</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/96848?ContentTypeID=1Wed, 23 Aug 2017 10:46:25 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7ccf3a30-ee24-4fa3-9794-3f1e3ff6ee87Sigurd<p>Hi,</p> <p>You can configure the RTT behavior if the buffer is full in <code>sdk_config.h</code> by setting <code>SEGGER_RTT_CONFIG_DEFAULT_MODE</code> to the mode you want.</p> <p>The following modes are supported:</p> <blockquote> <p>SKIP - Do not block, output nothing.</p> </blockquote> <blockquote> <p>TRIM - Do not block, output as much as fits</p> </blockquote> <blockquote> <p>BLOCK - Wait until there is space in the buffer</p> </blockquote> <p>The default mode is SKIP. You could also try to increase the buffer size(<code>SEGGER_RTT_CONFIG_BUFFER_SIZE_UP</code>) before changing the mode, and see if that solves your issue. E.g. change <code>SEGGER_RTT_CONFIG_BUFFER_SIZE_UP</code> from 512 to 1024.</p><div style="clear:both;"></div>