<?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>Segger Embedded Studio (SES) debug terminal fails to log some of the time.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/56895/segger-embedded-studio-ses-debug-terminal-fails-to-log-some-of-the-time</link><description>I&amp;#39;m working on a few projects for for a smart home company. My machine is running Windows 10 and I&amp;#39;m on SES version 4.40. I&amp;#39;m using my dev board (a PCA10040) to program the products I am developing. 
 Rarely, when I go to run the program on the device</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 27 Jan 2020 16:45:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/56895/segger-embedded-studio-ses-debug-terminal-fails-to-log-some-of-the-time" /><item><title>RE: Segger Embedded Studio (SES) debug terminal fails to log some of the time.</title><link>https://devzone.nordicsemi.com/thread/231247?ContentTypeID=1</link><pubDate>Mon, 27 Jan 2020 16:45:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f7b01cb2-2547-4456-bb6b-b1c49362e46c</guid><dc:creator>Ryjan</dc:creator><description>&lt;p&gt;Thank you. I will keep this updated. Restarting SES and even power cycling the computer had no effect. When it did start working, I had not restarted the computer or SES. It certainly is an odd issue.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Segger Embedded Studio (SES) debug terminal fails to log some of the time.</title><link>https://devzone.nordicsemi.com/thread/231013?ContentTypeID=1</link><pubDate>Mon, 27 Jan 2020 06:48:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d9a5b071-2cc5-434f-a639-e9f7b616f633</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Thanks for the update. I&amp;#39;m sorry, but I don&amp;#39;t have any idea what the reason for this could be. Did you close and restart SES at any point here, could there have been an update/hotfix to SES between these moments. Anyway, I&amp;#39;m glad you&amp;#39;re able to use the RTT logging now. Don&amp;#39;t hesitate to update the thread should the error reappear again.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Segger Embedded Studio (SES) debug terminal fails to log some of the time.</title><link>https://devzone.nordicsemi.com/thread/230937?ContentTypeID=1</link><pubDate>Fri, 24 Jan 2020 18:18:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:75f6cb8c-2b68-4ecf-a4e9-25d98419c65a</guid><dc:creator>Ryjan</dc:creator><description>&lt;p&gt;I have confirmed that definition is set to 0. I&amp;#39;m also not using RTT for anything else in this project. &lt;/p&gt;
&lt;p&gt;However, this morning the debug terminal has worked correctly every time I&amp;#39;ve started it. The computer has not been power cycled, the code was not altered since yesterday. When I left yesterday, it was maybe working once in 20 tries. Today it&amp;#39;s worked every time, from my first program run&amp;nbsp; to my latest, after I have done some clean up on the minor changes I have been making over the past week. I was about to try rolling back, but the problem is not repeatable as of this morning. If and when it comes back, I will try your next suggestion of rolling back to 4.12.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m still interested in finding the cause and I won&amp;#39;t be surprised if this issue shows up again. I&amp;#39;ll keep this updated.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Segger Embedded Studio (SES) debug terminal fails to log some of the time.</title><link>https://devzone.nordicsemi.com/thread/230796?ContentTypeID=1</link><pubDate>Fri, 24 Jan 2020 09:00:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0857ef67-800c-46bf-904e-ea51656cc3b7</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Are you using the RTT for something other than debugging in this project? Can you also confirm that you tried setting &lt;span&gt;NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED&amp;nbsp;to 0 in your sdk_config.h file?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I&amp;#39;ve also seen an issue where newer versions of SES has issues logging SDK v.15.3 projects. In the SDK v.15.3 release notes, you can see that the SES version used for testing and verification was SESv.4.12, and this version has been confirmed output the debug info in the debug terminal, so I suggest you try v.4.12 to see if it may be a problem with your version of SES (I thought this had been fixed by now, but I&amp;#39;d say it&amp;#39;s worth a shot).&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Simon&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Segger Embedded Studio (SES) debug terminal fails to log some of the time.</title><link>https://devzone.nordicsemi.com/thread/230669?ContentTypeID=1</link><pubDate>Thu, 23 Jan 2020 14:36:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f56f6e94-c266-4170-9df7-3e82cf8a9ec8</guid><dc:creator>Ryjan</dc:creator><description>&lt;p&gt;I forgot to include that I&amp;#39;m working with SDK15.3.0&lt;/p&gt;
&lt;p&gt;I checked the COM port and I receive nothing on it, unfortunately.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Segger Embedded Studio (SES) debug terminal fails to log some of the time.</title><link>https://devzone.nordicsemi.com/thread/230668?ContentTypeID=1</link><pubDate>Thu, 23 Jan 2020 14:36:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9dcdfa3e-f745-43ae-a4f8-3823b2044403</guid><dc:creator>Ryjan</dc:creator><description>&lt;p&gt;I checked the defines in sdk_config and those are all as the same except for NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE. Right now that is set to 1500. I have now tried it at 64 and also tried increasing it beyond 1500 to no avail. I just now attempted to increase NRF_LOG_BACKEND_RTT_TX_RETRY_CNT to 8 and there was no change. Also I have made sure that I am in debug mode and for good measure have compiled for release, run it and then done a clean recompile for debug and run it with no change as well.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Segger Embedded Studio (SES) debug terminal fails to log some of the time.</title><link>https://devzone.nordicsemi.com/thread/230612?ContentTypeID=1</link><pubDate>Thu, 23 Jan 2020 13:17:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f51ec21-35e5-4c98-bac7-72838316aa8d</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Please check your sdk_config.h file to see that the following defines are set to these values:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;// &amp;lt;/h&amp;gt; 
//==========================================================

