<?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>Zephyr/UARTE uart_tx reports BUSY after receiving TX_DONE</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/82298/zephyr-uarte-uart_tx-reports-busy-after-receiving-tx_done</link><description>I have an application where I need to periodically write a few KB of data from my nRF to a host computer. Since TXD.MAXCNT tops out at 255 bytes, I&amp;#39;m trying to set up all the writes to keep going until the buffer has been written out. I followed something</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 31 Jan 2022 08:50:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/82298/zephyr-uarte-uart_tx-reports-busy-after-receiving-tx_done" /><item><title>RE: Zephyr/UARTE uart_tx reports BUSY after receiving TX_DONE</title><link>https://devzone.nordicsemi.com/thread/350363?ContentTypeID=1</link><pubDate>Mon, 31 Jan 2022 08:50:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:446efb71-1dc2-4f28-bb54-ee6a6d37e8a2</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;I have not heard anything from David.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;David, if you have found the reason for this issue and a workaround, then please do care to update us with the new info.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zephyr/UARTE uart_tx reports BUSY after receiving TX_DONE</title><link>https://devzone.nordicsemi.com/thread/350033?ContentTypeID=1</link><pubDate>Thu, 27 Jan 2022 15:35:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7a4f8403-0ab4-4e25-9d1a-cb6e09904ea1</guid><dc:creator>sread</dc:creator><description>&lt;p&gt;I have seen what I think is very similar issue. In my case the UART locks up and spins at wait_tx_ready(). Did you find a resolution?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zephyr/UARTE uart_tx reports BUSY after receiving TX_DONE</title><link>https://devzone.nordicsemi.com/thread/341704?ContentTypeID=1</link><pubDate>Thu, 02 Dec 2021 12:59:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cde050d7-ccb6-4790-8a5a-871b07dc183e</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;What are the contexts in which you are sending the TX bytes?&lt;/p&gt;
&lt;p&gt;Based on your limited info, it sounds like a deadlock situation where the uart driver still thinks that the past transaction is still not complete.OR possibly TX is stopped for some reason? Can you please check if there are any errors in the uart register or if TXSTOPPED event occured?&lt;/p&gt;
&lt;p&gt;If none of them happened then probably it is best if you can help me replicate the problem at my end so that i can try to debug it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>