<?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>Power consumption reading a large fifo - Easydma list vs Cpu reading</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/25949/power-consumption-reading-a-large-fifo---easydma-list-vs-cpu-reading</link><description>I am reading a large FIFO buffer from a sensor and there are at least two ways to do it - by simply reading the FIFO using the CPU and SPI in chunks of 255 byte blocks, or using EasyDma list (also chunked). Both using SPI @ 8mbps. This post outlines the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 16 Oct 2017 17:19:03 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/25949/power-consumption-reading-a-large-fifo---easydma-list-vs-cpu-reading" /><item><title>RE: Power consumption reading a large fifo - Easydma list vs Cpu reading</title><link>https://devzone.nordicsemi.com/thread/102222?ContentTypeID=1</link><pubDate>Mon, 16 Oct 2017 17:19:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d3d41bde-3e59-438b-b28c-16707209b695</guid><dc:creator>ShannonPahl</dc:creator><description>&lt;p&gt;excellent, thanks.  #2 is the reason as I have the sensor on a breadboard connected to a DK. When I drop SPI down from 8M to 125K, the current drops from 3.9mA to 1.57mA during a (now longer) read. A pcb should fix this.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption reading a large fifo - Easydma list vs Cpu reading</title><link>https://devzone.nordicsemi.com/thread/102221?ContentTypeID=1</link><pubDate>Mon, 16 Oct 2017 10:37:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d13c7498-27b6-4690-a042-372896027dd2</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This is most likely caused by two reasons:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The DMA logic draws 1.2mA alone.&lt;/li&gt;
&lt;li&gt;Pin and trace capacitance combined with high frequency signals draw more current.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The current consumption caused by issue #2 is difficult to estimate, but at least you can figure out whether this is indeed the problem by reducing the frequency and see if the current goes down.&lt;/p&gt;
&lt;p&gt;It should be safe to assume that at least the CPU is in sleep mode since otherwise the current consumption would be even higher (CPU + DMA run currents would be ~4.9mA at best).&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;EDIT: &lt;a href="https://devzone.nordicsemi.com/question/117987/spi-vs-twi-current-consumption/"&gt;Relevant post with relevant equation&lt;/a&gt;. With this equation in mind you would need a relatively high capacitance to reach the mA range. The nRF52832&amp;#39;s pad capacitance is only ~3pF, but if you have connected your SPI slave with jumper wires, the capacitance quickly adds up.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>