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

L166 map file

Hi all,

We're using a rather old development kit (3.x) for our project.

1) Our current map-files do not give a summary of the total code/data size unfortunatly. Does the new linker (6.x?) produce more map-file output, including this info? It would be extremly useful if the linker coudl give the sizes mapped to each memory area/type (flash, iram, ram, etc.).

2) It would be nice if you could specify some sort of comment for "reserved memory" areas (in the linker file) which will be used in the map-file. That way it's easy to see what the reserved area is for.

Kind regards,
Joost Leeuwesteijn

Parents Reply Children
  • You may add comments in the linker invocation line. But this feature is there since a very long time (> 5 years). So I do not see why you need another way to add comments.

    Sorry for not making myself clear. What I meant was that it's not possible (as far as I know) to add text (not really comment, using ';' characters) to the RESERVE directive.
    At the moment, reserved sections end up in the map-file as * RESERVED MEMORY *.

    My suggestion was to add extra text so you could describe the section and the map-file would contain for instance:

    * RESERVED MEMORY * (LED's) 

    Regards,
    Joost Leeuwesteijn