<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NRF RTT Logging get buffered fragments</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/123926/nrf-rtt-logging-get-buffered-fragments</link><description>I am using NRF5340 with NRF connect (Zephyr) and logging out to RTT (printk or printf, etc) , which works but sometimes I get buffered fragments and dont see the rest of the print until more events happen that forces it to flush. Is it possible to force</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 26 Aug 2025 08:49:34 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/123926/nrf-rtt-logging-get-buffered-fragments" /><item><title>RE: NRF RTT Logging get buffered fragments</title><link>https://devzone.nordicsemi.com/thread/546728?ContentTypeID=1</link><pubDate>Tue, 26 Aug 2025 08:49:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5e2ee223-f06d-40b5-996c-f339d86e6a06</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;I strongly recommend looking into the source code here. RTT logging has a mountain of config options and its easier to see what these do in the code itself.&lt;/p&gt;
&lt;p&gt;I&amp;#39;d try configuring a bigger log buffer first, the 5340 usually has unused RAM left.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>