<?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>How do I &amp;quot;tap into&amp;quot; LOG_### to get the string that would be sent out to the RTT Console?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/102218/how-do-i-tap-into-log_-to-get-the-string-that-would-be-sent-out-to-the-rtt-console</link><description>Looking at the LOG_### output in the RTT Console is very helpful for development. This is not possible when our product is packaged up in its final state. 
 What I would like to do is get the string that otherwise would be displayed in the RTT Console</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 27 Jul 2023 06:56:37 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/102218/how-do-i-tap-into-log_-to-get-the-string-that-would-be-sent-out-to-the-rtt-console" /><item><title>RE: How do I "tap into" LOG_### to get the string that would be sent out to the RTT Console?</title><link>https://devzone.nordicsemi.com/thread/438418?ContentTypeID=1</link><pubDate>Thu, 27 Jul 2023 06:56:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5fa681b4-ee95-4133-b0e8-0508169a692d</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Yes, that is expected. Our developers want to ensure that the toolchain can be used with multiple future versions of our SDK.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;div&gt;New behavior is that multiple NCS versions can map to the same toolchain, which are versioned independently.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;/blockquote&gt;
[quote user="GameCodingNinja"] I&amp;#39;ll take a look at the example code. Thanks![/quote]
&lt;p&gt;You&amp;#39;re welcome :)&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do I "tap into" LOG_### to get the string that would be sent out to the RTT Console?</title><link>https://devzone.nordicsemi.com/thread/438266?ContentTypeID=1</link><pubDate>Wed, 26 Jul 2023 12:24:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1a5dc870-84ef-4868-b9a6-399cb095a75b</guid><dc:creator>GameCodingNinja</dc:creator><description>&lt;p&gt;I&amp;#39;m actually upgrading to v2.4.0 as I type. Started working on this yesterday. I&amp;#39;ll take a look at the example code. Thanks!&lt;/p&gt;
&lt;p&gt;Question. When I pulled down SDK v2.4.0, the folder in ncs/toolchains was named 31f4403e35. Normally the toolchain folder name is the same as the SDK. Why is that?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do I "tap into" LOG_### to get the string that would be sent out to the RTT Console?</title><link>https://devzone.nordicsemi.com/thread/438230?ContentTypeID=1</link><pubDate>Wed, 26 Jul 2023 10:59:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5fa1452b-e556-4830-b18e-d020823689cc</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span dir="ltr"&gt;During the summer season, our workforce is currently operating with reduced staff levels throughout the company, which may lead to slight delays in our response time as we await additional resources. Rest assured, we are actively addressing all issues and working diligently to resolve them promptly.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;What version of the nRF Connect SDK are you running? In nRF Connect SDK v2.4.0 there is the Logging sample which uses BLE Backend (&lt;em&gt;zephyr\samples\subsys\logging\ble_backend&lt;/em&gt;)&lt;/p&gt;
&lt;p&gt;Let me know if this solves your issue.&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>