https://devzone.nordicsemi.com/f/nordic-q-a/120494/deferred-logging-with-rttIs there any point to using deferred logging with the RTT backend? The way I understand RTT is that it writes the message to a buffer where it is fetched via DAP, skipping the delay of UART printing. So is there any argument for leavong deferreden-USTelligent Community 13Mon, 07 Apr 2025 06:37:05 GMThttps://devzone.nordicsemi.com/thread/530743?ContentTypeID=1Mon, 07 Apr 2025 06:37:05 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fb3cdc4e-838b-4bf2-963a-e84b0d69824bSusheel Nuguru<p>Another use case might be that you do not rely on any time sensitive log so you give the CPU time to higher priority/important processing and just process the logs during less time sensitive idle times.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/530711?ContentTypeID=1Sun, 06 Apr 2025 10:48:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a7a0bb3a-66b6-403b-bd91-496df72fbfe1Turbo J<p>The point is less stack usage for the thread that produced the message as it does not call printf() directly.</p> <p>Try enabling&nbsp; <code>CONFIG_LOG_DEFAULT_LEVEL=4</code> or something like <code>CONFIG_BT_LOG_LEVEL_DBG=y</code>. Those usually produce stack overflows with default stack sizes.</p><div style="clear:both;"></div>