UM0144 datasheet(35/92 Pages) STMICROELECTRONICS

35 / 92 page

ST7 Assembler Linker

4 Linker

UM0144

35/92

Linker

4.1

What the linker does

After having separately assembled all the component modules in your program, the next step is to link

them together into a .COD file which can then be sent on to its final destination using OBSEND.

This linking process is not just as a simple concatenation of the object modules. It resolves all the external

references. If a referenced label is not defined as PUBLIC, an error is detected. It also checks the type of

relocation to do, places the segment according to your mapping, and checks if any of them is overrun.

4.2

Invoking the linker

4.3

Command line

The linker needs the following arguments:

LYN <.OBJ file>[+<.OBJ file>...],

[<.COD file>],[<lib>][+<lib>...]

If all or any arguments are left out of the command line, you'll be prompted.

For example:

LYN

STMicroelectronics - Linker - rel

3.00

.OBJ files: begin

.COD file [begin.cod]: begin

Libraries:

The .OBJ files are simply a list of all the object files that form your program. The .OBJ suffix may be left

out, and if more than one is specified they should be separated by '+' characters, for example

game+scores+keys

would tell the linker to link 'game.obj', 'scores.obj' and 'key.obj'. Object file

path names should not include '-' or ';' characters. Character '.' should be avoided, except for suffixes.

The .COD file has a default name formed of the first object file's name with forced suffix of '.COD'. This will

be the name of the file produced at the end of the link session. It contains all the information from the link

session in a special format: however, OBSEND must be used on the .COD file before it is ready to use. If the

default filename is not what you want, the filename given at the prompt is used instead. The suffix will be

forced to .COD if left blank. The default is selected by leaving this argument blank at the command line, or

pressing <ENTER> at the prompt.

The 'Libraries' prompt asks for a list of library files generated by the lib utility that should be searched

in case of finding unresolved external references. The format for giving multiple libraries is the same as for

the .OBJ list, except the suffix .LIB is assumed.

Some examples:

Linking together the modules game.obj, scores.obj, key.obj, game1.obj, game2.obj and

game3.obj without using any libraries and generating a .COD file named game.cod,

requires the following command line:

LYN game+scores+keys+game1+game2+game3;

UM0144 датащи(PDF) 35 Page - STMicroelectronics

UM0144 датащи(HTML) 35 Page - STMicroelectronics

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92

датащи скачать

ссылки URL