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.

Compiler: ALIAS keyword in ARM m4 cortex linker



Tool/software: TI C/C++ Compiler

Hello,

According to the ARM assembly language tools manual, the linker has a keyword ALIAS that can be use to indicate the linker two memory ranges that are actually mapped to the same physical memory.

the example from the linker manual:

MEMORY
{
...
ALIAS
{
SRAM_CODE (RWX) : origin = 0x01000000
SRAM_DATA (RW) : origin = 0x20000000
} length = 0x0001000
...
}

I was trying to use this keyword according to the syntax the manual describes but the linker generate error message:

"V:/USRR_Projects/branches/guySBL/TDA3xx/SBL/SBL_Common/sbl_common.cmd", line 22: error #10024-D: expecting memory range specifier instead of "{"\

Can you please help explain what am i doing wrong - it looks like the linker does not recognize this syntax and/or keyword

Thanks

Guy

  • The memory range ALIAS feature is introduced in TI ARM compiler tools version 15.12.0.LTS.  What version do you use?

    Thanks and regards,

    -George

  • Hi, thanks.

    The version i am currently using is 5.2.8 (that explains why it does not work -is there some other syntax for my version?).

    problem is i also could not fund anywhere the manual for my (older) version - the only manual i found was for version 16. 

    Do you know what are the differences between versions 16.x.x to 5.2.x the number makes it sounds like a huge jump should it be safe to upgrade (also are there any downsides to upgrading)?

    Thanks

    Guy

  • Guy Mardiks said:
    The version i am currently using is 5.2.8 (that explains why it does not work -is there some other syntax for my version?).

    Unfortunately, no.

    Guy Mardiks said:
    Do you know what are the differences between versions 16.x.x to 5.2.x the number makes it sounds like a huge jump

    Despite the difference in the numbers, it is not a huge jump.  The version numbering scheme changed.  The first number is now the year of the release.  (Well, the last two digits of the year.)  You can read more details about it in the wiki article Compiler Version Numbers and What They Mean.  I think you will agree that an upgrade is the best choice for your situation.

    Thanks and regards,

    -George