Posted 2014-12-02 13:59:44 +0200

blogs->all

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's a bit difficult for humans to absorb.

I've whipped up a web page which uses the excellent D3.js library to draw a visualisation of your memory usage, using the *.Map file as input. Blocks of memory are drawn proportionally so it's easy to see how much memory you have left and where it's all being used. Click on a block to zoom in on it.

You can run the tool right off the github project page, or download it and modify it for your needs. Pull requests welcome.

https://github.com/eliotstock/memory

Cheers,

Eliot

Posted Dec. 2, 2014, 5:30 p.m.

Nice! Did you use specific flags to get more information? I only see FLASH and RAM and very little used out of both. See this prog.map file.

Posted Dec. 2, 2014, 5:56 p.m.

Because you have very long symbol names, like this...

.text.ZN4func6detail16function_manager19templated_call_copyIPFvbESaIS4_EEEvRNS0_20manager_storage_typeERKS6

... ld is wrapping the memory details onto the next line which is breaking the tool.

Posted Dec. 3, 2014, 2:30 p.m.

Ah, you are right. If I join the lines together with .text in them:

ex -c '%g/\.text/j' -c "wq" prog.map


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:

ex -c '%g/\.text\S*[\s]*\$/j' -c "wq" prog.map


And succeeded by replacing .text.blah with .text:

sed -i 's/\.text\S*/.text/g' prog.map


The only thing left is that the items get really small when you're program gets big. I've to look in the zooming options in your code, but thanks again!

Posted Dec. 3, 2014, 5:48 p.m.

Thanks for the pull request! Merged.

## Recent blog posts

Posted 2017-04-11 11:49:17 by Radosław Koppel
• ### Taking a deeper dive into Bluetooth 5

Posted 2017-04-07 14:53:51 by John Leonard
• ### Logging enabled by default in SDK Bluetooth examples

Posted 2017-03-29 11:27:02 by Håvard
• ### Monitor Mode Debugging with J-Link and GDB/Eclipse

Posted 2017-03-29 05:56:12 by Daniel Veilleux
• ### Getting started with Nordic's Secure DFU bootloader, a step by step guide

Posted 2017-03-20 17:13:52 by Hung Bui

## Recent questions

• ### nRF52832 one of output (p0.15) lost its power

Posted 2017-04-28 12:07:25 by Damian
• ### mesh dfu serial translate update file . 15 min？ why so slowlly？

Posted 2017-04-28 12:03:43 by mr_sev
• ### Ram related issue / What are the best practices (armgcc, linker) > nRF51 16 kB vs 32 kB

Posted 2017-04-28 11:39:06 by trdop
• ### SoftDevice Update size

Posted 2017-04-28 11:30:48 by Mihail
• ### How to setup a complete BLE5 enviornment ?

Posted 2017-04-28 10:33:28 by allankliu