<?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>Why NRF_LOG_INFO is going crazy ?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22474/why-nrf_log_info-is-going-crazy</link><description>I think I found the source of many of my recent problem. The print in Segger is going crazy.
I found out that if I increment a simple variable and print it when I hit debug and run ( then play button), they system will skip or stop in the middle : </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 01 Jun 2017 08:21:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22474/why-nrf_log_info-is-going-crazy" /><item><title>RE: Why NRF_LOG_INFO is going crazy ?</title><link>https://devzone.nordicsemi.com/thread/88352?ContentTypeID=1</link><pubDate>Thu, 01 Jun 2017 08:21:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:df55d3fc-b71e-4280-a0a2-014d58ab7b70</guid><dc:creator>Lola</dc:creator><description>&lt;p&gt;Thank you ! I wonder why am I the only one at least at Google, to having this kind of problems :)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why NRF_LOG_INFO is going crazy ?</title><link>https://devzone.nordicsemi.com/thread/88351?ContentTypeID=1</link><pubDate>Thu, 01 Jun 2017 05:45:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9a55cc1a-0be6-48b9-be30-dc672f3b83df</guid><dc:creator>Krzysztof Chruscinski</dc:creator><description>&lt;p&gt;You can also try to increase logger buffer size (NRF_LOG_DEFERRED_BUFSIZE in sdk_config.h). This is the buffer which holds log entries before they are processed and send to the host (NRF_LOG_PROCESS, NRF_LOG_FLUSH). But as Jorgen mentioned it can be that RTT is losing the data because it is not able to process.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why NRF_LOG_INFO is going crazy ?</title><link>https://devzone.nordicsemi.com/thread/88350?ContentTypeID=1</link><pubDate>Thu, 01 Jun 2017 05:36:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0305f870-ea3c-4c1b-a37f-f1727ab5fad8</guid><dc:creator>J&amp;#248;rgen Kvalvaag</dc:creator><description>&lt;p&gt;NRF_LOG is non-blocking so, as @Turbo J mentioned, by default it will skip if there is no space in buffer.&lt;/p&gt;
&lt;p&gt;You can configure thisbehaviour in sdk_config.h. Look under nRF_Segger_RTT -&amp;gt; segger_rtt -&amp;gt; SEGGER_RTT_CONFIG_DEFAULT_MODE, you can change it to BLOCK_IF_FIFO_FULL.&lt;/p&gt;
&lt;p&gt;This way you should be able to print whatever you want without inserting delays.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why NRF_LOG_INFO is going crazy ?</title><link>https://devzone.nordicsemi.com/thread/88349?ContentTypeID=1</link><pubDate>Wed, 31 May 2017 20:22:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c04fb343-98d0-4bc0-a8bc-be187dde65fc</guid><dc:creator>Lola</dc:creator><description>&lt;p&gt;Yea well I went with delay. thanks a lot.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why NRF_LOG_INFO is going crazy ?</title><link>https://devzone.nordicsemi.com/thread/88348?ContentTypeID=1</link><pubDate>Wed, 31 May 2017 20:06:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e5cf663b-5fef-466c-8d9e-a1221cce2fa7</guid><dc:creator>Lola</dc:creator><description>&lt;p&gt;@Turbo J Not sure I get it, so how to solve this and be able to print what ever I want ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why NRF_LOG_INFO is going crazy ?</title><link>https://devzone.nordicsemi.com/thread/88347?ContentTypeID=1</link><pubDate>Wed, 31 May 2017 20:05:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:616fee68-3cf5-4d64-98e4-172318854583</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;NRF_LOG_* functions like to skip messages when there is no buffer space available.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>