<?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>Periodic (~4s) current blip in Low Power mode NRF52832 SDK V12.3</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/29875/periodic-4s-current-blip-in-low-power-mode-nrf52832-sdk-v12-3</link><description>On a system using an NRF52832 with S132 softdevice (without no external LFCLK XTAL), in low power mode via sd_app_evt_wait() - we see a nominal current of ~3uA with a periodic current blip of ~100 uA. 
 There are a few other peripherals on the board</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 26 Jan 2018 15:37:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/29875/periodic-4s-current-blip-in-low-power-mode-nrf52832-sdk-v12-3" /><item><title>RE: Periodic (~4s) current blip in Low Power mode NRF52832 SDK V12.3</title><link>https://devzone.nordicsemi.com/thread/118779?ContentTypeID=1</link><pubDate>Fri, 26 Jan 2018 15:37:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e6382c2-b20e-4706-864a-1dfbafe554b5</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;You can also disable the SoftDevice, if using system OFF is not an option. Then it won&amp;#39;t schedule any clock calibration.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Periodic (~4s) current blip in Low Power mode NRF52832 SDK V12.3</title><link>https://devzone.nordicsemi.com/thread/118778?ContentTypeID=1</link><pubDate>Wed, 24 Jan 2018 17:23:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:97025fec-cb58-4ce2-a034-d888c51df29c</guid><dc:creator>AmbystomaLabs</dc:creator><description>&lt;p&gt;Then look over the following blog entry.  You will need to do an SD system power off.
Here is the link: &lt;a href="https://devzone.nordicsemi.com/question/90573/switching-off-nrf51-beacon/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Periodic (~4s) current blip in Low Power mode NRF52832 SDK V12.3</title><link>https://devzone.nordicsemi.com/thread/118777?ContentTypeID=1</link><pubDate>Wed, 24 Jan 2018 17:01:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1d8b6b41-0ef6-4bb9-8d2a-6c8e60e82866</guid><dc:creator>koniho</dc:creator><description>&lt;p&gt;Yes - the current behavior for the device should be just to wake up from button press via GIOTE event. We should be able to guarantee that when the device has gone to sleep that BLE core will be inactive.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Periodic (~4s) current blip in Low Power mode NRF52832 SDK V12.3</title><link>https://devzone.nordicsemi.com/thread/118776?ContentTypeID=1</link><pubDate>Wed, 24 Jan 2018 15:27:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:46808c5d-4912-40e6-b0e7-7155f0334514</guid><dc:creator>AmbystomaLabs</dc:creator><description>&lt;p&gt;I think the only way to avoid the cal is to do a system power off or maybe a sd disable. Doing a WFE as you are doing is just holding it up until the next event comes through.  The scheduled rtc cal is one of those events. And the ble core still needs to have an accurate clock for beacons, wakeup to listen events, etc. basically whatever you have told the ble core to do.&lt;/p&gt;
&lt;p&gt;Are you trying to do a deep sleep with wakeup on a button?  Exactly how were you planning to wake up the processor?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Periodic (~4s) current blip in Low Power mode NRF52832 SDK V12.3</title><link>https://devzone.nordicsemi.com/thread/118775?ContentTypeID=1</link><pubDate>Wed, 24 Jan 2018 00:09:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e51e9479-4889-4c94-8f40-7098119e1f52</guid><dc:creator>koniho</dc:creator><description>&lt;p&gt;If BLE is not required while the system is sleeping - can the LFCLK be disabled? or will having the SD present always require the LFCLK to be active?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Periodic (~4s) current blip in Low Power mode NRF52832 SDK V12.3</title><link>https://devzone.nordicsemi.com/thread/118774?ContentTypeID=1</link><pubDate>Tue, 23 Jan 2018 23:27:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e76d1486-a83b-47e8-924c-4788b23769e6</guid><dc:creator>AmbystomaLabs</dc:creator><description>&lt;p&gt;If you read through the SD spec, it discusses the periodic calibration of the LF_INT. The calibration is required to meet the BLE spec of 250ppm with the internal RC based RTC.  The period of the calibration interval is configurable in the RTC config struct.&lt;/p&gt;
&lt;p&gt;The RTC is the main clock when the system is asleep and for BLE it needs to be +/-250ppm all the time, thus the requirement to cal it against the HF_EXT.&lt;/p&gt;
&lt;p&gt;The normal cal interval is around 17msec every 4 sec.  Your plot looks consistent with it.&lt;/p&gt;
&lt;p&gt;Here is more info on it: &lt;a href="https://devzone.nordicsemi.com/question/81847/how-much-current-consumption-when-we-use-internal-32k-rc/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Periodic (~4s) current blip in Low Power mode NRF52832 SDK V12.3</title><link>https://devzone.nordicsemi.com/thread/118773?ContentTypeID=1</link><pubDate>Tue, 23 Jan 2018 23:07:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:59133b92-7fcd-4dc4-9e52-abacedd796b1</guid><dc:creator>Matt</dc:creator><description>&lt;p&gt;Same test result if you disable ALL the other peripherals?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>