Discussion Forum

L166 map file

Next Thread | Thread List | Previous Thread Start a Thread | Settings

DetailsMessage
Read-Only
Author
Joost Leeuwesteijn
Posted
13-Jul-2006 14:55 GMT
Toolset
C166
New! 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
Read-Only
Author
Andy Neil
Posted
13-Jul-2006 15:09 GMT
Toolset
C166
New! Before your very eyes...
You could download the free evaluation version and, well, evaluate it...! ;-)
Read-Only
Author
Joost Leeuwesteijn
Posted
13-Jul-2006 15:19 GMT
Toolset
C166
New! RE: Before your very eyes...
Downloading... :-)

But I was also hoping for a "you can also do/use this-and-that to quickly check total code/data sizes" :-)

Regards,
Joost Leeuwesteijn
Read-Only
Author
Reinhard Keil
Posted
14-Jul-2006 11:08 GMT
Toolset
C166
New! RE: Before your very eyes...
The current version outputs a size summary at the end of the build process.

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.
Read-Only
Author
Joost Leeuwesteijn
Posted
14-Jul-2006 11:16 GMT
Toolset
C166
New! RE: Before your very eyes...
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

Next Thread | Thread List | Previous Thread Start a Thread | Settings