<?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>nRF5340 (NCS 2.7.0): ~1.27 mA average during BLE advertising with power save enabled (should be in µA)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/124799/nrf5340-ncs-2-7-0-1-27-ma-average-during-ble-advertising-with-power-save-enabled-should-be-in-a</link><description>Environment 
 
 
 SoC: nRF5340 (app core + net core) 
 
 
 SDK: nRF Connect SDK v2.7.0 
 
 
 Toolchain: [Zephyr/West toolchain from NCS 2.7.0, compiler version] 
 
 
 Measurement: PPK2 
 
 
 Application/Config 
 
 
 BLE: Peripheral power profiling 
 </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 07 Oct 2025 14:07:02 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/124799/nrf5340-ncs-2-7-0-1-27-ma-average-during-ble-advertising-with-power-save-enabled-should-be-in-a" /><item><title>RE: nRF5340 (NCS 2.7.0): ~1.27 mA average during BLE advertising with power save enabled (should be in µA)</title><link>https://devzone.nordicsemi.com/thread/550825?ContentTypeID=1</link><pubDate>Tue, 07 Oct 2025 14:07:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5f3484d6-1a28-44b8-9dfb-50e95baa3b6f</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;Siddharth,&lt;/p&gt;
&lt;p&gt;Before we begin, I would like to point out that nRF Connect SDK (NCS) v2.7.0 is&amp;nbsp;a little old now. If you are evaluating NCS&amp;nbsp;and the nRF5340 for your project, then I recommend getting started with the&amp;nbsp;latest release, &lt;a href="https://docs.nordicsemi.com/bundle/ncs-3.1.1/page/nrf/gsg_guides.html"&gt;NCS v3.1.1&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Regarding NCS v2.7.0 specifically, it is a release where we were transitioning from the old &lt;a href="https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/nrf/config_and_build/multi_image.html"&gt;parent-child multi-image build system&lt;/a&gt; to &lt;a href="https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/zephyr/build/sysbuild/index.html#sysbuild"&gt;Sysbuild&lt;/a&gt;. There is a fairly common issue with this release (which was &lt;em&gt;fixed&lt;/em&gt; from the next release, 2.8.0). The&amp;nbsp;samples are intended to be built with Sysbuild, but out of tree projects are &lt;em&gt;not&lt;/em&gt; built with Sysbuild by default.&amp;nbsp;A quick test showed that this pitfall causes failure&amp;nbsp;to start advertising in the Power Profiling sample, keeping current above 1mA.&lt;br /&gt;I suspect you are having this issue. However, there should be a warning during the build highlighting this, as well as a clear error message on the runtime log. Furthermore,&amp;nbsp;you shouldn&amp;#39;t have any advertising peaks, so that bit is a little strange.&lt;/p&gt;
&lt;p&gt;To work around this issue, there are two ways:&lt;/p&gt;
&lt;p&gt;1. Build the sample using Sysbuild&lt;/p&gt;
&lt;p&gt;If you use the command line, you just need to add --sysbuild to your build command.&lt;br /&gt;If you are using the nRF Connect for VS Code Extension, you just need to remember to tick &amp;quot;Use sysbuild&amp;quot; when creating or editing the build configuration&lt;/p&gt;
&lt;p&gt;This is the recommended method.&lt;/p&gt;
&lt;p&gt;2. Restore the non-sysbuild support from NCS v2.6.0. This is not the recommended approach, so I&amp;nbsp;would rather not elaborate.&lt;/p&gt;
&lt;p&gt;Another common issue&amp;nbsp;often seen is that the PPK2 isn&amp;#39;t connected correctly. Please follow the guide here to ensure everything is connected correctly:&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/ug_ppk2/page/UG/ppk/setting_up.html"&gt;Setting up the Power Profiler Kit II&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Finally, the only thing drawing significant current&amp;nbsp;with the Peripheral Power Profiling&amp;nbsp;sample is the UART logging.&amp;nbsp;To achieve&amp;nbsp;µA current consumption, you don&amp;#39;t need any special configurations aside from setting CONFIG_SERIAL=n on both the application core and network core image.&lt;/p&gt;
&lt;p&gt;In the Sysbuild setup mentioned above, you can find the network core image config file in sysbuild/ipc_radio/prj.conf.&lt;/p&gt;
&lt;p&gt;For reference, here is the consumption I measured:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/4024.pastedimage1759846018652v2.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Hieu&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340 (NCS 2.7.0): ~1.27 mA average during BLE advertising with power save enabled (should be in µA)</title><link>https://devzone.nordicsemi.com/thread/550689?ContentTypeID=1</link><pubDate>Mon, 06 Oct 2025 11:52:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88a8f0b5-3c9d-4a8b-b5ac-b05b31a08e69</guid><dc:creator>Siddharth Burugu</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/prj.overlay.conf.txt"&gt;devzone.nordicsemi.com/.../prj.overlay.conf.txt&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Hi, Please find the prj.overlay.conf file&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>