<?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>High current consumption after updating to SDK 2.6.1</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/114486/high-current-consumption-after-updating-to-sdk-2-6-1</link><description>We&amp;#39;re using a nRF5340 module on our board, and have basically everything working as we&amp;#39;d like using SDK 2.1.0. 
 I&amp;#39;ve tried updating to SDK 2.6.1, and managed to resolve all the differences with the API calls, but have found current consumption is much</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 05 Sep 2024 11:08:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/114486/high-current-consumption-after-updating-to-sdk-2-6-1" /><item><title>RE: High current consumption after updating to SDK 2.6.1</title><link>https://devzone.nordicsemi.com/thread/501334?ContentTypeID=1</link><pubDate>Thu, 05 Sep 2024 11:08:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6fc53bea-d5a6-4d2c-bce1-5064964db5bc</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;All the currents you list here is considerably higher than the idle current of 3-4uA I would expect.&lt;/p&gt;
&lt;p&gt;I think it&amp;#39;s difficult to know exactly which is the problematic configuration here, but to just rule out any external components first, then I would have simply tried compling for instance the hello world with SERIAL=n to check if that yield the low power current.&lt;/p&gt;
&lt;p&gt;You can try to connect a debugger and simply go over the peripherals, and for instance check which are enabled if that may give a clue. E.g. there are two UARTs, so maybe check both are disabled.&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t know if you have mcuboot or not, but in theory here it could be 4 images (e.g. appcore and netcore, with each their own mcuboot), so it could in theory be any of them in worst case. So maybe build the application without mcuboot can also be something to try to narrow it down.&lt;/p&gt;
&lt;p&gt;The zephyr.dts file for each image in the build folder may also give some pointers.&lt;/p&gt;
&lt;p&gt;Another thing to test would be to go to the board file, and set SERIAL to n there, that should apply to all images, then you only needed to set SERIAL = y explicit when building for a specifif image.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>