<?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>Problem running nrf52 SDK 0.9.1 uart example.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8905/problem-running-nrf52-sdk-0-9-1-uart-example</link><description>Hi, 
 I&amp;#39;m trying to run the uart loopback example in the nrf52 0.9.1 SDK with DMA enabled but it is being caught in an error catch. It runs fine without DMA enabled though. I&amp;#39;m enabling DMA with the following change to the project: 
 nRF52_SDK_0.9.1_3639cc9</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 01 Sep 2015 07:33:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8905/problem-running-nrf52-sdk-0-9-1-uart-example" /><item><title>RE: Problem running nrf52 SDK 0.9.1 uart example.</title><link>https://devzone.nordicsemi.com/thread/32769?ContentTypeID=1</link><pubDate>Tue, 01 Sep 2015 07:33:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:26cb6ca2-efcb-43d0-ae99-0f5d6af37b17</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The engineer of the driver team explained that this is not necessarily a bug, it is the implementation limitation because of the way how app_uart works. So the app_fifo library is not ready to work with EasyDMA.
Anyhow I see that the nrf_driver_uart (layer below app_uart) has full capabilities to woth with easydma and with the workaround I provided above (in app_uart), it works just fine.
In the next SDK release, the driver team promised to update documentation for this and will also TRY to support app_uart with easydma.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem running nrf52 SDK 0.9.1 uart example.</title><link>https://devzone.nordicsemi.com/thread/32768?ContentTypeID=1</link><pubDate>Mon, 31 Aug 2015 13:17:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b5ad0f53-2e46-4695-8fe8-6b94c5952b58</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;in app_uart_fifo.c-&amp;gt; uart_event_handler function
Add these two lines in the start of the function&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;{
    static uint32_t  count = 0;
    if (count == 0) { count ++ ; return; }
}
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;for some reason the RX buffer gets a byte before the transmit is done. If you ignore the first RX event then everything else in sync. I will have to redirect it to the driver team, but this workaround will fix your problem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem running nrf52 SDK 0.9.1 uart example.</title><link>https://devzone.nordicsemi.com/thread/32767?ContentTypeID=1</link><pubDate>Mon, 31 Aug 2015 12:41:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cc682241-959d-4060-a02a-16b1defaaf6b</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;i confirm what you said. It does not work as intended, I will have a look into it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem running nrf52 SDK 0.9.1 uart example.</title><link>https://devzone.nordicsemi.com/thread/32766?ContentTypeID=1</link><pubDate>Fri, 28 Aug 2015 07:00:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:644f70aa-7785-46c0-84d2-24574304578a</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;i am working from home today and do not have access to hardware, i will test this on monday, sorry about that.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem running nrf52 SDK 0.9.1 uart example.</title><link>https://devzone.nordicsemi.com/thread/32765?ContentTypeID=1</link><pubDate>Wed, 26 Aug 2015 19:38:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9dcf77bc-0c15-413a-bc9f-c60688696dcd</guid><dc:creator>Chris smith</dc:creator><description>&lt;p&gt;Yes, I have connected TX with RX and RTS with CTS (Defined in pca10036.h:TX=6, RX=8, CTS=7, RTS=5). I&amp;#39;m pretty sure that I have everything set up correctly because the UART loopback works perfectly without EasyDma. I only changed what is stated above in the question. Let me know how your testing turns out and hopefully we can figure out whats going on.&lt;/p&gt;
&lt;p&gt;I tested the spi_master loopback example a little while back with both EasyDma enabled and disabled and it works.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem running nrf52 SDK 0.9.1 uart example.</title><link>https://devzone.nordicsemi.com/thread/32764?ContentTypeID=1</link><pubDate>Wed, 26 Aug 2015 07:59:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d2442464-2d90-477b-9d12-5a53eb3248e8</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;you have enabled loopback so have you connected TX with RX and if HW enabled RTS with CTS?
Yesterday I did exactly same thing for SPIM example modifying it to work with EasyDma and it worked perfectly. I will have to try your example today.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>