// &amp;lt;/h&amp;gt; 
//==========================================================

// &amp;lt;h&amp;gt; nRF_Log 

//==========================================================
// &amp;lt;e&amp;gt; NRF_LOG_BACKEND_RTT_ENABLED - nrf_log_backend_rtt - Log RTT backend
//==========================================================
#ifndef NRF_LOG_BACKEND_RTT_ENABLED
#define NRF_LOG_BACKEND_RTT_ENABLED 1
#endif
// &amp;lt;o&amp;gt; NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE - Size of buffer for partially processed strings. 
// &amp;lt;i&amp;gt; Size of the buffer is a trade-off between RAM usage and processing.
// &amp;lt;i&amp;gt; if buffer is smaller then strings will often be fragmented.
// &amp;lt;i&amp;gt; It is recommended to use size which will fit typical log and only the
// &amp;lt;i&amp;gt; longer one will be fragmented.

#ifndef NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE
#define NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE 64
#endif

// &amp;lt;o&amp;gt; NRF_LOG_BACKEND_RTT_TX_RETRY_DELAY_MS - Period before retrying writing to RTT 
#ifndef NRF_LOG_BACKEND_RTT_TX_RETRY_DELAY_MS
#define NRF_LOG_BACKEND_RTT_TX_RETRY_DELAY_MS 1
#endif

// &amp;lt;o&amp;gt; NRF_LOG_BACKEND_RTT_TX_RETRY_CNT - Writing to RTT retries. 
// &amp;lt;i&amp;gt; If RTT fails to accept any new data after retries
// &amp;lt;i&amp;gt; module assumes that host is not active and on next
// &amp;lt;i&amp;gt; request it will perform only one write attempt.
// &amp;lt;i&amp;gt; On successful writing, module assumes that host is active
// &amp;lt;i&amp;gt; and scheme with retry is applied again.

#ifndef NRF_LOG_BACKEND_RTT_TX_RETRY_CNT
#define NRF_LOG_BACKEND_RTT_TX_RETRY_CNT 3
#endif&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Can you confirm that your project settings are set to debug mode and not release? It might be that you&amp;nbsp;generally run this project in release mode.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Segger Embedded Studio (SES) debug terminal fails to log some of the time.</title><link>https://devzone.nordicsemi.com/thread/230468?ContentTypeID=1</link><pubDate>Thu, 23 Jan 2020 05:51:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f682cf81-d04a-4e8a-b4fc-8d988f5bfa63</guid><dc:creator>Ameer Usman</dc:creator><description>&lt;p&gt;Just out of curiosity, the DK also creates a COM Port where it throws the data, are you receiving data at the COM port?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>