<?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>rtt when link disconnected</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/25094/rtt-when-link-disconnected</link><description>I have an example combining BLE, UART and SPI in which I use RTT to watch the startup process.
The SoC is nRF52 (BLE Nano2); building with armgcc.
This works ok when JLink is connected. However, if I unplug the JLink the BLE fails with a GATT_CONN_TIMEOUT</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 21 Sep 2017 07:05:00 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/25094/rtt-when-link-disconnected" /><item><title>RE: rtt when link disconnected</title><link>https://devzone.nordicsemi.com/thread/98828?ContentTypeID=1</link><pubDate>Thu, 21 Sep 2017 07:05:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cdb4a441-e473-463d-8e05-7d9bc64b11b5</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;This &lt;a href="https://devzone.nordicsemi.com/question/54497/android-app-gatt-conn-timeout/"&gt;case&lt;/a&gt; might be able to help you out.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: rtt when link disconnected</title><link>https://devzone.nordicsemi.com/thread/98827?ContentTypeID=1</link><pubDate>Mon, 18 Sep 2017 13:28:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c52c89a0-b34a-4b99-8645-262c8d2ac238</guid><dc:creator>paul_tanner</dc:creator><description>&lt;p&gt;Thx.&lt;/p&gt;
&lt;p&gt;OK. so there&amp;#39;s some other issue.  I removed all the RTT calls and the problem is the same.  The timeout seen by the phone app is caused by the example crashing before BLE is connected.&lt;/p&gt;
&lt;p&gt;So evidently I have a hardware problem.  I have tried additional pullup and down on the SWDIO and SWDCLK. Does not fix it. Neither does pulsing nRESET pin low.&lt;/p&gt;
&lt;p&gt;Could the JLink have put the nRF52 in some mode where it needs to remain connected? Just guessing.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: rtt when link disconnected</title><link>https://devzone.nordicsemi.com/thread/98826?ContentTypeID=1</link><pubDate>Mon, 11 Sep 2017 20:17:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:751ad80c-f417-48b2-b11d-d9a975453dd7</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;No. RTT uses a fixed sized ring buffer which is overwritten if it fills up. RTT was designed to be able to be left in your code as it just harmlessly writes data, if a Segger isn&amp;#39;t connected, it just doesn&amp;#39;t get read or go anywhere.&lt;/p&gt;
&lt;p&gt;Segger used to have a much better description of RTT than it seems to now, there&amp;#39;s an old copy of it &lt;a href="https://www.phaedsys.com/principals/segger/seggerjlinksw.html"&gt;www.phaedsys.com/.../seggerjlinksw.html&lt;/a&gt; which has the original description of the ring buffer and a comment you can use it without a debugger connected.&lt;/p&gt;
&lt;p&gt;So that&amp;#39;s most likely not your problem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>