https://devzone.nordicsemi.com/f/nordic-q-a/11079/can-you-fix-nrf_log-in-sdk-11Not sure if forums or MyPage support requests are better for this. It seems NRF_LOG has taken a step backward from what was used in the previous nRF52 0.9.2 SDK. What I&#39;ve discovered is that there is no buffering at all taking place. If the remoteen-USTelligent Community 13Wed, 30 Dec 2015 20:01:42 GMThttps://devzone.nordicsemi.com/thread/41441?ContentTypeID=1Wed, 30 Dec 2015 20:01:42 GMT137ad170-7792-4731-bb38-c0d22fbe4515:34af3d5a-68b4-4d3a-9cbc-307189df1c7fRichard von Lehe<p>See my comment above and Wojtek&#39;s suggestion. I had forgotten that in the previous SDK I had swapped out app_uart and replaced it with app_fifo and app_uart_fifo. This works for me with IAR now, and I&#39;ll eventually figure out why it&#39;s not working for me with gcc.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/41439?ContentTypeID=1Wed, 30 Dec 2015 19:59:47 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e59ad3fb-a90b-4192-983b-2009669bbe6fRichard von Lehe<p>OK, all is well. I had completely forgotten that it is possible to swap <em>out</em> app_uart.c and swap <em>in</em> app_fifo.c and app_uart_fifo.c. I was able to do that with the new SDK. It seems the normal non-fifo UART functionality is not very useful, at least for my purposes. I also got RTT logging to work, and that might come in handy at some point, but it seems like it would be a bit less convenient since it ties up the JLINK connection. Maybe I need to look in to that further, as there must be a way to debug and view RTT logging simultanteously.</p> <p>In any case, I&#39;m marking this answered.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/41440?ContentTypeID=1Wed, 30 Dec 2015 12:26:26 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b0361c05-7646-4b84-8004-4001436bed8dWojtek<p>You can use flow control or fifo version of app_uart to get rid of that problem.</p><div style="clear:both;"></div>