<?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>Zephyr RAM, FLASH, CPU usage</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/67059/zephyr-ram-flash-cpu-usage</link><description>Hi, 
 Currently our team would like to start using Zephyr for our development, but some colleagues fear that it will use too many resources. They saw that our first test project is including a lot of Projects/Libraries in the Solution. (Shown in Segger</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 14 Oct 2020 09:25:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/67059/zephyr-ram-flash-cpu-usage" /><item><title>RE: Zephyr RAM, FLASH, CPU usage</title><link>https://devzone.nordicsemi.com/thread/274836?ContentTypeID=1</link><pubDate>Wed, 14 Oct 2020 09:25:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:229e61ae-0194-45ed-8f64-8dc3ac2b2b05</guid><dc:creator>newUser</dc:creator><description>&lt;p&gt;Perfect, thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zephyr RAM, FLASH, CPU usage</title><link>https://devzone.nordicsemi.com/thread/274803?ContentTypeID=1</link><pubDate>Wed, 14 Oct 2020 07:57:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6d7bd68a-1175-46e0-b725-6db55b1de594</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;As the screen-dump below shows, SES should give you a graphical display of the memory usage once the project is built.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Peripheral LBS example built for nrf52840dk_nrf52840:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/2275.pastedimage1602657756882v1.png" alt=" " /&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;CPU usage for NCS samples should be about the same for comparable nRF5 SDK examples. But if you wish to do actual profiling of the CPU usage you can enable&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/CONFIG_CPU_LOAD.html?highlight=cpu_load#cmdoption-arg-CONFIG_CPU_LOAD"&gt;CONFIG_CPU_LOAD&lt;/a&gt; option as explained below. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Enable periodic logging of CPU usage&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;1. Add the following config options to your prj.conf file:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="python"&gt;# Enable CPU tracing
CONFIG_CPU_LOAD=y
CONFIG_CPU_LOAD_LOG_INTERVAL=2000
CONFIG_CPU_LOAD_LOG_PERIODIC=y&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;2. Add &amp;quot;#include &amp;lt;debug/cpu_load.h&amp;gt;&amp;quot; and call cpu_load_init() in your startup code (e.g. at the beginning of main())&lt;/p&gt;
&lt;p&gt;3. Re-build the application and verify that the CPU load in percent is logged every 2 seconds.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/0284.pastedimage1602662314260v2.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>