This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Greetings,
In my linker command file, I created a GROUP with a load= parameter set to an undefined memory range. I would have expected a linker error, but there was nothing. I can even remove the LOAD= part, and there is no error.
GROUP
{
<an identifier>
} LOAD= <load_memory_range>
RUN= <execution_address>, PAGE = 0, PALIGN(8)
LOAD_START(<load_start_address>),
LOAD_SIZE(<load_size>),
LOAD_END(<load_end_address>),
RUN_START(<run_start_address>)
RUN_SIZE(<run_size>),
RUN_END(<run_end_address>)
The same is true if I configure the SECTION statement as:
<an identifier>: RUN= <execution_address>, PAGE = 0, PALIGN(8)
LOAD_START(<load_start_address>),
LOAD_SIZE(<load_size>),
LOAD_END(<load_end_address>),
RUN_START(<run_start_address>)
RUN_SIZE(<run_size>),
RUN_END(<run_end_address>)
I have some basic documents on command files which don't explain this. Should I have received an error? Is there a document which explains what I am observing?
Thank you,
Ed
Hi Ed,
Is the section being used in the application?
I tried it in one of my example project. I do get a linker error if the section is present in the application. However there is no error if there is no such section.
You can also check the .map file to check all the sections and where it is being allocated. You can find something like below
Regards,
Veena
Hi Veena,
You are right. I created it and will be adding things to it.
Thank you,
Ed