<?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>UART interrupt event handling on SDK14.0.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/25411/uart-interrupt-event-handling-on-sdk14-0-0</link><description>Hi 
 I have an application where I cannot use the FIFO buffers (HW or SW). Therefore I need an interrupt for each received byte. If I try to use the uart driver (nrf_drv_uart.c) I have problems enabling the RXDRDY event. Or more precise: If I enable</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 23 Sep 2017 11:21:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/25411/uart-interrupt-event-handling-on-sdk14-0-0" /><item><title>RE: UART interrupt event handling on SDK14.0.0</title><link>https://devzone.nordicsemi.com/thread/100155?ContentTypeID=1</link><pubDate>Sat, 23 Sep 2017 11:21:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f80799d0-be72-403e-bd4d-5e24ed5f1d08</guid><dc:creator>Kasper Leonhardt</dc:creator><description>&lt;p&gt;However it works if I just calls  nrf_drv_uart_rx for each byte. I can live with that.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART interrupt event handling on SDK14.0.0</title><link>https://devzone.nordicsemi.com/thread/100154?ContentTypeID=1</link><pubDate>Sat, 23 Sep 2017 10:57:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:244f36da-b552-44da-b537-aae72463383e</guid><dc:creator>Kasper Leonhardt</dc:creator><description>&lt;p&gt;Sorry, I ment nrf_drv_uart_rx.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART interrupt event handling on SDK14.0.0</title><link>https://devzone.nordicsemi.com/thread/100153?ContentTypeID=1</link><pubDate>Sat, 23 Sep 2017 10:54:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bc599761-64f7-4788-94b6-68da3c67534c</guid><dc:creator>Kasper Leonhardt</dc:creator><description>&lt;p&gt;Do I have to call nrf_drv_uart_rx each time I expects data to be received?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART interrupt event handling on SDK14.0.0</title><link>https://devzone.nordicsemi.com/thread/100152?ContentTypeID=1</link><pubDate>Sat, 23 Sep 2017 10:49:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:971e6d64-6fde-48aa-a7c0-6c34628c6168</guid><dc:creator>Kasper Leonhardt</dc:creator><description>&lt;p&gt;Then please let me know how to use the nrf_drv_uart in the most basic way without using the FIFO and DMA. If it is not possible to get a receive event when a byte is received I cannot see the purpose of the driver (at least when I do not want to use DMA/FIFO). The transmit events works fine.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART interrupt event handling on SDK14.0.0</title><link>https://devzone.nordicsemi.com/thread/100151?ContentTypeID=1</link><pubDate>Sat, 23 Sep 2017 10:32:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4bde48a0-f0d4-451a-b5b9-605e16f993c0</guid><dc:creator>Turbo J</dc:creator><description>&lt;blockquote&gt;
&lt;p&gt;Therefore I need an interrupt for each received byte.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;That also means you will have to drop nrf_drv_uart altogether and implement the UART interrupt service function(s) yourself using the reference manual.&lt;/p&gt;
&lt;p&gt;Trying to (mis-)use the nrf_drv_uart driver may actually be much more difficult in your case.&lt;/p&gt;
&lt;p&gt;Note that RXTO event only ever occures after the STOPRX task has been triggered.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>