This part refers to the different possible linking & debugging configurations and the different files implied in this processus.
In particular, linking in the different embedded memories will be reached. Debug in SRAM, Flash and remap considerations will be described.

• Linking Considerations (at91SAM7xxx_FLASH.xcl & at91SAM7xxx_RAM.xcl)
  The .xcl files are called linker command files. They describe the memory layout of the target system, inform the linker about the CPU family used, define the different code and data segments, the stack and heap size...
  
  The at91SAM7xxx_FLASH.xcl is dedicated to link in Flash, the at91SAM7xxx_RAM.xcl to link in SRAM.
  Please refer to these files for all the different segment definitions. A memory mapping is included to help the developper.
  
  In the example (Cstartup.s79) , the following instruction allows to link the exception vectors at the address 0x0:
  RSEG ICODE:CODE (2) ;- Begins a relocatable segment : corresponding address is 32-bit aligned
  
  
  • Linking in FLASH (Workspace Configurations: (Flash_Debug and Binary):
    
    This segment represents the internal SRAM start and aend address after a Remap:
    -Z(CONST)INTRAMSTART_REMAP=00200000
    -Z(CONST)INTRAMEND_REMAP=00203FFF

    This segment represents the read only area:
    -DROMSTART=00000000
    -DROMEND=0000FFFF
    
    This segment represents the read/write area:
    -DRAMSTART=00200000
    -DRAMEND=00203FFF

  • Linking in SRAM (Workspace Configurations: RAM_Debug):
    
    This segment represents the internal SRAM address after a Remap:
    -Z(CONST)INTRAMSTART_REMAP=00000000
    -Z(CONST)INTRAMEND_REMAP=00003FFF
    
    This segment represents the read only area:
    -DROMSTART=00000000
    -DROMEND=0000FFFF
    
    This segment represents the read/write area:
    -DRAMSTART=00000000
    -DRAMEND=00003FFF

The Stack segment (CSTACK) and the Heap segment (HEAP) are also defined here...
-Z(DATA)CSTACK+_CSTACK_SIZE=RAMSTART-RAMEND
-Z(DATA)HEAP+_HEAP_SIZE=RAMSTART-RAMEND

__ramfunc directive makes a function executed in RAM.
Functions declared __ramfunc are by default stored in the segment named CODE_I:

// __ramfunc code copied to and executed from RAM.
-Z(DATA)CODE_I=RAMSTART-RAMEND

Refer to the Memory Segment Section of the IAR ARM® IAR C/C++ Compiler Reference Guide for more details.

• Debugging Considerations (SAM7_FLASH.mac & SAM7_RAM.mac)
  A setup macro file is a standard macro file that you choose to load automatically when the IAR debugger starts.
  You can define the setup macro file to perform actions according to your needs, by using setup macro functions and system macros. Thus, by loading a setup macro file you can initialize the IAR debugger to automatically perform actions.
  
  IAR Toolchain supplies Setup Macro Functions which are automatically executed during the IAR debugger setup. Thus, it can be used to set up the simulation environment automatically.
  
  Refer to the Macro System Section of the IAR ARM® IAR C/C++ Compiler Reference Guide for more details.
  
  • Debugging Code in RAM
    The 2 setup macro functions execUserReset and execUserPreload are used in this example to make some basic initializations necessary to debug in SRAM.
    
    execUserPreload is executed before the code download takes place:
    
    execUserPreload() {
    __message "execUserPreload()";
    __hwReset(0); // Hardware Reset: CPU is automatically halted after the reset (JTAG is already configured to 32kHz)
    _InitPLL(); // Allow to load Code at JTAG Full Speed
    _MapRAMAt0(); // Remap RAM to address 0
    _InitRSTC(); // Enable User Reset to allow execUserReset() execution
    }
    
    execUserReset is used to reinitialize the memory mapping after an IAR Debugger reset:
    
    execUserReset() {
    __message "execUserReset()";
    __emulatorSpeed(30000); // Set JTAG speed to 30kHz to make a hardware reset
    __hwReset(0); // Hardware Reset: CPU is automatically halted after the reset
    _InitPLL(); // Allow to debug at JTAG Full Speed
    _MapRAMAt0(); // Remap RAM to address 0
    __emulatorSpeed(0); // Set JTAG speed to full speed
    }
    
  • Debugging Code in FLASH
    The setup macro function execUserResetis used in this example to make some basic initializations necessary to debug in Flash.
    
    execUserReset is used to reinitialize the memory mapping after an IAR Debugger reset:
    
    execUserReset() {
    __message "execUserReset()";
    __emulatorSpeed(30000); // Set JTAG speed to 30kHz to make a hardware reset
    __hwReset(0); // Hardware Reset: CPU is automatically halted after the reset (JTAG is already configured to 32kHz)
    _InitPLL(); // Allow to debug at JTAG Full Speed
    _InitRSTC(); // Enable User Reset to allow execUserReset() execution
    __emulatorSpeed(0); // Set JTAG speed to full speed
    }
    
    Refer to " An overview of the debugger startup" Section of the IAR ARM® IAR C/C++ Compiler Reference Guide for more details.