NAME

syslink - link an executable image from a set of object files


SYNOPSIS

syslink [-h] -T <textaddr> -o <outputfile> [-M <map>] <syslink.input>


ARGUMENTS

-h
print summary help

-Ttextaddr
start code at address addr

-oimagefile
create an object file called imagefile

-Mmapfile
create a map file called mapfile

-r
specifies ROM output format.

-v
version number

inputfile
use inputfile as input to the linker (for example, syslink.input)

-l
The linker to use.

-c
The version of object copy to use.


DESCRIPTION

b<It not intended to be used standalone, it is usually called from makefiles producted by aconfig>.

The syslink program first reads its list of directives from syslink.input, then processes each of the Shared directives, loading the specified file and adding its symbols to the shared symbol table. It then reads the unshared files, resolving any references by reference to the shared symbol table. Some symbols in the unshared code may cause references in the shared portion to be resolved (typically the symbols defined in init/init.o to reference process entry points). Finally the text and data segments are relocated, and the file written out in the ELF format. The program omits this stage if unresolved external references remain.

If the '-r' option is set the image is stripped and converted to a.out suitable for an ISOS boot ROM..

This version of syslink is merely a wrapper around arm-elf-ld. The map file produced is _not_ compatible with the mapfile format used by earlier versions of syslink.

The syslink.input directive file is usually generated by aconfig.


SEE ALSO

The ATMOS Book, DO-007001-TC

See the aconfig manpage and the mkproduct manpage.