xcl to icf conversion help required.

Dear members,

I need some guidance how can i convert following xcl file used in 4.4 version of IAR to .icf file for 5.3 IAR version. Any type of comments and help will be highly appricited.
Regards
Dani

// ---------------------
// ATMEL Microcontroller Software Support - ROUSSET -
// ---------------------
// The software is delivered "AS IS" without warranty or
// condition of any kind, either express, implied or
// statutory. This includes without limitation any warranty
// or condition with respect to merchantability or fitness
// for any particular purpose, or against the infringements of
// intellectual property rights of others.
// ---------------------
// File: at91SAM7S128_32KRAM.xlc
//
// 1.1 01/Mar/05 JPP : Creation for 4.11A
// $Revision: 1.3 $
//
// ---------------------

//*************************************************************************
// XLINK command file template for EWARM/ICCARM
//
// Usage: xlink -f lnkarm
// -s
//
// $Revision: 1.3 $
//*************************************************************************

//************************************************
// Inform the linker about the CPU family used.
// AT91SAM7S256 Memory mapping
// No remap
// ROMSTART
// Start address 0x0000 0000
// Size 128 Kbo 0x0002 0000
// RAMSTART
// Start address 0x0020 0000
// Size 32 Kbo 0x0000 8000
// Remap done
// RAMSTART
// Start address 0x0000 0000
// Size 32 Kbo 0x0000 8000
// ROMSTART
// Start address 0x0010 0000
// Size 128 Kbo 0x0002 0000

//************************************************
-carm

//*************************************************************************
// Internal Ram segments mapped AFTER REMAP 32 K.
//*************************************************************************
// Use these addresses for the .
-Z(CONST)INTRAMSTART_REMAP000000
-Z(CONST)INTRAMEND_REMAP007FFF

//*************************************************************************
// Read-only segments mapped to Flash 128 K.
//*************************************************************************
-DROMSTART000000
-DROMEND01FFFF
//*************************************************************************
// Read/write segments mapped to 23 K RAM.
//*************************************************************************
-DRAMSTART000000
-DRAMEND007FFF

//************************************************
// Address range for reset and exception
// vectors (INTVEC).
// The vector area is 32 bytes,
// an additional 32 bytes is allocated for the
// constant table used by ldr PC in cstartup.s79.
//************************************************
-Z(CODE)INTVEC-3F

//************************************************
// Startup code and exception routines (ICODE).
//************************************************
-Z(CODE)ICODE,DIFUNCT=ROMSTART-ROMEND
-Z(CODE)SWITAB=ROMSTART-ROMEND

//************************************************
// Code segments may be placed anywhere.
//************************************************
-Z(CODE)CODE=ROMSTART-ROMEND

//************************************************
// Various constants and initializers.
//************************************************
-Z(CONST)INITTAB,DATA_ID,DATA_C=ROMSTART-ROMEND
-Z(CONST)CHECKSUM=ROMSTART-ROMEND

//************************************************
// Data segments.
//************************************************
-Z(DATA)DATA_I,DATA_Z,DATA_N=RAMSTART-RAMEND

//************************************************
// __ramfunc code copied to and executed from RAM.
//************************************************
-Z(DATA)CODE_I=RAMSTART-RAMEND
-Z(CONST)CODE_ID=ROMSTART-ROMEND // Initializer for
-QCODE_I=CODE_ID

//************************************************
// ICCARM produces code for __ramfunc functions in
// CODE_I segments. The -Q XLINK command line
// option redirects XLINK to emit the code in the
// debug information associated with the CODE_I
// segment, where the code will execute.
//************************************************

//*************************************************************************
// Stack and heap segments.
//*************************************************************************
-D_CSTACK_SIZE=(100*4)
-D_IRQ_STACK_SIZE=(3*8*4)

-Z(DATA)CSTACK+_CSTACK_SIZE=RAMSTART-RAMEND
-Z(DATA)IRQ_STACK+_IRQ_STACK_SIZE=RAMSTART-RAMEND

//*************************************************************************
// ELF/DWARF support.
//
// Uncomment the line "-Felf" below to generate ELF/DWARF output.
// Available format specifiers are:
//
// "-yn": Suppress DWARF debug output
// "-yp": Multiple ELF program sections
// "-yas": Format suitable for debuggers from ARM Ltd (also sets -p flag)
//
// "-Felf" and the format specifiers can also be supplied directly as
// command line options, or selected from the Xlink Output tab in the
// IAR Embedded Workbench.
//*************************************************************************

// -Felf
Start a New Thread

Adnan schrieb:
> I need some guidance how can i convert following xcl file used in 4.4 version of IAR to .icf file for 5.3 IAR version. Any type of comments and help will be highly appricited.

I would not try to convert it. Just use the wizard and enter the values
found in the xcl

--
42Bastian
------------------
Parts of this email are written with invisible ink.

Note: SPAM-only account, direct mail to bs42@...
Start a New Thread

Thanks for reply,

Which wizard you are talking about. did you mean the .icf editor option avialible in linker options.

Regards

--- In A..., 42Bastian wrote:
>
> Adnan schrieb:
> > I need some guidance how can i convert following xcl file used in 4.4 version of IAR to .icf file for 5.3 IAR version. Any type of comments and help will be highly appricited.
>
> I would not try to convert it. Just use the wizard and enter the values
> found in the xcl
>
> --
> 42Bastian
> ------------------
> Parts of this email are written with invisible ink.
>
> Note: SPAM-only account, direct mail to bs42@
>
Start a New Thread

Adnan schrieb:
> Thanks for reply,
>
> Which wizard you are talking about. did you mean the .icf editor option avialible in linker options.

Right. I used it and the resulting icfS were just good enough
--
42Bastian
------------------
Parts of this email are written with invisible ink.

Note: SPAM-only account, direct mail to bs42@...
Start a New Thread