<?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>System-on sleep current on the nRF52840 when mesh is disabled. (nRF5 SKD for Mesh V2.1.1)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/36377/system-on-sleep-current-on-the-nrf52840-when-mesh-is-disabled-nrf5-skd-for-mesh-v2-1-1</link><description>Hi, 
 I have a question with regards to the system-on sleep current of the nRF52840. This is specific to when using the bluetooth mesh and the nrf_mesh_disable() function is called. It seems I cannot get a system-on sleep current less than ~520uA when</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 20 Aug 2018 11:46:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/36377/system-on-sleep-current-on-the-nrf52840-when-mesh-is-disabled-nrf5-skd-for-mesh-v2-1-1" /><item><title>RE: System-on sleep current on the nRF52840 when mesh is disabled. (nRF5 SKD for Mesh V2.1.1)</title><link>https://devzone.nordicsemi.com/thread/144927?ContentTypeID=1</link><pubDate>Mon, 20 Aug 2018 11:46:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:29f94292-0a55-4069-a61e-1c8a4275c02f</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;We have some issues with the SPI continuing to draw current after use. Please check out this: &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52840.Rev1.errata/dita/errata/nRF52840/Rev1/latest/anomaly_840_195.html?cp=2_0_1_0_1_26"&gt;http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52840.Rev1.errata/dita/errata/nRF52840/Rev1/latest/anomaly_840_195.html?cp=2_0_1_0_1_26&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: System-on sleep current on the nRF52840 when mesh is disabled. (nRF5 SKD for Mesh V2.1.1)</title><link>https://devzone.nordicsemi.com/thread/144033?ContentTypeID=1</link><pubDate>Tue, 14 Aug 2018 01:30:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:12323616-6f67-4119-825b-266892b7e536</guid><dc:creator>gordie</dc:creator><description>&lt;p&gt;Hi Stian, thanks for the reply. I use&amp;nbsp;one instance of I2C, and one SPI master, as well as one instance of SPI slave. I also use the SAADC to take readings from three channels, in scan mode.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: System-on sleep current on the nRF52840 when mesh is disabled. (nRF5 SKD for Mesh V2.1.1)</title><link>https://devzone.nordicsemi.com/thread/143929?ContentTypeID=1</link><pubDate>Mon, 13 Aug 2018 11:47:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e8b215dc-4c1d-4d20-abf3-a67308df5c1e</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;Based on the current (500uA) it seems like the HF clock is never released when you call the nrf_mesh_disable(). There are som issues with peripherals not releasing the HF clock when they are disabled. Do you use SPI? For logging etc? or any other peripherals?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: System-on sleep current on the nRF52840 when mesh is disabled. (nRF5 SKD for Mesh V2.1.1)</title><link>https://devzone.nordicsemi.com/thread/141220?ContentTypeID=1</link><pubDate>Wed, 25 Jul 2018 00:02:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b3c03268-118d-47a7-b215-e612b99d2c88</guid><dc:creator>gordie</dc:creator><description>&lt;p&gt;Hi, any ideas on this?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>