Motorola dsp assembler Reference Manual

Device-dependent Information
DSP56800 Information
MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
F-31
F.6.2   Macro Instructions
The DSP56800 Macros are defined in the file 56800mac, provided with the CLAS pack-
ages in the asm/ directory. These files are made available by including asm/56800mac.
For more details on including a file refer to Chapter 6.
BVC
— Branch if overflow cleared
BVS
— Branch if overflow bit set.
BPL
— Branch if plus
BMI
— Branch if minus
BR1CLR
— Branch if at least one selected bit is cleared
BR1SET
— Branch if at least one selected bit is set
BEC
— Branch if extension cleared
BES
— Branch if extension set
BLMC
— Branch if limit cleared
BLMS
— Branch if limit set
JVC
— Jump if overflow cleared
JVS
— Jump if overflow bit set.
JPL
— Jump if plus
JMI
— Jump if minus
JRCLR
— Jump if all selected bits are cleared
JRSET
— Jump if all selected bits are set
JR1SET
— Jump if at least one selected bit is set
JR1CLR
— Jump if at least one selected bit is cleared
JEC
— Jump if extension bit is cleared
JES
— Jump if extension bit is set
JLMC
— Jump if limit cleared
JLMS
— Jump if limit set
PUSH
— Push onto stack

---

Device-dependent Information
DSP56800 Information
F-32
DSP ASSEMBLER REFERENCE MANUAL
MOTOROLA
F.6.3   Register Names and Usage
The following DSP56800 register names, in either upper or lower case, cannot be used
as symbol names in an assembly language source file:
X0
Y
Y0
Y1
A
A0
A1
A2
B
B0
B1
B2
R0
R1
R2
R3
SP
N
M01
PC
MR
CCR SR
HWS OMR LA
LC
F.6.4   Condition Code Mnemonics
Following are the DSP56800 condition code mnemonics which correspond to the condi-
tional instructions based on the CCR condition codes. These tests may be used in an op-
erand comparison expression within a structured control statement (Chapter 7).
<CC>
— carry clear
<CS>
— carry set
<EQ>
— equal
<GE>
— greater than or equal
<GT>
— greater than
<HI>*
— higher than
<HS>*
— higher than or same
<LE>
— less than or equal
<LO>*
— lower than
<LS>*
— lower than or same
<LT>
— less than
<NE>
— not equal
<NN>
— not normalized
<NR>
— normalized
*Only available when CC bit set in OMR

---

MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
G-1
Appendix G
HOST-DEPENDENT INFORMATION
G.1
  INTRODUCTION
The Motorola DSP development software runs on several host machine and operating
system platforms.  The following sections give information on hardware requirements, in-
stallation, and other topics relating to specific host environments.  The descriptions below
refer directly to the DSP Assembler, but the sections on hardware requirements and in-
stallation apply similarly to the DSP linker and librarian as well.  See the appropriate chap-
ters in the DSP Linker/Librarian Reference Manual for more information on invocation
options and processing of these utilities.
G.2
  DOS/386 ENVIRONMENT
The Motorola DSP Assembler is delivered as an executable file on a CD rom. It may be
run from either a floppy drive or a hard disk, although a hard disk is recommended. The
Assembler will make use of extended memory if it is present, and will utilize available disk
space if physical memory is exhausted.
G.2.1   Hardware Requirements
The minimum hardware requirements for the Assembler in the DOS/386 environment in-
clude:
386-based PC or compatible with 80386 (or higher) CPU, 4MB of RAM, and a CD-
rom drive.
MS-DOS v3.0 or later.
Since the Assembler uses all of available memory for storage of symbols and macros, the
optimal system configuration would have at least 4 megabytes of extended memory. The
Assembler will make use of extended memory beyond 640K and may even use a virtual
memory disk file if necessary. A utility called PMINFO is supplied to provide memory re-
gion tuning and virtual file sizing for systems running under Microsoft Windows or other
DOS extended memory managers.

---

Host-dependent Information
DOS/386 Environment
G-2
DSP ASSEMBLER REFERENCE MANUAL
MOTOROLA
G.2.2   Installation
The Assembler is installed from the distribution CD-rom as part of the CLAS package. A
directory on the CD-rom is provided for each supported platform, containing a README
file containig the installation instructions
G.2.3   Source File Text
Input to the Assembler should be in a standard ASCII text file with carriage return/line feed
character pairs as line terminators. This type of file is created by most standard text editing
programs used on 386 PCs, such as the DOS-supplied editor EDIT.
Using word processing packages for creating Assembler input source files is a little more
involved, but can certainly be done. Word processing packages use special character en-
codings to indicate format and font settings, margins, indentation, and so forth. In some
cases these special encodings violate the input requirements of the Assembler, and must
be removed or changed.
Most word processing programs have a facility for converting internal-format documents
to standard ASCII text files. See Chapter 2, Input File Format, for more information on the
form and content of Assembler input files.
G.2.4   Invoking the Assembler
The Assembler is invoked from the DOS command line by entering the name of the As-
sembler executable without the extension, followed by any desired options, and finally the
names of the source files to be assembled. See Chapter 1, Running The Assembler, for
a list of options which can be included on the command line.
As an example, if the Assembler diskette was loaded in drive A, and the source file was
located on the disk in drive B, the following command at the DOS prompt would assemble
the file MYFILE.ASM, putting the object file MYFILE.CLN and the listing file OUT-
FILE.LST onto the disk in drive B as output:
A:ASM56000  -Bb:myfile.cln -Lb:outfile.lst  b:myfile
Since DOS supports standard input and output channels, in the example above any warn-
ing or error messages would appear both in the listing file and on the standard output (by
default the console screen).
DOS also supports I/O redirection, so that the Assembler listing can be sent to a file or
directly to an output device.  Given a hard disk environment where the Assembler execut-
able has been loaded into a directory BIN that is in the program search path, the following
command will assemble the source file FFT.ASM and send the listing output directly to the
Line Printer 1 device:
ASM56000  fft.dsp >LPT1:

---