HP 68302 User Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Measuring Instruments
  5. 68302
  6. User manual

HP 68302 User Manual

Hide thumbs Also See for 68302:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
Table of Contents

Advertisement

Quick Links

Download this manual
User's Guide
Real-Time C Debugger for
68302

Advertisement

Table of Contents
loading

Related Manuals for HP 68302

Summary of Contents for HP 68302

  • Page 1 User’s Guide Real-Time C Debugger for 68302...
  • Page 2 MS-DOS(R) is a U.S. registered trademark of Microsoft Corporation. HP-UX 9.* and 10.0 for HP 9000 Series 700 and 800 computers are X/Open Company UNIX 93 branded products. TrueType(TM) is a U.S. trademark of Apple Computer, Inc.
  • Page 3 Printing History New editions are complete revisions of the manual. The date on the title page changes only when a new edition is published. A software code may be printed before the date; this indicates the version level of the software product at the time the manual was issued. Many product updates and fixes do not require manual changes, and manual corrections may be done without accompanying product changes.
  • Page 4 The debugger controls HP 64700 emulators and analyzers either on the local area network (LAN) or connected to a personal computer with an RS-232C interface or the HP 64037 RS-422 interface. It takes full advantage of the emulator’s real-time capabilities to allow effective debug of C programs while running in real-time.
  • Page 5 • You can set breakpoints in the program and define macros (which are collections of debugger commands) that execute when the breakpoint is hit. Break macros provide for effective debugging without repeated command entry. You can display and modify processor resources •...
  • Page 6 In This Book This book documents the Real-Time C Debugger for 68302. It is organized into five parts whose chapters are described below. Part 1. Quick Start Guide Chapter 1 quickly shows you how to use the debugger. Part 2. User’s Guide Chapter 2 shows you how to use the debugger interface.

  • Page 7: Table Of Contents

    Contents Part 1 Quick Start Guide Getting Started Step 1. Start the debugger Step 2. Adjust the fonts and window size Step 3. Set the reset value for the supervisor stack pointer Step 4. Map memory for the demo program Step 5.
  • Page 8 Contents Part 2 User’s Guide Using the Debugger Interface How the Debugger Uses the Clipboard Debugger Function Key Definitions Starting and Exiting the Debugger To start the debugger To exit the debugger To create an icon for a different emulator Working with Debugger Windows To open debugger windows To copy window contents to the list file...
  • Page 9 Contents Configuring the Emulator Setting the Hardware Options To select the emulator clock source To enable or disable the target BR and BGACK signals To enable or disable the target BERR signal To enable or disable target DTACK for emulation memory accesses To enable or disable target system interrupts To enable or disable break on writes to ROM To specify the TRAP instruction for breakpoints...
  • Page 10 Step 5. Decide whether to use the foreground monitor Step 6. Set up the emulator for the foreground monitor Step 7. If you use the 68302 built-in DRAM refresh Step 8. Set up the DTACK signals Step 9. If emulator status shows HALTED Step 10.
  • Page 11 Contents Displaying Symbol Information To display program module information To display function information To display external symbol information To display local symbol information To display global assembler symbol information To display local assembler symbol information To create a user-defined symbol To display user-defined symbol information To delete a user-defined symbol To display the symbols containing the specified string...
  • Page 12 Contents Displaying and Editing Memory To display memory To edit memory To copy memory to a different location To copy target system memory into emulation memory To modify a range of memory with a value To search memory for a value or string Displaying and Editing I/O Locations To display I/O locations To edit an I/O location...
  • Page 13 Contents Part 3 Reference Command File and Macro Command Summary WAIT Command Dialog Box Expressions in Commands Numeric Constants Symbols Function Codes C Operators Menu Bar Commands File→Load Object... (ALT, F, L) File→Command Log→Log File Name... (ALT, F, C, N) File→Command Log→Logging ON (ALT, F, C, O) File→Command Log→Logging OFF (ALT, F, C, F) File→Run Cmd File...
  • Page 14 Contents Breakpoint→Delete Macro (ALT, B, L) Breakpoint→Edit... (ALT, B, E) Variable→Edit... (ALT, V, E) Variable Modify Dialog Box Trace→Function Flow (ALT, T, F) Trace→Function Caller... (ALT, T, C) Trace→Function Statement... (ALT, T, S) Trace→Variable Access... (ALT, T, V) Trace→Variable Break... (ALT, T, B) Trace→Edit...
  • Page 15 Contents Settings→Tabstops... (ALT, S, T) Settings→Symbols→Case Sensitive→ON (ALT, S, S, C, O) Settings→Symbols→Case Sensitive→OFF (ALT, S, S, C, F) Settings→Extended→Trace Cycles→User (ALT, S, X, T, U) Settings→Extended→Trace Cycles→Monitor (ALT, S, X, T, M) Settings→Extended→Trace Cycles→Both (ALT, S, X, T, B) Settings→Extended→Load Error Abort→ON (ALT, S, X, L, O) Settings→Extended→Load Error Abort→OFF (ALT, S, X, L, F) Settings→Extended→Source Path Query→ON (ALT, S, X, S, O)
  • Page 16 Contents Memory Window Commands Display→Linear (ALT, -, D, L) Display→Block (ALT, -, D, B) Display→Byte (ALT, -, D, Y) Display→16 Bit (ALT, -, D, 1) Display→32 Bit (ALT, -, D, 3) Search... (ALT, -, R) Utilities→Copy... (ALT, -, U, C) Utilities→Fill...
  • Page 17 Contents User defined→Add... (ALT, -, U, A) User defined→Delete (ALT, -, U, D) User defined→Delete All (ALT, -, U, L) Trace Window Commands Display→Mixed Mode (ALT, -, D, M) Display→Source Only (ALT, -, D, S) Display→Bus Cycle Only (ALT, -, D, C) Display→Count→Absolute (ALT, -, D, C, A) Display→Count→Relative (ALT, -, D, C, R) Copy→Window (ALT, -, P, W)
  • Page 18 General RS-422 communications error HP 64700 locked by another user HP 64700 not responding Incorrect DLL version Incorrect LAN Address (HP-ARPA, Windows for Workgroups) Incorrect LAN Address (Novell) Incorrect LAN Address (WINSOCK) Internal error in communications driver Internal error in Windows...
  • Page 19 Contents Part 4 Concept Guide 13 Concepts Debugger Windows The BackTrace Window The Button Window Device Regs Window Device Register Dialogs The Expression Window The I/O Window The Memory Window The Register Window The Source Window The Status Window The Symbol Window The Trace Window The WatchPoint Window Compiler/Assembler Specifications...
  • Page 20 Part 5 Installation Guide 14 Installing the Debugger Requirements Before Installing the Debugger Step 1. Connect the HP 64700 to the PC To connect via RS-232 To connect via LAN To connect via RS-422 If you cannot verify RS-232 communication If you cannot verify LAN communication Step 2.

  • Page 21: Part 1 Quick Start Guide

    Part 1 Quick Start Guide A few task instructions to help you get comfortable.
  • Page 22 Part 1...

  • Page 23: Getting Started

    Getting Started...
  • Page 24 Exit the debugger. Demo Programs Demo programs are included with the Real-Time C Debugger in the C:\HP\RTC\M302\DEMO directory (if C:\HP\RTC\M302 was the installation path chosen when installing the debugger software). Subdirectories exist for the SAMPLE demo program, which is a simple C...

  • Page 25: Step 1. Start The Debugger

    This tutorial shows you how to perform some measurements on the SAMPLE demo program. Step 1. Start the debugger • Open the HP Real-Time C Debugger group box and double-click the 68302 debugger icon. Choose the File→Run (ALT, F, R) command in the Windows Program Manager.

  • Page 26: Step 2. Adjust The Fonts And Window Size

    Chapter 1: Getting Started Step 2. Adjust the fonts and window size Step 2. Adjust the fonts and window size The first time RTC is used, a default window and font size is used. This may not be the best for your display. You may change the font type and size with the Settings→Font...

  • Page 27: Step 3. Set The Reset Value For The Supervisor Stack Pointer

    Choose the Settings→Emulator Config→Monitor... (ALT, S, E, O) command. Enter "8000" in the Reset Value for Supervisor Stack text box. Choose the OK button. The 68302 emulator requires the supervisor stack pointer to be set to an even address in emulation RAM or in target system RAM.
  • Page 28 Chapter 1: Getting Started Step 3. Set the reset value for the supervisor stack pointer When you break the emulation processor from the EMULATION RESET state into the RUNNING IN MONITOR state, the supervisor stack pointer is set to the address specified. You can also set the supervisor stack pointer by modifying the SSP register in the Register window.

  • Page 29: Step 4. Map Memory For The Demo Program

    (at 0F0H and 0F4H), the exception vector table (0 through 3FFH) should be mapped as emulation RAM. The internal memory space of the 68302 must be mapped as target RAM. Choose the Settings→Emulator Config→Memory Map... (ALT, S, E, M) command.
  • Page 30 Step 4. Map memory for the demo program Select "tram" in the Default group box. This maps all memory ranges not listed in the Current Map as target system RAM. The 68302 internal memory space is not listed in the Current Map; therefore, it is mapped as target system RAM.

  • Page 31: Step 5. Load The Demo Program

    Step 5. Load the demo program Choose the File→Load Object... (ALT, F, L) command. Choose the Browse button and select the sample program object file, C:\HP\RTC\M302\DEMO\SAMPLE\SAMPLE.X (if C:\HP\RTC\M302 was the installation path chosen when installing the debugger software). Choose the OK button in the Object File Name dialog box.

  • Page 32: Step 6. Display The Source File

    Chapter 1: Getting Started Step 6. Display the source file Step 6. Display the source file To display the sample.c source file starting from the main function: If the Source window is not open, double-click on the Source window icon to open the window. Or, choose the Window→Source command.

  • Page 33: Step 7. Set A Breakpoint

    Chapter 1: Getting Started Step 7. Set a breakpoint Step 7. Set a breakpoint To set a breakpoint on line 22 in sample.c: Cursor-select line 22 (that is, move the mouse pointer over line 22 and click the left mouse button). Choose the Breakpoint→Set at Cursor (ALT, B, S) command.

  • Page 34: Step 8. Run The Demo Program

    Chapter 1: Getting Started Step 8. Run the demo program Step 8. Run the demo program To run the demo program from the transfer address: Choose the Execution→Reset (ALT, E, E) command followed by the Execution→Break (ALT, E, B) command to initialize the supervisor stack pointer.

  • Page 35: Step 9. Delete The Breakpoint

    Chapter 1: Getting Started Step 9. Delete the breakpoint Step 9. Delete the breakpoint To delete the breakpoint set on line 22: Cursor-select line 22. Choose the Breakpoint→Delete at Cursor (ALT, B, D) command. The "BP" marker disappears in the Source window.

  • Page 36: Step 10. Single-Step One Line

    Chapter 1: Getting Started Step 10. Single-step one line Step 10. Single-step one line To single-step the demo program from the current program counter: • Choose the Execution→Single Step (ALT, E, N) command. Or, press the F2 key. Notice the C statement executed and the program counter is at the "convert" function.

  • Page 37: Step 11. Single-Step 10 Lines

    Chapter 1: Getting Started Step 11. Single-step 10 lines Step 11. Single-step 10 lines To single-step 10 consecutive executable statements from the current PC line: Choose the Execution→Step... (ALT, E, S) command. Select the Current PC option. Enter "10" in the Count text box. Choose the Step button.

  • Page 38: Step 12. Display A Variable

    Chapter 1: Getting Started Step 12. Display a variable Step 12. Display a variable To display the contents of auto variable "*mes": Drag "*mes" on line 45 in the Source window until it is highlighted. Choose the Variable→Edit... (ALT, V, E) command. The Variable text box displays "*mes".

  • Page 39: Step 13. Edit A Variable

    Chapter 1: Getting Started Step 13. Edit a variable Step 13. Edit a variable To edit the contents of variable "*mes": In the Variable Edit dialog box, choose the Modify button. Enter "41" in the Value text box. Choose the OK button. Notice the contents of the variable in the Value list box has changed to "41".

  • Page 40: Step 14. Monitor A Variable In The Watchpoint Window

    Chapter 1: Getting Started Step 14. Monitor a variable in the WatchPoint window Step 14. Monitor a variable in the WatchPoint window The WatchPoint window lets you define a set of variables that may be looked at and modified often. For these types of variables, using the WatchPoint window is more convenient than using the Variable→Edit...

  • Page 41: Step 15. Run Until Return From Current Function

    Chapter 1: Getting Started Step 15. Run until return from current function Step 15. Run until return from current function To execute the program until "convert_case" (the current PC function) returns to its caller: Choose the Execution→Run to Caller (ALT, E, T) command. The program executes until the line that called "convert_case".

  • Page 42: Step 16. Step Over A Function

    Chapter 1: Getting Started Step 16. Step over a function Step 16. Step over a function To step over "change_status": • Choose the Execution→Step Over (ALT, E, O) command. Or, press the F3 key. The "change_status" function executes, and the program counter indicates line 41.

  • Page 43: Step 17. Run The Program To A Specified Line

    Chapter 1: Getting Started Step 17. Run the program to a specified line Step 17. Run the program to a specified line To execute the demo program to the first line of "next_message": Cursor-select line 63. Choose the Execution→Run to Cursor (ALT, E, C) command. The program executes and stops immediately before line 63.

  • Page 44: Step 18. Display Register Contents

    Chapter 1: Getting Started Step 18. Display register contents Step 18. Display register contents Choose the Window→Register command. The Register window opens and displays the register contents. The display is updated periodically. To see the effects of preventing monitor intrusion (running in real-time mode), choose the RealTime→Monitor Intrusion→Disallowed (ALT, R, T, D) command.
  • Page 45 Chapter 1: Getting Started Step 18. Display register contents To run the program, choose the Execution→Run (ALT, E, U) command. Or, press the F5 key. Notice that register contents are replaced with "----" in the display. This shows the debugger cannot update the register display. In order for the emulator to update its register display, the emulation monitor must interrupt target program execution while it reads the registers.

  • Page 46: Step 19. Trace Function Flow

    Chapter 1: Getting Started Step 19. Trace function flow Step 19. Trace function flow • Choose the Trace→Function Flow (ALT, T, F) command. The Trace window becomes active and displays execution flow as shown below. The command traces, and stores in trace memory, only the entry points to functions.

  • Page 47: Step 20. Trace A Function's Callers

    Chapter 1: Getting Started Step 20. Trace a function’s callers Step 20. Trace a function’s callers To trace the caller of "next_message": Double-click "next_message" in the Trace window or on line 61 in the Source window. Choose the Trace→Function Caller... (ALT, T, C) command. Choose the OK button.
  • Page 48 Chapter 1: Getting Started Step 20. Trace a function’s callers statement of "next_message" is prefetched after "change_status", these states are also included in the trace.

  • Page 49: Step 21. Trace Access To A Variable

    Chapter 1: Getting Started Step 21. Trace access to a variable Step 21. Trace access to a variable To trace access to variable "message_id": Double-click "message_id" in the Trace window or on line 22 in the Source window. Choose the Trace→Variable Access... (ALT, T, V) command. Choose the OK button.

  • Page 50: Step 22. Exit The Debugger

    Chapter 1: Getting Started Step 22. Exit the debugger Step 22. Exit the debugger Choose the File→Exit (ALT, F, X) command. Choose the OK button. This will end your Real-Time C Debugger session.
  • Page 51 Part 2 User’s Guide A complete set of task instructions and problem-solving guidelines, with a few basic concepts.
  • Page 52 Part 2...

  • Page 53: Using The Debugger Interface

    Using the Debugger Interface...
  • Page 54 Using the Debugger Interface This chapter contains general information about using the debugger interface. • How the Debugger Uses the Clipboard • Debugger Function Key Definitions • Starting and Exiting the Debugger • Working with Debugger Windows • Using Command Files...

  • Page 55: How The Debugger Uses The Clipboard

    Chapter 2: Using the Debugger Interface How the Debugger Uses the Clipboard How the Debugger Uses the Clipboard Whenever something is selected with the standard windows double-click, it is placed on the clipboard. The clipboard can be pasted into selected fields by clicking the right mouse button.

  • Page 56: Debugger Function Key Definitions

    Chapter 2: Using the Debugger Interface Debugger Function Key Definitions Debugger Function Key Definitions Accesses context sensitive help. Context sensitive help is available for windows, dialog boxes, and menu items (with Ctrl+F1). Executes a single source line from the current program counter address (or a single instruction if disassembled mnemonics are mixed with source lines in the Source window).

  • Page 57: Starting And Exiting The Debugger

    Choose the File→Run (ALT, F, R) command in the Windows Program Manager. Enter the debugger filename, C:\HP\RTC\M302\B3621.EXE (if C:\HP\RTC\M302 was the installation path chosen when installing the debugger software). Choose the OK button. You can execute a command file when starting the debugger by using the...

  • Page 58: To Exit The Debugger

    <Connectname> should identify the emulator for the type of transport. For example, if the HP-ARPA transport is used, <connectname> should be the hostname or IP address of the HP 64700; if the RS232C transport is used, <connectname> should be COM1, COM2, etc.
  • Page 59 Chapter 2: Using the Debugger Interface Starting and Exiting the Debugger In the Working Directory text box, enter the directory that contains the debugger program (for example, C:\HP\RTC\M302). Choose the OK button.

  • Page 60: Working With Debugger Windows

    Chapter 2: Using the Debugger Interface Working with Debugger Windows Working with Debugger Windows This section shows you how: • To open debugger windows • To copy window contents to the list file • To change the list file destination •...

  • Page 61: To Copy Window Contents To The List File

    Chapter 2: Using the Debugger Interface Working with Debugger Windows To copy window contents to the list file • From the window’s control menu, choose the Copy→Windows (ALT, -, P, W) command. The information shown in the window is copied to the destination list file. You can change the name of the destination list file by choosing the Copy→Destination...

  • Page 62: To Change The Debugger Window Fonts

    Chapter 2: Using the Debugger Interface Working with Debugger Windows To change the debugger window fonts Choose the Settings→Font (ALT, S, F) command. Select the font, font style, and size. Notice that the Sample box previews the selected font. Choose the OK button. To set tab stops in the Source window Choose the Settings→Tabstops (ALT, S, T) command.

  • Page 63: To Set Colors In The Source Window

    To set colors in the Source window Exit the RTC interface and find the initialization file (B3621.INI). It should be in the directory where you installed the RTC product (C:\HP\RTC\, by default). Edit the initialization file to find the "color" entry. You will see: [Color] ColorMode=ON|OFF ColorPc=<color>...

  • Page 64: Using Command Files

    Chapter 2: Using the Debugger Interface Using Command Files Using Command Files This section shows you how: • To create a command file • To execute a command file • To create buttons that execute command files A command file is an ASCII text file containing one or more debugger commands.

  • Page 65: To Execute A Command File

    Chapter 2: Using the Debugger Interface Using Command Files To execute a command file Choose the File→Run Cmd File... (ALT, F, R) command. Select the command file to be executed. Choose the Execute button. You can execute command files that have been created by logging commands. Also, emulator configurations can be restored by executing the associated command file.

  • Page 66: To Create Buttons That Execute Command Files

    Chapter 2: Using the Debugger Interface Using Command Files To create buttons that execute command files Activate the Button window by clicking on the Button window icon or by choosing the Window→Button command. From the Button window’s control menu, choose the Edit... (ALT, -, E) command.

  • Page 67: Configuring The Emulator

    Configuring the Emulator...
  • Page 68 Configuring the Emulator This chapter contains information about configuring the emulator. • Setting the Hardware Options • Mapping Memory • Selecting the Type of Monitor • Setting Up the BNC Port • Saving and Loading Configurations • Setting the Real-Time Options...

  • Page 69: Setting The Hardware Options

    Chapter 3: Configuring the Emulator Setting the Hardware Options Setting the Hardware Options This section shows you how: • To select the emulator clock source • To enable or disable the target BR and BGACK signals • To enable or disable the target BERR signal •...

  • Page 70: To Select The Emulator Clock Source

    When the external clock has been selected, the emulator will operate using the clock driven to the emulator from the target system. The maximum clock speed with the HP 64746 emulator is 16.67 MHz. Note Changing the clock source selection resets the emulator.

  • Page 71: To Enable Or Disable The Target Berr Signal

    /BG; the address, data, and control signals will not be placed in a tristate condition. Internal 68302 DMA can happen regardless of the answer to this question. The /BGACK signal will always be active on internal DMA operations.

  • Page 72: To Enable Or Disable Target Dtack For Emulation Memory Accesses

    Choose the OK button to exit the Emulator Config dialog box. The 68302 can generate an internal /DTACK. Internal DTACK can be generated by chip selects or internal processor cycles. The source of the /DTACK for chip selects in the emulator is determined by the chip select configuration questions.

  • Page 73: To Enable Or Disable Target System Interrupts

    Chapter 3: Configuring the Emulator Setting the Hardware Options To enable or disable target system interrupts Choose the Settings→Emulator Config→Hardware... (ALT, S, E, H) command. Select or deselect the Enable target INT signal check box. Choose the OK button to exit the Emulator Config dialog box. When the check box is selected, the emulator detects interrupts from the target system while running in the user program or foreground monitor.

  • Page 74: To Specify The Trap Instruction For Breakpoints

    Chapter 3: Configuring the Emulator Setting the Hardware Options To specify the TRAP instruction for breakpoints Choose the Settings→Emulator Config→Hardware... (ALT, S, E, H) command. Enter a number from 0 to 0fh in the "TRAP number for Software break" text box. Choose the OK button to exit the Emulator Config dialog box.

  • Page 75: To Specify The Target Memory Access Size

    Chapter 3: Configuring the Emulator Setting the Hardware Options When the emulator is operating in-circuit, the BUSW pin selects the data bus width. To specify the target memory access size Choose the Settings→Emulator Config→Hardware... (ALT, S, E, H) command. Select either the 8 bits or 16 bits option for the Target Memory Access Size.

  • Page 76: To Select /Iack7 Pin Operation

    Chapter 3: Configuring the Emulator Setting the Hardware Options If external is selected, an active level on /CS[0-3] causes the emulator to drive /DTACK to the processor, from either the target system or the emulator based on the Emulation Memory Use Target DTACK setting. To select /IACK7 pin operation Choose the Settings→Emulator Config→Hardware...

  • Page 77: To Select The Normal Or Dedicated Interrupt Mode

    This options tells the emulator which interrupt mode the 68302 is programmed for -- it does not actually program the 68302 interrupt mode. If the 68302 is not in the selected mode when a break is attempted, the break will either fail or lead to unexpected interrupts.

  • Page 78: To Select Level Or Edge Sensitivity For /Irq7

    Chapter 3: Configuring the Emulator Setting the Hardware Options To select level or edge sensitivity for /IRQ7 Choose the Settings→Emulator Config→Hardware... (ALT, S, E, H) command. Select either the level or edge option for the /IRQ7 mode. Choose the OK button to exit the Emulator Config dialog box. You can only select level or edge sensitivity for /IRQ7 when the dedicated interrupt mode is selected.

  • Page 79: Mapping Memory

    Chapter 3: Configuring the Emulator Mapping Memory Mapping Memory This section shows you how: • To map memory To map memory Choose the Settings→Emulator Config→Memory Map... (ALT, S, E, M) command. Specify the starting address in the Start text box. Specify the end address in the End text box.
  • Page 80 For non-mapped memory areas, select any of the memory types in the Default option box. Note that the internal memory space of the 68302 must be mapped as target RAM. The BAR and SCR registers (located at 0F0H and 0F4H in the exception vector table) may be mapped as emulation RAM, but you should use the register commands to modify or examine these locations.
  • Page 81 Chapter 3: Configuring the Emulator Mapping Memory Example To map addresses 6000h through 0ffffh as an emulation RAM having "X" function code, specify the mapping term as shown below. Choose the Apply button to register the current map term. Then, choose the Close button to quit mapping.

  • Page 82: Selecting The Type Of Monitor

    Chapter 3: Configuring the Emulator Selecting the Type of Monitor Selecting the Type of Monitor This section shows you how: • To select the background monitor • To select the foreground monitor Refer to "Monitor Program Options" in the "Concepts" part for a description of emulation monitors and the advantages and disadvantages of using background or foreground emulation monitors.

  • Page 83: To Select The Background Monitor

    Chapter 3: Configuring the Emulator Selecting the Type of Monitor To select the background monitor Choose the Settings→Emulator Config→Monitor... (ALT, S, E, O) command. Select the Background option. Specify whether background monitor cycles should be driven to the target system by either selecting or deselecting the Drive Monitor Cycles to Target check box.

  • Page 84: To Select The Foreground Monitor

    Chapter 3: Configuring the Emulator Selecting the Type of Monitor To select the foreground monitor Edit the foreground monitor program source file to define its base address. Assemble and link the foreground monitor. Choose the Settings→Emulator Config→Monitor... (ALT, S, E, O) command.
  • Page 85 Chapter 3: Configuring the Emulator Selecting the Type of Monitor Load the foreground monitor by choosing the Execution→Reset (ALT, E, E) command or by choosing the File→Load Object... (ALT, F, L) command and entering the name of the foreground monitor object file.

  • Page 86: Setting Up The Bnc Port

    Choose the Settings→BNC→Outputs Analyzer Trigger (ALT, S, B, O) command. The HP 64700 Series emulators have a BNC port for connection with external devices such as logic analyzers or oscilloscopes. This command enables the trigger signal from the internal analyzer to be fed to external devices.

  • Page 87: Saving And Loading Configurations

    Chapter 3: Configuring the Emulator Saving and Loading Configurations Saving and Loading Configurations This section shows you how: • To save the current emulator configuration • To load an emulator configuration To save the current emulator configuration Choose the File→Save Emulator Config... (ALT, F, V) command. In the file selection dialog box, enter the name of the file to which the emulator configuration will be saved.
  • Page 88 Chapter 3: Configuring the Emulator Saving and Loading Configurations To load an emulator configuration Choose the File→Load Emulator Config... (ALT, F, E) command. Select the name of the emulator configuration command file to load from the file selection dialog box. Choose the OK button.
  • Page 89 Chapter 3: Configuring the Emulator Setting the Real-Time Options Setting the Real-Time Options This section shows you how: • To allow or deny monitor intrusion • To turn polling ON or OFF The monitor program is executed by the emulation microprocessor when target system memory, memory-mapped I/O, and microprocessor registers are displayed or edited.
  • Page 90 Chapter 3: Configuring the Emulator Setting the Real-Time Options To allow or deny monitor intrusion • To deny monitor intrusion, choose the RealTime→Monitor Intrusion→Disallowed (ALT, R, T, D) command. • To allow monitor intrusion, choose the RealTime→Monitor Intrusion→Allowed (ALT, R, T, A) command. When you deny monitor intrusion, any debugger command that may interrupt a running user program is prevented.
  • Page 91 Chapter 3: Configuring the Emulator Setting the Real-Time Options To turn polling ON or OFF • To turn I/O window polling ON or OFF, choose the RealTime→I/O Polling→ON (ALT, R, I, O) or RealTime→I/O Polling→OFF (ALT, R, I, F) command. •...
  • Page 93 Plugging the Emulator into Target Systems...
  • Page 94 Plugging the Emulator into Target Systems This chapter contains information about plugging the emulator into target systems and configuring the emulator so that it operates correctly. • Connecting the Emulator Probe • Configuring the Emulator for In-Circuit Operation...
  • Page 95 (that is, an extra PGA socket) between the probe and the target. PGA sockets are available from HP as HP part number 1200-1318. A MacKenzie Technology PGA-100M-003B1-1324 socket should also be suitable. To prevent emulator and probe components from being damaged by static electricity, store and use the emulator in a place resistant to static electricity.
  • Page 96 (Note that pin "A1" of the PGA matrix is signal "A14". Pin numbers DO NOT correspond to signal numbers for the 68302.) Turn ON power to the emulator. Turn ON power to the target system.
  • Page 97 Chapter 4: Plugging the Emulator into Target Systems Connecting the Emulator Probe Turning ON power to the emulator before turning ON power to the target system will prevent damage to sensitive components in the target system. Start the debugger.
  • Page 98 Step 11. Check your DTACK pullup resistor! • If you have problems Step 1. Understand the important concepts There are a few basic concepts related to 68302 emulation that should be understood before you begin. Understanding these concepts will help you avoid the common startup problems.
  • Page 99 An emulator configuration option is used to indicate which mode the 68302 will be in. If the 68302 is not in that mode when a break is attempted, the break will either fail or lead to unexpected interrupts.
  • Page 100 Freezing the watchdog timer will be discussed later. On-Chip Locations Most of the special features of the 68302 are controlled via a 4 Kbyte block of on-chip locations (RAM and special registers). The address of that 4 Kbyte block is determined by the value written to the BAR.
  • Page 101 Chapter 4: Plugging the Emulator into Target Systems Configuring the Emulator for In-Circuit Operation Method 1: Using a Command File to Setup Chip-Selects Use a series of commands or a command file that modifies the registers to the values you will need. For example, here is a command file that sets up CS0 and CS1.
  • Page 102 68302 emulator. Before you can successfully emulate in this mode, it is important that you understand how the 68302 uses chip-selects. When you enter memory map terms in your configuration, you will notice that you enter all address ranges without the option to qualify a specific range with a chip-select number.
  • Page 103 Chapter 4: Plugging the Emulator into Target Systems Configuring the Emulator for In-Circuit Operation memory ranges you map respond based on the value on the address bus (and optionally the function code). The chip-select signals are not used by the emulator to decode memory map terms.
  • Page 104 Chapter 4: Plugging the Emulator into Target Systems Configuring the Emulator for In-Circuit Operation ; A2 is used to point to where ROM WILL be. MOVEA.L #SWITCHED,A2 MOVEA.L A0,A1 MOVE.L #$317CA001,(A1)+ MOVE.L #$0834317C,(A1)+ MOVE.L #$C8010830,(A1)+ MOVE.W #$4ED2,(A1)+ (A0) SWITCHED ; it’s switched now!!!!!!! MOVE.L 0,D0 ;...
  • Page 105 Method 1: Using a Command File to Set the Interrupt Mode Use a series of commands or a command file that modifies the GIMR to force the 68302 to be in dedicated mode. For example, here is a command file that sets up the GIMR for dedicated mode:...
  • Page 106 GIMR register because the location of that register is calculated based on the value in the BAR. Note that doing a break when the 68302 is in a reset state does not require a level 7 interrupt, and therefore will work regardless of the interrupt mode setting.
  • Page 107 Chapter 4: Plugging the Emulator into Target Systems Configuring the Emulator for In-Circuit Operation When the emulator breaks into the monitor the 68302 will be in dedicated mode. You can now use the step and break command. Note that if you are just starting to debug your initialization code, and would like to step through each of your startup instructions, you should use Method Step 5.
  • Page 108 Chapter 4: Plugging the Emulator into Target Systems Configuring the Emulator for In-Circuit Operation this is not necessary. The 68302 SCR register contains a bit, which when set will suspend the watchdog timer whenever the FRZ pin is asserted. This bit is called "FRZW".
  • Page 109 Chapter 4: Plugging the Emulator into Target Systems Configuring the Emulator for In-Circuit Operation Note If you are using 1 Mbyte SIMMs in your 68302 emulator, you MUST locate the monitor on an 8 Kbyte boundary; otherwise, locate the the monitor on a 2 Kbyte boundary.
  • Page 110 Make sure that the address range 0FFF000H through 0FFFFFFH is mapped as "target RAM". This is important because the emulator will attempt to access the on-chip locations of the 68302 upon entering the monitor. It uses the default address for the BAR, placing the internal register section at address 0FFF000H.
  • Page 111 ROMs. If You Need Interrupts Serviced While Running in the Monitor By default, the foreground monitor leaves the Interrupt Mask of the 68302 at 7 after a "break" into the monitor. If you wish to have any interrupts other than level 7 interrupts serviced while the monitor is running, you must modify the monitor source code.
  • Page 112 DRAM with no additional target hardware. If your target system does not rely on this built-in feature of the 68302 you can skip this step. If you do use the built-in DRAM refresh feature, you must use the foreground monitor;...
  • Page 113 "internal"; otherwise, select "external". You may notice that the default for CS0 is "internal" and all others "external". This is because the 68302 CS0 is configured to generate an internal DTACK by default.
  • Page 114 The 68302 will halt itself if a double-bus fault occurs. Only a target system reset, or emulator reset command will clear the HALTED emulator status.
  • Page 115 Chapter 4: Plugging the Emulator into Target Systems Configuring the Emulator for In-Circuit Operation DC.L $440000 ; Stack begins at $43FFFC DC.L $400 ; Reset initialization code $400 MOVE.W #$0800,$F2 ; Set up the BAR for $800XXX MOVEA.L #$800000,A0 MOVE.W #$3F02,($832,A0) ;...
  • Page 116 (BERR). state -1 Because of the bus error in the previous cycle the 68302 will immediately begin to process a bus error exception. The first thing it will try to do is write the low word of the program counter value to the stack.
  • Page 117 Configuring the Emulator for In-Circuit Operation Step 11. Check your DTACK pullup resistor! It wouldn’t be fair to solve all these 68302 plug-in problems and not give the hardware engineer a chance to help out, so there’s one last thing you should check before you begin.
  • Page 118 Chapter 4: Plugging the Emulator into Target Systems Configuring the Emulator for In-Circuit Operation...
  • Page 119 Problem: You get "ERROR: Break failed" when trying to step. Cause: You have configured the emulator for dedicated mode interrupts but have not put the 68302 in dedicated mode by modifying the GIMR and setting the most significant bit. Or, the instruction that you single-stepped resulted in a double-bus fault and the processor is now halted.
  • Page 120 Chapter 4: Plugging the Emulator into Target Systems Configuring the Emulator for In-Circuit Operation Problem: You get "ERROR: BERR during background access to supervisor stack" when you first try to step or run. Cause: This problem occurs when the emulator attempts to modify the stack so that your run or step command will begin from the proper address.
  • Page 121 By using the trace analyzer, you can capture a real-time log of SCC-related bus activity. Problem: You are using the DRAM refresh controller of the 68302, but when you break into the monitor, the values in your DRAM become corrupted.
  • Page 122 Chapter 4: Plugging the Emulator into Target Systems Configuring the Emulator for In-Circuit Operation Problem: The emulator status shows HALTED Cause: A double-bus fault has occurred, or the target system has asserted the HLT pin. This is almost always caused by a double-bus fault.
  • Page 123 Debugging Programs...
  • Page 124 Debugging Programs This chapter contains information on loading and debugging programs. • Loading and Displaying Programs • Displaying Symbol Information • Stepping, Running, and Stopping the Program • Using Breakpoints and Break Macros • Displaying and Editing Variables • Displaying and Editing Memory •...
  • Page 125 Choose the Load button to load the program. Programs are only loaded into the memory ranges mapped with the same function code. With this command, you can load any IEEE-695 object file created with any of the Microtec or HP programming tools for 68000.
  • Page 126 Chapter 5: Debugging Programs Loading and Displaying Programs To display source code only Position the cursor on the starting line to be displayed. From the Source window control menu, choose the Display→Source Only (ALT, -, D, S) command. The Source window may be toggled between the C source only display and the C source/mnemonic mixed display.
  • Page 127 Chapter 5: Debugging Programs Loading and Displaying Programs Example C Source/Mnemonic Mode Display To display source files by their names Make the Source window the active window, and choose the Display→Select Source... (ALT, -, D, L) command from the Source window’s control menu.
  • Page 128 Chapter 5: Debugging Programs Loading and Displaying Programs To specify source file directories Make the Source window the active window, and choose the Display→Select Source... (ALT, -, D, L) command from the Source window’s control menu. Choose the Directory... button. Enter the directory name in the Directory text box.
  • Page 129 Chapter 5: Debugging Programs Loading and Displaying Programs To search for strings in the source files From the Source window’s control menu, choose the Search→String... (ALT, -, R, S) command. Type or paste the string into the String text box. Select whether the search should be case sensitive.
  • Page 130 Chapter 5: Debugging Programs Displaying Symbol Information Displaying Symbol Information This section shows you how: • To display program module information • To display function information • To display external symbol information • To display local symbol information • To display global assembler symbol information •...
  • Page 131 Chapter 5: Debugging Programs Displaying Symbol Information To display program module information • From the Symbol window’s control menu, choose the Display→Modules (ALT, -, D, M) command. To display function information • From the Symbol window’s control menu, choose the Display→Functions (ALT, -, D, F) command.
  • Page 132 Chapter 5: Debugging Programs Displaying Symbol Information To display external symbol information • From the Symbol window’s control menu, choose the Display→Externals (ALT, -, D, E) command. The name, type, and address of the global variables in the program are displayed.
  • Page 133 Chapter 5: Debugging Programs Displaying Symbol Information To display local symbol information From the Symbol window’s control menu, choose the Display→Locals... (ALT, -, D, L) command. Type or paste the function for which the local variable information is to displayed. Choose the OK button.
  • Page 134 Chapter 5: Debugging Programs Displaying Symbol Information To display global assembler symbol information • From the Symbol window’s control menu, choose the Display→Asm Globals (ALT, -, D, G) command. The name and address for the global assembler symbols in the program are displayed.
  • Page 135 Chapter 5: Debugging Programs Displaying Symbol Information To create a user-defined symbol From the Symbol window’s control menu, choose the User defined→Add... (ALT, -, U, A) command. Type the symbol name in the Symbol Name text box. Type the address in the Address text box. Choose the OK button.
  • Page 136 Chapter 5: Debugging Programs Displaying Symbol Information To display user-defined symbol information • From the Symbol window’s control menu, choose the Display→User defined (ALT, -, D, U) command. The command displays the name and address for the user-defined symbols. Example User-Defined Symbol Information Display...
  • Page 137 Chapter 5: Debugging Programs Displaying Symbol Information To delete a user-defined symbol From the Symbol window’s control menu, choose the Display→User defined (ALT, -, D, U) command to display the user-defined symbols. Select the user-defined symbol to be deleted. From the Symbol window’s control menu, choose the User defined→Delete (ALT, -, U, D) command.
  • Page 138 Chapter 5: Debugging Programs Stepping, Running, and Stopping the Program Stepping, Running, and Stopping the Program This section shows you how: • To step a single line or instruction • To step over a function • To step multiple lines or instructions •...
  • Page 139 Chapter 5: Debugging Programs Stepping, Running, and Stopping the Program To step over a function • Choose the Execution→Step Over (ALT, E, O) command. • Or, press the F3 key. This command steps a single source line or assembly language instruction except when the source line contains a function call or the assembly instruction makes a subroutine call.
  • Page 140 Chapter 5: Debugging Programs Stepping, Running, and Stopping the Program To step multiple lines or instructions Choose the Execution→Step... (ALT, E, S) command. Select one of the Current PC, Start Address, or Address options. (Enter the starting address when the Address option is selected.) In the Count text box, type the number of lines to be single-stepped.
  • Page 141 Chapter 5: Debugging Programs Stepping, Running, and Stopping the Program To run the program until the specified line Position the cursor in the Source window on the line that you want to run to. Choose the Execution→Run to Cursor (ALT, E, C) command. Execution stops immediately before the cursor-selected line.
  • Page 142 Chapter 5: Debugging Programs Stepping, Running, and Stopping the Program Note The debugger cannot properly run to the function return when the current program counter is at the first line of the function (immediately after its entry point). Before running to the caller, use the Execution→Single Step (ALT, E, N) command to step past the first line of the function.
  • Page 143 Chapter 5: Debugging Programs Stepping, Running, and Stopping the Program To reset the processor • Choose the Execution→Reset (ALT, E, E) command. Once the command has been completed, the processor remains reset if monitor intrusion is disallowed. If monitor intrusion is allowed, the emulation microprocessor may switch immediately from reset to running in monitor, for example, to update the contents of a register window.
  • Page 144 Chapter 5: Debugging Programs Using Breakpoints and Break Macros Using Breakpoints and Break Macros This section shows you how: • To set a breakpoint • To disable a breakpoint • To delete a single breakpoint • To list the breakpoints and break macros •...
  • Page 145 Chapter 5: Debugging Programs Using Breakpoints and Break Macros To set a breakpoint Position the cursor on the line where you wish to set a breakpoint. Choose the Breakpoint→Set at Cursor (ALT, B, S) command. When you run the program and the breakpoint is hit, execution stops immediately before the breakpoint line.

  • Page 146: Breakpoint→Edit

    Chapter 5: Debugging Programs Using Breakpoints and Break Macros To disable a breakpoint Choose the Breakpoint→Edit... (ALT, B, E) command. Select the breakpoint to be disabled. Choose the Enable/Disable button. Notice that "DI" appears next to the breakpoint in the list. To close the dialog box, choose the Close button.
  • Page 147 Chapter 5: Debugging Programs Using Breakpoints and Break Macros To list the breakpoints and break macros • Choose the Breakpoint→Edit... (ALT, B, E) command. The command displays breakpoints followed by break macro commands in parentheses. The Breakpoint Edit dialog box also allows you to delete breakpoints and break macros.
  • Page 148 Chapter 5: Debugging Programs Using Breakpoints and Break Macros To add macro commands to the top of an existing break macro, position the cursor on the line that contains the BP marker before choosing Breakpoint→Set Macro... (ALT, B, M). Example To set "EVALUATE"...
  • Page 149 Chapter 5: Debugging Programs Using Breakpoints and Break Macros Choose the Set button. Choose the Close button. The break macro is displayed in the Source window as shown below.
  • Page 150 Chapter 5: Debugging Programs Using Breakpoints and Break Macros To delete a single break macro Position the cursor on the line that contains the break macro to be deleted. Choose the Breakpoint→Delete Macro (ALT, B, L) command. To delete a single macro command that is part of a break macro, position the cursor on the macro command before choosing Breakpoint→Delete Macro (ALT, B, L).
  • Page 151 Chapter 5: Debugging Programs Using Breakpoints and Break Macros To delete all breakpoints and break macros Choose the Breakpoint→Edit... (ALT, B, E) command. Choose the Delete All button. Select the Global Disable and Delete All check box. Choose the Close button. The Breakpoint→Edit...

  • Page 152: Variable→Edit

    Chapter 5: Debugging Programs Displaying and Editing Variables Displaying and Editing Variables This section shows you how: • To display a variable • To edit a variable • To monitor a variable in the WatchPoint window To display a variable Position the mouse pointer over the variable in the Source window and double-click the left mouse button.
  • Page 153 Chapter 5: Debugging Programs Displaying and Editing Variables To edit a variable Position the mouse pointer over the variable in the Source window and double-click the left mouse button. Choose the Variable→Edit... (ALT, V, E) command. Choose the Modify button. This opens the Variable Modify dialog box.
  • Page 154 Chapter 5: Debugging Programs Displaying and Editing Variables To monitor a variable in the WatchPoint window Highlight the variable in the Source window by either double-clicking the left mouse button or by holding the left mouse button down and dragging the mouse pointer over the variable. Choose the Variable→Edit...
  • Page 155 Chapter 5: Debugging Programs Displaying and Editing Memory Displaying and Editing Memory This section shows you how: • To display memory • To edit memory • To copy memory to a different location • To copy target system memory into emulation memory •...
  • Page 156 Chapter 5: Debugging Programs Displaying and Editing Memory Display→Byte (ALT, -, D, Y) command is chosen, ASCII values are also displayed. To specify whether memory is displayed in a single-column or multicolumn format, access the Memory window’s control menu; then, choose the Display→Linear (ALT, -, D, L) or Display→Block (ALT, -, D, B) command.
  • Page 157 Chapter 5: Debugging Programs Displaying and Editing Memory To edit memory Assuming the location you wish to edit has already been displayed (and Memory window polling is turned ON): Double-click the location you wish to edit. Use the keyboard to enter a new value. Press the Enter key.
  • Page 158 Chapter 5: Debugging Programs Displaying and Editing Memory To copy memory to a different location From the Memory window’s control menu, choose the Utilities→Copy... (ALT, -, U, C) command. Enter the starting address of the range to be copied in the Start text box.
  • Page 159 Chapter 5: Debugging Programs Displaying and Editing Memory To copy target system memory into emulation memory Map the address range to be copied as emulation memory. Because the processor cannot read target system memory when it is in the EMULATION RESET state, choose the Execution→Break (ALT, E, B) command, or press the F4 key, to break execution into the monitor.
  • Page 160 Chapter 5: Debugging Programs Displaying and Editing Memory Example To copy the contents of addresses 0h through ffffh with "X" function code from target system memory to the corresponding emulation memory address range: To modify a range of memory with a value From the Memory window’s control menu, choose the Utilities→Fill...
  • Page 161 Chapter 5: Debugging Programs Displaying and Editing Memory To search memory for a value or string From the Memory window’s control menu, choose the Search... (ALT, -, R) command. Enter in the Value or String text box the value or string to search for. Enter the starting address in the Start text box.
  • Page 162 • To display I/O locations • To edit an I/O location With the 68302 microprocessor, I/O locations are memory-mapped. To display I/O locations Choose the Window→I/O command. From the I/O window’s control menu, choose the Define... (ALT, -, D) command.
  • Page 163 Chapter 5: Debugging Programs Displaying and Editing I/O Locations Example To display the contents of address 2000: To edit an I/O location Display the I/O value to be changed with the Window→I/O command. Double-click the value to be changed. Use the keyboard to enter a new value. Press the Enter key.
  • Page 164 Chapter 5: Debugging Programs Displaying and Editing Registers Displaying and Editing Registers This section shows you how: • To display registers • To edit registers To display registers • Choose the Window→Register command. The register values displayed in the window are periodically updated to show you how the values change during program execution.
  • Page 165 Chapter 5: Debugging Programs Displaying and Editing Registers Example Register Contents Displayed in the Register Window...
  • Page 166 Chapter 5: Debugging Programs Displaying and Editing Registers To edit registers Display the register contents by choosing the Window→Register command. Double-click the value to be changed. Use the keyboard to enter a new value. Press the Enter key. Modifying register contents temporarily interrupts program execution. You cannot modify register contents while the user program is running and monitor intrusion is disallowed.
  • Page 167 Making Coverage Measurements This section shows you how: • To display execution coverage Coverage measurements are not supported when using the HP 64170 emulation memory board. To display execution coverage Coverage measurements are not supported when using the HP 64170 emulation memory board.
  • Page 168 Chapter 5: Debugging Programs Making Coverage Measurements Note The coverage display also highlights a source symbol when the source symbol corresponds to a single assembly language instruction and the instruction is prefetched. Example Execution Coverage Displayed in Source Window...
  • Page 169 Chapter 5: Debugging Programs Tracing Program Execution Tracing Program Execution This section shows you how: • To trace function flow • To trace callers of a specified function • To trace execution within a specified function • To trace accesses to a specified variable •...
  • Page 170 Note The analyzer traces unexecuted instructions due to prefetching in 68302. Trace Window Contents When traces are completed, the Trace window is automatically opened to display the trace results.
  • Page 171 Chapter 5: Debugging Programs Tracing Program Execution To trace function flow • Choose the Trace→Function Flow (ALT, T, F) command. The command stores function entry points, and the resulting trace shows program execution flow. The command traces C function entry points only. It does not trace execution for assembly language routines.
  • Page 172 Note The analyzer may fail in tracing the caller due to prefetching in 68302. To avoid this failure, specify the function by a value of its address + 2.
  • Page 173 Chapter 5: Debugging Programs Tracing Program Execution Example To trace the caller of "next_message": Double-click "next_message". Choose the Trace→Function Caller... (ALT, T, C) command. The Trace window becomes active and displays the trace results. You can see how prefetching affects tracing by choosing the Display→Mixed Mode (ALT, -, D, M) command from the Trace window’s control menu.
  • Page 174 Chapter 5: Debugging Programs Tracing Program Execution To trace execution within a specified function Double-click the function name in the Source window. Choose the Trace→Function Statement... (ALT, T, S) command. This command traces C functions only. It does not trace execution of assembly language subroutines.
  • Page 175 Chapter 5: Debugging Programs Tracing Program Execution To trace accesses to a specified variable Double-click the global variable name in the Source window. Choose the Trace→Variable Access... (ALT, T, V) command. The command also traces access to the Assembler symbol specified by its name and size.
  • Page 176 Chapter 5: Debugging Programs Tracing Program Execution To trace before a particular variable value and break Double-click the desired global variable. Choose the Trace→Variable Break... (ALT, T, B) command. Enter the value in the Value text box. Choose the OK button. The Trace→Variable Break...
  • Page 177 Chapter 5: Debugging Programs Tracing Program Execution Example To break execution as soon as "message_id" contains "0": Double-click "message_id". Choose the Trace→Variable Break... (ALT, T, B) command. Enter "0" in the Value text box. Choose the OK button. The debugger halts execution as soon as the program writes "0" to the "message_id"...
  • Page 178 Stop a trace before the trace buffer becomes full. To repeat the last trace • Choose the Trace→Again (ALT, T, A) command, or press the F7 key. The Trace→Again (ALT, T, A) command traces program execution using the last trace specification stored in the HP 64700.
  • Page 179 Chapter 5: Debugging Programs Tracing Program Execution To identify bus arbitration cycles in the trace Choose the Settings→Emulator Config→Hardware... (ALT, S, E, H) command. Select the Tag Bus Arbitration for Analyzer option. Choose the OK button to confirm your selection. When the Tag Bus Arbitration for Analyzer option is selected, a state is stored in trace memory when a bus arbitration cycle occurs.
  • Page 180 Chapter 5: Debugging Programs Tracing Program Execution Example Bus Cycles Displayed in Trace with "Mixed Mode" selected: To display absolute or relative counts • From the Trace window’s control menu, choose the Display→Count→Absolute (ALT, -, D, C, A) or Display→Count→Relative (ALT, -, D, C, R) command. Choosing the Display→Count→Relative (ALT, -, D, C, R) command selects the relative mode where the state-to-state time intervals are displayed.
  • Page 181 • To load a stored trace specification Note The analyzer traces unexecuted instructions due to prefetching in 68302. Note Analyzer memory is unloaded two states at a time. If you use a storage qualifier to capture states that do not occur often, it’s possible that one of these states has been captured and stored but cannot be displayed because another state must be stored before the pair can be unloaded.
  • Page 182 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications To set up a "Trigger Store" trace specification Choose the Trace→Trigger Store... (ALT, T, T) command. Specify the trigger condition using the Address, Data, and/or Status text boxes within the Trigger group box. Specify the trigger position by selecting the trigger start, trigger center, or trigger end option in the Trigger group box.
  • Page 183 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications Example To trace execution after the "convert_case" function: Choose the Trace→Trigger Store... (ALT, T, T) command. Enter "convert_case" in the Address text box in the Trigger group box. Choose the OK button. Example To trace execution before and after the "convert_case"...
  • Page 184 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications Example To specify the trigger condition as any address in the range 1000h through 1fffh:...
  • Page 185 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications To set up a "Find Then Trigger" trace specification Choose the Trace→Find Then Trigger... (ALT, T, D) command. Specify the sequence, which is made up of the enable, trigger store, trigger, and store conditions. Specify the restart, count, and prestore conditions.
  • Page 186 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications "a" through "h", "range", or "arm" as the condition. Patterns "a" through "h", "range", and "arm" are grouped into two sets, and resources within a set may be combined using the "or" or "nor" logical operators. Resources from the two sets may be combined using the OR or AND logical operators.
  • Page 187 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications If you double-click on the range resource, the Trace Range dialog box is opened to let you select either the Address range or the Data range option and enter the minimum and maximum values in the range. Example To trace execution after the "convert_case"...
  • Page 188 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications Enter "convert_case" in the Address text box in the Trace Pattern dialog box. Choose the OK button in the Trace Pattern dialog box. Choose the OK button in the Find Then Trigger Trace dialog box.
  • Page 189 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications Example To trace about the "next_message" function when it follows the "change_status" function and store all states after the "change_status" function:...
  • Page 190 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications To set up a "Sequence" trace specification Sequence trace specifications let you trigger the analyzer on a sequence of several captured states. There are 8 sequence levels. When a trace is started, the first sequence level is active.
  • Page 191 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications If you want emulator execution to break to the monitor when the trigger condition occurs, select the Break On Trigger check box. Choose the OK button to set up the analyzer and start the trace. The Trace→Sequence...
  • Page 192 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications The range and pattern resources are defined by double-clicking on the resource name in the Pattern/Range list box. If you double-click on a pattern name, the Trace Pattern dialog box is opened to let you specify address, data, and status values.
  • Page 193 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications Example To specify address "convert_case" as the trigger condition: Example To specify execution of "convert_case" and "next_message" as the trigger sequence:...
  • Page 194 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications To edit a trace specification Choose the Trace→Edit... (ALT, T, E) command. Using the Sequence Trace dialog box, edit the trace specification as desired. Choose the OK button. You can use this command to edit trace specifications, including trace specifications that are automatically set up.
  • Page 195 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications sequence level stores the states you’re interested in while searching for the window disable state. If you want to store the window of code execution before and after the trigger condition, use two sets of paired sequence levels: one window enable/disable pair of sequence levels before the trigger, and another disable/enable pair after the trigger as shown below.
  • Page 196 Chapter 5: Debugging Programs Setting Up Custom Trace Specifications Example To trace the window of code execution between lines 46 and 51 of the sample program, triggering on any state in the window: Notice that the analyzer triggers on the entry to sequence level 3. The primary branch condition in level 2 actually specifies the trigger condition.

  • Page 197: Trace→Edit

    Chapter 5: Debugging Programs Setting Up Custom Trace Specifications To load a stored trace specification Choose the Trace→Trigger Store... (ALT, T, T), Trace→Find Then Trigger... (ALT, T, D), Trace→Sequence... (ALT, T, Q), or Trace→Edit... (ALT, T, E) command. Choose the Load... button. Select the desired trace specification file.
  • Page 198 Part 3 Reference Descriptions of the product in a dictionary or encyclopedia format.
  • Page 199 Part 3...
  • Page 200 Command File and Macro Command Summary...
  • Page 201 Command File and Macro Command Summary This section lists the Real-Time C Debugger break macro and command file commands, providing syntax and brief description for each of the listed commands. For details on each command, refer to the command descriptions. The characters in parentheses can be ignored for shortcut entry.
  • Page 202 Chapter 6: Command File and Macro Command Summary address Registering watchpoint DEL(ETE) address Deleting watchpoint DEL(ETE) Deleting all watchpoints Breakpoint Commands Command Param_1 Param_2 Param_3 Param_4 Operation MODE BKP(TBREAK) ON|OFF Deletes all/prevents new breakpoints linenumber command Setting break macro plinenum command Setting break macro DEL(ETE)
  • Page 203 Chapter 6: Command File and Macro Command Summary MOD(E) TRACECLOCK BACKGROUND Trace background cycles MOD(E) TRACECLOCK BOTH Trace all processor cycles MOD(E) TRACECLOCK USER Trace user program cycles File Command Command Param_1 Param_2 Param_3 Param_4 Operation FIL(E) SOU(RCE) modulename Displaying source file FIL(E) OBJ(ECT) filename...
  • Page 204 Chapter 6: Command File and Macro Command Summary Command File Control Command Command Param_1 Param_2 Param_3 Param_4 Operation EXIT Exiting command file EXIT VAR(IABLE) address value Exiting with variable cont. EXIT REG(ISTER) regname value Exiting with register cont. EXIT MEM(ORY) size address value...
  • Page 205 Chapter 6: Command File and Macro Command Summary Parameters Parameter Description Notation address Address See "Reference". addr-range Address range case Case sensing command Macro command Commands listed in the "Reference". config-ans Setting See "Reference". config-item Configuration See "Reference". count Count Decimal notation direction Search direction...
  • Page 206 Expressions in Commands...
  • Page 207 Expressions in Commands When you enter values and addresses in commands, you can use: • Numeric constants (hexadecimal, decimal, octal, or binary values). • Symbols (identifiers). • Function codes. • C operators (pointers, arrays, structures, unions, unary minus operators) and parentheses (specifying the order of operator evaluation).
  • Page 208 Chapter 7: Expressions in Commands Numeric Constants Numeric Constants All numeric constants are assumed to be hexadecimal, except when the number refers to a count; count values are assumed to be decimal. By appending a suffix to the numeric value, you can specify its base. The debugger expressions support the following numeric constants with or without radix: Hexadecimal...
  • Page 209 Chapter 7: Expressions in Commands Symbols Symbols The debugger expressions support the following symbols (identifiers): • Symbols defined in C source code. • Symbols defined in assembly language source code. • Symbols added with the Symbol window control menu’s User defined→Add...
  • Page 210 Chapter 7: Expressions in Commands Symbols The symbol names can also include either * or & to explicitly specify the evaluation of the symbol. Symbol address &symbol_name Symbol data *symbol_name Format Specification The format specifications define the variable display format or size for the variable access or break tracing: String Decimal...
  • Page 211 Chapter 7: Expressions in Commands Symbols dat→message,s Display the structure element "message" pointed to by the "dat" pointer as a string. dat→message,x32 Display the structure element "message" pointed to by the "dat" pointer as a 32-bit hex number. sample\\data[1].status,d32 Display the structure element "status" in the second element of the array "data"...
  • Page 212 Chapter 7: Expressions in Commands Function Codes Function Codes Addresses can be specified with any of the function codes. The function codes are appended to the addresses, preceded by @ (for example: 0a3bc@up). You must include a function code when referring to an address that was mapped with a function code other than X.
  • Page 214 Menu Bar Commands...
  • Page 215 Menu Bar Commands This chapter describes the commands that can be chosen from the menu bar. Command descriptions are in the order they appear in the menu bar (top to bottom, left to right). • File→Load Object... (ALT, F, L) •...
  • Page 216 Chapter 8: Menu Bar Commands • Trace→Variable Access... (ALT, T, V) • Trace→Variable Break... (ALT, T, B) • Trace→Edit... (ALT, T, E) • Trace→Trigger Store... (ALT, T, T) • Trace→Find Then Trigger... (ALT, T, D) • Trace→Sequence... (ALT, T, Q) •...
  • Page 217 Chapter 8: Menu Bar Commands • Window→Cascade (ALT, W, C) • Window→Tile (ALT, W, T) • Window→Arrange Icons (ALT, W, A) • Window→1-9 <win_name> (ALT, W, 1-9) • Window→More Windows... (ALT, W, M) • Help→About Debugger/Emulator... (ALT, H, D)

  • Page 218: File→Load Object

    Microtec MCC68K Compiler Microtec ASM68K Assembler Microtec LNK68K Linker HP AxLS CC68000 Compiler HP AxLS AS68K Assembler HP AxLS LD68K Linker You can also load Motorola S-Record and Intel Hexadecimal format files; however, no symbolic information from these files will be loaded.
  • Page 219 Chapter 8: Menu Bar Commands File→Load Object... (ALT, F, L) Current Shows the currently loaded object file. File Name Specifies the object file to be loaded. The system defaults the file extension to ".x". Fcode Assigns any of the function codes to the destination memory area.
  • Page 220 Chapter 8: Menu Bar Commands File→Load Object... (ALT, F, L) FIL(E) APP(END) file_name func_code Appends the symbol information from the specified object file to the currently loaded symbol information. See Also "To load user programs" in the "Loading and Displaying Programs" section of the "Debugging Programs"...

  • Page 221: File→Command Log→Log File Name

    Chapter 8: Menu Bar Commands File→Command Log→Log File Name... (ALT, F, C, N) File→Command Log→Log File Name... (ALT, F, C, N) Lets you name a new command log file. The current command log file is closed and the specified command log file is opened.

  • Page 222: File→Command Log→Logging On (Alt, F, C, O)

    Chapter 8: Menu Bar Commands File→Command Log→Logging ON (ALT, F, C, O) File→Command Log→Logging ON (ALT, F, C, O) Starts command log file output. The File→Command Log→Log File Name... (ALT, F, C, N) command specifies the destination file. Command File Command MOD(E) LOG ON See Also "To create a command file"...

  • Page 223: File→Command Log→Logging Off (Alt, F, C, F)

    Chapter 8: Menu Bar Commands File→Command Log→Logging OFF (ALT, F, C, F) File→Command Log→Logging OFF (ALT, F, C, F) Stops command log file output. The File→Command Log→Log File Name... (ALT, F, C, N) command specifies the destination file. Command File Command MOD(E) LOG OFF See Also "To create a command file"...
  • Page 224 Chapter 8: Menu Bar Commands File→Run Cmd File... (ALT, F, R) File→Run Cmd File... (ALT, F, R) Executes the specified command file. Command files can be: • Files created with the File→Command Log→Log File Name... (ALT, F, C, N) command. •...
  • Page 225 Chapter 8: Menu Bar Commands File→Run Cmd File... (ALT, F, R) File Name Lets you enter the name of the command file to be executed. Directory Shows the current directory and the command files in that directory. You can select the command file name from this list.

  • Page 226: File→Load Debug

    Chapter 8: Menu Bar Commands File→Load Debug... (ALT, F, D) File→Load Debug... (ALT, F, D) Loads a debug environment file. This command opens a file selection dialog box from which you select the debug environment file. Debug environment files have the extension ".ENV". Debug environment files contain information about: •...

  • Page 227: File→Save Debug

    Chapter 8: Menu Bar Commands File→Save Debug... (ALT, F, S) File→Save Debug... (ALT, F, S) Saves a debug environment file. This command opens a file selection dialog box from which you select the debug environment file. The following information is saved in the debug environment file: •...

  • Page 228: File→Load Emulator Config

    Chapter 8: Menu Bar Commands File→Load Emulator Config... (ALT, F, E) File→Load Emulator Config... (ALT, F, E) Loads a hardware configuration command file. This command opens a file selection dialog box from which you select the hardware configuration file. Emulator configuration command files contain: •...

  • Page 229: File→Save Emulator Config

    Chapter 8: Menu Bar Commands File→Save Emulator Config... (ALT, F, V) File→Save Emulator Config... (ALT, F, V) Saves the current hardware configuration to a command file. The following information is saved in the emulator configuration file: • Hardware configuration settings. •...

  • Page 230: File→Copy Destination

    Chapter 8: Menu Bar Commands File→Copy Destination... (ALT, F, P) File→Copy Destination... (ALT, F, P) Names the listing file to which debugger information may be copied. The contents of most of the debugger windows can be copied to the destination listing file by choosing the Copy→Window command from the window’s control menu.

  • Page 231: File→Exit (Alt, F, X)

    Chapter 8: Menu Bar Commands File→Exit (ALT, F, X) File→Exit (ALT, F, X) Exits the debugger. Command File Command QUI(T) See Also "To exit the debugger" in the "Starting and Exiting the Debugger" section of the "Using the Debugger Interface" chapter. File→Exit HW Locked (ALT, F, H)

  • Page 232: File→Exit Hw Locked (Alt, F, H)

    Exits the debugger and locks the emulator hardware. When the emulator hardware is locked, your user name and ID are saved in the HP 64700 and other users are prevented from accessing it. You can restart the debugger and resume your debug session after reloading the symbolic information with the File→Load Object...
  • Page 233 Chapter 8: Menu Bar Commands File Selection Dialog Boxes File Selection Dialog Boxes File selection dialog boxes are used with several of the debugger commands. An example of a file selection dialog box is shown below. File Name You can select the name of the file from the list box and edit it in the text box.
  • Page 234 Chapter 8: Menu Bar Commands Execution→Run (F5), (ALT, E, U) Execution→Run (F5), (ALT, E, U) Runs the program from the current program counter address. Command File Command...
  • Page 235 Chapter 8: Menu Bar Commands Execution→Run to Cursor (ALT, E, C) Execution→Run to Cursor (ALT, E, C) Runs from the current program counter address up to the Source window line that contains the cursor. This command sets a breakpoint at the cursor-selected source line and runs from the current program counter address;...

  • Page 236: Execution→Run To Caller (Alt, E, T)

    Chapter 8: Menu Bar Commands Execution→Run to Caller (ALT, E, T) Execution→Run to Caller (ALT, E, T) Executes the user program until the current function returns to its caller. Because this command determines the address at which to stop execution based on stack frame data and object file function information, the following restrictions are imposed: •...

  • Page 237: Execution→Run

    Chapter 8: Menu Bar Commands Execution→Run... (ALT, E, R) Execution→Run... (ALT, E, R) Executes the user program starting from the specified address. This command sets the processor status to RUNNING IN USER PROGRAM. Note If you try to run from an address whose symbol is START, STA, RESET, or RES (or any upper- or lower-case variation), the debugger instead runs from the start address or reset address, respectively, because these are the keywords used with the RUN command.
  • Page 238 Chapter 8: Menu Bar Commands Execution→Run... (ALT, E, R) User Reset The emulator drives the target reset line and begins executing from the contents of exception vector 0 (this will occur within a few cycles of the /RESET signal). Address Lets you enter the address from which to run.
  • Page 239 Chapter 8: Menu Bar Commands Execution→Single Step (F2), (ALT, E, N) Execution→Single Step (F2), (ALT, E, N) Executes a single instruction or source line at the current program counter address. A single source line is executed when in the source only display mode, unless no source is available or an assembly language program is loaded;...
  • Page 240 Chapter 8: Menu Bar Commands Execution→Step Over (F3), (ALT, E, O) Execution→Step Over (F3), (ALT, E, O) Executes a single instruction or source line at the current program counter except when the instruction or source line makes a subroutine or function call, in which case the entire subroutine or function is executed.
  • Page 241 Chapter 8: Menu Bar Commands Execution→Step... (ALT, E, S) Execution→Step... (ALT, E, S) Single-steps the specified number of instructions or source lines, starting from the specified address. Single source lines are executed when in the source only display mode, unless no source is available or an assembly language program is loaded; in these cases, single assembly language instructions are executed.
  • Page 242 Chapter 8: Menu Bar Commands Execution→Step... (ALT, E, S) Step Dialog Box Choosing the Execution→Step... (ALT, E, S) command opens the following dialog box: Current PC Specifies that stepping start from the current program counter address. Start Address Specifies that stepping start from the start address or transfer address.
  • Page 243 Chapter 8: Menu Bar Commands Execution→Step... (ALT, E, S) Step Single-steps the specified number of instructions or source lines, starting from the specified address. Close Closes the dialog box. Stop Stops single-stepping. Command File Command STE(P) count Single-steps the specified number of instructions or source lines, starting from the current program counter address.

  • Page 244: Execution→Single Step (Alt, E, N) Execution→Step Over (Alt, E, O) Execution→Step

    Chapter 8: Menu Bar Commands Execution→Step... (ALT, E, S) Execution→Single Step (ALT, E, N) Execution→Step Over (ALT, E, O)
  • Page 245 Chapter 8: Menu Bar Commands Execution→Break (F4), (ALT, E, B) Execution→Break (F4), (ALT, E, B) Stop user program execution and break into the monitor. This command can also be used to break into the monitor when the processor is in the EMULATION RESET status. Once the command has been completed, the processor transfers to the RUNNING IN MONITOR status.

  • Page 246: Execution→Reset (Alt, E, E)

    Chapter 8: Menu Bar Commands Execution→Reset (ALT, E, E) Execution→Reset (ALT, E, E) Resets the emulation microprocessor. If a foreground monitor is being used, it will automatically be loaded when this command is chosen. While the processor is in the EMULATION RESET state, no display or modification is allowed for the contents of target system memory or registers.

  • Page 247: Breakpoint→Set At Cursor (Alt, B, S)

    Chapter 8: Menu Bar Commands Breakpoint→Set at Cursor (ALT, B, S) Breakpoint→Set at Cursor (ALT, B, S) Sets a breakpoint at the cursor-selected address in the Source window. The breakpoint marker "BP" appears on lines at which breakpoints are set. When a breakpoint is hit, program execution stops immediately before executing the instruction or source code line at which the breakpoint is set.

  • Page 248: Breakpoint→Delete At Cursor (Alt, B, D)

    Chapter 8: Menu Bar Commands Breakpoint→Delete at Cursor (ALT, B, D) Breakpoint→Delete at Cursor (ALT, B, D) Deletes the breakpoint set at the cursor-selected address in the Source window. This command is only applicable to lines that contain "BP" markers (which indicate set breakpoints).

  • Page 249: Breakpoint→Set Macro

    Chapter 8: Menu Bar Commands Breakpoint→Set Macro... (ALT, B, M) Breakpoint→Set Macro... (ALT, B, M) Sets a break macro immediately before the cursor-selected address in the Source window. Break macro lines are marked with the "BP" breakpoint marker, and the corresponding addresses or line numbers are displayed in decimal format.
  • Page 250 Chapter 8: Menu Bar Commands Breakpoint→Set Macro... (ALT, B, M) Breakpoint Edit Dialog Box Choosing the Breakpoint→Set Macro... (ALT, B, M) command opens the following dialog box: Breakpoint Displays the specified line number or address followed by a Address decimal point and the break macro line number. Add Macro Activates the Macro Command text box.
  • Page 251 Chapter 8: Menu Bar Commands Breakpoint→Set Macro... (ALT, B, M) Global Disable Disables and deletes all current breakpoints and break and Delete All macros. Current Displays the addresses and line numbers of the current Breakpoints breakpoints and break macros. Allows you to select breakpoints or break macros to be deleted.

  • Page 252: Breakpoint→Delete Macro (Alt, B, L)

    Chapter 8: Menu Bar Commands Breakpoint→Delete Macro (ALT, B, L) Breakpoint→Delete Macro (ALT, B, L) Removes the break macro set at the cursor-indicated address in the Source window. This command is only applicable to lines that contain "BP" markers (which indicate set breakpoints) or break macro lines.

  • Page 253: Breakpoint→Edit

    Chapter 8: Menu Bar Commands Breakpoint→Edit... (ALT, B, E) Breakpoint→Edit... (ALT, B, E) Lets you set, list, or delete breakpoints and break macros. Breakpoints are always globally enabled on initial entry into the RTC interface. Breakpoint Edit Dialog Box Choosing the Breakpoint→Edit... (ALT, B, E) command opens the following dialog box: Breakpoint Lets you specify the address at which to set a breakpoint or...
  • Page 254 Chapter 8: Menu Bar Commands Breakpoint→Edit... (ALT, B, E) Global Disable When selected, all existing breakpoints are deleted (not and Delete All simply disabled), and no new breakpoints can be added. Current Displays the addresses and line numbers of the current Breakpoints breakpoints and break macros.

  • Page 255: Variable→Edit

    Chapter 8: Menu Bar Commands Variable→Edit... (ALT, V, E) Variable→Edit... (ALT, V, E) Displays or modifies the contents of the specified variable or copies it to the WatchPoint window. A dynamic variable can be registered as a watchpoint when the current program counter is in the function in which the variable is declared.
  • Page 256 Chapter 8: Menu Bar Commands Variable→Edit... (ALT, V, E) Update Reads and displays the contents of the variable specified in the Variable text box. Modify Modifies the contents of the specified variable. Choosing this button opens the Variable Modify Dialog Box, which lets you edit the contents of the variable.
  • Page 257 Chapter 8: Menu Bar Commands Variable Modify Dialog Box Variable Modify Dialog Box Choosing the Modify button in the Variable Edit dialog box opens the following dialog box, where you enter the new value and choose the OK button to confirm the new value. Variable Shows the variable to be edited.

  • Page 258: Trace→Function Flow (Alt, T, F)

    Chapter 8: Menu Bar Commands Trace→Function Flow (ALT, T, F) Trace→Function Flow (ALT, T, F) Traces function flow by storing function entry points in the trace buffer. The analyzer identifies function entry points by looking for the following sequence: A program fetch of the LINK instruction. A data write (the first word of the stack pointer push).

  • Page 259: Trace→Function Caller

    C function name, and the prestored states will show the instructions that called the subroutine. Note Because of prefetching by the 68302 processor, the analyzer may fail in tracing the caller. Function Caller Trace Dialog Box Choosing the Trace→Function Caller...
  • Page 260 Chapter 8: Menu Bar Commands Trace→Function Caller... (ALT, T, C) Command File Command TRA(CE) FUNC(TION) CAL(L) address See Also "To trace callers of a specified function" in the "Tracing Program Execution" section of the "Debugging Programs" chapter.

  • Page 261: Trace→Function Statement

    Because the analyzer is set up based on function information from the object file, this command cannot be used to trace non-C functions. Note The analyzer traces unexecuted instructions due to prefetching by 68302 processor. Function Statement Trace Dialog Box Choosing the Trace→Function Statement...
  • Page 262 Chapter 8: Menu Bar Commands Trace→Function Statement... (ALT, T, S) Command File Command TRA(CE) FUNC(TION) STA(TEMENT) address See Also "To trace execution within a specified function" in the "Tracing Program Execution" section of the "Debugging Programs" chapter.

  • Page 263: Trace→Variable Access

    Chapter 8: Menu Bar Commands Trace→Variable Access... (ALT, T, V) Trace→Variable Access... (ALT, T, V) Traces accesses to the specified variable. The variable name can be selected from another window (in other words, copied to the clipboard) before choosing the command; it will automatically appear in the dialog box that is opened.
  • Page 264 Chapter 8: Menu Bar Commands Trace→Variable Access... (ALT, T, V) See Also "To trace accesses to a specified variable" in the "Tracing Program Execution" section of the "Debugging Programs" chapter.

  • Page 265: Trace→Variable Break

    Chapter 8: Menu Bar Commands Trace→Variable Break... (ALT, T, B) Trace→Variable Break... (ALT, T, B) Traces before, and breaks program execution when, a value is written to a variable. The variable name can be selected from another window (in other words, copied to the clipboard) before choosing the command;...
  • Page 266 Chapter 8: Menu Bar Commands Trace→Variable Break... (ALT, T, B) See Also "To trace before a particular variable value and break" in the "Tracing Program Execution" section of the "Debugging Programs" chapter.

  • Page 267: Trace→Edit

    Chapter 8: Menu Bar Commands Trace→Edit... (ALT, T, E) Trace→Edit... (ALT, T, E) Edits the trace specification of the last trace command. This command is useful for making modifications to the last entered trace command, even if the analyzer was setup automatically as with the Trace→Function or Trace→Variable commands.

  • Page 268: Trace→Trigger Store

    Status values identify the types of microprocessor bus cycles. You may select status values from a predefined list. Note The analyzer traces unexecuted instructions due to prefetching by the 68302 processor. Trigger Store Trace Dialog Box Choosing the Trace→Trigger Store... (ALT, T, T) command opens the...
  • Page 269 Chapter 8: Menu Bar Commands Trace→Trigger Store... (ALT, T, T) Trigger This box groups the items that make up the trigger condition. Specifies any state that does not match the Address, Data, and Status values. Address Specifies the address portion of the state qualifier. End Address Specifies the end address of an address range.
  • Page 270 Chapter 8: Menu Bar Commands Trace→Trigger Store... (ALT, T, T) Command File Command TRA(CE) LOA(D) filename Loads the specified trace setting file. TRA(CE) CUS(TOMIZE) Traces program execution using the loaded trace setting file. See Also "To set up a ’Trigger Store’ trace specification" in the "Setting Up Custom Trace Specifications"...

  • Page 271: Trace→Find Then Trigger

    You can enter address, data, and status values that qualify state(s) by setting up pattern or range resources. These patterns and range resources are used when defining the various conditions. Note The analyzer traces unexecuted instructions due to prefetching by the 68302 processor.
  • Page 272 Chapter 8: Menu Bar Commands Trace→Find Then Trigger... (ALT, T, D) Find Then Trigger Trace Dialog Box Choosing the Trace→Find Then Trigger... (ALT, T, D) command opens the following dialog box: The Sequence group box specifies a two term sequential trigger condition. It also lets you specify store conditions during the sequence.
  • Page 273 Chapter 8: Menu Bar Commands Trace→Find Then Trigger... (ALT, T, D) Count Specifies whether time or the occurrences of a particular state are counted; you can also turn counts OFF. See the Condition Dialog Boxes. Prestore Qualifies the states that may be stored before each normally stored state.
  • Page 274 Chapter 8: Menu Bar Commands Trace→Find Then Trigger... (ALT, T, D) Starts the specified trace and closes the dialog box. Cancel Cancels trace setting and closes the dialog box. Clear Restores the dialog box to its default state. Load... Opens a file selection dialog box from which you select the name of a trace specification file previously saved from the Trigger Store Trace or Find Then Trigger Trace dialog boxes.

  • Page 275: Trace→Sequence

    When the analyzer reaches the sequence level specified in Trigger On, the analyzer is triggered. During the above described operation, the analyzer stores the states specified in the Store text box. Note The analyzer traces unexecuted instructions due to prefetching by the 68302 processor.
  • Page 276 Chapter 8: Menu Bar Commands Trace→Sequence... (ALT, T, Q) Sequence Trace Dialog Box Choosing the Trace→Sequence... (ALT, T, Q) command opens the following dialog box: The Sequence group box specifies two types of branch conditions for transferring from one sequence level to another. It also specifies store conditions for each of sequence levels 1 through 8.
  • Page 277 Chapter 8: Menu Bar Commands Trace→Sequence... (ALT, T, Q) Count Specifies whether time or the occurrences of a particular state are counted; you can also turn counts OFF. See the Condition Dialog Boxes. Prestore Qualifies the states that may be stored before each normally stored state.
  • Page 278 Chapter 8: Menu Bar Commands Trace→Sequence... (ALT, T, Q) Clear Restores the dialog box to its default state. Load... Opens a file selection dialog box from which you select the name of a trace specification file previously saved from any of the trace setting dialog boxes.

  • Page 279: Trace→Until Halt (Alt, T, U)

    Chapter 8: Menu Bar Commands Trace→Until Halt (ALT, T, U) Trace→Until Halt (ALT, T, U) Traces program execution until the Trace→Halt (ALT, T, H) command is chosen. This command is useful in tracing execution that leads to a processor halt or a break to the background monitor.

  • Page 280: Trace→Halt (Alt, T, H)

    Chapter 8: Menu Bar Commands Trace→Halt (ALT, T, H) Trace→Halt (ALT, T, H) Stops a running trace. This command stops a currently running trace whether the trace was started with the Trace→Until Halt (ALT, T, U) command or another trace command. As soon as the analyzer stops the trace, stored states are displayed in the Trace window.

  • Page 281: Trace→Again (F7), (Alt, T, A)

    If you haven’t entered a trace command since you started the debugger, the last trace specification stored in the HP 64700 may be a trace specification set up by a different user; in this case, you cannot view or edit the trace specification.

  • Page 282: Condition Dialog Boxes

    Chapter 8: Menu Bar Commands Condition Dialog Boxes Condition Dialog Boxes Choosing the buttons associated with enable, trigger, primary branch, secondary branch, store, or prestore conditions opens the following dialog box: Choosing the button associated with the count condition opens the following dialog box: no state No state meets the specified condition.
  • Page 283 Chapter 8: Menu Bar Commands Condition Dialog Boxes state This group box lets you qualify the state that will meet the specified condition. You can qualify the state as one of the patterns "a" through "h", the "range", or the "arm", or you can qualify the state as a combination of the patterns, range, or arm by using the interset or intraset operators.
  • Page 284 Chapter 8: Menu Bar Commands Condition Dialog Boxes Count Appearing in Trace Condition dialog boxes, this value specifies the number of occurrences of the state that will satisfy the condition. Applies the state qualifier to the specified condition and closes the dialog box. Cancel Closes the dialog box.

  • Page 285: Trace Pattern Dialog Box

    Chapter 8: Menu Bar Commands Trace Pattern Dialog Box Trace Pattern Dialog Box Selecting one of the patterns in the Pattern/Range list box opens the following dialog box: Lets you specify all values other than the address, data, and/or status values specified. Address Lets you enter the address value for the pattern.
  • Page 286 Chapter 8: Menu Bar Commands Trace Pattern Dialog Box Cancel Closes the dialog box. See Also "To set up a ’Find Then Trigger’ trace specification" and "To set up a ’Sequence’ trace specification" in the "Setting Up Custom Trace Specifications" section of the "Debugging Programs" chapter. Trace→Find Then Trigger...

  • Page 287: Trace Range Dialog Box

    Chapter 8: Menu Bar Commands Trace Range Dialog Box Trace Range Dialog Box Selecting the range in the Pattern/Range list box opens the following dialog box: Address Selects a range of address values. Data Selects a range of data values. Minimum Lets you enter the minimum value for the range.
  • Page 288 Chapter 8: Menu Bar Commands Trace Range Dialog Box Trace→Find Then Trigger... (ALT, T, D) Trace→Sequence... (ALT, T, Q)

  • Page 289: Sequence Number Dialog Box

    Chapter 8: Menu Bar Commands Sequence Number Dialog Box Sequence Number Dialog Box Choosing the buttons associated with "to" or Trigger On opens the following dialog box: These options specify the sequence level. Applies the selected sequence level and closes the dialog box.

  • Page 290: Realtime→Monitor Intrusion→Disallowed (Alt, R, T, D)

    Chapter 8: Menu Bar Commands RealTime→Monitor Intrusion→Disallowed (ALT, R, T, D) RealTime→Monitor Intrusion→Disallowed (ALT, R, T, D) Activates the real-time mode. When the user program is running in real-time mode, no command that would normally cause temporary suspension of program execution is allowed. Also, the system hides: •...

  • Page 291: Realtime→Monitor Intrusion→Allowed (Alt, R, T, A)

    Chapter 8: Menu Bar Commands RealTime→Monitor Intrusion→Allowed (ALT, R, T, A) RealTime→Monitor Intrusion→Allowed (ALT, R, T, A) Deactivates the real-time mode. Commands that cause temporary breaks to the monitor during program execution are allowed. Command File Command MOD(E) REA(LTIME) OFF See Also "To allow or deny monitor intrusion"...

  • Page 292: Realtime→I/O Polling→On (Alt, R, I, O)

    Chapter 8: Menu Bar Commands RealTime→I/O Polling→ON (ALT, R, I, O) RealTime→I/O Polling→ON (ALT, R, I, O) Enables access to I/O. Command File Command MOD(E) IOG(UARD) OFF See Also "To turn polling ON or OFF" in the "Setting the Real-Time Options" section of the "Configuring the Emulator"...

  • Page 293: Realtime→I/O Polling→Off (Alt, R, I, F)

    Chapter 8: Menu Bar Commands RealTime→I/O Polling→OFF (ALT, R, I, F) RealTime→I/O Polling→OFF (ALT, R, I, F) Disables access to I/O. When polling is turned OFF, values in the I/O window are updated on entry to the monitor. When monitor intrusion is not allowed during program execution, the I/O window is not updated and contents are replaced by dashes (-).

  • Page 294: Realtime→Watchpoint Polling→On (Alt, R, W, O)

    Chapter 8: Menu Bar Commands RealTime→Watchpoint Polling→ON (ALT, R, W, O) RealTime→Watchpoint Polling→ON (ALT, R, W, O) Turns ON polling to update values displayed in the WatchPoint window. When polling is turned ON, temporary breaks in program execution occur when the WatchPoint window is updated. Command File Command MOD(E) WAT(CHPOLL) ON See Also...

  • Page 295: Realtime→Watchpoint Polling→Off (Alt, R, W, F)

    Chapter 8: Menu Bar Commands RealTime→Watchpoint Polling→OFF (ALT, R, W, F) RealTime→Watchpoint Polling→OFF (ALT, R, W, F) Turns OFF polling to update values displayed in the WatchPoint window. When polling is turned OFF, values in the WatchPoint window are updated on entry to the monitor.

  • Page 296: Realtime→Memory Polling→On (Alt, R, M, O)

    Chapter 8: Menu Bar Commands RealTime→Memory Polling→ON (ALT, R, M, O) RealTime→Memory Polling→ON (ALT, R, M, O) Turns ON polling to update target memory values displayed in the Memory window. When polling is turned ON, temporary breaks in program execution occur when target system memory locations in the Memory window are updated.

  • Page 297: Realtime→Memory Polling→Off (Alt, R, M, F)

    Chapter 8: Menu Bar Commands RealTime→Memory Polling→OFF (ALT, R, M, F) RealTime→Memory Polling→OFF (ALT, R, M, F) Turns OFF polling to update target memory values displayed in the Memory window. When polling is turned OFF, values in the Memory window are updated on entry to the monitor.

  • Page 298: Assemble

    Chapter 8: Menu Bar Commands Assemble... (ALT, A) Assemble... (ALT, A) In-line assembler. This command lets you modify programs by specifying assembly language instructions which are assembled and loaded into program memory. Assembler Dialog Box Choosing the Assemble... (ALT, A) command opens the following dialog box: Label Lets you assign a user-defined symbol to the specified address.

  • Page 299: Settings→Emulator Config→Hardware

    Chapter 8: Menu Bar Commands Settings→Emulator Config→Hardware... (ALT, S, E, H) Settings→Emulator Config→Hardware... (ALT, S, E, Specifies the emulator configuration. Hardware Config Dialog Box Choosing the Settings→Emulator Config→Hardware... (ALT, S, E, H) command opens the following dialog box: Clock Source Specifies the Internal or an External clock as the emulation microprocessor clock source.
  • Page 300 Chapter 8: Menu Bar Commands Settings→Emulator Config→Hardware... (ALT, S, E, H) Enable Break on Enables or disables breaks to the monitor when the user Write to ROM program writes to memory mapped as ROM. TRAP Number Specifies the breakpoint trap instruction number. for Software Breakpoint Data Bus Width Specifies the size of the processor data bus.
  • Page 301 Chapter 8: Menu Bar Commands Settings→Emulator Config→Hardware... (ALT, S, E, H) CON(FIG) CLO(CK) EXT(ERNAL) Selects the external clock. CON(FIG) BR ENA(BLE) Enables /BR input from the target system. CON(FIG) BR DIS(ABLE) Disables /BR input from the target system. CON(FIG) BER(R) EN(ABLE) Enables /BERR input from the target system.
  • Page 302 Chapter 8: Menu Bar Commands Settings→Emulator Config→Hardware... (ALT, S, E, H) CON(FIG) ACC(ESS) WOR(DS) Specifies that target memory is accessed in 16-bit word sized locations. CON(FIG) ARB(ITRATION) ENA(BLE) Enables tracing of the DMA cycles. CON(FIG) ARB(ITRATION) DIS(ABLE) Disables tracing of the DMA cycles. CON(FIG) ARB(ITRATION) TAG Enables a single state in the trace each time an external bus arbitration sequence occurs.

  • Page 303: Settings→Emulator Config→Memory Map

    Chapter 8: Menu Bar Commands Settings→Emulator Config→Memory Map... (ALT, S, E, M) Settings→Emulator Config→Memory Map... (ALT, S, E, M) Maps memory ranges. You can map up to 7 address ranges (map terms). The minimum amount of emulation memory that can be allocated to a range is 512 bytes for 128 Kbyte memory boards and 1024 bytes for 512 Kbyte memory boards.
  • Page 304 Chapter 8: Menu Bar Commands Settings→Emulator Config→Memory Map... (ALT, S, E, M) Memory Map Dialog Box Choosing the Settings→Emulator Config→Memory Map... (ALT, S, E, M) command opens the following dialog box: Start Specifies the starting address of the address range to be mapped.
  • Page 305 Chapter 8: Menu Bar Commands Settings→Emulator Config→Memory Map... (ALT, S, E, M) Current Map Lists currently mapped ranges. Available Indicates the amount of emulation memory available. Delete Deletes the address range selected in the Current Map list box. Delete All Deletes all of the address ranges in the Current Map list box.

  • Page 306: Settings→Emulator Config→Monitor

    Chapter 8: Menu Bar Commands Settings→Emulator Config→Monitor... (ALT, S, E, O) Settings→Emulator Config→Monitor... (ALT, S, E, O) Selects the type of monitor program and other monitor options. Monitor Config Dialog Box Choosing the Settings→Emulator Config→Monitor... (ALT, S, E, O) command opens the following dialog box: Type Lets you choose between a background monitor and a foreground monitor.
  • Page 307 The starting address must be located on a 2 Kbyte boundary unless you’re using the HP 64170 memory board with 1 Mbyte memory modules; in this case, the starting address must be located on an 8 Kbyte boundary.
  • Page 308 Chapter 8: Menu Bar Commands Settings→Emulator Config→Monitor... (ALT, S, E, O) Browse... Opens a file selection dialog box from which you can select the foreground monitor object file to be loaded. Modifies the monitor configuration as specified and closes the dialog box. When you have selected a foreground monitor, it is not loaded when you choose OK;...
  • Page 309 Chapter 8: Menu Bar Commands Settings→Emulator Config→Monitor... (ALT, S, E, O) MON(ITOR) STA(CK) address Specifies the value the stack pointer is set to when the emulator breaks into the monitor from the EMULATION RESET status. MON(ITOR) LOC(ATE) address Specifies the starting address of the monitor. MON(ITOR) STA(CK) SUP(ER)/NON(E) Assigns Supervisor function code to the monitor.

  • Page 310: Settings→Communication

    Choosing this command opens the RTC Emulation Connection Dialog Box which lets you identify and set up the communication channel between the personal computer and the HP 64700. RTC Emulation Connection Dialog Box Choosing the Settings→Communication... (ALT, S, C) command opens the...
  • Page 311 Setup button. User Name This name tells the HP 64700 and other users who you are. When other users attempt to access the HP 64700 while you are using it or while it is locked, a message tells them you’re using it.
  • Page 312 Chapter 8: Menu Bar Commands Settings→Communication... (ALT, S, C) The Connect button in any of these Setup dialog boxes starts the debugger with the specified communication settings. Close Either closes the Real-Time C Debugger, if the current connection failed, or simply closes the dialog box. The Real-Time C Debugger does not allow you to change connection or transport information without leaving the debugger and reentering it.

  • Page 313: Settings→Bnc→Outputs Analyzer Trigger (Alt, S, B, O)

    CAUTION Do not drive the BNC beyond the range of 0 to 5 volts. Doing so may cause permanent damage to the HP 64700. The BNC’s drivers can drive 50 ohm loads. The following is a logical diagram of the BNC connection. The physical implementation and values of resistors are not exact;...
  • Page 314 Chapter 8: Menu Bar Commands Settings→BNC→Outputs Analyzer Trigger (ALT, S, B, O) See Also "To output the trigger signal on the BNC port" in the "Setting Up the BNC Port" section of the "Configuring the Emulator" chapter.

  • Page 315: Settings→Bnc→Input To Analyzer Arm (Alt, S, B, I)

    "set2" of the Trace Condition or Count Condition dialog boxes. The BNC port is internally terminated with about 500 ohms; if using a 50 ohm driver, use an external 50 ohm termination (such as the HP 10100C 50 Ohm Feedthrough Termination) to reduce bouncing and possible incorrect triggering.

  • Page 316: Settings→Coverage→Coverage On (Alt, S, V, O)

    Settings→Coverage→Coverage ON (ALT, S, V, O) Settings→Coverage→Coverage ON (ALT, S, V, O) Selects execution coverage display in the Source window. This command is not supported when using the HP 64170 emulation memory board. When the execution coverage display is selected, accessed lines are highlighted in the Source window.

  • Page 317: Settings→Coverage→Coverage Off (Alt, S, V, F)

    Chapter 8: Menu Bar Commands Settings→Coverage→Coverage OFF (ALT, S, V, F) Settings→Coverage→Coverage OFF (ALT, S, V, F) Deselects execution coverage display in the Source window. This command is not supported when using the HP 64170 emulation memory board. Command File Command COV(ERAGE) OFF See Also "To display execution coverage"...

  • Page 318: Settings→Coverage→Coverage Reset (Alt, S, V, R)

    Settings→Coverage→Coverage Reset (ALT, S, V, R) Settings→Coverage→Coverage Reset (ALT, S, V, R) Resets the coverage calculation. This command is not supported when using the HP 64170 emulation memory board. The coverage calculation must be initialized with this command before it is started with the Settings→Coverage→Coverage ON (ALT, S, V, O)

  • Page 319: Settings→Font

    Chapter 8: Menu Bar Commands Settings→Font... (ALT, S, F) Settings→Font... (ALT, S, F) Selects the fonts used in the debugger windows. Font Dialog Box Choosing the Settings→Font... (ALT, S, F) command opens the following dialog box: Font Lets you select the font to be used in the Real-Time C Debugger interface.

  • Page 320: Settings→Font

    Chapter 8: Menu Bar Commands Settings→Font... (ALT, S, F) See Also "To change the debugger window fonts" in the "Working with Debugger Windows" section of the "Using the Debugger Interface" chapter.

  • Page 321: Settings→Tabstops

    Chapter 8: Menu Bar Commands Settings→Tabstops... (ALT, S, T) Settings→Tabstops... (ALT, S, T) Sets the number of spaces between tab stops. Source Tab Dialog Box Choosing the Settings→Tabstops... (ALT, S, T) command opens the following dialog box: Tab width in Enter the number of spaces between tab stops.

  • Page 322: Settings→Symbols→Case Sensitive→On (Alt, S, S, C, O)

    Chapter 8: Menu Bar Commands Settings→Symbols→Case Sensitive→ON (ALT, S, S, C, O) Settings→Symbols→Case Sensitive→ON (ALT, S, S, C, O) Symbol database search is case sensitive. Command File Command MOD(E) SYM(BOLCASE) ON See Also Settings→Symbols→Case Sensitive→OFF (ALT, S, S, C, F) Settings→Symbols→Case Sensitive→OFF (ALT, S, S, C, F) Symbol database search is not case sensitive.

  • Page 323: Settings→Extended→Trace Cycles→User (Alt, S, X, T, U)

    Chapter 8: Menu Bar Commands Settings→Extended→Trace Cycles→User (ALT, S, X, T, U) Settings→Extended→Trace Cycles→User (ALT, S, X, T, U) Traces foreground emulation microprocessor operation. This is the normal setting. Command File Command MOD(E) TRA(CECLOCK) USE(R) See Also Settings→Extended→Trace Cycles→Monitor (ALT, S, X, T, M) Settings→Extended→Trace Cycles→Both (ALT, S, X, T, B) Settings→Extended→Trace Cycles→Monitor (ALT, S, X, T, M)

  • Page 324: Settings→Extended→Trace Cycles→Both (Alt, S, X, T, B)

    Chapter 8: Menu Bar Commands Settings→Extended→Trace Cycles→Both (ALT, S, X, T, B) Settings→Extended→Trace Cycles→Both (ALT, S, X, T, B) Traces both foreground and background emulation microprocessor operation. Command File Command MOD(E) TRA(CECLOCK) BOT(H) See Also Settings→Extended→Trace Cycles→User (ALT, S, X, T, U) Settings→Extended→Trace Cycles→Monitor (ALT, S, X, T, M)

  • Page 325: Settings→Extended→Load Error Abort→On (Alt, S, X, L, O)

    Chapter 8: Menu Bar Commands Settings→Extended→Load Error Abort→ON (ALT, S, X, L, O) Settings→Extended→Load Error Abort→ON (ALT, S, X, L, O) An error during an object file or memory load causes an abort. Normally, when an error occurs during an object file or memory load, you want the load to stop so that you can fix whatever caused the error.

  • Page 326: Settings→Extended→Source Path Query→On (Alt, S, X, S, O)

    Chapter 8: Menu Bar Commands Settings→Extended→Source Path Query→ON (ALT, S, X, S, O) Settings→Extended→Source Path Query→ON (ALT, S, X, S, O) You are prompted for source file paths. When the debugger cannot find source file information for the Source or Trace windows, it may prompt you for source file paths depending on the MODE SOURCE setting.
  • Page 327 Chapter 8: Menu Bar Commands Window→Cascade (ALT, W, C) Window→Cascade (ALT, W, C) Arranges, sizes, and overlaps windows. Windows are sized, evenly, to be as large as possible. Window→Tile (ALT, W, T) Arranges and sizes windows so that none are overlapped. Windows are sized evenly.
  • Page 328 Chapter 8: Menu Bar Commands Window→1-9 (ALT, W, 1-9) Window→1-9 (ALT, W, 1-9) Opens the window associated with the number. The nine most recently opened windows appear in the menu list. If the window you wish to open is not on the list, choose the Window→More Windows...
  • Page 329 Chapter 8: Menu Bar Commands Window→More Windows... (ALT, W, M) Window→More Windows... (ALT, W, M) Presents a list box from which you can select the window to be opened. Select Window Dialog Box Choosing the Window→More Windows... (ALT, W, M) command opens the following dialog box: Opens the window selected in the list box.
  • Page 330 Chapter 8: Menu Bar Commands Help→About Debugger/Emulator... (ALT, H, D) Help→About Debugger/Emulator... (ALT, H, D) Provides information on the Real-Time C Debugger. Choosing the Help→About Debugger/Emulator... (ALT, H, D) command opens a dialog box containing the version information on the current Real-Time C Debugger and emulator.
  • Page 331 Chapter 8: Menu Bar Commands Source Directory Dialog Box Source Directory Dialog Box When the source file associated with a symbol cannot be found in the current directory, the following dialog box is opened: Module Shows the symbol whose source file could not be found. Directory Lets you enter the directory in which the source file associated with the symbol may be found.
  • Page 332 Chapter 8: Menu Bar Commands WAIT Command Dialog Box WAIT Command Dialog Box This dialog box appears when the WAIT command is included in a command file, break macro, or button. Choosing the STOP button cancels the WAIT command.
  • Page 334 Window Control Menu Commands...
  • Page 335 Window Control Menu Commands This chapter describes the commands that can be chosen from the control menus in debugger windows. • Common Control Menu Commands • Button Window Commands • Device Regs Window Commands • Expression Window Commands • I/O Window Commands •...
  • Page 336 Chapter 9: Window Control Menu Commands Common Control Menu Commands Common Control Menu Commands This section describes commands that appear in the control menus of most of the debugger windows: • Copy→Window (ALT, -, P, W) • Copy→Destination... (ALT, -, P, D) Copy→Window (ALT, -, P, W) Copies the current window contents to the destination file specified with the File→Copy Destination...
  • Page 337 Chapter 9: Window Control Menu Commands Common Control Menu Commands Copy→Destination... (ALT, -, P, D) Names the listing file to which debugger information may be copied. This command opens a file selection dialog box from which you can select the listing file.
  • Page 338 Chapter 9: Window Control Menu Commands Button Window Commands Button Window Commands This section describes the following command: • Edit... (ALT, -, E) Edit... (ALT, -, E) Lets you define and label buttons in the Button window. You can set up buttons to execute commonly used commands or command files.
  • Page 339 Chapter 9: Window Control Menu Commands Button Window Commands Button Edit Dialog Box Choosing the Edit... (ALT, -, E) command opens the following dialog box: Command Specifies the command to be associated with the button. Command syntax is described at the bottom of most help topics under the "Command File Command"...
  • Page 340 Chapter 9: Window Control Menu Commands Button Window Commands Delete Deletes the button definition selected in the Button Definitions list box. Delete All Deletes all buttons from the Button window. Close Closes the dialog box. Command File Command BUTTON label "command" See Also "To create buttons that execute command files"...
  • Page 341 Chapter 9: Window Control Menu Commands Device Regs Window Commands Device Regs Window Commands This section describes the following command: • Continuous Update (ALT, -, U) Continuous Update (ALT, -, U) Specifies whether the Device Regs window contents should be continuously updated while running programs.
  • Page 342 Chapter 9: Window Control Menu Commands Expression Window Commands Expression Window Commands This section describes the following commands: • Clear (ALT, -, R) • Evaluate... (ALT, -, E) Clear (ALT, -, R) Erases the contents of the Expression window. Command File Command EVA(LUATE) CLE(AR)
  • Page 343 Chapter 9: Window Control Menu Commands Expression Window Commands Evaluate... (ALT, -, E) Evaluates expressions and displays the results in the Expression window. Evaluate Expression Dialog Box Choosing the Evaluate... (ALT, -, E) command opens the following dialog box: Expression Lets you enter the expression to be evaluated.
  • Page 344 Chapter 9: Window Control Menu Commands I/O Window Commands I/O Window Commands This section describes the following command: Define... (ALT, -, D) Define... (ALT, -, D) Adds or deletes memory mapped I/O locations from the I/O window. I/O Setting Dialog Box Choosing the Edit→Definition...
  • Page 345 Chapter 9: Window Control Menu Commands I/O Window Commands Address Specifies the address of the I/O location to be defined. Size Specifies the data format of the I/O location to be defined. You can select the Byte or 16 Bits option. Space Specifies whether the I/O location is in memory or I/O space.
  • Page 346 Chapter 9: Window Control Menu Commands Memory Window Commands Memory Window Commands This section describes the following commands: • Display→Linear (ALT, -, D, L) • Display→Block (ALT, -, D, B) • Display→Byte (ALT, -, D, Y) • Display→16 Bits (ALT, -, D, 1) •...
  • Page 347 Chapter 9: Window Control Menu Commands Memory Window Commands Display→Block (ALT, -, D, B) Displays memory contents in multicolumn format. Command File Command MEM(ORY) BLO(CK) Display→Byte (ALT, -, D, Y) Displays memory contents as bytes. Command File Command MEM(ORY) BYTE Display→16 Bit (ALT, -, D, 1) Displays memory contents as 16-bit values.
  • Page 348 Chapter 9: Window Control Menu Commands Memory Window Commands Search... (ALT, -, R) Searches for a value or string in a range of memory. When the value or string is found, the location is displayed in the Memory window. Choose the Window→Memory command to open the window. The value or string can be selected from another window (in other words, copied to the clipboard) before choosing the command;...
  • Page 349 Chapter 9: Window Control Menu Commands Memory Window Commands Close Closes the dialog box. Command File Command SEA(RCH) MEM(ORY) BYTE/WORD/LONG addr_range value SEA(RCH) MEM(ORY) STR(ING) "string" See Also "To search memory for a value or string" in the "Displaying and Editing Memory"...
  • Page 350 Chapter 9: Window Control Menu Commands Memory Window Commands Utilities→Copy... (ALT, -, U, C) Copies the contents of one memory area to another. Memory Copy Dialog Box Choosing the Utilities→Copy... (ALT, -, U, C) command opens the following dialog box: Start Lets you enter the starting address of the source memory area.
  • Page 351 Chapter 9: Window Control Menu Commands Memory Window Commands See Also "To copy memory to a different location" in the "Displaying and Editing Memory" section of the "Debugging Programs" chapter. Utilities→Fill... (ALT, -, U, F) Fills a range of memory with a specified value. Memory Fill Dialog Box Choosing the Utilities→Fill...
  • Page 352 Chapter 9: Window Control Menu Commands Memory Window Commands Close Closes the dialog box. Command File Command MEM(ORY) FIL(L) size address_range data See Also "To modify a range of memory with a value" in the "Displaying and Editing Memory" section of the "Debugging Programs" chapter. Utilities→Image...
  • Page 353 Chapter 9: Window Control Menu Commands Memory Window Commands Start Lets you enter the starting address of the memory area. Lets you enter end address of the memory area. Size Selects the data size using the Byte, 16 Bits, or 32 Bits option buttons.
  • Page 354 Chapter 9: Window Control Menu Commands Memory Window Commands Utilities→Load... (ALT, -, U, L) Loads memory contents from a previously stored file. Load Binary File Dialog Box Choosing the Utilities→Load... (ALT, -, U, L) command opens the following dialog box: File Name Lets you enter the name of the file to load memory from.
  • Page 355 Chapter 9: Window Control Menu Commands Memory Window Commands See Also "To copy target system memory into emulation memory" in the "Displaying and Editing Memory" section of the "Debugging Programs" chapter. Utilities→Store... (ALT, -, U, S) Utilities→Store... (ALT, -, U, S) Stores memory contents to a binary file.
  • Page 356 Chapter 9: Window Control Menu Commands Memory Window Commands Start Lets you enter the starting address of the memory range to be stored. Lets you enter the ending address of the memory range to be stored. Store Starts the memory store. Cancel Closes the dialog box.
  • Page 357 Chapter 9: Window Control Menu Commands Register Window Commands Register Window Commands This section describes the following command: Copy→Registers (ALT, -, P, R) Copy→Registers (ALT, -, P, R) Copies the current Register window contents to the destination file specified with the File→Copy Destination... (ALT, F, P) command. Command File Command COP(Y) REG(ISTER)
  • Page 358 Chapter 9: Window Control Menu Commands Register Window Commands Register Bit Fields Dialog Box When a register has bit-fields, a dialog will pop-up and the register value may be edited by changing the whole value or by editing individual bit-fields. When editing in the dialog box, a carriage-return is the same as choosing the OK button.
  • Page 359 Chapter 9: Window Control Menu Commands Register Window Commands Modifies the register as specified, and closes the dialog box. Cancel Closes the dialog box without modifying the register.
  • Page 360 Chapter 9: Window Control Menu Commands Source Window Commands Source Window Commands This section describes the following commands: • Display→Mixed Mode (ALT, -, D, M) • Display→Source Only (ALT, -, D, S) • Display→Select Source... (ALT, -, D, L) • Search→String...
  • Page 361 Chapter 9: Window Control Menu Commands Source Window Commands Display→Source Only (ALT, -, D, S) Chooses the source only display mode. Command File Command MOD(E) MNE(MONIC) OFF See Also "To display source code only" in the "Loading and Displaying Programs" section of the "Debugging Programs"...
  • Page 362 Chapter 9: Window Control Menu Commands Source Window Commands Source Files Lists C source files associated with the loaded object file. You can select the source file to be displayed from this list. Select Switches the Source window contents to the selected source file.
  • Page 363 Chapter 9: Window Control Menu Commands Source Window Commands Search String Dialog Box Choosing the Search→String... (ALT, -, R, S) command opens the following dialog box: Find What Lets you enter the string. Match Case Selects or deselects case matching. Specifies that the search be from the current cursor position backward.
  • Page 364 Chapter 9: Window Control Menu Commands Source Window Commands Search→Function... (ALT, -, R, F) Searches for, and displays, a function in the Source window. The object file and symbols must be loaded before you can choose this command. Note This command displays the source file based on the function information in the object file.
  • Page 365 Chapter 9: Window Control Menu Commands Source Window Commands See Also "To search for function names in the source files" in the "Loading and Displaying Programs" section of the "Debugging Programs" chapter. Search→Address... (ALT, -, R, A) Searches for, and displays, an address in the Source window. Address expressions such as function names or symbols can be selected from another window (in other words, copied to the clipboard) before choosing the command;...
  • Page 366 Chapter 9: Window Control Menu Commands Source Window Commands Command File Command CUR(SOR) address When used before the COME command, this command can be used to run to a particular address. See Also "To search for addresses in the source files" in the "Loading and Displaying Programs"...
  • Page 367 Chapter 9: Window Control Menu Commands Source Window Commands Search Directories Dialog Box Choosing the Directories... button in the Select Source dialog box opens the following dialog box: Directory Lets you enter the directory to be added to the source file search path.
  • Page 368 Chapter 9: Window Control Menu Commands Symbol Window Commands Symbol Window Commands This section describes the following commands: • Display→Modules (ALT, -, D, M) • Display→Functions (ALT, -, D, F) • Display→Externals (ALT, -, D, E) • Display→Locals... (ALT, -, D, L) •...
  • Page 369 Chapter 9: Window Control Menu Commands Symbol Window Commands See Also "To display program module information" in the "Displaying Symbol Information" section of the "Debugging Programs" chapter. Display→Functions (ALT, -, D, F) Displays the symbolic function information from the loaded object file. The Symbol window displays the name, type and address range for C functions.
  • Page 370 Chapter 9: Window Control Menu Commands Symbol Window Commands Display→Locals... (ALT, -, D, L) Displays the local variable information on the specified function. The function name can be selected from another window (in other words, copied to the clipboard) before choosing the command; the clipboard contents automatically appear in the dialog box that is opened.
  • Page 371 Chapter 9: Window Control Menu Commands Symbol Window Commands Display→Asm Globals (ALT, -, D, G) Displays the global Assembler symbol information from the loaded object file. The Symbol window displays the name and address for the global assembler symbols. Command File Command SYM(BOL) LIS(T) GLO(BALS) See Also "To display global assembler symbol information"...
  • Page 372 Chapter 9: Window Control Menu Commands Symbol Window Commands Assembler Symbol Dialog Box Choosing the Display→Asm Locals... (ALT, -, D, A) command opens the following dialog box: Module Selects the module for which the local symbols are displayed. Executes the command and closes the dialog box. Cancel Cancels the command and closes the dialog box.
  • Page 373 Chapter 9: Window Control Menu Commands Symbol Window Commands Display→User defined (ALT, -, D, U) Displays the user-defined symbol information. The Symbol window displays the name and address for the user-defined symbols. The User defined→Add... (ALT, -, D, U) command adds the user-defined symbols.
  • Page 374 Chapter 9: Window Control Menu Commands Symbol Window Commands Copy→All (ALT, -, P, A) Copies all the symbol information to the specified listing file. The listing file is specified with the File→Copy Destination... (ALT, F, P) command. Command File Command SYM(BOL) COP(Y) ALL FindString→String...
  • Page 375 Chapter 9: Window Control Menu Commands Symbol Window Commands Command File Command SYM(BOL) MAT(CH) string See Also "To display the symbols containing the specified string" in the "Displaying Symbol Information" section of the "Debugging Programs" chapter. User defined→Add... (ALT, -, U, A) Adds the specified user-defined symbol.
  • Page 376 Chapter 9: Window Control Menu Commands Symbol Window Commands Symbol Name Specifies the symbol to be added. Address Specifies the address of the symbol. Executes the command and closes the dialog box. Cancel Cancels the command and closes the dialog box. Command File Command SYM(BOL) ADD symbol_nam address See Also...
  • Page 377 Chapter 9: Window Control Menu Commands Symbol Window Commands User defined→Delete All (ALT, -, U, L) Deletes all the user-defined symbols. Command File Command SYM(BOL) DEL(ETE) ALL...
  • Page 378 Chapter 9: Window Control Menu Commands Trace Window Commands Trace Window Commands This section describes the following commands: • Display→Mixed Mode (ALT, -, D, M) • Display→Source Only (ALT, -, D, S) • Display→Bus Cycle Only (ALT, -, D, C) •...
  • Page 379 Chapter 9: Window Control Menu Commands Trace Window Commands Display→Source Only (ALT, -, D, S) Selects the source only display mode. Command File Command TRA(CE) DIS(PLAY) SOU(RCE) See Also "To display bus cycles" in the "Tracing Program Execution" section of the "Debugging Programs"...
  • Page 380 Chapter 9: Window Control Menu Commands Trace Window Commands Display→Count→Absolute (ALT, -, D, C, A) Selects the absolute mode (the total time elapsed since the trigger) for count information. Command File Command TRA(CE) DIS(PLAY) ABS(OLUTE) See Also "To display absolute or relative counts" in the "Tracing Program Execution" section of the "Debugging Programs"...
  • Page 381 Chapter 9: Window Control Menu Commands Trace Window Commands Copy→Window (ALT, -, P, W) Copies the information currently in the Trace window to the specified listing file. The listing file is specified with the File→Copy Destination... (ALT, F, P) command. Command File Command TRA(CE) COP(Y) DIS(PLAY) See Also...
  • Page 382 Chapter 9: Window Control Menu Commands Trace Window Commands Search→Trigger (ALT, -, R, T) Positions the trigger state at the top of the Trace window. Command File Command TRA(CE) FIN(D) TRI(GGER) Search→State... (ALT, -, R, S) Positions the specified state at the top of the Trace window. Search Trace State Dialog Box Choosing the Search→State...
  • Page 383 Chapter 9: Window Control Menu Commands Trace Window Commands Trace Spec Copy→Specification (ALT, -, T, S) Copies the current trace specification to the listing file. Command File Command TRA(CE) COP(Y) SPE(C) Trace Spec Copy→Destination... (ALT, -, T, D) Names the listing file to which debugger information may be copied. This command opens a file selection dialog box from which you can select the listing file.
  • Page 384 Chapter 9: Window Control Menu Commands WatchPoint Window Commands WatchPoint Window Commands This section describes the following command: Edit... Edit... (ALT, -, E) Registers or deletes watchpoints. Variables can be selected from the another window (in other words, copied to the clipboard) before choosing the Edit...
  • Page 385 Chapter 9: Window Control Menu Commands WatchPoint Window Commands WatchPoint Dialog Box Choosing the Edit... (ALT, -, E) command from the WatchPoint window’s control menu opens the following dialog box: Variable Lets you enter the name of the variable to be registered as a watchpoint.
  • Page 386 Chapter 9: Window Control Menu Commands WatchPoint Window Commands Command File Command WP SET address Registers the specified address as a watchpoint. WP DEL(ETE) address Deletes the specified watchpoint. WP DEL(ETE) ALL Deletes all the current watchpoints. See Also "To monitor a variable in the WatchPoint window" in the "Displaying and Editing Variables"...
  • Page 388 Window Pop-Up Commands...
  • Page 389 Window Pop-Up Commands This chapter describes the commands that can be chosen from the pop-up menus in debugger windows. Pop-Up menus are accessed by clicking the right mouse button in the window. • BackTrace Window Pop-Up Commands • Source Window Pop-Up Commands...
  • Page 390 Chapter 10: Window Pop-Up Commands BackTrace Window Pop-Up Commands BackTrace Window Pop-Up Commands • Source at Stack Level Source at Stack Level For the cursor-selected function in the BackTrace window, this command displays the function call in the Source window.
  • Page 391 Chapter 10: Window Pop-Up Commands Source Window Pop-Up Commands Source Window Pop-Up Commands • Set Breakpoint • Clear Breakpoint • Evaluate It • Add to Watch • Run to Cursor Set Breakpoint Sets a breakpoint on the line containing the cursor. Refer to the Breakpoint→Set at Cursor (ALT, B, S) command.
  • Page 392 Chapter 10: Window Pop-Up Commands Source Window Pop-Up Commands Add to Watch Adds the selected variable (that is, the variable copied to the clipboard) to the WatchPoint window. Refer to the Variable→Edit... (ALT, V, E) command. Run to Cursor Executes the program up to the Source window line containing the cursor. Refer to the Execution→Run to Cursor (ALT, R C) command.
  • Page 394 Other Command File and Macro Commands...
  • Page 395 Other Command File and Macro Commands This chapter describes the commands that are only available in command files, break macros, or buttons. • BEEP • EXIT • FILE CHAINCMD • FILE RERUN • • TERMCOM • WAIT...
  • Page 396 Chapter 11: Other Command File and Macro Commands BEEP BEEP Sounds beep during command file or break macro execution. Command File Command BEEP...
  • Page 397 Chapter 11: Other Command File and Macro Commands EXIT EXIT Exits, or conditionally exits, command file execution. Command File Command EXIT Exits command file execution. EXIT VAR(IABLE) address value Exits command file execution if the variable contains the value. EXIT REG(ISTER) regname value Exits command file execution if the register contains the value.
  • Page 398 Chapter 11: Other Command File and Macro Commands FILE CHAINCMD FILE CHAINCMD Chains command file execution. This command lets you run one command file from another nonrecursively; in other words, control is not returned to the original command file. By contrast, the FILE COMMAND command is recursive; if you use the FILE COMMAND command to run one command file from another, control will be returned to the original command file.
  • Page 399 Chapter 11: Other Command File and Macro Commands FILE RERUN FILE RERUN Starts command file execution over again. This command is useful for looping stimulus files or running a demo or other command file continuously. Command File Command FILE RERUN...
  • Page 400 Chapter 11: Other Command File and Macro Commands No operation. This command may be used to prefix comment lines in command files. Command File Command NOP comments...
  • Page 401 TERMCOM Sends Terminal Interface commands to the HP 64700. The HP 64700 Card Cage contains a low-level Terminal Interface, which allows you to control the emulator’s functions directly. You can use the TERMCOM command to bypass the RTC Interface and send commands directly to the low-level Terminal Interface.
  • Page 402 Chapter 11: Other Command File and Macro Commands TERMCOM Do not use the following Terminal Interface commands with the RTC TERMCOM command: • stty, po, xp: These commands will change the operation of the communications channel, and are likely to hang the RTC Interface. •...
  • Page 403 Chapter 11: Other Command File and Macro Commands WAIT WAIT Inserts wait delays during command file execution. Command File Command WAI(T) MON(ITOR) Waits until MONITOR status. WAI(T) RUN Waits until RUN status. WAI(T) UNK(NOWN) Waits until UNKNOWN status. WAI(T) SLO(W) Waits until SLOW CLOCK status.
  • Page 404 Error Messages...
  • Page 405 • HP 64700 locked by another user • HP 64700 not responding • Incorrect DLL version • Incorrect LAN Address (HP-ARPA, Windows for Workgroups) • Incorrect LAN Address (Novell) • Incorrect LAN Address (WINSOCK) • Internal error in communications driver •...
  • Page 406 Chapter 12: Error Messages • LAN Socket error • Object file format ERROR • Out of DOS Memory for LAN buffer • Out of Windows timer resources • PC is out of RAM memory • Timed out during communications Refer to the end of Chapter 4 for further discussions of specific error conditions.
  • Page 407 Chapter 12: Error Messages Bad RS-232 port name Bad RS-232 port name RS-232 port names must be of the form "COM<number>" where <number> is a decimal number from 1 to the number of communications ports within your Bad RS-422 card I/O address The RS-422 card’s I/O address must be a hexadecimal number from 100H through 3F8H whose last digit is 0 or 8 (example 100, 108, 110).
  • Page 408 Choose "Data Only" in the Load Object File dialog box and try to load the file. If the symbols loaded, but the data fails to load, the problem is in your program code. Call your local HP representative.
  • Page 409 Emulator restricted to real-time runs. Enter the command, "RealTime→Monitor Intrusion→Allowed". • Emulator not executing the monitor. Enter the command, "Execution→Break". Another message often occurs along with this message. View the help information for the other message, if available. Call your local HP representative.
  • Page 410 If you get this message other than during connection, you can try to fix the problem by: • Reducing the length of the RS-232 cable between the PC and the HP 64700. • Reducing the number of tasks running under Windows.
  • Page 411 Unlock button in the error dialog box, check with the other user before unlocking the HP 64700. Note that if the other user is actually using an interface to the HP 64700, an Unlock request will fail. HP 64700 not responding The HP 64700 has not responded within the timeout period.
  • Page 412 Note The directory of the "hosts" file may be different on your system. If "HP Probe" or "DNR" (Domain Name Resolution) is available on your PC, those are consulted first for a mapping between the hostname and the IP address. If the hostname is not found by that method, or if those services are unavailable, the local "hosts"...
  • Page 413 Chapter 12: Error Messages Incorrect LAN Address (Novell) Incorrect LAN Address (Novell) A LAN address can be one of two types: an IP address, or a host name. An IP address consists of four digits separated by dots. Example: 15.6.28.0 A hostname is a name that is related (mapped) to an IP address by a database.
  • Page 414 Chapter 12: Error Messages Internal error in communications driver Internal error in communications driver These types of errors typically occur because other applications have used up a limited amount of some kind of global resource (such as memory or sockets). You usually have to reboot the PC to free the global resources used by the communications driver.
  • Page 415 Chapter 12: Error Messages Interrupt execution (during step) Interrupt execution (during step) The Step dialog box appears when stepping a source line or assembly instruction and the source line or instruction does not execute within the number of milliseconds specified by StepTimerLen in the .INI file of the debugger application.
  • Page 416 Invalid transport name Invalid transport name The transport name chosen does not match any of the possible transport names (RS232C, HP-ARPA, Novell-WP, WINSOCK1.1, W4WG-TCP, or HP-RS422). The transport name can be specified either on the command line with the -t option or in the .INI file:...
  • Page 417 Chapter 12: Error Messages LAN communications error LAN communications error This message may appear after any kind of LAN error. Refer to the documentation for your LAN software for descriptions of the types of problems that can cause LAN errors. LAN MAXSENDSIZE is too small This message indicates you have configured your LAN with a value or MAXSENDSIZE that is less than 100 bytes.
  • Page 418 Unknown construct. Perhaps the construct of your file is unfamiliar to the reader. To respond to this error message, verify the file format, and ensure that the reader can understand the file format in use. If these steps do not solve the problem, call your local HP representative.
  • Page 419 Chapter 12: Error Messages Out of DOS Memory for LAN buffer Out of DOS Memory for LAN buffer This means that there is not enough memory in the lower 1 Mbyte of address space (that is, conventional memory) for the LAN driver to allocate a buffer to communicate with the LAN TSR.
  • Page 420 Chapter 12: Error Messages Out of Windows timer resources Out of Windows timer resources The debugger is not able to acquire the timer resources it needs. There are a limited number of timer resources in Windows. You may be able to free timer resources by closing other applications.
  • Page 421 RS-232 communications or some network problem could have disrupted communications. The timeout period for reading and writing to the HP 64700 is defined by TimeoutSeconds in either the [RS232C], [HP-ARPA], [Novell-WP], or [HP-RS422] section of the b3621.INI file. For example, if you are using the...
  • Page 422 Emulators for some microprocessors take up to one minute per megabyte to perform a memory fill operation. Timeout default values for RTC interfaces shipped from HP are typically 45 seconds. First Workaround. Modify the TimeoutSeconds field (discussed above) to increase the TimeoutSeconds value. Then exit the interface and restart it (to ensure that the new value of TimeoutSeconds is read).
  • Page 424 Part 4 Concept Guide Topics that explain concepts and apply them to advanced tasks.
  • Page 425 Part 4...
  • Page 426 Concepts...
  • Page 427 Concepts This chapter describes the following topics. • Debugger Windows • Compiler/Assembler Specifications • Monitor Programs • Trace Signals and Predefined Status Values...
  • Page 428 Chapter 13: Concepts Debugger Windows Debugger Windows This section describes the following debugger windows: • BackTrace • Button • Device Regs • Expression • • Memory • Register • Source • Status • Symbol • Trace • WatchPoint...
  • Page 429 Chapter 13: Concepts Debugger Windows The BackTrace Window The BackTrace window displays the function associated with the current program counter value and this function’s caller functions in backward order. Applicable addresses are prefixed with module\#linenum information. The current arguments of these functions are also displayed. The BackTrace window is updated when program execution stops at an occurrence of breakpoint, break, or Step command.
  • Page 430 Chapter 13: Concepts Debugger Windows The Button Window The Button window contains user-defined buttons that, when chosen, execute debugger commands or command files. The Button window’s control menu provides the Edit... (ALT, -, E) command which lets you add and delete buttons from the window. See Also "Using Command Files"...
  • Page 431 Chapter 13: Concepts Debugger Windows Device Regs Window The Device Regs window shows all of the internal registers that are used to control various devices. Each register is represented by a row which holds a mnemonic name, a current value, and a description of the register contents. The registers may be edited by either single clicking or double-clicking on the value.
  • Page 432 Chapter 13: Concepts Debugger Windows Device Register Dialogs When a register has bit-fields, a dialog will pop-up and the register value may be edited by changing the whole value or by editing individual bit-fields. When editing in the dialog box, a carriage-return is the same as choosing the OK button.
  • Page 433 Chapter 13: Concepts Debugger Windows The Expression Window The Expression window displays the results of the EVALUATE commands in command files or break macros. When a variable name is specified with the EVALUATE command, the Expression window displays the evaluation of the variable. When a quoted string of ASCII characters is specified with the EVALUATE command, the Expression window displays the string.
  • Page 434 Chapter 13: Concepts Debugger Windows The I/O Window The I/O window displays the contents of the I/O locations. You can modify the contents of I/O locations by double-clicking on the value, using the keyboard to type in the new value, and pressing the Enter key. The I/O window contents are updated periodically when the processor is running the user program.
  • Page 435 Chapter 13: Concepts Debugger Windows The Memory Window The Memory window displays memory contents. The Memory window has control menu commands that let you change the format of the memory display and the size of the locations displayed or modified. When the absolute (single-column) format is chosen, symbols corresponding to addresses are displayed.
  • Page 436 Chapter 13: Concepts Debugger Windows See Also "Displaying and Editing Memory" in the "Debugging Programs" chapter. "Memory Window Commands" in the "Window Control Menu Commands" chapter. The Register Window The Register window displays contents of registers. You can modify register contents by double-clicking on the register value, using the keyboard to type in the new value, and pressing the Enter key.
  • Page 437 Chapter 13: Concepts Debugger Windows A temporary break from the user program into the monitor program must occur in order for the debugger to update or modify register contents. If it’s important that the user program execute without these types of interruptions, you should disallow monitor intrusion.
  • Page 438 Chapter 13: Concepts Debugger Windows The Source Window The Source window displays source files, optionally with disassembled instructions intermixed. The Source window contains a cursor whose position is used when setting or deleting breakpoints or break macros or when running the program up to a certain line.
  • Page 439 The breakpoint marker, "BP", appears at the beginning of the breakpoint lines or break macro lines. Execution The accessed (executed) lines are highlighted when Coverage program execution coverage is enabled. This is not available when using the HP 64170 emulation memory board.
  • Page 440 Chapter 13: Concepts Debugger Windows Break Macro Decimal points following line numbers or addresses Lines indicate break macro lines. Note When programs are stored in target system memory and the emulator is running in real-time, source code cannot be displayed. See Also "Loading and Displaying Programs", "Stepping, Running, and Stopping the Program",...
  • Page 441 Chapter 13: Concepts Debugger Windows The Status Window The Status window shows: • Emulator status. • Trace status. • Scope of the current program counter value. • Progress of symbols being loaded from a file. • Last five asynchronous messages from the emulator. Emulation Processor Status Messages EMULATION RESET The emulation processor is being held in the reset state by the emulator.
  • Page 442 Chapter 13: Concepts Debugger Windows • Any on-screen information that would be periodically updated by temporarily interrupting user program execution (target system memory or register contents, for example) is disabled. WAITING FOR TARGET RESET The emulation processor is waiting for a RESET signal from the target system.
  • Page 443 Chapter 13: Concepts Debugger Windows WRITE TO ROM BREAK Program execution has stopped due to a write to location mapped as ROM. These types of breaks must be enabled in the emulator configuration. ACCESS TO GUARD BREAK Program execution has stopped due to a write to a location mapped as guarded memory.
  • Page 444 Chapter 13: Concepts Debugger Windows The Symbol Window The Symbol window displays information on the following types of symbols: • Modules • Functions • Global symbols • Local symbols • Global Assembler symbols • Local Assembler symbols • User-defined symbols The Symbol window has control menu commands that let you display various types of symbols, add or delete user-defined symbols, copy Symbol window information, or search for symbols that contain a particular string.
  • Page 445 The << and >> buttons let you move between the multiple frames of trace data that are available with newer analyzers for the HP 64700. The type of state can be a sequence level branch (SEQ), a state that satisfies the prestore condition (PRE), or a normal state that matches the store conditions (in which case the type field is empty).
  • Page 446 Chapter 13: Concepts Debugger Windows can be selected by using the Trace window control menu’s Display→Mixed Mode (ALT, -, D, M) command. In the source/bus cycle mixed display mode, each source code line is immediately followed by the corresponding bus cycles.
  • Page 447 Chapter 13: Concepts Debugger Windows The WatchPoint Window The WatchPoint window displays the contents of variables that have been registered with the Variable→Edit... (ALT, V, E) command or with the Edit... (ALT, -, E) command in the WatchPoint window’s control menu. The contents of dynamic variables are displayed only when the current program counter is in the function in which the variable is declared.
  • Page 448 • Microtec MCC68K Compiler • Microtec ASM68K Assembler • HP AxLS Compiler • HP AxLS Assembler Assembly Language Source File Display The IEEE-695 object files do not contain assembly language source file information. Instead, memory contents are disassembled.
  • Page 449 Chapter 13: Concepts Compiler/Assembler Specifications Pragma Statement and Debugger Display When a "pragma" statement is used to describe an assembly language instruction in C source files, the source information is generated as follows in the IEEE-695 object files: • A pragma instruction has a single line number. •...
  • Page 450 Chapter 13: Concepts Compiler/Assembler Specifications Compiling Programs with MCC68K Compile the source files with the mcc68k command. Assemble the source files with the asm68k command. Link the object files with the lnk68k command. Required Compiler/Assembler/Linker Compiler Microtec MCC68K Compiler Assembler Microtec ASM68K Assembler Linker Microtec LNK68K Linker...
  • Page 451 Compile the source files with the cc68000 command. Assemble the source files with the as68k command. Link the object files with the ld68k command. Required Compiler/Assembler/Linker Compiler HP AxLS CC68000 Compiler Assembler HP AxLS AS68K Assembler Linker HP AxLS LD68K Linker...
  • Page 452 Chapter 13: Concepts Compiler/Assembler Specifications Compiling For compiling, use the cc68000 command in your HP AxLS C Compiler with the following option switches: -Wc,-F Disables register variables. Note The -Wc,-F option allows the debugger to display arguments during backtracing. Assembling For assembling, use the as68k command in your HP AxLS Assembler without any option switch.
  • Page 453 Monitor Program Options The emulation monitor program is a program that the emulation microprocessor executes as directed by the HP 64700 system controller. The emulation monitor program gives the system controller access to the target system. For example, when you modify target system memory, the system controller writes a command code to a communications area and switches, or breaks, emulation processor execution into the monitor program.
  • Page 454 Chapter 13: Concepts Monitor Programs The emulation monitor program can also execute out of the same memory system as user programs. This memory system is known as foreground memory and consists of emulation memory and target system memory. A monitor program executing out of foreground memory is known as a foreground monitor program.
  • Page 455 Monitor Programs The starting address can be specified on a 2 Kbyte boundary starting from 800H. If you’re using the HP 64170 emulation memory board with 1 Mbyte memory modules, the starting address must be specified on an 8 Kbyte boundary.
  • Page 456 Chapter 13: Concepts Monitor Programs Assembling and Linking the Foreground Monitor with AxLS The foreground monitor can be assembled and linked with an HP Assembler/Linker. To assemble the foreground monitor, enter: as68k -L fgmon.s > fgmon.lst To link the foreground monitor, enter: ld68k -c fgmon.k -L >...
  • Page 457 Chapter 13: Concepts Trace Signals and Predefined Status Values Trace Signals and Predefined Status Values This section describes how emulation analyzer trace signals are assigned to microprocessor address bus, data bus, and control signals. Emulation Analyzer Trace Signals Trace Signals Signal Name Signal Description -------...
  • Page 458 Part 5 Installation Guide Instructions for installing the product.
  • Page 459 Part 5...
  • Page 460 Installing the Debugger...
  • Page 461 This chapter shows you how to install the Real-Time C Debugger. • Requirements • Before Installing the Debugger • Step 1. Connect the HP 64700 to the PC • Step 2. Install the debugger software • Step 3. Start the debugger •...
  • Page 462 • 3 Megabytes available disk space. • Serial port, HP 64037 RS-422 port, or Novell LAN with Lan Workplace for DOS or Microsoft Lan Manager with HP ARPA Services. • Revision A.04.00 or greater of HP 64700 system firmware. The last step...
  • Page 463 • If the HP 64700 is to communicate with the PC via LAN: Make sure the HP 64700 LAN interface is installed (see the "HP 64700 Series Installation/Service" manual). Install the LAN card into the PC, and install the required PC networking software.
  • Page 464 Step 1. Connect the HP 64700 to the PC You can connect the HP 64700 to an RS-232 serial port on the PC, the Local Area Network that the PC is on, or an HP 64037 RS-422 interface that has been installed in the PC.
  • Page 465 HP 24542M 9-pin to 25-pin cable or an HP 13242N 25-pin to 25-pin cable). If you want to build your own RS-232 cable, follow one of the pin-outs for HP cables shown in the following figure. You can also use an RS-232C printer cable, but you must set HP 64700 configuration switch 4 to 1.
  • Page 466 You should now be able to press the Enter key in the Terminal window to see the HP 64700’s Terminal Interface prompt (for example, "R>", "M>", or "U>". The "->" prompt indicates the present firmware does not match the emulator probe, or there is no probe connected).
  • Page 467 Administrator. You can change the Gateway Address with the "lan -g <new gateway address>" command. The "lan -s" line will be shown if you are using the HP 64700A, and will not be shown if you are using the HP 64700B. If this line is not shown, the Subnet Mask is automatically configured.
  • Page 468 "lan -p 6470" command. The Internet Address and any other LAN parameters you change are stored in nonvolatile memory and will take effect the next time the HP 64700 is powered off and back on again.
  • Page 469 Chapter 14: Installing the Debugger Step 1. Connect the HP 64700 to the PC Set the HP 64700 configuration switches for LAN communication. Switch 16 must be set to one (1) indicating that a LAN connection is being made. Switch 15 should be zero (0) if you are connecting to the BNC connector or set to one (1) if a 15 pin AUI connection is made.
  • Page 470 HP 64700’s Terminal Interface prompt (for example, "R>", "M>", "U>", etc.). If you see the prompt, you have verified LAN communication. If you cannot connect to the HP 64700’s IP address, refer to "If you cannot verify LAN communication".
  • Page 471 Step 1. Connect the HP 64700 to the PC To connect via RS-422 Before you can connect the HP 64700 to the PC via RS-422, the HP 64037 RS-422 Interface must have already been installed into the PC. Set the HP 64700 configuration switches for RS-422 communication.
  • Page 472 The most common type of data communications configuration problem involves the configuration of the HP 64700 as a DCE or DTE device and the selection of the RS-232 cable. If you are using the wrong type of cable for the device selected, no prompt will be displayed.
  • Page 473 You can use CTRL+c to interrupt the repetitive command and get the Terminal Interface prompt. It’s also possible for there to be a problem with the HP 64700 firmware while the LAN interface is still up and running. In this case, you must turn OFF...
  • Page 474 B3621.INI file because it will be overwritten by the installation process. Start MS Windows in the 386 enhanced mode. Insert the 68302 REAL-TIME C DEBUGGER Disk 1 of 2 into floppy disk drive A or B. Choose the File→Run... (ALT, F, R) command in the Windows Program Manager.
  • Page 475 You will be asked to enter your user ID. This information is important if the HP 64700 is on the LAN and may be accessed by other users. It tells other users who is currently using, or who has locked, the HP 64700. This information can be modified while using the Real-Time C Debugger by choosing the Settings→Communication...
  • Page 476 Chapter 14: Installing the Debugger Step 2. Install the debugger software You will be asked to select the type of connection to be made to the HP 64700. This information can be modified while using the Real-Time C Debugger by choosing the Settings→Communication... (ALT, S, C) command.
  • Page 477 Chapter 14: Installing the Debugger Step 3. Start the debugger Step 3. Start the debugger If the "HP Real-Time C Debugger" group box is not opened, open it by double-clicking in the icon. Double-click the "M68302 Real-Time C Debugger" icon.
  • Page 478 If the switches are in the correct position and you still do not get a prompt when you press return, check the following: Turn off power to the HP 64700 and then turn it on again. Press return to see if you get a prompt.
  • Page 479 Step 3. Start the debugger • If you wish to build your own RS-232 cable, refer to "To connect via RS-232" in the paragraph titled, "Step 1. Connect the HP 64000 to the PC" earlier in this chapter. • When using certain RS-232 cards, connecting to an RS-232 port where the HP 64700 is turned OFF (or not connected) will halt operation of the PC.
  • Page 480 If the emulator still does not respond to a "ping," you need to verify the IP address and subnet mask of the HP 64700. To do this, connect the HP 64700 to a terminal (or to the Terminal application on the PC), change the emulator’s switch settings so it is connected to RS-232, and enter the "lan"...
  • Page 481 Occasionally the emulator or the PC will "lock up" the LAN due to excessive network traffic. If this happens, all you can do is turn OFF power to the HP 64700 or PC and turn it back ON, again. If this happens two frequently, you can try placing a gateway between the emulator/PC and the rest of your network.
  • Page 482 If the switches are in the correct position and you still do not get a prompt when you hit return, try turning OFF the power to the HP 64700 and tuning it ON again. If you still don’t get a prompt, make sure the HP 17355M RS-422 cable is...
  • Page 483 • Choose the Help→About Debugger/Emulator... (ALT, H, D) command. The version information under HP 64700 Series Emulation System must show A.04.00 or greater. If the version number is less than A.04.00, you must update your HP 64700 system firmware as described in the...
  • Page 484 Chapter 14: Installing the Debugger Optimizing PC Performance for the Debugger Optimizing PC Performance for the Debugger The Real-Time C Debugger is a memory and I/O intensive Windows program. Slow user interface performance may be caused by many things: • Underpowered PC -- The Real-Time C Debugger requires an IBM compatible or NEC PC with an 80486 class microprocessor, 8 megabytes of memory, and 20 megabytes of MS Windows swap space.
  • Page 486 Installing/Updating HP 64700 Firmware...
  • Page 487 This chapter shows you how to install or update HP 64700 firmware. Note If you are using an HP 64700A, it must contain the optional Flash EPROM memory card before you can install or update HP 64700 system firmware. Flash EPROM memory is standard in the HP 64700B card cage.
  • Page 488 Step 1. Connect the HP 64700 to the PC Set the COMM CONFIG switches for RS-232C communication. To do this, locate the DIP switches on the HP 64700 rear panel, and set them as shown below. Notice that switches 12 and 13 are set to 1 and 0, respectively. This sets the RTS/CTS hardware handshake, which is needed to make sure all characters are processed.
  • Page 489 You should now be able to press the Enter key in the Terminal window to see the HP 64700’s Terminal Interface prompt (for example, p>, R>, M>, and U>. A → prompt indicates the present firmware does not match the emulator probe, or there is no probe connected).
  • Page 490 1.5 Mbytes of disk space. Start MS Windows in the 386 enhanced mode. Insert the HP 64700 EMUL/ANLY FIRMWARE Disk 1 of 2 into floppy disk drive A or B. Choose the File→Run... (ALT, F, R) command in the Windows Program Manager.
  • Page 491 Chapter 15: Installing/Updating HP 64700 Firmware Step 2. Install the firmware update utility Wait until the Setup Exit Message dialog box appears. This indicates installation of the firmware update utility is complete. After completing the installation, use the editor of your choice and edit the C:\CONFIG.SYS file to include these lines:...
  • Page 492 Chapter 15: Installing/Updating HP 64700 Firmware Step 2. Install the firmware update utility If you are using COM3 or COM4 port to update your firmware, you need to edit the <installation_path>\TABLES\64700TAB file. Either add another line or modify one of the existing lines. For example:...
  • Page 493 Step 3. Run PROGFLASH to update HP 64700 firmware Start MS Windows in the 386 enhanced mode. If the "HP 64700 Firmware Utility" group box is not opened, open it by double-clicking the icon. Double-click the "PROGFLASH" icon. (You can abort the PROGFLASH command by pressing CTRL+c.)
  • Page 494 Step 3. Run PROGFLASH to update HP 64700 firmware The PROGFLASH command downloads code from files on the host computer into Flash EPROM memory in the HP 64700. During this download, you will see messages similar to the following: Rebooting HP64700...with init -r Downloading flash programming code: ’/hp64700/lib/npf.X’...
  • Page 495 Chapter 15: Installing/Updating HP 64700 Firmware Step 4. Verify emulator performance Step 4. Verify emulator performance • Do the performance verification procedure shown in the Installation/Service/Terminal Interface User’s Guide.
  • Page 496 Glossary Defines terms that are used in the debugger help information. analyzer An instrument that captures data on signals of interest at discreet periods. The emulation bus analyzer captures emulator bus cycle information synchronously with the processor’s clock signal. arm condition A condition that enables the analyzer. The analyzer is always armed unless you set the analyzer up to be armed by a signal received on the BNC port;...
  • Page 497 Glossary count condition Specifies whether time or the occurrences of a particular state are counted for each state in the trace buffer. embedded microprocessor system The microprocessor system that the emulator plugs into. emulation memory Memory provided by the emulator that can be used in place of memory in the target system.
  • Page 498 Glossary macro Refers to a break macro, which is a breakpoint followed by any number of macro commands (which are the same as command file commands). monitor A program, executed by the emulation microprocessor (as directed by the emulation system controller), that gives the emulator access to target system memory, microprocessor registers, and other target system resources.
  • Page 499 Glossary address and data values) when specifying trigger and store conditions. The status values defined for the 68302 emulator are listed under "Predefined Status Values" at the end of Chapter 13, "Concepts." store condition Specifies which states get stored in the trace buffer.
  • Page 500 Index abort, during object file or memory load, 326 absolute count information, displaying, 181, 381 access size, target memory, 75, 116 Add to Watch command, 393 addresses, searching, 129, 366 analyzer, 497-500 trace signals, 458 editing the trace specification, 195, 268 halting, 179, 281 repeating last trace, 179, 282 setting up with "Find Then Trigger", 186, 272-275...
  • Page 501 Index background memory, 497-500 background monitor, 454 program, 497-500 selecting, 83, 307-310 background operation, tracing, 324-325 BackTrace window, 430 displaying source files, 391 Bad RS-232 port name, 408 Bad RS-422 card I/O address, 408 baud rate, RS-232, 311 baud rate, RS-422, 311 beep, sounding from command file, 397 BERR signal (target), enabling or disabling, 71 BGACK signal (target), enabling or disabling, 70...
  • Page 502 Index breakpoints deleting, 35, 147, 152, 249 disabling and enabling, 147 listing, 148, 254-255 preventing new breakpoints, 152 setting, 33, 146, 248 specifying TRAP instruction for, 74 bus arbitration cycles, identifying in the trace, 180 bus cycles only, displaying, 380 bus cycles, displaying, 180 Button window, 431 editing, 66, 339...
  • Page 503 Index command line options, 57-58, 65 for connection and transport, 311 command summary, 202 comments in command files, 401 communications (emulator), setting up, 311-313 CONFIG.SYS file, 491-493 configuration, emulator, 300-303 saving and loading, 87-88 connection problems LAN, 481 RS-232, 478 RS-422, 483 connection, command line option, 311 Continuous Update (ALT, -, U) command, 342...
  • Page 504 Index data bus width, selecting, 74 DCE or DTE selection and RS-232 cable, 473 debugger arranging icons in window, 328 cascaded windows, 328 exiting, 50, 58, 232 exiting locked, 233 installing software, 475-477 opening windows, 60, 329-330 overview, 4 starting, 25, 57, 478-483 startup options, 58 tiled windows, 328 decimal values, how to enter, 209...
  • Page 505 Bad RS-422 card I/O address, 408 Could not open initialization file, 408 Could not write Memory, 409 Error occurred while processing Object file, 410 general RS-232 communications error, 411 general RS-422 communications error, 411 HP 64700 locked by another user, 412...
  • Page 506 Index HP 64700 not responding, 412 Incorrect DLL version, 412 Incorrect LAN Address (HP-ARPA, Windows for Workgroups), 413 Incorrect LAN Address (Novell), 414 Incorrect LAN Address (WINSOCK), 414 Internal error in communications driver, 415 Internal error in Windows, 415 Interrupt execution (during run to caller), 415...
  • Page 507 File→Save Debug... (ALT, F, S) command, 228 File→Save Emulator Config... (ALT, F, V) command, 230 firmware update utility, installing, 491-493 firmware update, connecting the HP 64700 to the PC, 489-490 firmware version information, 331 firmware, ensuring performance after update, 496...
  • Page 508 RS-232, 465 connecting via RS-422, 472 environment variable, 491-493 HP 64700 firmware update utility, installing, 491-493 HP 64700 firmware update, connecting the HP 64700 to the PC, 489-490 HP 64700 firmware ensuring performance after update, 496 using PROGFLASH to update, 494-495...
  • Page 509 98-122 important concepts, 98 in-line assembler, 299 Incorrect DLL version, 412 Incorrect LAN Address (HP-ARPA, Windows for Workgroups), 413 Incorrect LAN Address (Novell), 414 Incorrect LAN Address (WINSOCK), 414 .INI file, 311 installation path, 475-477...
  • Page 510 LAN communications error, 418 LAN connection problems, 481 LAN MAXSENDSIZE is too small, 418 LAN socket error, 418 LAN, connecting HP 64700, 468 levels, trace sequence, 191, 195, 276-279, 290 limitations, Symbol window, 445 line (source file), running until, 43, 142, 236...
  • Page 511 Index memory abort during load, 326 copying, 159, 351 displaying, 156 editing, 158 loading from stored file, 355 mapping, 79-81, 304-306 mapping for demo program, 29-30 modifying a range, 161, 352 searching for a value or string in, 162 storing to a binary file, 356 messages, error, 406 microprocessor, resetting, 144, 247 mixed display mode, 126, 361, 379, 449...
  • Page 512 327 patterns, trace, 186, 191, 272-279, 283-287 PC is out of RAM memory, 421 connecting HP 64700, 465-474 locating in Source window, 367 performance (PC), optimizing for the debugger, 485 performance verification after firmware update, 496...
  • Page 513 RS-232 connections, 478 return (function), running until, 41, 142, 237 ROM, enabling or disabling breaks on writes to, 73 RS-232 cable and DCE or DTE selection, 473 connection problems, 478 connections restriction, 478 connecting HP 64700, 465...
  • Page 514 Index RS-422 connection problems, 483 connecting HP 64700, 472 RTC Emulation Connection dialog box, 311 Run to Cursor command, 393 screen fonts, changing, 26 search path for source files, 128, 368 Search→Address... (ALT, -, R, A) command, 366 Search→Current PC (ALT, -, R, C) command, 367 Search→Function...
  • Page 515 Index Settings→Symbols→Case Sensitive→ON (ALT, S, S, C, O) command, 323 Settings→Tabstops... (ALT, S, T) command, 322 single-step one line, 36 software, installing debugger, 475-477 Source at Stack Level command, 391 source directory, 332 source display mode, toggling, 361-362 source file line, running until, 43, 142, 236 source files displaying, 32, 127, 362 displaying from BackTrace window, 391...
  • Page 516 Index strings displaying symbols containing, 138, 375 searching memory for, 162, 349 searching source files, 130, 363 structures (C operators), 213 subnet mask, 468, 481 subroutines, stepping over, 241 supervisor stack pointer, setting up the reset value, 27-28 symbols, 210-212 Symbol window, 445 copying information, 374-375 searching for strings, 375...
  • Page 517 Index trace specification copying, 384 editing, 195, 268 loading, 198 specifying the destination, 384 storing, 197 trace state, 497-500 searching for in Trace Window, 383 TRACE vector, setting up, 457 Trace window, 446 copying information, 382 displaying absolute count information, 381 displaying bus cycles only, 380 displaying relative count information, 381 displaying source only, 380...
  • Page 518 Index unary minus operator, 213 unions (C operators), 213 unlock emulator, 311 user ID, 311, 475-477 user name, 311 user programs, loading, 125 user-defined symbols creating, 136, 376 deleting, 138, 377-378 displaying, 137, 374 Utilities→Copy... (ALT, -, U, C) command, 351 Utilities→Fill...
  • Page 519 Index Window→1-9 (ALT, W, 1-9) command, 329 Window→Arrange Icons (ALT, W, A) command, 328 Window→Cascade (ALT, W, C) command, 328 Window→More Windows... (ALT, W, M) command, 330 Window→Tile (ALT, W, T) command, 328 windows (debugger), opening, 329-330 windows of program execution, tracing, 195 writes to ROM, enabling or disabling breaks on, 73...
  • Page 520 This Hewlett-Packard system product is warranted against defects in materials and workmanship for a period of 90 days from date of installation. During the warranty period, HP will, at its option, either repair or replace products which prove to be defective.
  • Page 521 No other warranty is expressed or implied. HP specifically disclaims the implied warranties of merchantability and fitness for a particular purpose.
  • Page 522 Safety Summary of Safe Procedures The following general safety precautions must be observed during all phases of operation, service, and repair of this instrument. Failure to comply with these precautions or with specific warnings elsewhere in this manual violates safety standards of design, manufacture, and intended use of the instrument. Hewlett-Packard Company assumes no liability for the customer’s failure to comply with these requirements.
  • Page 523 Do Not Service Or Adjust Alone Do not attempt internal service or adjustment unless another person, capable of rendering first aid and resuscitation, is present. Do Not Substitute Parts Or Modify Instrument Because of the danger of introducing additional hazards, do not install substitute parts or perform any unauthorized modification of the instrument.
  • Page 524 Safety Symbols Used In Manuals The following is a list of general definitions of safety symbols used on equipment or in manuals: Instruction manual symbol: the product is marked with this symbol when it is necessary for the user to refer to the instruction manual in order to protect against damage to the instrument.
  • Page 525 Caution The Caution sign denotes a hazard. It calls your attention to an operating procedure, practice, condition, or similar situation, which, if not correctly performed or adhered to, could result in damage to or destruction of part or all of the product. Warning The Warning sign denotes a hazard.

Table of Contents