TMS320C5x DSP STARTER KIT USER'S GUIDE

Notational ConventionsNotational ConventionsThis document uses the following conventions. Program listings, program examples, interactive displays, filenames, andsymbol names are shown in a special typeface similar to a typewriter’s.Examples use a bold version of the special typeface for emphasis; interactivedisplays use a bold version of the special typeface to distinguishcommands that you enter from items that the system displays (such asprompts, command output, error messages, etc.).Here is a sample program listing:00001 ——— 0a00 .ps 0a00h00002 ——— ——— .entry>>>>> ENTRY POINT SET TO 0a0000003 0a00 8b88 mar *,AR000004 0a01 8ba9 loop mar *+, AR1Here is an example of a system prompt and a command that you mightenter:C:> dska testfile.asm In syntax descriptions, the instruction, command, or directive is in a bold facefont and parameters are in an italics. Portions of a syntax that are in boldshould be entered as shown; portions of a syntax that are in italics describethe type of information that should be entered. Syntax that is entered on acommand is centered in a bounded box. Syntax that is used in a text file isleft-justified in an unbounded box. Here is an example of a directive syntax:.include”filename”.include is the directive. This directive has one parameter, indicated by filename.When you use .include, the parameter must be an actual filename,enclosed in double quotes. Square brackets ( [ and ] ) identify an optional parameter. If you use anoptional parameter, you specify the information within the brackets; youdon’t enter the brackets themselves. Here’s an example of an instructionthat has an optional parameter:LACC16-bit constant [, shift]iv