<?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/"><channel><title>Visualising your memory usage</title><link>/nordic/nordic-blog/b/blog/posts/visualising-your-memory-usage</link><description>The linker in the GCC toolchain, ld, produces a *.Map file which shows you how the memory on your micro is being used. This file is a goldmine of information but it&amp;#39;s a bit difficult for humans to absorb.
I&amp;#39;ve whipped up a web page which uses the ex</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>RE: Visualising your memory usage</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/visualising-your-memory-usage</link><pubDate>Wed, 20 Sep 2023 09:10:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7edcd1ba-4db3-4059-ac7f-521c3e818ad2</guid><dc:creator>noblekeon</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Nice! Did you utilize any special flags to drill down into details? Only FLASH and RAM are present, and I can only make out the former.&amp;nbsp; &lt;a href="https://geometry-dash.io/"&gt;geometry dash&lt;/a&gt;&lt;/p&gt;&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=770&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Visualising your memory usage</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/visualising-your-memory-usage</link><pubDate>Wed, 03 Dec 2014 16:48:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7edcd1ba-4db3-4059-ac7f-521c3e818ad2</guid><dc:creator>Eliot Stock</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Thanks for the pull request! Merged.&lt;/p&gt;
&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=770&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Visualising your memory usage</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/visualising-your-memory-usage</link><pubDate>Wed, 03 Dec 2014 13:30:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7edcd1ba-4db3-4059-ac7f-521c3e818ad2</guid><dc:creator>Anne van Rossum</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Ah, you are right. If I join the lines together with .text in them:&lt;/p&gt;
&lt;pre&gt;ex -c &amp;#39;%g/\.text/j&amp;#39; -c &amp;quot;wq&amp;quot; prog.map
&lt;/pre&gt;
&lt;p&gt;then I get a lot more info. A better one would be the one that leaves alone the lines that are already on one line:&lt;/p&gt;
&lt;pre&gt;ex -c &amp;#39;%g/\.text\S*[\s]*$/j&amp;#39; -c &amp;quot;wq&amp;quot; prog.map
&lt;/pre&gt;
&lt;p&gt;And succeeded by replacing .text.blah with .text:&lt;/p&gt;
&lt;pre&gt;sed -i &amp;#39;s/\.text\S*/.text/g&amp;#39; prog.map
&lt;/pre&gt;
&lt;p&gt;The only thing left is that the items get really small when you&amp;#39;re program gets big. I&amp;#39;ve to look in the zooming options in your code, but thanks again!&lt;/p&gt;
&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=770&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Visualising your memory usage</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/visualising-your-memory-usage</link><pubDate>Tue, 02 Dec 2014 16:56:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7edcd1ba-4db3-4059-ac7f-521c3e818ad2</guid><dc:creator>Eliot Stock</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Because you have very long symbol names, like this...&lt;/p&gt;
&lt;p&gt;.text.&lt;em&gt;ZN4func6detail16function_manager19templated_call_copyIPFvbESaIS4_EEEvRNS0_20manager_storage_typeERKS6&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;... ld is wrapping the memory details onto the next line which is breaking the tool.&lt;/p&gt;
&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=770&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Visualising your memory usage</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/visualising-your-memory-usage</link><pubDate>Tue, 02 Dec 2014 16:30:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7edcd1ba-4db3-4059-ac7f-521c3e818ad2</guid><dc:creator>Anne van Rossum</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Nice! Did you use specific flags to get more information? I only see FLASH and RAM and very little used out of both. See &lt;a href="https://github.com/mrquincle/bluenet/tree/master/docs"&gt;this prog.map&lt;/a&gt; file.&lt;/p&gt;
&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=770&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>