Motorola dsp assembler Reference Manual

Host-dependent Information
SunOS/SOLARIS ENVIRONMENT
MOTOROLA_DSP_ASSEMBLER_REFERENCE_MANUAL_G-3'>MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
G-3
In this example no object file is created and all errors and warnings are sent to LPT1: (e.g.
they do not appear on the console screen).  The input file is assumed to be in the current
directory.  See the IBM or Microsoft DOS manual for more information on directory struc-
ture, I/O redirection, and command paths.
G.3
  SUNOS/SOLARIS ENVIRONMENT
The Motorola DSP Assembler is delivered on the Development Tools distribution CD-rom
written in SunOS tar format.
G.3.1   Hardware Requirements
The Assembler will run on any SparcStation 2 or higher running SunOS version 4.0 or lat-
er or SOLARIS 2.5 or later. A CR-rom drive is required for installation.
G.3.2   Installation
See the readme file in the SunOS and SOLARIS directories on the CD-rom for installation
instructions.
The Assembler may be placed in any generally accessible area, usually /usr/bin or /usr/
local/bin. Be sure that it is located in a directory listing in the PATH environment variable
of those who need to use it. Also, insure that the execute access bits for the file are set
when it is copied to disk; this can be done with the chmod utility (see your User Manual
for information on chmod).
G.3.3   Source File Text
Input to the Assembler should be a standard ASCII text file with newline characters (ASCII
LF, 0AH) as line terminators.  This type of file is created by the standard Unix text editors
such as vi, and by other editors which run in the SunOS environment such as Emacs.
Assembler source code imported from other environments may need to be converted, de-
pending on the level of filtering done on the code when it was transferred to the Sun sys-
tem. Binary text files sent from, for example, a PC or compatible machine will need to have
carriage return characters (ASCII CR, 0DH) and possibly end-of-file markers (ASCII SUB,
1AH) stripped before being processed by the Assembler.
G.3.4   Invoking the Assembler
The Assembler is invoked from the shell (usually csh in SunOS) by entering the name of
the Assembler executable, 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.

---

Host-dependent Information
HP 700 Environment
G-4
DSP ASSEMBLER REFERENCE MANUAL
MOTOROLA
As an example, if the Assembler executable was located in a directory listed in the user
PATH environment variable, the following command would assemble the file myfile.asm
in the current working directory, putting the object file myfile in the objects subdirectory
and the listing file outfile into the listings subdirectory:
asm96000 -bobjects/myfile.cln -llistings/outfile.lst  myfile
Since SunOS supports standard input and output channels, in the example above any
warning or error messages would appear both in the listing file and on the standard output
(by default the terminal screen).
SunOS also supports I/O redirection, so that the Assembler listing can be sent to a file or
arbitrary output device. Assume a user wanted a list of errors from the assembly, but a full
source code listing was not required. This can be accomplished with the following Assem-
bler command line:
asm96000 -l/dev/null  test  >test.err
In this example no object file is created and all errors and warnings are routed to the file
test.err. The input file test.asm is assumed to be in the current working directory. Note
that the -L option is used to send the full Assembler listing to the null device.
G.4
  HP 700 ENVIRONMENT
The Motorola DSP Assembler is delivered a CD-rom written in tar format.
G.4.1   Hardware Requirements
The Assembler will run on any HP 700 series workstation running HP-UX.
G.4.2   Installation
See the file readme in directory hp on the installation CD-rom for installation instructions.
The Assembler may be placed in any generally accessible area, usually /usr/bin or /usr/
local/bin. Be sure that it is located in a directory listing in the PATH environment variable
of those who need to use it. Also, insure that the execute access bits for the file are set
when it is copied to disk; this can be done with the chmod utility (see your User Manual
for information on chmod).
G.4.3   Source File Text
Input to the Assembler should be a standard ASCII text file with newline characters (ASCII
LF, 0AH) as line terminators. This type of file is created by the standard Unix text editors
such as vi, and by other editors which run in the HP-UX environment such as Emacs.

---

Host-dependent Information
HP 700 Environment
MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
G-5
Assembler source code imported from other environments may need to be converted, de-
pending on the level of filtering done on the code when it was transferred to the HP sys-
tem. Binary text files sent from, for example, a PC or compatible machine will need to have
carriage return characters (ASCII CR, 0DH) and possibly end-of-file markers (ASCII SUB,
1AH) stripped before being processed by the Assembler.
G.4.4   Invoking the Assembler
The Assembler is invoked from the shell (usually ksh in HP-UX) by entering the name of
the Assembler executable, 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 executable was located in a directory listed in the user
PATH environment variable, the following command would assemble the file myfile.asm
in the current working directory, putting the object file myfile in the objects subdirectory
and the listing file outfile into the listings subdirectory:
asm96000 -bobjects/myfile.cln -llistings/outfile.lst  myfile
Since HP-UX supports standard input and output channels, in the example above any
warning or error messages would appear both in the listing file and on the standard output
(by default the terminal screen).
HP-UX also supports I/O redirection, so that the Assembler listing can be sent to a file or
arbitrary output device. Assume a user wanted a list of errors from the assembly, but a full
source code listing was not required. This can be accomplished with the following Assem-
bler command line:
asm96000 -l/dev/null  test  >test.err
In this example no object file is created and all errors and warnings are routed to the file
test.err. The input file test.asm is assumed to be in the current working directory. Note
that the -L option is used to send the full Assembler listing to the null device.

---