??? 06/28/08 01:34 Modified: 06/28/08 01:57 Read: times |
#156279 - Linker output Responding to: ???'s previous message |
Hi
here is the linker output BL51 BANKED LINKER/LOCATER V5.03 06/28/2008 00:51:25 PAGE 2 * * * * * * * X D A T A M E M O R Y * * * * * * * XDATA 0000H 0035H UNIT _XDATA_GROUP_ XDATA 0035H 0003H UNIT ?XD?AUTOMHASPLITNUT?PLC XDATA 0038H 0002H UNIT ?XD?_READENC?PLC 003AH 00C6H *** GAP *** XDATA 0100H 0010H ABSOLUTE XDATA 0110H 0020H ABSOLUTE XDATA 0130H 0040H ABSOLUTE XDATA 0170H 0040H ABSOLUTE XDATA 01B0H 0040H ABSOLUTE XDATA 01F0H 0040H ABSOLUTE XDATA 0230H 0040H ABSOLUTE XDATA 0270H 0040H ABSOLUTE XDATA 02B0H 0050H ABSOLUTE XDATA 0300H 0040H ABSOLUTE XDATA 0340H 0030H ABSOLUTE XDATA 0370H 0008H ABSOLUTE XDATA 0378H 0030H ABSOLUTE XDATA 03A8H 0058H ABSOLUTE XDATA 0400H 0010H ABSOLUTE XDATA 0410H 0010H ABSOLUTE XDATA 0420H 0010H ABSOLUTE XDATA 0430H 0010H ABSOLUTE XDATA 0440H 0020H ABSOLUTE XDATA 0460H 0040H ABSOLUTE XDATA 04A0H 0060H ABSOLUTE XDATA 0500H 0020H ABSOLUTE XDATA 0520H 0040H ABSOLUTE XDATA 0560H 0004H ABSOLUTE XDATA 0564H 0004H ABSOLUTE XDATA 0568H 0004H ABSOLUTE XDATA 056CH 0D14H UNIT ?XD?PLC 1280H 0D80H *** GAP *** XDATA 2000H 0001H ABSOLUTE I think the variables affected are in ?XD?PLC i.e from 0x56CH to 0x1280. Around 3348 bytes are decided by linker. the same scheme I am using for the other projects also. I am assuming linker understands this absolute addressing and takes care about it. Since I located all the absolute variables as one piece, the linker is automatically using remaining space. I also observed in another project where absolute variables are scattered and still the linker using spaces avaialbe in between the absolute variables, for different modules. at the end of Listing file... MODULE INFORMATION: STATIC OVERLAYABLE CODE SIZE = 35996 ---- CONSTANT SIZE = 4376 ---- XDATA SIZE = 3348 24 PDATA SIZE = ---- ---- DATA SIZE = 70 16 IDATA SIZE = ---- ---- BIT SIZE = 35 3 END OF MODULE INFORMATION. in the above data XDATA size is 3348 but output says the following Program Size : data = 94.4 xdata = 4539 code 46615 why it is showing different values ? 3348 + 1128 (absolute Space) = 4476 Best Regards Haribabu btw : what is the meaning of "OVERLAYABLE" here ? |
Topic | Author | Date |
Strange problem with Keil Compiler | 01/01/70 00:00 | |
Try volatile | 01/01/70 00:00 | |
Probably not the volatile | 01/01/70 00:00 | |
Who can know what is in the mind of the compiler | 01/01/70 00:00 | |
cut out the optimizer (set to 2) and see | 01/01/70 00:00 | |
Assembler Dump | 01/01/70 00:00 | |
well | 01/01/70 00:00 | |
XRAM is enabled | 01/01/70 00:00 | |
the most likel7y reason is that | 01/01/70 00:00 | |
You may want to let the linker know | 01/01/70 00:00 | |
he is using a '124 | 01/01/70 00:00 | |
I know | 01/01/70 00:00 | |
Linker output | 01/01/70 00:00 | |
OVERLAYABLE | 01/01/70 00:00 | |
OVERLAYABLE ?![]() | 01/01/70 00:00 | |
Eh, no debugger for silabs chip? | 01/01/70 00:00 | |
I am using CA51 which dont have debugging | 01/01/70 00:00 | |
it will | 01/01/70 00:00 |