Memory size

To find the actual use, run 'objdump -p' on the elf image, that defines the memory areas that the JTAG loader (and other loaders) copy from the program file into system memory.

You might also want to look at the 'objdump -h' output and teh symbol table.

Note that the ldscript the IDE tools use will link all initialised data onto the end of the code segment, and add startup code to copy that to the requested memory block. This doesn't work if you are loading code into tightly-coupled instruction memory - as it is unlikely to have enough space for all the data.

I've forgotten the PATH for objdump! but it is in the directory tree somewhere.