<?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 management differences between SDK 15 and SDK 11</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/47166/power-management-differences-between-sdk-15-and-sdk-11</link><description>Hi There, 
 I have developed an initial application on SDK11, based on the UART example, with Keil and it worked perfectly with the nice low power that you guys are capable of. 
 Then I moved my application to the SDK15 and Segger, and I struggled a lot</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 14 May 2019 14:32:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/47166/power-management-differences-between-sdk-15-and-sdk-11" /><item><title>RE: Power management differences between SDK 15 and SDK 11</title><link>https://devzone.nordicsemi.com/thread/187036?ContentTypeID=1</link><pubDate>Tue, 14 May 2019 14:32:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a44497a3-62e6-4353-829c-a15d91274326</guid><dc:creator>GeneralSpontz</dc:creator><description>&lt;p&gt;Ok, thanks, that&amp;#39;s what I thought.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power management differences between SDK 15 and SDK 11</title><link>https://devzone.nordicsemi.com/thread/186839?ContentTypeID=1</link><pubDate>Tue, 14 May 2019 07:06:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e58b6bde-1b57-492a-b3ca-f8c5e8e9851e</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi Spontz&lt;/p&gt;
&lt;p&gt;After some digging it seems you are right. You have to make your own loop for deinitializing and reinitializing your peripherals when using SDK15. I have not been able to find an equivalent function to the power_manage function in SDK11.&amp;nbsp;&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: Power management differences between SDK 15 and SDK 11</title><link>https://devzone.nordicsemi.com/thread/186782?ContentTypeID=1</link><pubDate>Mon, 13 May 2019 16:17:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5e5d75f2-81e5-4d13-ba5d-ef7ae2ee6707</guid><dc:creator>GeneralSpontz</dc:creator><description>&lt;p&gt;Hi Simon,&lt;/p&gt;
&lt;p&gt;I start with the UART example (BLE_peripheral /BLE UART) because I needed basic data communication on BLE. I use SPI to communicate with a MEMS sensor on my board.&lt;/p&gt;
&lt;p&gt;In the SDK11, I just called PowerManage() and it took care of putting the SPI peripheral into sleep.&lt;/p&gt;
&lt;p&gt;In the SDK15, the &lt;span style="background-color:#ffffff;"&gt;idle_state_handle&lt;/span&gt;() function does not do that. I have to explicitly call de-init the SPI before sleep, then call init again everytime I wake up. I wake up on a timer event every 50ms.&lt;/p&gt;
&lt;p&gt;I use the legacy SPI driver. (identical in SDK11 and 15)&lt;/p&gt;
&lt;p&gt;So my question is related to SDK15:&lt;/p&gt;
&lt;p&gt;- is what I do (de-init / re-init) the right way to manage a peripheral power when using sleep/wake ?&lt;/p&gt;
&lt;p&gt;- is there a higher level function that can desactivate all peripherals before entering sleep? It seems to exist in SDK11.&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Spontz&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power management differences between SDK 15 and SDK 11</title><link>https://devzone.nordicsemi.com/thread/186554?ContentTypeID=1</link><pubDate>Mon, 13 May 2019 07:08:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:12f2131d-a094-41ce-9760-5198be08a8d9</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi Spontz&lt;/p&gt;
&lt;p&gt;1. Why would the SPI be initialized at all in the UART example? The idle state handle should do the same as the power_manage function&amp;nbsp;&lt;strong&gt;after&lt;/strong&gt; handling any pending operations. So I am guessing the extra current draw is for the application to finish up any pending operations before going to sleep.&lt;/p&gt;
&lt;p&gt;2. The pins not used in the SEGGER example, should all be disconnected, so yes, you will have to initialize the other IOs. Struggling a bit to understand what is the problem in this question.&lt;/p&gt;
&lt;p&gt;How high of a current draw are you experiencing compared to the SDK11 example? It shouldn&amp;#39;t be too hard to achieve the same results if you are using the same kind of chip.&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></channel></rss>