Motorola dsp assembler Reference Manual

Motorola DSP Assembler
Assembler Options
MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
1-7
below. Note that if this option is not used the Assembler runs with all latest
revision level enhancements on by default.
Processor
Identifier
DSP56001 Rev. C
56001c
DSP56002
56002
DSP56004
56004
DSP56166
56166
DSP96001 Rev. B
96001b
DSP96002
96002
Example: ASM56000  -P56001c myprog.asm
Assemble MYPROG.ASM with the DSP56000 Revision C enhance-
ments.
-Q
On some hosts the Assembler displays a banner on the console when in-
voked.  This option inhibits the banner display.  It has no effect on hosts
where the signon banner is not displayed by default.
Example: ASM56000  -Q  myprog.asm
Assemble the file MYPROG.ASM but do not display the signon ban-
ner on the console.
-R
Run the Assembler without the specified processor revision level enhance-
ments. This is for backward compatibility so that the Assembler will flag new
constructions as illegal.  can be any of the revision specifiers given be-
low, but must be appropriate for the target processor.
This option is superseded by the -P option.
Processor
Revision
DSP56001 Rev. C
C
DSP56002
2
DSP56004
4
DSP56166
6
DSP96000 Rev. B
B
DSP96001
1
Example: ASM56000  -RC  myprog.asm
Assemble MYPROG.ASM without the DSP56000 Revision C en-
hancements.

---

Motorola DSP Assembler
Assembler Options
1-8
DSP ASSEMBLER REFERENCE MANUAL
MOTOROLA
-V
This option causes the Assembler to report assembly progress (beginning
of passes, opening and closing of input files) to the standard error output
stream.  This is useful to insure that assembly is proceeding normally.
Example: ASM56000  -V  myprog.asm
Assemble the file MYPROG.ASM and send progress lines to the
standard error output.
-Z
This option causes the Assembler to strip symbol information from the ab-
solute load file.  Normally symbol information is retained in the object file for
symbolic reference purposes.  Note that this option is valid only when the
Assembler is in absolute mode via the -A command line option and when an
object file is created (-B option).
Example: ASM56000  -A -B -Z  myprog.asm
Assemble the file MYPROG.ASM in absolute mode and strip symbol
information from the load file created as output.

A list of operating system compatible filenames (including optional path-
names). If no extension is supplied for a given file, the Assembler first will
attempt to open the file using the filename as supplied. If that is not success-
ful the Assembler appends .ASM to the filename and attempts to open the
file again. If no pathname is specified for a given file, the Assembler will look
for that file in the current directory. The list of files will be processed sequen-
tially in the order given and all files will be used to generate the object file
and listing.
The Assembler will redirect the output listing to the standard output if the output listing is
not suppressed with the IL option, or if it is not redirected via the -L command line option
described above.  The standard output generally goes to the console or terminal screen
by default, but can be diverted to a file or to a printer by using the I/O redirection facilities
of the host operating system, if available.  Error messages will always appear on the stan-
dard output, regardless of any option settings.  Note that some options (-B, -L) allow a
hyphen as an optional argument which indicates that the corresponding output should be
sent to the standard output stream.  Unpredictable results may occur if, for example, the
object file is explicitly routed to standard output while the listing file is allowed to default to
the same output stream.
For more details on Assembler operation in a particular machine environment see Appen-
dix G, Host-dependent Information.

---

Motorola DSP Assembler
Assembler Processing
MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
1-9
1.6
  ASSEMBLER PROCESSING
The Motorola  DSP Assembler is a two-pass Assembler.  During the first pass the source
program is read to build the symbol and macro tables.  During the second pass the object
file is generated (assembled) with reference to the tables created during pass one.  It is
also during the second pass that the source program listing is produced.
Each source statement is processed completely before the next source statement is read.
As each line is read in, any translations specified by the DEFINE directive are applied.
Each statement is then processed, and the Assembler examines the label, operation
code, operand, and data transfer fields.  The macro definition table is scanned for a match
with the operation code.  If there is no match, the operation code and directive tables are
scanned for a match with a known opcode.
Any errors detected by the Assembler are displayed before the actual line containing the
error is printed.  Errors and warnings are accumulated, and a total number of errors and
warnings is printed at the end of the source listing.  If no source listing is produced, error
messages are still displayed to indicate that the assembly process did not proceed nor-
mally.  The number of errors is returned as an exit status when the Assembler returns con-
trol to the host operating system.
1.7
  DEFINITION OF TERMS
Since the Motorola DSP architectures are different from normal microprocessors, the pro-
grammer may not be familiar with some of the terms used in this document.  The following
discussion serves to clarify some of the concepts discussed later in this manual.
The Motorola DSP architecture can have as many as five separate memory spaces re-
ferred to as the X, Y, L, P (Program), and E (EMI - Extended Memory Interface) memory
spaces. L memory space is a concatenation of X and Y data memory and is considered
by the Assembler as a superset of the X and Y memory spaces. E memory is specific to
the DSP56004 processor, and provides for different data representations for various
memory hardware configurations. The Assembler will generate object code for each
memory space, but object code can only be generated for one memory space at a time.
The memory space and address location into which the object code generated by the As-
sembler will be loaded are referred to as the load memory space and load address, re-
spectively. Because the DSP architecture allows data transfers between memory spaces,
sometimes object code is loaded into an address of one memory space but will later be
transferred to a different memory space and address before the program is run. One ex-
ample of this might be a program located in an external EPROM that will be transferred
into external program RAM before it is run. The transfer of code/data from one memory
space/address to a different memory space/address is called an overlay.
When the object code for a part of the program is generated that later will be used as an
overlay, the load memory space and load address do not correspond to the memory
space and address where the program will be run. The memory space and address loca-
tion where the code/data will be located when the program is run are referred to as the

---