PDF《TUSB2136/ TUSB3210/》

s ISD51 Feature, gives general information and specific pointers for the use of Keil debugging software with the TUSBxxxx. Chapter 4, File List, contains a source code listing for each C routine and header file used for debugging. Notational Conventions This document uses the following conventions. - Program listings, program examples, and interactive displays are shown in a special typeface similar to a typewriter'

s. 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:

0011 0005

0001 .field 1,

2 0012

0005 0003 .field 3,

4 0013

0005 0006 .field 6,

3 0014

0006 .even Contents iv Here is an example of a system prompt and a command that you might enter: C: csr ?a /user/ti/simuboard/utilities - 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 a directive syntax: .asect section name , address .asect is the directive. This directive has two parameters, indicated by section name and address. When you use .asect, the first parameter must be an actual section name, enclosed in double quotes;

the second parameter must be an address. - 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. Here is an example of an instruction that has an optional parameter: LALK 16?bit constant [, shift] The LALK instruction has two parameters. The first parameter, 16-bit constant, is required. The second parameter, shift, is optional. As this syntax shows, if you use the optional second parameter, you must precede it with a comma. Square brackets are also used as part of the pathname specification for VMS pathnames;

in this case, the brackets are actually part of the pathname (they are not optional). - Braces ( { and } ) indicate a list. The symbol | (read as or) separates items within the list. Here is an example of a list: This provides three choices:or *?. Unless the list is enclosed in square brackets, you must choose one item from the list. - Some directives can have a varying number of parameters. For example, the .byte directive can have up to

100 parameters. The syntax for this di- rective is: .byte value1 valuen] This syntax shows that .byte must have at least one value parameter, but you have the option of supplying additional value parameters, separated by commas. Trademarks v Related Documentation From Texas Instruments TUSB2136 Universal Serial Bus Keyboard Hub Controller Data Manual, TI literature number SLLS442 TUSB3210 Universal Serial Bus General-Purpose Device Controller Data Manual, TI literature number SLLS466 Trademarks Hyperterminal is a trademark of Hilgraeve, Incorporated. IAR Embedded Workbench is a trademark of IAR Systems AB, Sweden. Windows is a trademark of Microsoft Corporation. Other trademarks are the property of their respective owners. vi Contents vii Contents

1 Introduction 1-1

2 Debug Strings 2-1

3 In-System Debugging Using Keil'

s ISD51 Feature 3-1 3.1 Operation 3-2 3.2 Resource Requirements 3-2 3.3 Limitations 3-3