<?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>Serial port libray and  NRF_LOG does not co-exist..?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/49162/serial-port-libray-and-nrf_log-does-not-co-exist</link><description>I&amp;#39;m using SDK 15.3.2 with SD 132. SES and the 10040 DK. 
 I&amp;#39;m not clear how NRF_LOG module and the new serial port library is support to work together. 
 I can easily make the serial port example work, and NRF_LOG works in various projects. 
 However</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 01 Jul 2019 06:49:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/49162/serial-port-libray-and-nrf_log-does-not-co-exist" /><item><title>RE: Serial port libray and  NRF_LOG does not co-exist..?</title><link>https://devzone.nordicsemi.com/thread/195505?ContentTypeID=1</link><pubDate>Mon, 01 Jul 2019 06:49:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:78a2f915-71db-487b-8e19-723b47e52a00</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;There is only one UART on the NRF chip, and NRF_LOG uses it by default.&lt;/p&gt;
&lt;p&gt;Using the on-board JLink, you can switch NRF_LOG to use Segger RTT as transport backend. This will free the UART in order to be used by the serial port lib.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>