LPCXpresso MAP file

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

LPCXpresso MAP file

1,224 Views
shlomi
Contributor I

When mapping variables to memory regions other then the default BSS, the map file seems to not attach the variable name.

Why is that?

E.g.:

static osStack_t digitaliotaskstack[128];

Will appear in the map file:

.bss.digitaliotaskstack
                       0x02002d64 0x200 ./app/digital_io.o

Where as mapped to RAM3 bank:

static __BSS(RAM3) osStack_t digitaliotaskstack[128];

it will appear in the map file as:

 .bss.$RAM3     0x02005868      0x200 ./app/digital_io.o

That seem strange to me.

Thanks in advance,

Shlomi

1 Reply

862 Views
lpcxpresso_supp
NXP Employee
NXP Employee

The naming used is to allow the item to be placed into the correct memory block by the linker script. However the cr_section_macros.h header also provides macros "__BSS_EXT" and __DATA_EXT" which can be used to place DATA/BSS items into a more specifically named section than the default ".BSS.$RAM3" etc using something like:

__BSS_EXT(RAM3,digitaliotaskstack) osStack_t digitaliotaskstack[128];

Regards,

LPCXpresso Support