<?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>UARTE enable, then disable</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/83698/uarte-enable-then-disable</link><description>My project uses nRF52832 and I&amp;#39;m at the point of the project where I&amp;#39;m trying to minimize power consumption. 
 To assist in this, I created a very small main() that goes through all my peripherals/subsystems and turns them on, then off in one second intervals</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 19 Jan 2022 13:20:03 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/83698/uarte-enable-then-disable" /><item><title>RE: UARTE enable, then disable</title><link>https://devzone.nordicsemi.com/thread/348515?ContentTypeID=1</link><pubDate>Wed, 19 Jan 2022 13:20:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:17174c78-3e50-43a7-a919-ac6419ef67d2</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Sorry if I misunderstood, but are you satisfied with the workaround you mention here? It sounds like a solid option to me, so I don&amp;#39;t have any input on that. Let me know if we can close this case or if you have any follow up questions.&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: UARTE enable, then disable</title><link>https://devzone.nordicsemi.com/thread/348382?ContentTypeID=1</link><pubDate>Tue, 18 Jan 2022 20:27:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4b8d3c35-1699-4921-a8cc-33782f7af166</guid><dc:creator>CktDesigner</dc:creator><description>&lt;p&gt;Hi Simon,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m too far along in the project to replace libuarte with the simple UARTE&amp;nbsp; (we are about to go into production).&amp;nbsp; &amp;nbsp; It looks like I can&amp;#39;t use the code in the recommended link since it is not compatible with libuarte.&amp;nbsp; &amp;nbsp;&lt;/p&gt;
&lt;p&gt;For now, when we put our device in test mode, libuarte is enabled, and when test mode exits, the device is reset, thereby disabling libuarte and we return back to the expected power level.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In the next version, I&amp;#39;ll replace libuarte with a simple UARTE.&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UARTE enable, then disable</title><link>https://devzone.nordicsemi.com/thread/348219?ContentTypeID=1</link><pubDate>Tue, 18 Jan 2022 09:53:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9f07041f-dc3f-4a73-9faa-dddf6677cf01</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Let me know if you&amp;#39;re tried the suggestion by Sigurd in the thread I linked to, and whether you got it up and running or not.&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: UARTE enable, then disable</title><link>https://devzone.nordicsemi.com/thread/348143?ContentTypeID=1</link><pubDate>Mon, 17 Jan 2022 22:45:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4ac93603-cff9-43ca-bcab-07dc1328712a</guid><dc:creator>CktDesigner</dc:creator><description>&lt;p&gt;Hi Simon,&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;
&lt;p&gt;Yes, this is an nRF5 SDK project.&amp;nbsp; I&amp;#39;m using nRF_SDK_17.0.2_d674dde&lt;/p&gt;
&lt;p&gt;I&amp;#39;m using the UART for a test interface, and using the libuarte was convenient.&amp;nbsp; &amp;nbsp;Just wanted to be able to completely power it down when not in test mode...&lt;/p&gt;
&lt;p&gt;Thanks again!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UARTE enable, then disable</title><link>https://devzone.nordicsemi.com/thread/348065?ContentTypeID=1</link><pubDate>Mon, 17 Jan 2022 13:55:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cdec1fde-20ae-426f-81b9-db14e98a57eb</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;What SDK version are you using specifically? It looks like an nRF5 SDK project, but please confirm that as well as which version exactly you&amp;#39;re using.&lt;/p&gt;
&lt;p&gt;libuarte_async was designed to have RX always on, which is likely the main reason for this high current consumption. It&amp;#39;s primary goal is to be able to reliably receive data even without flow control which is achieved by not stopping RX (ENDRX-&amp;gt;STARTRX short). You can check out the&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/54271/nrf52840-fails-to-go-to-low-power-mode-when-using-uart-rx-double-buffering"&gt; latest edit by Sigurd in this thread&lt;/a&gt;, where he experimented with stopping the RX properly, and I think you should be able to achieve the lower current consumption by implementing this.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Is there a specific reason you&amp;#39;re using libuarte and not the regular UARTE example for your application?&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>