AnsweredAssumed Answered

Interpreting/Understanding map file

Question asked by Ben Griffiths on Jan 26, 2017
Latest reply on Jan 27, 2017 by Ben Griffiths

I've recently switched to using Code Warrior. I'm looking at the .map file output, and I'm struggling to interpret some sections of it.

(I'm used to using IAR Embedded Workbench)


I know I'm running close to the limit of my target's code size. So I want to know:

  1. What my current Code Size is?
  2. Which area of the source is generating the largest output? (So I can target that area)

Looking at my .map file I can see it's telling me in the Memory Configuration section how much I've allocated to each area (m_text, m_data), but I already knew that because I can read that from the linker file. What I can't see is how much of each section is actually used.


Is there any documentation explaining the output in the .map file?