<?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>SPI VS UART For Minimal Data Transfer &amp;amp; Sleep</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/64364/spi-vs-uart-for-minimal-data-transfer-sleep</link><description>Hi devs, 
 I&amp;#39;m using the NRF52810 to occasionally reprogram a PIC16F15 series chip on boot using SPI. It&amp;#39;s working well. Once the NRF main routine is entered I periodically need to transfer a single byte to the PIC (TX only no confirm) using a timer and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 31 Jul 2020 11:59:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/64364/spi-vs-uart-for-minimal-data-transfer-sleep" /><item><title>RE: SPI VS UART For Minimal Data Transfer &amp; Sleep</title><link>https://devzone.nordicsemi.com/thread/262567?ContentTypeID=1</link><pubDate>Fri, 31 Jul 2020 11:59:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f31648d2-31cd-4337-8ec2-c983ddd75aa7</guid><dc:creator>snoopy20</dc:creator><description>&lt;p&gt;For some reason I can&amp;#39;t close based on your answer, but yes I&amp;#39;m sticking with SPI. There is another advantage, the slave device (in my case a PIC16) can use the pin clk and fully Sleep until the buffer is read.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPI VS UART For Minimal Data Transfer &amp; Sleep</title><link>https://devzone.nordicsemi.com/thread/262557?ContentTypeID=1</link><pubDate>Fri, 31 Jul 2020 11:43:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ef3664d5-7189-43f5-bcfb-9fddaf83504e</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;UART with EasyDMA will draw quite a bit of current as you say, so I think I would lean towards SPI in this case as well. If you, by sd_sleep routine, mean the nRF&amp;#39;s sleep, then that will indeed be interrupted if you&amp;#39;re triggering UART I believe, so you won&amp;#39;t be able to stay asleep while the UART is running. Indeed, the SPI will keep the HF clock running until it is finished.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPI VS UART For Minimal Data Transfer &amp; Sleep</title><link>https://devzone.nordicsemi.com/thread/262466?ContentTypeID=1</link><pubDate>Thu, 30 Jul 2020 19:04:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fc1661f0-239a-485c-870b-738be88f0700</guid><dc:creator>snoopy20</dc:creator><description>&lt;p&gt;It looks like I&amp;#39;m sticking with SPI, there are no power advantages over UART from what I can see. This assumes the transaction is triggered by PPI via a timer and afterwards the CPU tries to enter sleep mode (the HF won&amp;#39;t turn off until the SPI transaction is over, I think).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>