<?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 stop receive task timeout RXTO</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/52394/uarte-stop-receive-task-timeout-rxto</link><description>I&amp;#39;m facing problem when I want to stop receive task, event EVENT_RXTO came at long time period. 4 to 5 baudrate bytes. 
 Is trere any documentation where could read time between task TASK_STOPRX and event EVENT_RXTO and task TASK_FLUSHRX and EVENT_ENDRX</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 20 Sep 2019 11:25:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/52394/uarte-stop-receive-task-timeout-rxto" /><item><title>RE: UARTE stop receive task timeout RXTO</title><link>https://devzone.nordicsemi.com/thread/210911?ContentTypeID=1</link><pubDate>Fri, 20 Sep 2019 11:25:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:972e9ba1-e833-460f-a353-83f0d32fbf66</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This seems to be according to spec. Here is an excerpt from the nRF52840 PS:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/ps_nrf52840/uarte.html?cp=3_0_0_5_33_2#concept_uzb_p2m_wr"&gt;The UARTE is able to receive up to four bytes after the STOPRX task has been triggered as long as these are sent in succession immediately after the RTS signal is deactivated. This is possible because after the RTS is deactivated the UARTE is able to receive bytes for an extended period equal to the time it takes to send 4 bytes on the configured baud rate.&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;So the timing will depend on what baud-rate you use. But is the problem that you&amp;#39;re receiving too many bytes? In that case, can you read&amp;nbsp;&lt;span&gt;RXD.AMOUNT before triggering the stop task, and then discard any additional bytes that come in after?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>