Avago Technologies LSI53C1010 - Manual (Page 126)

4-6 Using the LSI Logic Assembler NASM™
4.3.10 Patch Offsets
The -x option produces an assembly level output file, including a list of
patch addresses for each symbol. These addresses indicate where to
patch each individual symbol value.
4.4 Example Assembler Command Lines
The following command lines are typical examples of how to use the
various options.
NASM demoPCI.ss
This command line produces no output files, but allows a quick syntax
check on the SCRIPTS instructions in the file named DEMOPCI.SS
NASM demoPCI.ss -a 875 -l -o -e errors.txt
This command line requests that NASM check the syntax and generate
code for the LSI53C875 chip. It generates the listing, error log, and
standard C header. Since no filenames were specified for the listing and
C header files, they will take the name of the input file, but with
.LIS and
.OUT as the file extensions, respectively. The error log is sent to the file
named ERRORS.TXT
4.5 How NASM Parses SCRIPTS Files
SCSI SCRIPTS programs contain a series of lines. Blank lines, lines
containing only white space, and anything after a semicolon on a line are
ignored.
The assembler is token oriented. It reads the source file and splits it up
into tokens. White space and anything from a semicolon to the end of
the line is not part of any token, and is ignored by the first pass of the
assembler.
There are two types of tokens. Any string of consecutive letters,
numbers, dollar signs, and underscores is a token. The second type of
token consists of characters that are not part of other tokens. Anything
that is not a letter, a digit, an underscore, or a dollar sign, will become a