Determines whether your program loads and executes from RAM and/or ROM. The most common choices are:

standalone_ram.ld - the program is loaded to and executes from RAM

standalone_romcopy.ld - the program is loaded to ROM. During startup the program copies itself to RAM

standalone_romrun.ld - the program is loaded to and executes from ROM

Controls how your executable is linked and loaded in to memory. This file is where you define the starting address and size of memory regions and specify which sections will be loaded in to those regions.

The program is linked so that it is loaded into, and executes out of RAM. Such programs are usually downloaded and started by running the Debugger and a debug server. This layout is generally used in the early stages of development.

The program is linked so that it can be loaded into ROM/FLASH, but copies itself to RAM and executes out of RAM. Such programs are burned into flash and connected to by using the Debugger and a debug server. This layout can be used for producing a final executable. It is faster than the romrun layout and offers software breakpoint debugging, but takes longer to initialize and requires more RAM.

The program is linked so that it can be loaded into, and executes out of ROM/FLASH. Such programs must be burned into flash (for example, by using MULTI Fast Flash Programmer) and connected to by using the Debugger and a debug server. This layout may be used for producing a final executable. It requires the least amount of RAM, but is typically slower, and cannot be debugged using software breakpoints. Some Debugger features that rely on software breakpoints may not be available in this mode, including System Calls, Command Line Procedure Calls, and Run-Time Error Checking.

The program is linked so that it can be loaded into, and executes primarily out of ROM/FLASH, with a few hook functions used by the Debugger copied into and executing from RAM. Such programs must be burned into flash (for example, by using MULTI Fast Flash Programmer) and connected to by using the Debugger and a debug server. This layout may be used for producing a final executable. It requires only slightly more RAM than romrun mode, with similar performance. It cannot be debugged using software breakpoints, but some Debugger features not available in romrun mode will work, including System Calls, Command Line Procedure Calls, and Run-Time Error Checking.

Creates an executable with code sections that can be located anywhere in memory.

Creates an executable with data sections that can be located anywhere in memory.

Creates an executable with code and data sections that can be located anywhere in memory.

Documentation for Linker Directives

You can include customizable versions of standard Green Hills libraries.

Configuring a Standalone Program The settings in this dialog control how your program is linked and allow you to include optional, customizable versions of various libraries.