# Compiler output memory map?

**URL:** https://community.particle.io/t/compiler-output-memory-map/17293
**Category:** General
**Created:** [November 9, 2015, 3:58pm UTC](https://community.particle.io/t/compiler-output-memory-map/17293 "2015-11-09T15:58:33Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![GrahamS](https://avatars.discourse-cdn.com/v4/letter/g/7feea3/32.png) [@GrahamS](https://community.particle.io/u/GrahamS)
#### Post date: [November 9, 2015, 3:58pm UTC](https://community.particle.io/t/compiler-output-memory-map/17293/1 "2015-11-09T15:58:33Z")

</div>

Hi,

OK so I primarily use Dev to build and deploy code during development. When that gives me undefined errors - I resort to CLI compile - which gives much more detail of failures and warnings.

CLI also dumps a memory usage summary - which helps now that I know how to read it - thanks ScruffR 😉

I now find that I would like to view the actual memory map (which most compilers/linkers produce ???). Is this possible from CLI - if so - how please ???. I an hoping that it will help me to find a ‘feature’ (in my code somewhere) which seems to be taking too much RAM (just got to fast cyan flashing after a build until I dropped an array to smaller size :-O). bss is telling me I am using \> 57k :-O, thats after a BIG code overhaul…so I obviously screwed something up 😮

Thanks  
Graham

---

<div class="post-metadata">

### Author: ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)
#### Post date: [November 9, 2015, 4:34pm UTC](https://community.particle.io/t/compiler-output-memory-map/17293/2 "2015-11-09T16:34:52Z")

</div>

I don’t know of a way to do this with CLI, but maybe @suda or @kennethlimcp do (or can add the feature).

With a local toolchain you would get an `.elf` file and I guess the CLI build farm does or at least could produce one too, and if there was a CLI parameter to download that along or instead of the `.bin` you could get what you need.

---

<div class="post-metadata">

### Author: ![kennethlimcp](https://avatars.discourse-cdn.com/v4/letter/k/c0e974/32.png) [@kennethlimcp](https://community.particle.io/u/kennethlimcp)
#### Post date: [November 9, 2015, 4:35pm UTC](https://community.particle.io/t/compiler-output-memory-map/17293/3 "2015-11-09T16:35:48Z")

</div>

The endpoint might be returning it but the CLI didn’t extract the info since the feature was “removed” months back. We will need to add it back

---

<div class="post-metadata">

### Author: ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)
#### Post date: [November 9, 2015, 4:37pm UTC](https://community.particle.io/t/compiler-output-memory-map/17293/4 "2015-11-09T16:37:48Z")

</div>

Yup, I found the regarding thread, but how about not actually extracting and displaying the info, but returning the whole “raw” `.elf` file?

---

<div class="post-metadata">

### Author: ![kennethlimcp](https://avatars.discourse-cdn.com/v4/letter/k/c0e974/32.png) [@kennethlimcp](https://community.particle.io/u/kennethlimcp)
#### Post date: [November 9, 2015, 4:38pm UTC](https://community.particle.io/t/compiler-output-memory-map/17293/5 "2015-11-09T16:38:42Z")

</div>

Oh that one… I don’t think there’s an endpoint for it (might be wrong)

---

<div class="post-metadata">

### Author: ![GrahamS](https://avatars.discourse-cdn.com/v4/letter/g/7feea3/32.png) [@GrahamS](https://community.particle.io/u/GrahamS)
#### Post date: [November 9, 2015, 6:06pm UTC](https://community.particle.io/t/compiler-output-memory-map/17293/7 "2015-11-09T18:06:55Z")

</div>

Hi,  
Sorry to have opened up a hornets nest ;-).

My need for this is reduced anyway as I found my bug without a RAM map, BUT of course if I had one it would have been immediately more obvious 😉

Sorry…

Graham