Texas Instruments TMS320C54x User Manual page 4

Notational Conventions How to Use This Manual / Notational Conventions
Notational Conventions
iv
-
Reference material provides supplementary information. This section
contains technical data about the internal format and structure of COFF
object files. It discusses symbolic debugging directives that the C compiler
uses. Finally, it includes hex conversion utility examples, assembler and
linker error messages, and a glossary.
This document uses the following conventions:
-
Program listings, program examples, and interactive displays appear in a
special typeface. Examples use a bold version of the special
typeface for emphasis; interactive displays use a bold version of the
special typeface to distinguish commands that you enter from items that
the system displays (such as prompts, command output, error messages,
etc.).
Here is a sample program listing:
2 0001 2f
3 0002 32
4 0003
-
In syntax descriptions, the instruction, command, or directive is in a bold
typeface font and parameters are in an italic typeface . Portions of a syntax
that are in bold should be entered as shown; portions of a syntax that are
in italics describe the type of information that should be entered. Here is
an example of command line syntax:
abs500 filename
abs500 is a command. The command invokes the absolute lister and has
one parameter, indicated by filename . When you invoke the absolute
lister, you supply the name of the file that the absolute lister uses as input.
-
Square brackets ( [ and ] ) identify an optional parameter. If you use an
optional parameter, you specify the information within the brackets; you
don't enter the brackets themselves. This is an example of a command
that has an optional parameter:
hex500 [ –options ] filename
The hex500 command has two parameters. The first parameter, –options ,
is optional. Since options is plural, you may select several options. The
second parameter, filename , is required.
x .byte 47
z .byte 50
.text