<?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>Adding UART breaks code&amp;#39;s functionality</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/20440/adding-uart-breaks-code-s-functionality</link><description>Hi, I&amp;#39;m learning to use the nrf52832 (PCA10040).
I&amp;#39;m on SDK12.2.0 S132. 
 I&amp;#39;ve done those basic tutorials while merging codes from the examples.
My code can currently read the die temperature and broadcast it via BLE notification every 1 second. </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 15 Mar 2017 09:55:24 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/20440/adding-uart-breaks-code-s-functionality" /><item><title>RE: Adding UART breaks code's functionality</title><link>https://devzone.nordicsemi.com/thread/79691?ContentTypeID=1</link><pubDate>Wed, 15 Mar 2017 09:55:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bb1c81f1-8989-44f1-a905-cc14e0a57d5f</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;&lt;strong&gt;1)&lt;/strong&gt; Yes, that&amp;#39;s correct. There is only one UART on nRF52832, so it can either be used by NRF_LOG or by your application for other purposes.  Since you are using the nRF52-DK, you can use logging over RTT instead of UART. By doing so, you free up the UART for your application.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2)&lt;/strong&gt; The reason that nRFConnect cannot find your board anymore, is probably because the problem in the code is during the initialization, so the board never starts to advertise. Could you run the chip in debug mode, and check if (and where) it fails in the initialization?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>