<?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>Dynamically turning UART logging on and off</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/116003/dynamically-turning-uart-logging-on-and-off</link><description>This issue is exposed, or exacerbated, by our ongoing project of trying to upgrade from NCS 2.3.0 (Zephyr 3.2.99) to NCS 2.6.1 (Zephyr 3.5.99). 
 In our product, we emit log messages over USB UART, for development purposes. 
 Once we launch, when the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 04 Nov 2024 13:47:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/116003/dynamically-turning-uart-logging-on-and-off" /><item><title>RE: Dynamically turning UART logging on and off</title><link>https://devzone.nordicsemi.com/thread/508962?ContentTypeID=1</link><pubDate>Mon, 04 Nov 2024 13:47:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b64c02df-0189-4d56-9d33-16e2a9482596</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;This was more of a generic suggestion than pointing to anything in particular for your use case. I see that you seem to have understood how the logging works, and that this is more of a technical question in how it&amp;nbsp;&lt;strong&gt;should&lt;/strong&gt; be done. I&amp;#39;m afraid I don&amp;#39;t have any specific suggestions, as the &amp;quot;suggested&amp;quot; way would be to use this LOG_BACKEND_DEFINE, but in your case I think making this change is warranted. Just know that with this change you should also do thorough testing to make sure it is running as it should and won&amp;#39;t trig any bugs on your end. I&amp;#39;d say this looks like an okay workaround.&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: Dynamically turning UART logging on and off</title><link>https://devzone.nordicsemi.com/thread/508830?ContentTypeID=1</link><pubDate>Fri, 01 Nov 2024 14:28:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5c06e68f-fe0d-4bd0-ae08-652474fa6073</guid><dc:creator>Yaron Shragai</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t see anything in those guides that is relevant to this issue. What am I missing?&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;
&lt;p&gt;Yaron&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Dynamically turning UART logging on and off</title><link>https://devzone.nordicsemi.com/thread/508798?ContentTypeID=1</link><pubDate>Fri, 01 Nov 2024 12:01:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:04827746-b966-4a49-addc-f45f104f18f9</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;First off, have you followed the migration guides to NCS &lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_guide_2.5.html"&gt;&lt;strong&gt;2.5.0&lt;/strong&gt; &lt;/a&gt;and &lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_guide_2.6.html"&gt;&lt;strong&gt;2.6.0&lt;/strong&gt; &lt;/a&gt;to which should help you move from an older SDK version to a newer one? I&amp;#39;d recommend starting there to move to correctly move to the newer SDK and see if the issue is still reproducible.&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></channel></rss>