<?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 consumption on FreeRTOS(17.1.0) and zephyr(NCS 2.5.0)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/105775/power-consumption-on-freertos-17-1-0-and-zephyr-ncs-2-5-0</link><description>We have following measurement with PPK2: ( switch to ‘nRF only’, and PPK2 connect to &amp;#39;External supply&amp;#39; ) 
 
 
 
 
 HW+OS 
 
 
 advertising 
 
 
 connected 
 
 
 
 
 nRF52840 + ble_app_hrs_freertos 
 
 
 218 uA 
 
 
 83 uA 
 
 
 
 
 nRF52840 + zephyr+</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 23 Nov 2023 06:36:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/105775/power-consumption-on-freertos-17-1-0-and-zephyr-ncs-2-5-0" /><item><title>RE: Power consumption on FreeRTOS(17.1.0) and zephyr(NCS 2.5.0)</title><link>https://devzone.nordicsemi.com/thread/457065?ContentTypeID=1</link><pubDate>Thu, 23 Nov 2023 06:36:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:12c15544-ab4c-4ae8-8c1d-c499a807d9de</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Yes, this looks more like the expected current consumption. Let me know if you have any further questions.&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 consumption on FreeRTOS(17.1.0) and zephyr(NCS 2.5.0)</title><link>https://devzone.nordicsemi.com/thread/457052?ContentTypeID=1</link><pubDate>Thu, 23 Nov 2023 01:46:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:16f1021d-95f4-4ecc-888f-6494f7ea1676</guid><dc:creator>TC</dc:creator><description>&lt;p&gt;It looks better now after progran NET core with prj_minimal.conf.&lt;br /&gt;Thanks!&lt;/p&gt;
&lt;table data-number-column="false" data-layout="default" data-autosize="false" data-table-local-id="ef749bae-2db6-41eb-8292-aeb48b799249"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th class="pm-table-header-content-wrap"&gt;
&lt;p&gt;&lt;/p&gt;
&lt;/th&gt;
&lt;th class="pm-table-header-content-wrap"&gt;
&lt;p&gt;advertising&lt;/p&gt;
&lt;/th&gt;
&lt;th class="pm-table-header-content-wrap"&gt;
&lt;p&gt;connected&lt;/p&gt;
&lt;/th&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class="pm-table-cell-content-wrap"&gt;
&lt;p&gt;&lt;strong&gt;nRF52840 + zephyr+ peripheral_hr&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td class="pm-table-cell-content-wrap"&gt;
&lt;p&gt;114 uA&lt;/p&gt;
&lt;/td&gt;
&lt;td class="pm-table-cell-content-wrap"&gt;
&lt;p&gt;137 uA&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class="pm-table-cell-content-wrap"&gt;
&lt;p&gt;&lt;strong&gt;nRF5340 + zephyr+ peripheral_hr&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td class="pm-table-cell-content-wrap"&gt;
&lt;p&gt;78 uA&lt;/p&gt;
&lt;/td&gt;
&lt;td class="pm-table-cell-content-wrap"&gt;
&lt;p&gt;115 uA&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption on FreeRTOS(17.1.0) and zephyr(NCS 2.5.0)</title><link>https://devzone.nordicsemi.com/thread/456986?ContentTypeID=1</link><pubDate>Wed, 22 Nov 2023 15:15:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6e2292e5-04d8-49a2-93f8-a85159376c20</guid><dc:creator>TC</dc:creator><description>&lt;p&gt;How to make sure both&amp;nbsp;&lt;span&gt;the APP core and the NET core is built with the minimal configs?&lt;br /&gt;Is that mean I need to build two FWs for cpuapp and cpunet, and program respectively?&lt;br /&gt;So far, I select the board nrf5340dk_nrf5340_cpuapp with prj_minimal.conf for building the fw.&lt;br /&gt;In&amp;nbsp;prj_minimal.conf, both&amp;nbsp;CONFIG_LOG&amp;nbsp;and&amp;nbsp;CONFIG_SERIAL&amp;nbsp; set to n laready.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption on FreeRTOS(17.1.0) and zephyr(NCS 2.5.0)</title><link>https://devzone.nordicsemi.com/thread/456942?ContentTypeID=1</link><pubDate>Wed, 22 Nov 2023 13:38:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4b807a18-f95c-4d95-a088-bd2c644cdd4e</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;It seems quite a bit higher in the nRF5340. Since the nRF5340 has two cores, have you made sure both the APP core and the NET core is built with the minimal configs? From the guide on nRF5340 power optimization you can see that for example making sure that CONFIG_LOG and CONFIG_SERIAL is set =n in both images (prj.conf and hci_rpmsg.conf) and possibly adding system and device power mangement to your project might be necessary to get it closer to the nRF52 series.&lt;/p&gt;
&lt;p&gt;As you can see from the Online Power Profiler, the nRF5340 (when fully optimized) has almost identical power consumption to the nRF52 series.&amp;nbsp;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/power/w/opp/2/online-power-profiler-for-bluetooth-le"&gt;Online Power Profiler for Bluetooth LE&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption on FreeRTOS(17.1.0) and zephyr(NCS 2.5.0)</title><link>https://devzone.nordicsemi.com/thread/456802?ContentTypeID=1</link><pubDate>Wed, 22 Nov 2023 02:42:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:22142e6b-1b89-4a10-9bbd-8156c26fb6f2</guid><dc:creator>TC</dc:creator><description>&lt;p&gt;Thanks for hint!&lt;br /&gt;In our measurement the nRF5340 getting higher power consumption, is that as expected?&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;table data-number-column="false" data-layout="default" data-autosize="false" data-table-local-id="ef749bae-2db6-41eb-8292-aeb48b799249"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th class="pm-table-header-content-wrap"&gt;
&lt;p&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/p&gt;
&lt;/th&gt;
&lt;th class="pm-table-header-content-wrap"&gt;
&lt;p&gt;advertising&lt;/p&gt;
&lt;/th&gt;
&lt;th class="pm-table-header-content-wrap"&gt;
&lt;p&gt;connected&lt;/p&gt;
&lt;/th&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class="pm-table-cell-content-wrap"&gt;
&lt;p&gt;&lt;strong&gt;nRF52840 + zephyr+ peripheral_hr&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td class="pm-table-cell-content-wrap"&gt;
&lt;p&gt;114 uA&lt;/p&gt;
&lt;/td&gt;
&lt;td class="pm-table-cell-content-wrap"&gt;
&lt;p&gt;137 uA&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class="pm-table-cell-content-wrap"&gt;
&lt;p&gt;&lt;strong&gt;nRF5340 + zephyr+ peripheral_hr&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td class="pm-table-cell-content-wrap"&gt;
&lt;p&gt;266 uA&lt;/p&gt;
&lt;/td&gt;
&lt;td class="pm-table-cell-content-wrap"&gt;
&lt;p&gt;284 uA&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption on FreeRTOS(17.1.0) and zephyr(NCS 2.5.0)</title><link>https://devzone.nordicsemi.com/thread/456604?ContentTypeID=1</link><pubDate>Tue, 21 Nov 2023 08:14:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:78050dad-8422-4e6b-9010-892b3d3976cf</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;I find a prj_minimal.conf in peripheral_hr as well. I suggest you test with this one first.&lt;/p&gt;
&lt;p&gt;For the nRF5340, it seems that CONFIG_MAIN_STACK_SIZE=640 is a bit to small for this sample. Try to increase the main stack size and try again.&lt;br /&gt;I found this by enabling logs and CONFIG_THREAD_NAME, giving me the following error:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;[00:00:00.432,739] &amp;lt;err&amp;gt; os: ***** USAGE FAULT *****
[00:00:00.432,769] &amp;lt;err&amp;gt; os:   Stack overflow (context area not valid)
[00:00:00.432,769] &amp;lt;err&amp;gt; os: r0/a1:  0x20001118  r1/a2:  0x20001208  r2/a3:  0x00000020
[00:00:00.432,800] &amp;lt;err&amp;gt; os: r3/a4:  0x00000000 r12/ip:  0x00000003 r14/lr:  0x0000fe0b
[00:00:00.432,800] &amp;lt;err&amp;gt; os:  xpsr:  0x29000200
[00:00:00.432,800] &amp;lt;err&amp;gt; os: Faulting instruction address (r15/pc): 0x0000fd06
[00:00:00.432,830] &amp;lt;err&amp;gt; os: &amp;gt;&amp;gt;&amp;gt; ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
[00:00:00.432,861] &amp;lt;err&amp;gt; os: Current thread: 0x20001538 (main)
[00:00:00.490,386] &amp;lt;err&amp;gt; os: Halting system
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;This error log gives me both that it is a stack overlfow, and which thread fails.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption on FreeRTOS(17.1.0) and zephyr(NCS 2.5.0)</title><link>https://devzone.nordicsemi.com/thread/456134?ContentTypeID=1</link><pubDate>Fri, 17 Nov 2023 11:22:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8c6717a4-8a60-4444-8ac8-bd9edac9c31a</guid><dc:creator>TC</dc:creator><description>&lt;p&gt;Hi:&lt;br /&gt;We want to compare power based on hr sample.&lt;br /&gt;The&amp;nbsp;&lt;span class="go"&gt;prj_minimal.conf getting lower current in nRF52840 DK for sure in my side.&lt;br /&gt;But when I try to apply&amp;nbsp;&lt;span&gt;prj_minimal.conf&amp;nbsp;&lt;/span&gt;in nRF5340 DK, seems no advertising in peripheral_hr sample.&lt;br /&gt;Any suggestion?&lt;/span&gt;&lt;/p&gt;
&lt;pre id="codecell0"&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption on FreeRTOS(17.1.0) and zephyr(NCS 2.5.0)</title><link>https://devzone.nordicsemi.com/thread/456103?ContentTypeID=1</link><pubDate>Fri, 17 Nov 2023 09:59:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:14db7bde-475d-4894-b313-f5802e331629</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Have a look at our &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/test_and_optimize/optimizing/power.html"&gt;Power optimization docs&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I think our &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/peripheral_lbs/README.html#minimal-build"&gt;peripheral_lbs sample with minimal build&lt;/a&gt; draws low current. Try that and maybe see how it is configured to apply the same to peripheral_hs.&lt;/p&gt;
&lt;p&gt;You can also estimate Bluetooth LE power consumption with out &lt;a href="https://devzone.nordicsemi.com/power/w/opp/2/online-power-profiler-for-bluetooth-le"&gt;Online Power Profiler for Bluetooth LE&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Also see &amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/optimizing-power-on-nrf53-designs"&gt;Optimizing Power on nRF5340 SoC Designs&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Sigurd Hellesvik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>