<?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 hardware timeout</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/123682/uarte-hardware-timeout</link><description>Board: nRF5340-DK SDK: nrf ncs v3.0.2 Hi, On the project I am working on there is a tight timing constraint for DMA timeout (30-40us). Also there was a need for specific baudrate. Regarding baudrate I&amp;#39;ve successfully added support for it NRF_UARTE_BAUDRATE_307200</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 22 Aug 2025 15:42:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/123682/uarte-hardware-timeout" /><item><title>RE: UARTE hardware timeout</title><link>https://devzone.nordicsemi.com/thread/546493?ContentTypeID=1</link><pubDate>Fri, 22 Aug 2025 15:42:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1632c795-f183-44b2-aa3d-46cd78c2ebe8</guid><dc:creator>Nemanja Jovicic</dc:creator><description>&lt;p&gt;Hi Hung,&lt;br /&gt;&lt;br /&gt;Colleague opened similar ticket with more info and ongoing discussion here&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/123764/uart-async-rx-latency-when-using-stoprx-task-on-nrf5340/546081"&gt;UART Async RX Latency When Using STOPRX Task on nRF5340 - Nordic Q&amp;amp;A - Nordic DevZone - Nordic DevZone&lt;br /&gt;&lt;br /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;We can close this ticket as duplicate.&lt;br /&gt;Thank you&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UARTE hardware timeout</title><link>https://devzone.nordicsemi.com/thread/545943?ContentTypeID=1</link><pubDate>Mon, 18 Aug 2025 14:19:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:82e76eb8-0619-4f6b-8549-3c0686c7c24c</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Nemanja,&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;Do you use 32kHz RC as the source for the LFCLK ? Have you used the 32kHz crystal as the clock source ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I think you are coming close to the limit of the driver. The smallest time the LFCLK can count is&amp;nbsp;30.517us (with some tolerance).&amp;nbsp;&lt;br /&gt;You are doing 80us timeout with divider = 2. The CPU has to go through some instructions between the interrupt and the time count. So I&amp;#39;m not so sure 80 with divider = 2 is still in the limit.&amp;nbsp;&amp;nbsp;&lt;br /&gt;You may have to modify the driver to be able to achieve smaller timeout.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Could you give us a more detailed requirement / how your protocol work so we can give you some advice ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>