This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

meaning of sizes in the .map file

What's the exact meaning of the "Code (inc. data)", "Debug" sizes in the .map file? Why is the Debug-size so big?

      Code (inc. data)   RO Data    RW Data    ZI Data      Debug   Object Name

       208         72          0          4          0      94225   main.o

thanks in advance
Georg

Parents
  • I saw this call in the .map file (in the execution area of my flash ROM).

    At the beginning of this list, there is the RESET vector and the startup, after that I can see all the RO data from all c-files of my project. This part is clear to me. But after that there are lines like

    0x100003ac   0x00000008   Ven    RO          116    .text               uidiv.o(mc_t.l)
    

    or

     0x100003dc   0x00000010   Code   RO          312    .text               callvia.o(h_t.l)
    

    I don't know what "mc_t.l" means.

    best regards
    Georg

Reply
  • I saw this call in the .map file (in the execution area of my flash ROM).

    At the beginning of this list, there is the RESET vector and the startup, after that I can see all the RO data from all c-files of my project. This part is clear to me. But after that there are lines like

    0x100003ac   0x00000008   Ven    RO          116    .text               uidiv.o(mc_t.l)
    

    or

     0x100003dc   0x00000010   Code   RO          312    .text               callvia.o(h_t.l)
    

    I don't know what "mc_t.l" means.

    best regards
    Georg

Children
No data