AnsweredAssumed Answered

MC56F84xxx Linker command file when using Quickstart

Question asked by q1444 Employee on Feb 26, 2016
Latest reply on Mar 11, 2016 by Fiona Kuang

Hi all,

 

customer Mile have questions regarding the Linker command file in Codewarrior 10.6 when using the Quickstart stationaries.

Compared to the .cmd file coming from Codewarrior project wizard the generated file from Quickstart looks different:

The colored parts below are not clear for them:

 

MEMORY

{

.p_flash_ROM_vect     (RX)  : ORIGIN = 0x0000,   LENGTH = 0x0200
.p_flash_ROM          (RX)  : ORIGIN = 0x0208,   LENGTH = 0xFdf8

 

###############################

# The internal RAM is physically shared among P-RAM and X-RAM so the user

# has to do partitioning between the two when putting variables. These two

# lines define full memory areas (just for an information, not used for variables). 
.p_all_internal_RAM   (RWX) : ORIGIN = 0x60000, LENGTH = 0x3000

.x_all_internal_RAM   (RW)  : ORIGIN = 0x0000, LENGTH = 0x3000

  
###############################

# the partitioning is made here (0x2fe0 of X-RAM vs. 0x020 of P-RAM)

.p_internal_RAM        (RWX) : ORIGIN = 0x63fe0, LENGTH = 0x0020

.x_internal_RAM         (RW)  : ORIGIN = 0x0001, LENGTH = 0x2fdf

 

# ximage MUST be set same as x_internal_RAM above (with X flag set)

.p_internal_RAM_ximage  (RX)  : ORIGIN = 0x0001, LENGTH = 0x2fdf

.x_onchip_peripherals   (RW)  : ORIGIN = 0xC000, LENGTH = 0x3000

.x_onchip_far           (RW)  : ORIGIN = 0x018000, LENGTH = 0x4798  # 18328 words

.x_EOnCE                (R)   : ORIGIN = 0xFFFF00, LENGTH = 0x0100

}

 

Questions:

What is ".p_internal_RAM" exactly used for?

Why is ".x_internal_RAM" reduced by 0x20?  (LENGTH=0x2fdf instead of 0x3000)

 

 

Thanks for quick help.

 

br

Guenter

Outcomes