- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Hello All,
We have a very strange situation that the linker cannot link a structure of 0x98 in size into an output section section that is 0x98.
The linker output looks like this: error #10099-D: program will not fit into available memory, or the section contains a call site that requires a trampoline that can't be generated for this section.placement with alignment.blocking fails for section xxx size 0x98page0. Available memory ranges MEM_xxx size 0x98 unused: 0x98 max hole: 0x98
the memory where we plan to locate the section is defined like this:
#define LEN_xxx 0x98
MEM_xxx : origin = 0x0C0000 - LEN_xxx, length = LEN_xxx
Some important facts:
if instead the data structure with size 0x98 we use an array with size 0x98 the linking works fine
if we use 0xA0 and 0xB0 for LEN_xxx and the data structure as input sectiuon the linking does not work
if we use 0xC0 for LEN_xxx and the data structure as input section the linking works ok. After linking complete, when we inspect the map file we can clearly observe that the size of the structure is, as expected, 0x98.
a fuew questions arrize:
1 - why does linking work for an array but not for a data structure of the same size
2 - why does linking work for an arbitrarly higher section size (0xC0) and not for 0xA0 or 0xB0 when the located data is, in this case, 0x98.
If any of you has an idea of why the locating does not work in the first place, please let me know.
We are using the compiler that comes with the code composer studio 10.2
Thank you,
Eugen
