<?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 current consumption.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/64922/spi-current-consumption</link><description>Hi 
 We are using nrf51822 with SDK 10 and softdevice s110. We completed the software and in general everything works fine. In the final step, we decided to add the peripheral device which needs SPI. In the main function, I added spi_master_init(&amp;amp;m_spi_master_0</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 19 Aug 2020 06:42:30 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/64922/spi-current-consumption" /><item><title>RE: SPI current consumption.</title><link>https://devzone.nordicsemi.com/thread/265218?ContentTypeID=1</link><pubDate>Wed, 19 Aug 2020 06:42:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4706e691-673a-49fb-92f2-2bf418ed8b46</guid><dc:creator>control</dc:creator><description>&lt;p&gt;thanks for the fast response. I added in my project (in which SDK 10 is used) the library nrf_drv_spi from SKD 11 and the functions enable and disable of SPI communication works like a charm. It seems that SDK 10 has some bugs regarding&amp;nbsp;SPI communication which reflects in higher current consumption.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPI current consumption.</title><link>https://devzone.nordicsemi.com/thread/265083?ContentTypeID=1</link><pubDate>Tue, 18 Aug 2020 11:58:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:85229420-b4bf-45af-a6ab-e8393b42284c</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Can you try to uninit the SPI and then write 0 followed by 1 to the POWER register (address 0xFFC)?&lt;/p&gt;
&lt;p&gt;Make sure the SPI is uninit (disabled) when doing this:&lt;/p&gt;
&lt;p&gt;If TWI0 or SPI0 is used:&lt;br /&gt;*(volatile uint32_t *)0x40003FFC = 0;&lt;br /&gt;*(volatile uint32_t *)0x40003FFC;&lt;br /&gt;*(volatile uint32_t *)0x40003FFC = 1;&lt;/p&gt;
&lt;p&gt;If TWI1 or SPI1 is used:&lt;br /&gt;*(volatile uint32_t *)0x40004FFC = 0;&lt;br /&gt;*(volatile uint32_t *)0x40004FFC;&lt;br /&gt;*(volatile uint32_t *)0x40004FFC = 1;&lt;/p&gt;
&lt;p&gt;This should confirm if it&amp;#39;s the SPI that is the problem, or if there is another mode or peripheral that is causing the current consumption.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>