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
1 Like
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.
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
Yup, I found the regarding thread, but how about not actually extracting and displaying the info, but returning the whole ārawā .elf file?
Oh that oneā¦ I donāt think thereās an endpoint for it (might be wrong)
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
1 Like