1. Manuals
  2. Brands
  3. HP Manuals
  4. Computer Hardware
  5. 64751
  6. User manual

HP 64751 User Manual

Graphical user interface
Hide thumbs
1
2
3
4
5
6
Table Of Contents
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
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
Table of Contents

Advertisement

Quick Links

Download this manual
User's Guide for the Graphical User Interface
HP 64751 68340 Emulator
HP 64704 Analyzer

Advertisement

Table of Contents
loading

Related Manuals for HP 64751

Summary of Contents for HP 64751

  • Page 1 User’s Guide for the Graphical User Interface HP 64751 68340 Emulator HP 64704 Analyzer...
  • Page 2 Hewlett-Packard Company. The information contained in this document is subject to change without notice. HP is a trademark of Hewlett-Packard Company. Microtec is a registered trademark of Microtec Research Inc. MS-DOS is a trademark of Microsoft Corporation.
  • Page 3 Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR 52.227-19(c)(1,2). 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.
  • Page 4 The emulator can be used with the HP 64704 Emulation Bus Analyzer or the HP 64794 Deep Memory Emulation Bus Analyzer which capture 80 channels of emulation processor bus cycle information synchronously with the processor’s...
  • Page 5 Start and stop up to 16 emulators at the same time (up to 32 if modifications are made). • Use the analyzer in one HP 64700 to arm (that is, activate) the analyzers in other HP 64700 card cages or to cause emulator execution in other HP 64700 card cages to break.
  • Page 6 In This Book This book describes the Graphical User Interface and the Softkey Interface when used with the HP 64751 68340 emulator and the HP 64704 analyzer. It is organized into five parts whose chapters are described below. Part 1. Quick Start Guide Chapter 1 presents an overview of emulation and analysis and quickly shows you how to use the emulator and analyzer.

  • Page 7: Table Of Contents

    Contents Part 1 Quick Start Guide 1 Getting Started The Emulator/Analyzer Interface — At a Glance The Softkey Interface Softkey Interface Conventions The Graphical User Interface Graphical User Interface Conventions The Getting Started Tutorial Step 1. Start the demo Step 2: Display the program in memory Step 3: Run from the transfer address Step 4: Step high-level source lines Step 5: Display the previous mnemonic display...
  • Page 8 Step 3. Select the emulator clock source Step 4. Plug the 68340 PGA emulator probe into the target system Step 5. Turn ON power 3 Starting and Exiting HP 64700 Interfaces Starting the Emulator/Analyzer Interface To start the emulator/analyzer interface...
  • Page 9 Contents 4 Entering Commands Using Menus, the Entry Buffer, and Action Keys To choose a pulldown menu item using the mouse (method 1) To choose a pulldown menu item using the mouse (method 2) To choose a pulldown menu item using the keyboard To choose popup menu items To place values into the entry buffer using the keyboard To copy-and-paste to the entry buffer...
  • Page 10 Contents Forwarding Commands to Other HP 64700 Interfaces To forward commands to the high-level debugger To forward commands to the software performance analyzer 5 Configuring the Emulator Using the Configuration Interface To start the configuration interface To modify a configuration section...
  • Page 11 Contents Configuring the Emulator Pod To set the reset values of the SSP and PC To specify the user memory access size Setting the Debug/Trace Options To enable/disable breaks on writes to ROM To trace background cycles 6 Using the Emulator Using the Emulator Configuration Registers To view the SIM register differences To synchronize to the 68340 SIM registers...
  • Page 12 Contents Executing User Programs To run programs from the current PC To run programs from an address To run programs from the transfer address To run programs from reset To run programs until an address To stop (break from) user program execution To step high-level source lines To step assembly-level instructions To reset the emulation processor...
  • Page 13 Contents Changing the Interface Settings To set the source/symbol modes To set the display modes Using System Commands To set UNIX environment variables To display the name of the emulation module To display the event log To display the error log To edit files To copy information to a file or printer To open a terminal emulation window...
  • Page 14 Contents Qualifying Trigger and Store Conditions To qualify the trigger state and position To trigger on a number of occurrences of some state To qualify states stored in the trace To prestore states before qualified store states To change the count qualifier To trace until the analyzer is halted To break emulator execution on the analyzer trigger Using the Sequencer...
  • Page 15 Contents 8 Making Software Performance Measurements Activity Performance Measurements To set up the trace command for activity measurements To initialize activity performance measurements To interpret activity measurement reports Duration Performance Measurements To set up the trace command for duration measurements To initialize duration performance measurements To interpret duration measurement reports Running Measurements and Creating Reports...
  • Page 16 Contents 10 Setting X Resources To modify the Graphical User Interface resources To use customized scheme files To set up custom action keys To set initial recall buffer values To set up demos or tutorials Part 3 Reference 11 Emulator/Analyzer Interface Commands How Pulldown Menus Map to the Command Line How Popup Menus Map to the Command Line Syntax Conventions...
  • Page 17 Contents reset SEQUENCING specify step stop_trace store --SYMB-- sync_sim_registers trace TRIGGER wait WINDOW 12 Error Messages Graphical/Softkey Interface Messages - Unnumbered Graphical/Softkey Interface Messages - Numbered Terminal Interface Messages Emulator Messages 68340 Emulator Messages General Emulator and System Messages Analyzer Messages 13 Specifications and Characteristics Emulator Specifications and Characteristics Electrical...
  • Page 18 15 Installation Installing Hardware Step 1. Connect the Emulator Probe Cables Step 2. Install Boards into the HP 64700 Card Cage Step 3. Install emulation memory modules on emulator probe Step 4. Plug the emulator probe into the demo target system Step 5.
  • Page 19 Contents Installing Sun SPARCsystem Software Step 1. Install the software from the media Step 2. Start the X server and OpenWindows Step 3. Set the necessary environment variables Step 4. Verify the software installation Step 5. Map your function keys Verifying the Installation Step 1.

  • Page 21: Part 1 Quick Start Guide

    Part 1 Quick Start Guide A one-glance overview of the product and a few task instructions to help you get comfortable.
  • Page 22 Part 1...

  • Page 23: Getting Started

    Getting Started...

  • Page 24: The Emulator/Analyzer Interface - At A Glance

    Chapter 1: Getting Started The Emulator/Analyzer Interface — At a Glance When an X Window System that supports OSF/Motif interfaces is running on the host computer, the emulator/analyzer interface is the Graphical User Interface which provides pull-down and pop-up menus, point and click setting of breakpoints, cut and paste, on-line help, customizable action keys and pop-up recall buffers, etc.

  • Page 25: Softkey Interface Conventions

    Chapter 1: Getting Started Status line. Displays the emulator and analyzer status. Also, when error and status messages occur, they are displayed on the status line in addition to being saved in the error log. Command line. Commands are entered on the command line by pressing softkeys (or by typing them in) and executed by pressing the Return key.

  • Page 26: The Graphical User Interface

    Chapter 1: Getting Started The Graphical User Interface Menu bar Action keys Entry buffer Entry buffer recall button. Display area. Scroll bar. Status line. Command line. Command line entry area. Softkey pushbuttons Command buttons. Includes command Cursor buttons for command line area recall button.
  • Page 27 Chapter 1: Getting Started Entry Buffer. Wherever you see "()" in a pulldown menu, the contents of the entry buffer are used in that command. You can type values into the entry buffer, or you can cut and paste values into the entry buffer from the display area or from the command line entry area.

  • Page 28: Graphical User Interface Conventions

    Chapter 1: Getting Started The command Recall button allows you to recall previous or predefined commands. When you click on the command Recall button, a dialog box appears that allows you to select a command. • Cursor buttons for command line area control. Allow you to move the cursor in the command line entry area forward or backward, clear to the end of the command line, or clear the whole command line entry area.
  • Page 29 Mouse Button Bindings and Description Bindings: Generic Button Name Description HP 9000 SPARCsystem paste left left Paste from the display area to the entry buffer. command paste middle...
  • Page 30 Chapter 1: Getting Started The following tables show the default keyboard bindings. Keyboard Key Bindings Generic Key Name HP 9000 Sun SPARCsystem menu select extend char extend char insert insert char insert char delete delete char delete char left-arrow left arrow...

  • Page 31: The Getting Started Tutorial

    • The HP 64751 emulator and HP 64704 analyzer are installed into the HP 64700 Card Cage, the HP 64700 is connected to the host computer, and the emulator/analyzer interface software has been installed as outlined in the "Installation" chapter.

  • Page 32: Step 1. Start The Demo

    "platformScheme" resource setting in the "Xdefaults.emul" file. For example, if the Graphical User Interface will be run on a HP 9000 computer and displayed on a Sun SPARCsystem computer, change the platform scheme to "SunOS".

  • Page 33: Step 2: Display The Program In Memory

    Chapter 1: Getting Started Step 2: Display the program in memory Step 2: Display the program in memory 1 If the symbol "main" is not already in the entry buffer, move the mouse pointer to the entry buffer (notice the flashing I-beam cursor) and type in "main". 2 Choose Display→Memory→Mnemonic ().

  • Page 34: Step 3: Run From The Transfer Address

    Chapter 1: Getting Started Step 3: Run from the transfer address Step 3: Run from the transfer address The transfer address is the entry address defined by the software development tools and included with the program’s symbol information. • Click on the Run Xfer til () action key. Or, using the command line, enter: run from transfer_address until main <RETURN>...

  • Page 35: Step 4: Step High-Level Source Lines

    Chapter 1: Getting Started Step 4: Step high-level source lines Step 4: Step high-level source lines You can step through the program by high-level source lines. The emulator executes as many instructions as are associated with the high-level program source lines.

  • Page 36: Step 5: Display The Previous Mnemonic Display

    Chapter 1: Getting Started Step 5: Display the previous mnemonic display Step 5: Display the previous mnemonic display • Click on the Disp Src Prev action key. Or, using the command line, enter: display memory mnemonic previous_display <RETURN> This command is useful, for example, when you have stepped into a function that you do not wish to look at—you can display the previous mnemonic display and run until the source line that follows the function call.

  • Page 37: Step 6: Run Until An Address

    Chapter 1: Getting Started Step 6: Run until an address Step 6: Run until an address When displaying memory in mnemonic format, a selection in the popup menu lets you run from the current program counter address until a specific source line. •...

  • Page 38: Step 7: Display Data Values

    Chapter 1: Getting Started Step 7: Display data values Step 7: Display data values 1 Position the mouse pointer over "num_checks" in the source line that reads "num_checks++;" and click the paste mouse button (notice "num_checks" is cut and pasted into the entry buffer). 2 Click on the Disp Var () action key.

  • Page 39: Step 8: Display Registers

    Chapter 1: Getting Started Step 8: Display registers Step 8: Display registers You can display the contents of the processor registers. • Choose Display→Registers→BASIC. Or, using the command line, enter: display registers <RETURN>...

  • Page 40: Step 9: Step Assembly-Level Instructions

    Chapter 1: Getting Started Step 9: Step assembly-level instructions Step 9: Step assembly-level instructions You can step through the program one instruction at a time. • To step one instruction from the current program counter, click on the Step Asm action key.

  • Page 41: Step 10: Trace The Program

    Chapter 1: Getting Started Step 10: Trace the program Step 10: Trace the program When the analyzer traces program execution, it looks at the data on the emulation processor’s bus and control signals at each clock cycle. The information seen at a particular clock cycle is called a state.
  • Page 42 Chapter 1: Getting Started Step 10: Trace the program Notice that now the message on the status line is "Emulation trace complete". This shows the trigger state has been found and the analyzer trace memory has been filled. 5 To view the captured states, choose Display→Trace. Or, using the command line, enter: display trace <RETURN>...

  • Page 43: Step 11: Display Memory At An Address In A Register

    Chapter 1: Getting Started Step 11: Display memory at an address in a register Step 11: Display memory at an address in a register 1 Click on the Disp @REG action key. Or, using the command line, enter the name of the command file: mematreg <RETURN>...

  • Page 44: Step 12: Patch Assembly Language Code

    Chapter 1: Getting Started Step 12: Patch assembly language code Step 12: Patch assembly language code The Patch () action key lets you patch code in your program. 1 With "main" still in the entry buffer, click on the Run Xfer til () action key. 2 To display memory with assembly-level instructions intermixed with the high-level source lines, click on the Disp Src &...
  • Page 45 Chapter 1: Getting Started Step 12: Patch assembly language code Notice in the emulator/analyzer interface that the instruction at address "main" has changed. 4 Click on the Patch () action key again. A window running the vi editor again appears, allowing you to modify the patch code that was just created.
  • Page 46 Chapter 1: Getting Started Step 12: Patch assembly language code 5 Type "main+4 thru main+15" in the entry buffer. By entering an address range in the entry buffer (that is, <address> thru <address>) before clicking on the Patch () action key, you can modify a patch template file which allows you to insert as much or as little code as you wish.

  • Page 47: Step 13: Exit The Emulator/Analyzer Interface

    Chapter 1: Getting Started Step 13: Exit the emulator/analyzer interface Step 13: Exit the emulator/analyzer interface • To exit the emulator/analyzer interface and release the emulator, choose File→Exit→Released. Or, using the command line, enter: end release_system <RETURN>...

  • Page 49: Part 2 User's Guide

    Part 2 User’s Guide A complete set of task instructions and problem-solving guidelines, with a few basic concepts.
  • Page 50 Part 2...

  • Page 51: Plugging Into A Target System

    Plugging into a Target System...
  • Page 52 Select the emulator clock source. Plug the emulator probe into the target system. Turn ON power (first the HP 64700, then the target system). After you plug the emulator into your target system, you must configure the emulator so that it operates properly with your target system (refer to the "Configuring the Emulator"...

  • Page 53: Step 1. Turn Off Power

    HP 64700 power is OFF before removing or installing the emulator probe into the target system. Do not turn HP 64700 power OFF while the emulator is plugged into a target system whose power is ON. 1 If the emulator is currently plugged into a different target system, turn that target system’s power OFF.

  • Page 54: Step 2. Unplug Probe From Demo Target System

    Chapter 2: Plugging into a Target System Step 2. Unplug probe from demo target system Step 2. Unplug probe from demo target system 1 If the emulator is currently connected to a different target system, unplug the emulator probe; otherwise, disconnect the emulator probe from the demo target system.

  • Page 55: Step 3. Select The Emulator Clock Source

    For 64751-66508 and higher numbered active probe printed-circuit boards, the selection of the internal or external clock source is made by positioning a jumper module on the board. If your active probe board number is 64751-66506 or lower, go on to Step 4; otherwise, perform the following steps.
  • Page 56 Chapter 2: Plugging into a Target System Step 3. Select the emulator clock source 1 Remove plastic rivets that secure the plastic cover on the top of the emulator probe, and remove the cover.
  • Page 57 Chapter 2: Plugging into a Target System Step 3. Select the emulator clock source 2 To select the 32.768 KHz crystal internal to the emulator, insert the jumper module such that pin 1 of the module aligns with pin 1 of the socket. The target system MUST drive MODCK high (or allow a pullup resistor in the emulator to pull it high) during reset to enable the 68340 VCO and programmable clock mode.
  • Page 58 Chapter 2: Plugging into a Target System Step 3. Select the emulator clock source 3 Replace the plastic cover, and insert new plastic rivets (supplied with the emulator) to secure the cover.
  • Page 59 Chapter 2: Plugging into a Target System Step 3. Select the emulator clock source You can also replace the jumper with a prototyping socket on which a crystal and any capacitors or tank circuitry are assembled. (One such prototyping socket is part number 20314-36-455 from Electronic Molding Corp., 96 Mill Street, Woonsocket RI.) The figure below shows the connections that are made to the socket.

  • Page 60: Step 4. Plug The 68340 Pga Emulator Probe Into The Target System

    Chapter 2: Plugging into a Target System Step 4. Plug the 68340 PGA emulator probe into the target system Step 4. Plug the 68340 PGA emulator probe into the target system CAUTION Possible Damage to the Emulator Probe. The emulator probe is provided with a pin extender.

  • Page 61: Step 5. Turn On Power

    Chapter 2: Plugging into a Target System Step 5. Turn ON power Step 5. Turn ON power 1 Turn emulator power ON. 2 Turn target system power ON.

  • Page 63: Starting And Exiting Hp 64700 Interfaces

    Starting and Exiting HP 64700 Interfaces...
  • Page 64 Up to 10 interface windows may be started for the same emulator. Only one C debugger interface window and one SPA window are allowed, but you can start multiple emulator/analyzer interface windows. The tasks associated with starting and exiting HP 64700 interfaces are grouped into the following sections: •...

  • Page 65: Starting The Emulator/Analyzer Interface

    Chapter 3: Starting and Exiting HP 64700 Interfaces Starting the Emulator/Analyzer Interface Starting the Emulator/Analyzer Interface Before starting the emulator/analyzer interface, the emulator and interface software must have already been installed as described in the "Installation" chapter. This section describes how to: •...

  • Page 66: To Start The Interface Using The Default Configuration

    Chapter 3: Starting and Exiting HP 64700 Interfaces Starting the Emulator/Analyzer Interface Examples To start the emulator/analyzer interface for the 68340 emulator: $ emul700 em68340 <RETURN> The "em68340" in the command above is the logical emulator name given in the HP 64700 emulator device table file (/usr/hp64000/etc/64700tab.net).

  • Page 67: To Run A Command File On Interface Startup

    Chapter 3: Starting and Exiting HP 64700 Interfaces Starting the Emulator/Analyzer Interface To run a command file on interface startup • Use the emul700 -c <cmd_file> <emul_name> command. You can cause command files to be run upon starting the interface by using the -c <cmd_file>...

  • Page 68: To Unlock An Interface That Was Left Locked By Another User

    Chapter 3: Starting and Exiting HP 64700 Interfaces Starting the Emulator/Analyzer Interface Or, the information may be similar to: em68340 - m68340 running; user = guest@myhost description: M68340 emulation w/internal analysis, 260Kb emul mem user interfaces: xdebug, xemul, xperf, skemul, sktiming internet address: 21.17.9.143...

  • Page 69: Opening Other Hp 64700 Interface Windows

    Opening Other HP 64700 Interface Windows The File→Emul700 menu lets you open additional emulator/analyzer interface windows or other HP 64700 interface windows if those products have been installed (for example, the software performance analyzer (SPA) interface and the high-level debugger interface).

  • Page 70: To Open The High-Level Debugger Interface Window

    Chapter 3: Starting and Exiting HP 64700 Interfaces Opening Other HP 64700 Interface Windows To open the high-level debugger interface window • Choose File→Emul700→High-Level Debugger ... under "Graphic Windows", or enter the emul700 -u xdebug <emul_name> command in another terminal emulation window.

  • Page 71: Exiting Hp 64700 Interfaces

    Exiting HP 64700 Interfaces Exiting HP 64700 Interfaces There are several options available when exiting the HP 764700 interfaces. You can simply close one of the open interface windows, or you can exit the debug session by closing all the open windows. When exiting the debug session, you can lock the emulator so that you can continue later, or you can release the emulation system so that others may use it.

  • Page 72: To Exit A Debug/Emulation Session

    Chapter 3: Starting and Exiting HP 64700 Interfaces Exiting HP 64700 Interfaces To exit a debug/emulation session • To exit the interface, save your configuration to a temporary file, and lock the emulator so that it cannot be accessed by other users, choose File→Exit→Locked.

  • Page 73: Entering Commands

    Entering Commands...
  • Page 74 Using menus, the entry buffer, and action keys. • Using the command line with the mouse. • Using the command line with the keyboard. • Using command files. • Using pod commands. • Forwarding commands to other HP 64700 interfaces.

  • Page 75: Using Menus, The Entry Buffer, And Action Keys

    Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys Using Menus, the Entry Buffer, and Action Keys This section describes the tasks you perform when using the Graphical User Interface to enter commands. This section describes how to: •...

  • Page 76: To Choose A Pulldown Menu Item Using The Mouse (Method 1)

    Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To choose a pulldown menu item using the mouse (method 1) 1 Position the mouse pointer over the name of the menu on the menu bar. 2 Press and hold the command select mouse button to display the menu. 3 While continuing to hold down the mouse button, move the mouse pointer to the desired menu item.

  • Page 77: To Choose A Pulldown Menu Item Using The Mouse (Method 2)

    • To initially display a pulldown menu, press and hold the menu select key (for example, the "Extend char" key on a HP 9000 keyboard) and then type the underlined character in the menu label on the menu bar. (For example, "f" for "File".
  • Page 78 Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys • To move left to another pulldown menu after having initially displayed a menu, press the left-arrow key. • To move down one menu item within a menu, press the down-arrow key. •...

  • Page 79: To Choose Popup Menu Items

    Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To choose popup menu items 1 Move the mouse pointer to the area whose popup menu you wish to access. (If a popup menu is available, the mouse pointer changes from an arrow to a hand.) 2 Press and hold the select mouse button.

  • Page 80: To Place Values Into The Entry Buffer Using The Keyboard

    Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To place values into the entry buffer using the keyboard 1 Position the mouse pointer within the text entry area. (An "I-beam" cursor will appear.) 2 Enter the text using the keyboard. To clear the entry buffer text area from beginning until end, press the <Ctrl>u key combination.
  • Page 81 Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys contains only numbers 0 through 9 and characters "a" through "f") automatically has an "h" appended. Note If you have multiple Graphical User Interface windows open, a copy-and-paste action in any window causes the text to appear in all entry buffers in all windows.
  • Page 82 Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys Example To paste the symbol "num_checks" into the entry buffer from the interface display area, position the mouse pointer over the symbol and then click the paste mouse button.

  • Page 83: To Recall Entry Buffer Values

    Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To recall entry buffer values • Position the mouse pointer over the Recall button just to the right of the entry buffer text area, click the mouse button to bring up the Entry Buffer Recall dialog box, and then choose a string from that dialog box.

  • Page 84: To Copy-And-Paste From The Entry Buffer To The Command Line Entry Area

    Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To copy-and-paste from the entry buffer to the command line entry area 1 Place text to be pasted into the command line in the entry buffer text area. You may do that by: •...

  • Page 85: To Use The Action Keys

    Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To use the action keys 1 If the action key uses the contents of the entry buffer, place the desired information in the entry buffer. 2 Position the mouse pointer over the action key and click the action key. Action keys are user-definable pushbuttons that perform interface or system functions.
  • Page 86 Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys File Selection From the working directory, you can select an existing file name or specify a new file name. Entry Buffer Recall You can recall a previously used entry buffer text string, a predefined entry buffer text string, or a newly entered entry buffer string, to the entry buffer text area.
  • Page 87 Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys Examples To use the File Selection dialog box: The file filter selects specific files. A list of filter-matching files from the current directory. A list of files previously accessed during the emulation session.
  • Page 88 Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To use the Directory Selection dialog box: Label informs you of the type of list displayed. A list of predefined or previously accessed d irectories. A single click on a directory name from the list highlights the name and copies...

  • Page 89: To Access Help Information

    Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To access help information 1 Display the Help Index by choosing Help→General Topic... or Help→Command Line..2 Choose a topic of interest from the Help Index. The Help Index lists topics covering operation of the interface as well other information about the interface.

  • Page 90: Using The Command Line With The Mouse

    Chapter 4: Entering Commands Using the Command Line with the Mouse Using the Command Line with the Mouse When using the Graphical User Interface, the command line portion of the interface gives you the option of entering commands in the same manner as they are entered in the Softkey Interface.

  • Page 91: To Enter A Command

    Chapter 4: Entering Commands Using the Command Line with the Mouse Off means the command line is not displayed and you use only the pulldown menus and the action keys to control the interface. The command line area begins just below the status line and continues to the bottom of the emulator/analyzer window.

  • Page 92: To Edit The Command Line Using The Command Line Pushbuttons

    Chapter 4: Entering Commands Using the Command Line with the Mouse To edit the command line using the command line pushbuttons • To clear the command line, click the Clear pushbutton. • To clear the command line from the cursor position to the end of the line, click the Clear to end pushbutton.

  • Page 93: To Edit The Command Line Using The Command Line Popup Menu

    Chapter 4: Entering Commands Using the Command Line with the Mouse To edit the command line using the command line popup menu • To clear the command line: position the mouse pointer within the Command Line entry area; press and hold the select mouse button until the Command Line popup menu appears;...

  • Page 94: To Recall Commands

    Chapter 4: Entering Commands Using the Command Line with the Mouse To recall commands 1 Click the pushbutton labeled Recall in the Command Line to display the dialog box. 2 Choose a command from the buffer list. (You can also enter a command directly into the text entry area of the dialog box.) Because all command entry methods in the interface —...

  • Page 95: Using The Command Line With The Keyboard

    Chapter 4: Entering Commands Using the Command Line with the Keyboard Using the Command Line with the Keyboard When using the command line with the keyboard, you enter commands by pressing softkeys whose labels appear at the bottom of the screen. Softkeys provide for quick command entry, and minimize the possibility of errors.

  • Page 96: To Recall Commands

    Chapter 4: Entering Commands Using the Command Line with the Keyboard To recall commands • Press <CTRL>r or <CTRL>b. The most recent 20 commands you enter are stored in a buffer and may be recalled by pressing <CTRL>r. Pressing <CTRL>b cycles forward through the recall buffer. Examples For example, to recall and execute the command prior to the last command: <CTRL>r <CTRL>r <RETURN>...

  • Page 97: To Access On-Line Help Information

    Chapter 4: Entering Commands Using the Command Line with the Keyboard To access on-line help information • Use the help or ? commands. To access the command line’s on-line help information, type either help or ? on the command line. You will notice a new set of softkeys. By pressing one of these softkeys and <RETURN>, you can display information on that topic.

  • Page 98: Using Command Files

    Chapter 4: Entering Commands Using Command Files Using Command Files You can execute a series of commands that have been stored in a command file. You can create command files by logging commands while using the interface or by using an editor on your host computer. Once you create a command file, you can execute the file in the emulation environment by typing the name of the file on the command line and pressing <RETURN>.
  • Page 99 The only way to pass a parameter containing a space is to enclose the parameter in double quotes (") or single quotes (’). Thus, to pass the parameter HP 9000 to a command file, you can use either "HP 9000" or ’HP 9000’.
  • Page 100 Chapter 4: Entering Commands Using Command Files When you execute CMDFILE, you will be prompted with: Define command file parameter [&ADDR] To pass the parameter, enter the address of the first memory location to be modified. You will then be prompted for &VALUE1. If you enter, for example, "0,-1,20, 0ffffh, 4+5*4", the first parameter "0,-1,20,"...

  • Page 101: To Start Logging Commands To A Command File

    Chapter 4: Entering Commands Using Command Files characters for shell commands which are double quotes ("), single quotes (’), and the backslash symbol (\). For example, the following three lines are treated as a single shell command. The two hidden line feeds are ignored because they are inside the two single quotes (’): !awk ’/$/ { blanks++ } END { print blanks }...

  • Page 102: To Playback (Execute) A Command File

    Chapter 4: Entering Commands Using Command Files To playback (execute) a command file • Choose File→Log→Playback and use the dialog box to select the name of the command file you wish to execute. • Using the command line, enter the name of the command file and press <RETURN>.

  • Page 103: Using Pod Commands

    Chapter 4: Entering Commands Using Pod Commands Using Pod Commands Pod commands are Terminal Interface commands. The Terminal Interface is the low-level interface that resides in the firmware of the emulator. A pod command used in the Graphical User Interface bypasses the interface and goes directly to the emulator.

  • Page 104: To Display The Pod Commands Screen

    Chapter 4: Entering Commands Using Pod Commands To display the pod commands screen • Choose Display→Pod Commands. The pod commands screen displays the results of pod (Terminal Interface) commands. To set the interface to use pod commands, choose Settings→Pod Command Keyboard. To use pod commands •...

  • Page 105: Forwarding Commands To Other Hp 64700 Interfaces

    Forwarding Commands to Other HP 64700 Interfaces To allow the emulator/analyzer interface to run concurrently with other HP 64700 interfaces like the high-level debugger and software performance analyzer, a background "daemon" process is necessary to coordinate actions in the interfaces.

  • Page 106: To Forward Commands To The Software Performance Analyzer

    Chapter 4: Entering Commands Forwarding Commands to Other HP 64700 Interfaces To forward commands to the software performance analyzer • Enter the forward perf "<command string>" command using the command line. Examples To send the "profile" command to the software performance analyzer:...

  • Page 107: Configuring The Emulator

    Configuring the Emulator...
  • Page 108 Configuring for Operation in the Target System After you plug the emulator into a target system and turn on power to the HP 64700, you need to configure the emulator so that it operates properly with your target system. Before the emulator can operate in your target system, you must: Map memory.
  • Page 109 Chapter 5: Configuring the Emulator replaces slower target system memory that requires wait states, synchronizing emulation memory to the target system causes wait states to be inserted on emulation memory accesses as they would be on target system memory accesses. Refer to the "Mapping Memory"...

  • Page 110: Using The Configuration Interface

    Chapter 5: Configuring the Emulator Using the Configuration Interface Using the Configuration Interface This section shows you how to modify, store, and load configurations using the emulator configuration interface. This section shows you how to: • Start the configuration interface. •...

  • Page 111: To Start The Configuration Interface

    Chapter 5: Configuring the Emulator Using the Configuration Interface To start the configuration interface • Choose Modify→Emulator Config... from the emulator/analyzer interface pulldown menu. • Using the command line, enter the modify configuration command. The configuration interface main menu (see example below) is displayed. The configuration sections that are presented depend on the hardware and features of your particular emulator.
  • Page 112 Chapter 5: Configuring the Emulator Using the Configuration Interface Examples The 68340 emulator configuration interface main menu is shown below. Clicking on one of these lines selects a particular configuration section. Clicking this button presents the questions for the selected configuration section.

  • Page 113: To Modify A Configuration Section

    Chapter 5: Configuring the Emulator Using the Configuration Interface To modify a configuration section 1 Start the emulator configuration interface. 2 Click on a section name in the configuration interface main menu, and click the "Modify Section" pushbutton. 3 Use the command line to answer the configuration questions. If you’re using the Softkey Interface: The configuration questions in the "General Items"...
  • Page 114 Chapter 5: Configuring the Emulator Using the Configuration Interface Each configuration section presents a window similar to the following. The menu bar. Configuration help text display area. Emulator status and error message line. Command line text entry area. Pushbutton softkeys. Command control and cursor control pushbuttons.

  • Page 115: To Store A Configuration

    Chapter 5: Configuring the Emulator Using the Configuration Interface At the last question of a configuration section, you are asked if you wish to return to the main menu. You can click the "next_sec" softkey pushbutton to access the questions in the next configuration section. To recall a configuration question, click the "RECALL"...

  • Page 116: To Change The Configuration Directory Context

    Chapter 5: Configuring the Emulator Using the Configuration Interface For more information on how to use dialog boxes, refer to the "To use dialog boxes" description in the "Using Menus, the Entry Buffer, and Action Keys" section of the "Entering Commands" chapter. To change the configuration directory context •...

  • Page 117: To Display The Configuration Context

    Chapter 5: Configuring the Emulator Using the Configuration Interface To display the configuration context • When answering the configuration questions, choose Display→Context... from the pulldown menu. The current directory context and the current configuration files are displayed in a window. Click the "Done" pushbutton when you wish to close the window. To access help information •...

  • Page 118: To Exit The Configuration Interface

    Chapter 5: Configuring the Emulator Using the Configuration Interface To exit the configuration interface • When answering the configuration questions, choose File→Exit... from the pulldown menu (or type <CTRL>x), and click "Yes" in the confirmation dialog box. • From the configuration interface main menu, click the "Exit Window" button, and click "Yes"...

  • Page 119: Modifying The General Configuration Items

    Turn OFF the restriction to real-time runs. To select the emulator’s clock source For 64751-66508 and higher numbered active probe printed-circuit boards, the selection of the internal or external clock source is made by positioning a jumper module on the board as described in the "Plugging into a Target System" chapter.

  • Page 120: To Enable/Disable Entry Into The Monitor After Configuration

    Chapter 5: Configuring the Emulator Modifying the General Configuration Items Your target system clock must conform to the specifications for the 68340 microprocessor. Note that changing the clock source drives the emulator into the reset state. The emulator may later break into the monitor depending on how the "Enter monitor after configuration?"...

  • Page 121: To Turn Off The Restriction To Real-Time Runs

    Chapter 5: Configuring the Emulator Modifying the General Configuration Items dual-port emulation memory is reserved for foreground monitor programs when they are used. • Synchronize SIM registers. If you want to enter one of these commands, you must first make an explicit break into the monitor using the break command.

  • Page 122: Reconfiguring The Emulator Configuration Registers

    Chapter 5: Configuring the Emulator Reconfiguring the Emulator Configuration Registers Reconfiguring the Emulator Configuration Registers In order to modify the general configuration items, you must first start the configuration interface and access the "Reconfigure Internal Registers" configuration section (refer to the previous "Using the Configuration Interface" section).

  • Page 123: Selecting The Emulation Monitor

    Chapter 5: Configuring the Emulator Selecting the Emulation Monitor Selecting the Emulation Monitor This section shows you how to: • Select the background monitor (implemented with the 68340 Background Debug Mode (BDM)). • Select the foreground monitor program. • Use a custom foreground monitor program. When you power up the emulator, or when you initialize it, the background monitor is selected.
  • Page 124 4 Kbyte block of the 68340’s address range. The foreground monitor program is included with the interface software as /usr/hp64000/monitor/fm64751.s. It can be assembled with the HP AxLS 68000/10/20 Assembler/Linker/Librarian or with the Microtec Research 68000 assembler and linker.

  • Page 125: To Select The Background Monitor

    Chapter 5: Configuring the Emulator Selecting the Emulation Monitor To select the background monitor 1 Access the configuration questions. 2 Answer "yes" to the "Modify memory configuration?" question. 3 Answer "background" to the "Monitor type?" question. 4 Answer "yes" to the "Reset map (change of monitor type requires map reset)?" question.

  • Page 126: To Select The Foreground Monitor Program

    Chapter 5: Configuring the Emulator Selecting the Emulation Monitor To select the foreground monitor program 1 Access the configuration questions. 2 Answer "yes" to the "Modify memory configuration?" question. 3 Answer "foreground" to the "Monitor type?" question. 4 Answer "yes" to the "Reset map (change of monitor type requires map reset)?" question.
  • Page 127 Chapter 5: Configuring the Emulator Selecting the Emulation Monitor The starting address of the monitor block is set by answering the "Monitor’s base address?" question, and your response to the "Enable /DSACK interlocking on monitor addresses?" question determines whether the dsi (/DSACK interlock) memory attribute is added.
  • Page 128 Chapter 5: Configuring the Emulator Selecting the Emulation Monitor The current memory map will be deleted, and a new map term is added for the monitor. Specifying Target Synchronization If you wish to synchronize monitor cycles to the target system (that is, interlock the emulation and target system /DSACK on accesses to the monitor memory block), answer "yes"...

  • Page 129: To Use A Custom Foreground Monitor Program

    Chapter 5: Configuring the Emulator Selecting the Emulation Monitor To use a custom foreground monitor program 1 Edit the monitor program source file to define its base address. 2 Assemble and link the monitor program. 3 Access the configuration questions. 4 Answer "yes"...
  • Page 130 Examples The following examples of how to set up and use a foreground monitor program assume the HP 64870 or HP B1464 68000/08/10/20/302 Assembler/Linker/Librarian is installed on the host computer. To copy the foreground monitor program source file: $ cp /usr/hp64000/monitor/fm64751.s .
  • Page 131 Chapter 5: Configuring the Emulator Selecting the Emulation Monitor To assemble and link the monitor program, enter the following commands (which assume that /usr/hp64000/bin is defined in the PATH environment variable): $ as68k -L fm64751.s > fm64751.lis <RETURN> $ ld68k -c fm64751.k -L > fm64751.map <RETURN> Where the “fm64751.k”...
  • Page 132 Chapter 5: Configuring the Emulator Selecting the Emulation Monitor To modify the TRACE exception vector to point to the TRACE_ENTRY label in the monitor program (so that the emulator can single-step), enter the following commands using the command line: modify memory 24h long to 20800h <RETURN> Now, you are ready to use the emulator.

  • Page 133: Mapping Memory

    The emulator contains 4 Kbytes of dual-port emulation memory and provides two slots for additional emulation memory modules: • HP 64171A 256 Kbyte Memory Modules or HP 64171B 1 Mbyte Memory Modules (0 wait state emulation memory through 16.7 MHz, 1 wait state above 16.7 MHz).
  • Page 134 External DMA Access to Emulation Memory External direct memory access (DMA) to emulation memory is not permitted. The HP 64751 emulator supports operation of the two 68340 on-chip DMA channels in both single- and dual-address modes. Dual-address transfers can access emulation memory;...

  • Page 135: To Map Memory Ranges

    Chapter 5: Configuring the Emulator Mapping Memory To map memory ranges 1 Access the configuration questions. 2 Answer "yes" to the "Modify memory configuration?" question. 3 Enter the address range, memory type, and optionally an attribute for the memory range. You can characterize memory ranges as emulation RAM, emulation ROM, target system RAM, target system ROM, or as guarded memory.
  • Page 136 Chapter 5: Configuring the Emulator Mapping Memory The attributes can be: Dual-port emulation memory. One emulation memory range, up to 4 Kbytes in length, can be given the dp attribute. The dp attribute specifies that the range be mapped to the 4 Kbyte block of dual-port emulation memory.
  • Page 137 Chapter 5: Configuring the Emulator Mapping Memory dsi_cs0 Combination of the dsi and cs0 attributes. dp_dsi_cs0 Combination of the dp, dsi, and cs0 attributes. Examples Consider the following section summary from the linker load map output listing. SECTION SUMMARY --------------- SECTION ATTRIBUTE START...
  • Page 138 Chapter 5: Configuring the Emulator Mapping Memory Enter the following commands to map memory for the above program. delete all <RETURN> 0 thru 6fffh emulation rom <RETURN> 7000h thru 16fffh emulation ram <RETURN> The resulting memory mapper screen is shown below. To synchronize emulation memory accesses in the range 0 through 6FFFH, you would enter the following command in place of the command above: 0 thru 6fffh emulation rom dsi <RETURN>...

  • Page 139: To Characterize Unmapped Ranges

    Chapter 5: Configuring the Emulator Mapping Memory To characterize unmapped ranges 1 Access the configuration questions. 2 Answer "yes" to the "Modify memory configuration?" question. 3 Use the default softkey to characterize unmapped ranges. The default softkey in the memory mapper allows you to characterize unmapped memory ranges.

  • Page 140: To Delete Memory Map Ranges

    Chapter 5: Configuring the Emulator Mapping Memory To delete memory map ranges 1 Access the configuration questions. 2 Answer "yes" to the "Modify memory configuration?" question. 3 Use the delete softkey to delete mapped ranges. Note that programs should be reloaded after deleting mapper terms. The memory mapper may re-assign blocks of emulation memory after the insertion or deletion of mapper terms.

  • Page 141: To Map Memory Ranges That Use Function Codes

    Chapter 5: Configuring the Emulator Mapping Memory To map memory ranges that use function codes • Specify function codes with address ranges when mapping memory. Memory mapper softkeys that represent the different function codes are: supervisor user program data supervisor program supervisor data user program user data...
  • Page 142 Chapter 5: Configuring the Emulator Mapping Memory Examples Suppose you’re developing a system with the following characteristics: • Input port at 100 hex. • Output port at 400 hex. • Supervisor program from 1000 through 1fff hex. • User program from 3000 through 3fff hex. •...

  • Page 143: To Emulate Global Chip Select Operation

    Chapter 5: Configuring the Emulator Mapping Memory To emulate global chip select operation 1 Use the cs0 attribute when mapping the boot ROM address range. 2 Make sure the CF_MBAR register is valid, and modify the CF_CS0ADDR and CF_CS0MASK registers to appropriate values. Load a previously saved configuration that has appropriate values of CF_MBAR, CF_CS0ADDR, and CF_CS0MASK.
  • Page 144 Chapter 5: Configuring the Emulator Mapping Memory Examples This example shows how to use the cs0 memory map attribute to emulate the 68340’s global chip select operation. To map the boot ROM address range in emulation memory, access the configuration questions, and answer the questions as shown below. Modify memory configuration? yes Entering the following mapper commands.
  • Page 145 Chapter 5: Configuring the Emulator Mapping Memory To run from reset: run from reset <RETURN> To display the trace: display trace <RETURN> Notice the supervisor stack pointer and program counter values that were loaded at 80000H and 80004H are fetched from memory locations 0 through 7 and the program begins running at 81000H.
  • Page 146 Chapter 5: Configuring the Emulator Mapping Memory To modify the emulator configuration registers so appropriate information is sent to the analyzer: modify register CF_SIM CF_MBAR to 100001h <RETURN> modify register CF_SIM CF_CS0ADDR to 0ff000001h <RETURN> modify register CF_SIM CF_CS0MASK to 0fffdh <RETURN> To load the supervisor stack pointer and program counter values that will be fetched from the boot ROM after reset: modify memory 0ff000000h long to 0 , 0ff001000h <RETURN>...
  • Page 147 Chapter 5: Configuring the Emulator Mapping Memory Notice the supervisor stack pointer and program counter values that were loaded at 0FF000000H appear to be fetched from memory locations 0FF000000H through 0FF000007H when they are really fetched from locations 0 through 7. This is because the upper 8 bits of the CF_CS0ADDR register are sent to the analyzer instead of A31-A24 (this is true even if Port A is set up to be address lines).

  • Page 148: Configuring The Emulator Pod

    Chapter 5: Configuring the Emulator Configuring the Emulator Pod Configuring the Emulator Pod In order to configure the emulator pod, you must first start the configuration interface and access the "Emulator Pod Settings" configuration section (refer to the previous "Using the Configuration Interface" section). This section shows you how to: •...

  • Page 149: To Specify The User Memory Access Size

    Chapter 5: Configuring the Emulator Configuring the Emulator Pod To specify the user memory access size • Answer the "User memory access size?" question. When accessing target system memory locations or single-port emulation memory locations, the access mode specifies the type of microprocessor cycles that are used to read or write the value(s).

  • Page 150: Setting The Debug/Trace Options

    Chapter 5: Configuring the Emulator Setting the Debug/Trace Options Setting the Debug/Trace Options In order to set the debug/trace options, you must first start the configuration interface and access the "Debug/Trace Options" configuration section (refer to the previous "Using the Configuration Interface" section). This section shows you how to: •...

  • Page 151: To Trace Background Cycles

    Chapter 5: Configuring the Emulator Setting the Debug/Trace Options To trace background cycles • Answer "background" or "both" to the "Trace background or foreground operation?" question. Answering "background" specifies that the analyzer trace only background cycles. This is rarely a useful setting for user program debugging. Because the background monitor is implemented using the 68340 background debug mode (BDM), only memory accesses are captured when tracing background cycles.

  • Page 153: Using The Emulator

    Using the Emulator...
  • Page 154 Using the Emulator This chapter describes general tasks you may wish to perform while using the emulator. These tasks are grouped into the following sections: • Using the emulator configuration registers. • Loading absolute files. • Using symbols. • Using context commands. •...

  • Page 155: Using The Emulator Configuration Registers

    The SIM can be programmed or configured in a variety of ways to suit the need of various systems. The HP 64751A emulator contains circuitry that accommodates the flexibility of the 68340 SIM and maintains consistent emulation features.
  • Page 156 Chapter 6: Using the Emulator Using the Emulator Configuration Registers In the previous figure, there is a block labeled DE-SIM module. It receives as inputs from the 68340: • Port A which can be address lines 31-24, interrupt acknowledge inputs, or general purpose I/O lines.
  • Page 157 Chapter 6: Using the Emulator Using the Emulator Configuration Registers The default programming of the DE-SIM matches the reset values of the 68340 SIM (refer to the Motorola MC68340 Integrated Processor User’s Manual for specific values). If desired, the programming of the DE-SIM can be transferred into the 68340 SIM with the sync_sim_registers to_68340_from_config command.

  • Page 158: To View The Sim Register Differences

    Chapter 6: Using the Emulator Using the Emulator Configuration Registers To view the SIM register differences • Enter the sync_sim_registers difference command. Before displaying the SIM configuration register differences, make sure the contents of the MBAR register is valid (in other words, its least significant bit should be 1).

  • Page 159: To Synchronize To The Emulator Configuration Registers

    Chapter 6: Using the Emulator Using the Emulator Configuration Registers To synchronize to the emulator configuration registers • Enter the sync_sim_registers to_68340_from_config command. The contents of the emulator’s configuration registers are copied to the 68340 SIM registers. The contents of the CF_MBAR register must be valid (that is, its least significant bit should be 1).

  • Page 160: Loading And Storing Absolute Files

    • Using the command line, enter the load <absolute_file> command. You can load absolute files into emulation or target system memory. You can load IEEE-695 format absolute files. You can also load HP format absolute files. The store memory command creates HP format absolute files.

  • Page 161: To Load Absolute Files Without Symbols

    Chapter 6: Using the Emulator Loading and Storing Absolute Files Examples To load the demo program absolute file, enter the following command: load ecs.x <RETURN> To load only portions of the absolute file that reside in target system RAM: load user_mem absfile <RETURN> To load only portions of the absolute file that reside in emulation memory: load emul_mem absfile <RETURN>...

  • Page 162: To Store Memory Contents Into Absolute Files

    To store memory contents into absolute files • Using the command line, enter the store memory command. You can store emulation or target system memory contents into HP format absolute files on the host computer. Absolute files are stored in the current directory. If no extension is given for the absolute file name, it is given a ".X"...

  • Page 163: Using Symbols

    Chapter 6: Using the Emulator Using Symbols Using Symbols If symbol information is present in the absolute file, it is loaded along with the absolute file (unless you use the nosymbols option). Both global symbols and symbols that are local to a program module can be displayed. Long symbol names can be truncated in the symbols display;...

  • Page 164: To Display Global Symbols

    Chapter 6: Using the Emulator Using Symbols Examples To load symbols from the demo program: load symbols ecs.x <RETURN> To display global symbols • Choose Display→Global Symbols. • Using the command line, enter the display global_symbols command. Listed are: address ranges associated with a symbol, the segment the symbol is associated with, and the offset of that symbol within the segment.

  • Page 165: To Display Local Symbols

    Chapter 6: Using the Emulator Using Symbols To display local symbols • When displaying symbols, position the mouse pointer over a symbol on the symbol display screen and click the select mouse button. • When displaying symbols, position the mouse pointer over the symbol, press and hold the select mouse button, and choose Display Local Symbols from the popup menu.
  • Page 166 Chapter 6: Using the Emulator Using Symbols Examples To use the Symbols Display popup menu: View the local symbols associated with the highlighted symbol by choosing this menu item.
  • Page 167 Chapter 6: Using the Emulator Using Symbols Using the command line: To display local symbols in a module: display local_symbols_in update_sys <RETURN> To display local symbols in a procedure: display local_symbols_in update_sys.save_points <RETURN>...
  • Page 168 Chapter 6: Using the Emulator Using Symbols To display address ranges associated with the high-level source line numbers: display local_symbols_in update_sys."update_sys.c": <RETURN>...

  • Page 169: To Display A Symbol's Parent Symbol

    Chapter 6: Using the Emulator Using Symbols To display a symbol’s parent symbol • When displaying symbols, position the mouse pointer over the symbol, press and hold the select mouse button, and choose Display Parent Symbols from the popup menu. Examples View the parent symbol associated...

  • Page 170: To Copy-And-Paste A Full Symbol Name To The Entry Buffer

    Chapter 6: Using the Emulator Using Symbols To copy-and-paste a full symbol name to the entry buffer • When displaying symbols, position the mouse pointer over the symbol, press and hold the select mouse button, and choose Cut Full Symbol Name from the popup menu.

  • Page 171: Using Context Commands

    Chapter 6: Using the Emulator Using Context Commands Using Context Commands The commands in this section display and control the directory and symbol contexts for the interface. Directory context. The current directory context is the directory accessed by all system references for files—primarily load, store, and copy commands—if no explicit directory is mentioned.

  • Page 172: To Display The Current Directory And Symbol Context

    Chapter 6: Using the Emulator Using Context Commands To display the current directory and symbol context • Choose Display→Context. • Using the command line, enter the pwd and pws commands. The current directory and working symbol contexts are displayed, and also the name of the last executable file from which symbols were loaded.

  • Page 173: To Change The Current Working Symbol Context

    Chapter 6: Using the Emulator Using Context Commands You can predefine directories and set the maximum number of entries for the Directory Selection dialog box by setting X resources (see the "Setting X Resources" chapter). To change the current working symbol context •...

  • Page 174: Executing User Programs

    Chapter 6: Using the Emulator Executing User Programs Executing User Programs You can use the emulator to run programs, break program execution into the monitor, step through the program by high-level source lines or by assembly language instructions, and reset the emulation processor. When displaying memory in mnemonic format, a highlighted bar shows the current program counter address.

  • Page 175: To Run Programs From An Address

    Chapter 6: Using the Emulator Executing User Programs To run programs from an address • Position the mouse pointer in the entry buffer and enter the address you want to run from; then, choose Execution→Run→from (). • Using the command line, enter the run from <address> command. Examples To run from address 9C0H: run from 9c0h <RETURN>...

  • Page 176: To Run Programs Until An Address

    Chapter 6: Using the Emulator Executing User Programs A reset command followed by a run command will load the interrupt stack pointer and program counter values specified during configuration into the emulation processor and run from the loaded program counter value. This is true for both background and foreground monitors.

  • Page 177: To Step High-Level Source Lines

    Chapter 6: Using the Emulator Executing User Programs If the user program executes a STOP or LPSTOP instruction, you cannot break to the emulator’s monitor state while the processor is in the stopped state. The break command uses the emulation processor background debug mode (BDM), and the processor must be executing instructions in order to enter the BDM.

  • Page 178: To Step Assembly-Level Instructions

    Chapter 6: Using the Emulator Executing User Programs To step assembly-level instructions • Choose Execution→Step Instruction and select one of the items from the cascade menu. • Using the command line, enter the step command. The step command allows you to step through program execution an instruction or a number of instructions at a time.

  • Page 179: Using Software Breakpoints

    Note Version A.04.00 or greater of the HP 64700 system firmware provides support for permanent as well as temporary breakpoints. If your version of HP 64700 system firmware is less than A.04.00, only temporary breakpoints are supported.

  • Page 180: To Display The Breakpoints List

    Chapter 6: Using the Emulator Using Software Breakpoints • Re-activate a breakpoint. • Clear a breakpoint. • Clear all breakpoints. CAUTION Software breakpoints should not be set, cleared, enabled, or disabled while the emulator is running user code. If any of these commands are entered while the emulator is running user code, and the emulator is executing code in the area where the breakpoint is being modified, program execution may be unreliable.

  • Page 181: To Enable/Disable Breakpoints

    Chapter 6: Using the Emulator Using Software Breakpoints pending Which means the temporary breakpoint has been set but not encountered during program execution. These breakpoints are inactivated when the breakpoint is encountered. permanent Which means the permanent breakpoint is active. inactivated Which means the breakpoint has been inactivated somehow.
  • Page 182 Chapter 6: Using the Emulator Using Software Breakpoints by zero) are encountered. If software breakpoints are disabled, exception processing may result in "access to guarded memory" errors and/or other unpredictable behavior. To prevent this, a special global symbol, XEnv_68k_except, is included in the library. When the XEnv_68k_except symbol is present, the 68340 emulator writes a value to this location.
  • Page 183 Chapter 6: Using the Emulator Using Software Breakpoints Examples To enable software breakpoints using the breakpoints display popup menu: Bring up menu and choose this item to change states.

  • Page 184: To Set A Permanent Breakpoint

    • Using the command line, enter the modify software_breakpoints set <address> permanent command. Permanent breakpoints are available if your version of HP 64700 system firmware is A.04.00 or greater. The breakpoints feature must be enabled before individual breakpoints can be set.

  • Page 185: To Set A Temporary Breakpoint

    • Place an absolute or symbolic address in the entry buffer; then, choose Breakpoints→Temporary () (or Breakpoints→Set () if your version of HP 64700 system firmware is less than A.04.00). • Using the command line, enter the modify software_breakpoints set <address>...

  • Page 186: To Set All Breakpoints

    Chapter 6: Using the Emulator Using Software Breakpoints Note that you must only set software breakpoints at memory locations which contain instruction opcodes (not operands or data). When displaying memory in mnemonic format, asterisks (*) appear next to breakpoint addresses. An asterisk shows the breakpoint is active. Also, if assembly level code is being displayed, the disassembled instruction mnemonic at the breakpoint address will show the breakpoint instruction.

  • Page 187: To Re-Activate A Breakpoint

    Chapter 6: Using the Emulator Using Software Breakpoints To re-activate a breakpoint • When displaying breakpoints, position the mouse pointer over the line displaying the inactivated breakpoint and click the select mouse button. Or, press and hold the select mouse button and choose Set/Inactivate Breakpoint from the popup menu. The "inactivated"...
  • Page 188 Chapter 6: Using the Emulator Using Software Breakpoints Examples To re-activate breakpoints using the breakpoints display popup menu: Change status with a mouse click on this line (menu and highlight do not appear). Choose this menu item to change the state of the highlighted breakpoint.

  • Page 189: To Clear A Breakpoint

    Chapter 6: Using the Emulator Using Software Breakpoints To clear a breakpoint • When displaying memory in mnemonic format, position the mouse pointer over the program line at which you wish to clear a currently set breakpoint (notice the asterisk at the left of the line) and click the select mouse button. Or, press and hold the select mouse button and choose Set/Clear Software Breakpoint from the popup menu.
  • Page 190 Chapter 6: Using the Emulator Using Software Breakpoints Examples To clear a software breakpoint using the breakpoints display popup menu: Bring up the menu and choose this item to clear the highlighted breakpoint.

  • Page 191: To Clear All Breakpoints

    Chapter 6: Using the Emulator Using Software Breakpoints To clear all breakpoints • When displaying breakpoints, position the mouse pointer within the Breakpoints Display screen, press and hold the select mouse button, and choose Clear (delete) All Breakpoints from the popup menu. •...

  • Page 192: Displaying And Modifying Registers

    Chapter 6: Using the Emulator Displaying and Modifying Registers Displaying and Modifying Registers This section describes tasks related to displaying and modifying emulation processor registers. You can display the contents of an individual register or of all the registers. The register classes and names are listed in the following table.
  • Page 193 Chapter 6: Using the Emulator Displaying and Modifying Registers Register Class Register Description MBAR Module Base Address Register Module Configuration Register SIM_MCR (System SYNCR Clock Synthesizer Control Register Integration Autovector Register Reset Status Register Module) PORTA Port A Data DDRA Port A Data Direction Port A Pin Assignment 1 PPARA1...
  • Page 194 Chapter 6: Using the Emulator Displaying and Modifying Registers Register Class Register Description SERIAL SERIAL_MCR Module Configuration Register Interrupt Level (Serial Module) Interrupt Vector Mode Register 1A MR1A Status Register A CSRA Clock-Select Register A Command Register A Receiver Buffer A Transmitter Buffer A IPCR Input Port Change Register...
  • Page 195 Chapter 6: Using the Emulator Displaying and Modifying Registers Register Class Register Description CF_SIM CF_MBAR Module Base Address Register CF_SIM_MCR Module Configuration Register (Emulator CF_PPARA1 Port A Pin Assignment 1 Configuration CF_PPARA2 Port A Pin Assignment 2 Registers) CF_CS0MASK Address Mask CS0 CF_CS0ADDR Base Address CS0 CF_CS1MASK...

  • Page 196: To Display Register Contents

    Chapter 6: Using the Emulator Displaying and Modifying Registers To display register contents • Choose Display→Registers. • Using the command line, enter the display registers command. When displaying registers, you can display classes of registers and individual registers. The least significant bit of the emulation processor’s MBAR register must be a 1 (which means the MBAR contents are valid) before you can display or modify registers in the SIM, DMA1, DMA2, SERIAL, TIMER1, or TIMER2 register classes.

  • Page 197: To Modify Register Contents

    Chapter 6: Using the Emulator Displaying and Modifying Registers To modify register contents • Choose Modify→Registers... and use the dialog box to name the register and specify its value. Clicking the "Recall" pushbutton lets you select register names and values from predefined or previously specified entries.

  • Page 198: Displaying And Modifying Memory

    Chapter 6: Using the Emulator Displaying and Modifying Memory Displaying and Modifying Memory You can display and modify the contents of memory in hexadecimal formats and in real number formats. You can also display the contents of memory in assembly language mnemonic format.

  • Page 199: To Display Memory In Mnemonic Format

    Chapter 6: Using the Emulator Displaying and Modifying Memory To display memory in mnemonic format • To display memory at a particular address, place an absolute or symbolic address in the entry buffer; then, choose Display→Memory→Mnemonic (), or, using the command line, enter the display memory <address>...

  • Page 200: To Display Memory In Hexadecimal Format

    Chapter 6: Using the Emulator Displaying and Modifying Memory To display memory in hexadecimal format • Place an absolute or symbolic address in the entry buffer; then, choose Display→Memory→Hex () and select the size from the cascade menu. • Using the command line, enter the display memory <address> blocked <size> command.

  • Page 201: To Display Memory In Real Number Format

    Chapter 6: Using the Emulator Displaying and Modifying Memory To display memory in blocked byte format: display memory ascii_old_data blocked bytes <RETURN> To display memory in real number format • Place an absolute or symbolic address in the entry buffer; then, choose Display→Memory→Real () and select the size from the cascade menu.

  • Page 202: To Display Memory At An Address

    Chapter 6: Using the Emulator Displaying and Modifying Memory Examples To display memory in 64-bit real number format: display memory real long <RETURN> To display memory at an address • Place an absolute or symbolic address in the entry buffer; then, choose Display→Memory→At ().

  • Page 203: To Display Memory Repetitively

    Chapter 6: Using the Emulator Displaying and Modifying Memory To display memory repetitively • Choose Display→Memory→Repetitively. • Using the command line, enter the display memory repetitively command. The memory display is constantly updated. The format is specified by the last memory display command.

  • Page 204: Displaying Data Values

    Chapter 6: Using the Emulator Displaying Data Values Displaying Data Values The data values display lets you view the contents of memory as data types. You can display data values in the following formats: bytes 8-bit integers unsigned 8-bit integers chars words 16-bit integers...

  • Page 205: To Clear The Data Values Display And Add A New Item

    Chapter 6: Using the Emulator Displaying Data Values To clear the data values display and add a new item • Place an absolute or symbolic address in the entry buffer; then, choose Display→Data Values→New () and select the data type from the cascade menu. •...

  • Page 206: Changing The Interface Settings

    Chapter 6: Using the Emulator Changing the Interface Settings Changing the Interface Settings This section shows you how to: • Set the source/symbol modes. • Set the display modes. To set the source/symbol modes • To display assembly language mnemonics with absolute addresses, choose Settings→Source/Symbol Modes→Absolute, or, using the command line, enter the set source off symbols off command.

  • Page 207: To Set The Display Modes

    Chapter 6: Using the Emulator Changing the Interface Settings To set the display modes • Choose Settings→Display Modes... to open the display modes dialog box. Press and hold the select mouse button and drag the mouse to select "Source Only", "Source Mixed", or "Off".
  • Page 208 Chapter 6: Using the Emulator Changing the Interface Settings Source/Symbols View Source in Memory specifies whether source lines are included, mixed with assembly code, or excluded from mnemonic memory displays. Source in Trace specifies whether source lines are included, mixed with stored states, or excluded from trace displays.

  • Page 209: Using System Commands

    Chapter 6: Using the Emulator Using System Commands Using System Commands With the system commands, you can: • Set UNIX environment variables while in the Softkey Interface. • Display the name of the emulation module. • Display the event log. •...

  • Page 210: To Display The Name Of The Emulation Module

    Chapter 6: Using the Emulator Using System Commands To display the name of the emulation module • Using the command line, enter the name_of_module command. While operating your emulator, you can verify the name of the emulation module. This is also the logical name of the emulator in the emulator device file. Examples To display the name of your emulation module: name_of_module <RETURN>...

  • Page 211: To Display The Error Log

    Chapter 6: Using the Emulator Using System Commands To display the error log • Choose Display→Error Log. • Position the mouse pointer on the status line, press and hold the select mouse button, and then choose Display Error Log from the popup menu. •...

  • Page 212: To Edit Files

    Chapter 6: Using the Emulator Using System Commands To edit files • Choose File→Edit→File and use the dialog box to specify the file name. • To edit a file based on an address in the entry buffer, place an address reference (either absolute or symbolic) in the entry buffer;...
  • Page 213 Chapter 6: Using the Emulator Using System Commands Examples To edit a file that defines a symbol: Choosing this menu item brings up a terminal window with an edit session open on the file where the highlighted symbol is defined.
  • Page 214 Chapter 6: Using the Emulator Using System Commands To edit a file at a source line: Choosing this menu item brings up a terminal window with an edit session open on the file where the highlighted source line exists.

  • Page 215: To Copy Information To A File Or Printer

    Chapter 6: Using the Emulator Using System Commands To copy information to a file or printer • Choose File→Copy, select the type of information from the cascade menu, and use the dialog box to select the file or printer. • Using the command line, enter the copy command. ASCII characters are copied to the file or printer.

  • Page 216: To Open A Terminal Emulation Window

    Chapter 6: Using the Emulator Using System Commands Status ... Copies the emulator/analyzer status display. Global Symbols ... Copies the global symbols. If symbols have not been loaded, this menu item is grayed-out and unresponsive. Local Symbols () ... Copies the local symbols from the symbol scope named (by an enclosing symbol) in the entry buffer.

  • Page 217: Using Simulated I/O

    Chapter 6: Using the Emulator Using Simulated I/O Using Simulated I/O Simulated I/O is a feature of the emulator/analyzer interface that lets you use the same keyboard and display that you use with the interface to provide input to programs and display program output. To use simulated I/O, your programs must communicate with the simulated I/O control address and the buffer locations that follow it.

  • Page 218: To Use Simulated I/O Keyboard Input

    Chapter 6: Using the Emulator Using Simulated I/O Examples A message tells you whether the display is open or closed. You can modify the configuration to enable status messages. To use simulated I/O keyboard input • To begin using simulated I/O input, choose Settings→Simulated IO Keyboard. •...

  • Page 219: Using Basis Branch Analysis

    This section shows you how to: • Store BBA data to a file. Refer to the HP Branch Validator (BBA) User’s Guide for complete details on the BBA product and how it works. To store BBA data to a file •...

  • Page 221: Using The Emulation Analyzer

    Using the Emulation Analyzer...
  • Page 222 Using the Emulation Analyzer This chapter describes tasks you perform while using the emulation analyzer. These tasks are grouped into the following sections: • The basics of starting, stopping, and displaying traces. • Qualifying trigger and store conditions. • Using the sequencer. •...

  • Page 223: The Basics Of Starting, Stopping, And Displaying Traces

    Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces The Basics of Starting, Stopping, and Displaying Traces This section describes the basic tasks that relate to starting and stopping trace measurements. When you start a trace measurement, the analyzer begins looking at the data on the emulation processor’s bus and control signals on each analyzer clock signal.

  • Page 224: To Start A Trace Measurement

    Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces To start a trace measurement • Choose Trace→Everything. • Using the command line, enter the trace command. The trace command tells the analyzer to begin monitoring the states which appear on the trace signals.
  • Page 225 Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces Examples To display the trace status: display status <RETURN> The first line of the emulation trace status display shows the user trace has been "completed"; other possibilities are that the trace is still "running" or that the trace has been "halted".
  • Page 226 Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces The "States" line shows the number of states that have been stored (out of the number that is possible to store) and the line numbers that the stored states occupy. (The trigger state is always stored on line 0.) The "Sequence term"...

  • Page 227: To Stop A Trace Measurement

    Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces To stop a trace measurement • Choose Trace→Stop. • Using the command line, enter the stop_trace command. You can, and most likely will, specify traces whose trigger or storage states are never found.

  • Page 228: To Display The Trace

    Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces To display the trace • Choose Trace→Display or Display→Trace. • Using the command line, enter the display trace command. You can display captured trace data with the display trace command. The available options to the display trace command are described in the "Modifying the Trace Display"...

  • Page 229: To Position The Trace Display On Screen

    Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces The fourth column shows the count information (time is counted by default). "Relative" indicates that each count is relative to the previous state. You can use the scrollbar in the Graphical User Interface or the <NEXT> and <PREV>...

  • Page 230: To Change The Trace Depth

    Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces To change the trace depth • Using the command line, enter the display trace depth command. The display trace depth command allows you to specify the number of states that are displayed.

  • Page 231: Qualifying Trigger And Store Conditions

    Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions Qualifying Trigger and Store Conditions This section describes tasks relating to the qualification of trigger and storage states. You can trigger on, or store, specific states or specific values on a set of trace signals (which are identified by trace labels).
  • Page 232 Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions Hexadecimal (example: 0a7fh). You must precede any hexadecimal number that begins with an A, B, C, D, E, or F with a zero. Don’t care digits may be included in binary, octal, or hexadecimal numbers and they are represented by the letters X or x.
  • Page 233 Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions However, you cannot add two symbols unless one of them is an EQU type symbol. Emulation Analyzer Trace Signals When you qualify states, you specify values that should be found on the analyzer trace signals.
  • Page 234 Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions Emulation Analyzer Trace Signals Trace Signal Signal Signals Name Description 0-31 A0-A31 Address Lines 0-31. 32-47 D0-D15 Data Lines 0-15. BKG_L Background Debug Mode (BDM) active. This signal is used to qualify the analyzer clock for tracing only foreground or only background cycles.
  • Page 235 Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions State Qualifiers Whenever a state can be specified in the trace command (trigger state, storage state, prestore state, etc.), you will see the following softkeys that allow you to qualify the state: address The value following this softkey is searched for on the lines that...
  • Page 236 Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions Predefined Equates for Analyzer Status Equate Value Description 0xxxx x0xx xxxx xxxxb buserror /BERR active 0xxx0 xxxx xxxx xxxxb code code execution cycles code_tfr 0xx00 xxxx xxxx xxxxb first instruction following a pipeline flush 0xxxx xxxx xxxx 111xb CPU space function code 0xxxx xx11 0xxx xxxxb...

  • Page 237: To Qualify The Trigger State And Position

    Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions To qualify the trigger state and position • Enter a trigger state specification in the entry buffer; then, choose Trace→After (), Trace→About (), or Trace→Before (). • When displaying memory in mnemonic format, position the mouse pointer over the source line where you want to set the trace trigger, press and hold the select mouse button and choose Trace After, Trace Before, or Trace About from the popup menu.
  • Page 238 Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions Examples Suppose you want to look at the execution of the demo program after the call of the "update_system()" function (main.c: line 102) occurs. To trigger on this address, enter: trace after address main."main.c": line 102 <RETURN>...

  • Page 239: To Trigger On A Number Of Occurrences Of Some State

    Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions To trigger on a number of occurrences of some state • Use the occurs <#TIMES> after specifying the trigger state. When specifying a trigger state, you can include an occurrence count. The occurrence count specifies that the analyzer trigger on the Nth occurrence of some state.

  • Page 240: To Qualify States Stored In The Trace

    Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions To qualify states stored in the trace • Enter a storage state specification in the entry buffer; then, choose Trace→Only (). • Using the command line, use the only option in the trace command. By default, all captured states are stored;...

  • Page 241: To Prestore States Before Qualified Store States

    Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions To prestore states before qualified store states • Enter a storage state specification in the entry buffer; then, choose Trace→Only () Prestore. • Use the prestore option in the trace command. Prestore allows you to save up to two states which precede a normal store state.

  • Page 242: To Change The Count Qualifier

    Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions To change the count qualifier • Use the counting option in the trace command. After initializing the analyzer, the default count qualifier is "time", which means that the time between states is saved. When time is counted, up to 512 states can be stored in the trace.

  • Page 243: To Trace Until The Analyzer Is Halted

    Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions The trace listing above shows that the program loops 4 times for each call of the "do_sort" function. To trace until the analyzer is halted • Choose Trace→Until Stop. •...

  • Page 244: To Break Emulator Execution On The Analyzer Trigger

    Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions To break emulator execution on the analyzer trigger • Enter a trigger state specification in the entry buffer; then, choose Trace→Until (). • Using the command line, use the break_on_trigger option to the trace command. The break_on_trigger option to the trace command allows you to cause the emulator to break when the analyzer finds the trigger state.

  • Page 245: Using The Sequencer

    Chapter 7: Using the Emulation Analyzer Using the Sequencer Using the Sequencer When you use the analyzer’s sequencer, you can specify traces that trigger on a series, or sequence, of states. You can specify a state which, when found, causes the analyzer to restart the search for the sequence of states.
  • Page 246 Chapter 7: Using the Emulation Analyzer Using the Sequencer Examples In the demo program, suppose you wish to trigger on the following sequence of events: the "save_points" function, the "interrupt_sim" function, and finally the "do_sort" function. Also, suppose you wish to store only opcode fetches of the assembly language LINK A6,#0 instruction (data values that equal 4E56H) to show function entry addresses.

  • Page 247: To Specify A Global Restart State

    Chapter 7: Using the Emulation Analyzer Using the Sequencer To specify a global restart state • Use the restart option to the trace command. When using the analyzer’s sequencer, an additional sequence restart term is also allowed. This restart is a "global restart"; that is, it applies to all the sequence terms. The restart term is a state which, when captured before the analyzer has found the trigger state, causes the search for the sequence of states to start over.

  • Page 248: To Trace "Windows" Of Program Execution

    Chapter 7: Using the Emulation Analyzer Using the Sequencer Notice in the preceding trace (you may have to press <PREV> in order to see the states captured prior to the trigger) that, in addition to states captured in the sequence, "sq adv" is also shown next to states which cause a sequencer restart. To trace "windows"...
  • Page 249 Chapter 7: Using the Emulation Analyzer Using the Sequencer If you wish to combine the windowing and sequencing functions of the analyzer, there are some restrictions: • Up to four sequence terms are available when windowing is in effect. • Global restart is not available when windowing is in effect.

  • Page 250: Modifying The Trace Display

    Chapter 7: Using the Emulation Analyzer Modifying the Trace Display Modifying the Trace Display This section describes the options available when displaying trace lists. This section describes how to: • Display a dequeued trace. • Display the trace about a line number. •...

  • Page 251: To Display A Dequeued Trace

    Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display a dequeued trace • Use the dequeue on option to the display trace command. Unused prefetches are removed from the trace display, and data transactions are aligned with the instructions that caused them to occur. Examples To display a dequeued trace: display trace dequeue on <RETURN>...

  • Page 252: To Display The Trace About A Line Number

    Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace about a line number • Use the <LINE #> option to the display trace command. The <LINE #> trace display option allows you to specify the line number to be centered in the display.

  • Page 253: To Display The Trace, Disassembling From A Line Number

    Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace, disassembling from a line number • Use the disassemble_from_line_number option to the display trace command. The "disassemble_from_line_number" trace display option causes the inverse assembler to attempt to begin disassembling the trace information from the specified line number.

  • Page 254: To Display Instruction Cycles Only

    Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display instruction cycles only • Use the disassemble_from_line_number <LINE #> instructions_only option to the display trace command. Only the lines that contain an instruction opcode are displayed in the trace. Examples To display the trace about line number 66 displaying only instruction cycles: display trace disassemble_from_line_number 66...

  • Page 255: To Display The Trace In Absolute Format

    Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace in absolute format • Use the absolute option to the display trace command. The absolute trace display option allows you to display status information in absolute format (binary, hex, or mnemonic). The absolute status mnemonic display is the same as default mnemonic display, except that opcodes are not disassembled.

  • Page 256: To Display The Trace In Mnemonic Format

    Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace in mnemonic format • Use the mnemonic option to the display trace command. The mnemonic trace display option allows you to display the trace information in mnemonic format (that is, opcodes and status).

  • Page 257: To Display The Trace With High-Level Source Lines

    Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace with high-level source lines • Use the set source command. To include high-level source lines in the trace display, you must use the set command. The set command allows you to include symbolic information in trace, memory, register, and software breakpoint displays.
  • Page 258 Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To set the number of source lines to be displayed at 12: set source on number_of_source_lines 12 <RETURN> display trace <RETURN>...

  • Page 259: To Display The Trace With Symbol Information

    Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace with symbol information The set symbols on/off command allows you to specify that address information be displayed in terms of program symbols. Examples To display the trace with symbol information: set source off symbols on <RETURN>...

  • Page 260: To Change Column Widths In The Trace Display

    Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To change column widths in the trace display • Use the set width command. The set width command allows you to change the width of the address and mnemonic (or absolute) columns in the trace list. Values from one to 80 can be entered.

  • Page 261: To Display Time Counts In Absolute Or Relative Format

    Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display time counts in absolute or relative format • Use the count option to the display trace command. Count information may be displayed two ways: relative (which is the default), or absolute.

  • Page 262: To Display The Trace With Addresses Offset

    Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace with addresses offset • Use the offset_by option to the display trace command. The offset_by trace display option allows you to cause the address information in the trace display to be offset by the amount specified.

  • Page 263: To Return To The Default Trace Display

    Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To return to the default trace display • Use the set default command. The set default command allows you to return to the default display. Examples To return to the default trace display: set default <RETURN>...

  • Page 264: Saving And Restoring Traces

    Chapter 7: Using the Emulation Analyzer Saving and Restoring Traces Saving and Restoring Traces The emulator/analyzer interface allow you to save trace commands and trace lists. You can restore trace commands in order to set up the same trace specification. You can restore traces in order to view trace data captured in the stored trace.

  • Page 265: To Restore Trace Commands

    Chapter 7: Using the Emulation Analyzer Saving and Restoring Traces To restore trace commands • Choose File→Load→Trace Spec. • Using the command line, enter the load trace_spec command. Trace commands that are restored will always work, even if symbols have been changed;...

  • Page 266: To Restore Traces

    Chapter 7: Using the Emulation Analyzer Saving and Restoring Traces To restore traces • Choose File→Load→Trace Data. • Using the command line, enter the load trace command. The restored trace depth is the depth specified when the trace was stored and cannot be increased.

  • Page 267: Making Software Performance Measurements

    Making Software Performance Measurements...
  • Page 268 The SPMT allows you to make some of the measurements that are possible with the HP 64708 Software Performance Analyzer and its Graphical User Interface (HP B1487). The SPMT post-processes information from the analyzer trace list. When you end a performance measurement, the SPMT dumps the post-processed information to a binary file, which is then read using the perf32 report generator utility.

  • Page 269: Activity Performance Measurements

    Chapter 8: Making Software Performance Measurements Activity Performance Measurements Activity Performance Measurements Activity measurements are measurements of the number of accesses (reads or writes) within an address range. The SPMT shows you the percentage of analyzer trace states that are in the specified address range, as well as the percentage of time taken by those states.
  • Page 270 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Program Activity State Percent Rel = 0.18 Abs = 0.18 Mean = 0.90 Sdv = 0.88 Time Percent Rel = 0.16 Abs = 0.16 stack Address Range 40000H thru 43FFFH Memory Activity State Percent Rel = 11.72...

  • Page 271: To Set Up The Trace Command For Activity Measurements

    Chapter 8: Making Software Performance Measurements Activity Performance Measurements Absolute count - state 5120 Absolute count - time - Us 2221.20 This section describes how to: • Set up the trace command for activity measurements. • Initialize activity performance measurements. •...

  • Page 272: To Initialize Activity Performance Measurements

    Chapter 8: Making Software Performance Measurements Activity Performance Measurements Examples To specify a trace depth of 512: display trace depth 512 <RETURN> To trace after any state, store all states, and count time: trace counting time <RETURN> To initialize activity performance measurements •...
  • Page 273 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Initialization with User Defined Ranges You can specifically give the SPMT address ranges to use by placing the information in a file and entering the file name in the performance_measurement_initialize command. Address range files may contain program symbols (procedure name or static), user defined address ranges, and comments.
  • Page 274 Chapter 8: Making Software Performance Measurements Activity Performance Measurements You can also use the local_symbols_in option with procedure symbols; this allows you to measure activity related to the symbols defined in a single function or procedure. Restoring the Current Measurement The performance_measurement_initialize restore command allows you to restore old performance measurement data from the perf.out file in the current directory.
  • Page 275 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Examples Suppose the "addr_ranges" file contains the names of all the functions in the "ecs" demo program loop: combsort do_sort gen_ascii_data get_targets graph_data interrupt_sim proc_specific read_conditions save_points set_outputs strcpy8 update_system write_hdwr Since these labels are program symbols, you do not have to specify the address range associated with each label;...

  • Page 276: To Interpret Activity Measurement Reports

    Chapter 8: Making Software Performance Measurements Activity Performance Measurements To interpret activity measurement reports • View the performance measurement report. Activity measurements are measurements of the number of accesses (reads or writes) within an address range. The reports generated for activity measurements show you the percentage of analyzer trace states that are in the specified address range, as well as the percentage of time taken by those states.
  • Page 277 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Standard Deviation Deviation from the mean of state count. The following equation is used to calculate standard deviation: Where: Number of traces in the measurement. Average number of states in the range per trace. mean Sum of squares of states in the range per trace.
  • Page 278 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Error Tolerance and Confidence Level An approximate error may exist in displayed information. Error tolerance for a level of confidence is calculated using the mean of the standard deviations and the mean of the means. Error tolerance gives an indication of the stability of the information.
  • Page 279 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Label set_outputs Address Range 177AH thru 180AH Memory Activity State Percent Rel = 31.31 Abs = 25.00 Mean = 128.00 Sdv = 227.46 Time Percent Rel = 31.30 Abs = 24.95 Program Activity State Percent Rel =...
  • Page 280 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Mean = 25.60 Sdv = 114.49 Time Percent Rel = 6.26 Abs = 4.99 Program Activity State Percent Rel = 5.72 Abs = 5.00 Mean = 25.60 Sdv = 114.49 Time Percent Rel = 5.71...
  • Page 281 Chapter 8: Making Software Performance Measurements Activity Performance Measurements graph_data Address Range 197EH thru 1A36H Memory Activity State Percent Rel = 0.00 Abs = 0.00 Mean = 0.00 Sdv = 0.00 Time Percent Rel = 0.00 Abs = 0.00 Program Activity State Percent Rel = 0.00...
  • Page 282 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Graph of Memory Activity relative state percents >= 1 set_outputs 31.31% **************** strcpy8 21.77% *********** interrupt_sim 18.78% ********** write_hdwr 12.52% ******* get_targets 6.26% update_system 6.26% combsort 2.08% Graph of Memory Activity relative time percents >= 1 set_outputs 31.30% ****************...
  • Page 283 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Summary Information for 20 traces Memory Activity State count Relative count 8177 Mean sample 31.45 Mean Standard Dv 75.74 95% Confidence 112.76% Error tolerance Time count Relative Time - Us 5838.56 Program Activity State count Relative count...

  • Page 284: Duration Performance Measurements

    Chapter 8: Making Software Performance Measurements Duration Performance Measurements Duration Performance Measurements Duration measurements provide a best-case/worst-case characterization of code execution time. These measurements record execution times that fall within a set of specified time ranges. The analyzer trace command is set up to store only the entry and exit states of the module to be measured (for example, a C function or Pascal procedure).

  • Page 285: To Set Up The Trace Command For Duration Measurements

    Chapter 8: Making Software Performance Measurements Duration Performance Measurements If a module is entered at the normal point, and then exited by a point other than the defined exit point, the entry point will be ignored. It will be judged the same as any other unused prefetch, and no time-duration measurement will be made.
  • Page 286 Chapter 8: Making Software Performance Measurements Duration Performance Measurements trace after module_name start or module_name end only module_name start or module_name end counting time <RETURN> Where "symbol_entry" and "symbol_exit" are symbols from the user program. Or, where "module_name" is the name of a C function or Pascal procedure (and is listed as a procedure symbol in the global symbol display).

  • Page 287: To Initialize Duration Performance Measurements

    Chapter 8: Making Software Performance Measurements Duration Performance Measurements To initialize duration performance measurements • Use the performance_measurement_initialize command with the duration option. After you set up the trace command, you must tell the SPMT the time ranges to be used in the duration measurement.
  • Page 288 Chapter 8: Making Software Performance Measurements Duration Performance Measurements When no user defined time range file is specified, the following set of default time ranges are used. 1 us 10 us 10.1 us 100 us 100.1 us 500 us 500.1 us 1 ms 1.001 ms 5 ms 5.001 ms 10 ms 10.1 ms 20 ms...

  • Page 289: To Interpret Duration Measurement Reports

    Chapter 8: Making Software Performance Measurements Duration Performance Measurements To interpret duration measurement reports • View the performance measurement report. Duration measurements provide a best-case/worst-case characterization of code execution time. These measurements record execution times that fall within a set of specified time ranges.
  • Page 290 Chapter 8: Making Software Performance Measurements Duration Performance Measurements Standard Deviation Deviation from the mean of time. The following equation is used to calculate standard deviation: Where: Number of intervals. mean Average time. Sum of squares of time in the intervals. sumq Error Tolerance and Confidence Level An approximate error may exist in displayed information.
  • Page 291 Chapter 8: Making Software Performance Measurements Duration Performance Measurements Mean of the means (i.e., mean of the average times in each time range). Examples Consider the following duration measurement report (generated with the commands shown): display trace depth 512 <RETURN> trace after interrupt_sim start or interrupt_sim end only interrupt_sim start or interrupt_sim end counting time <RETURN>...
  • Page 292 Chapter 8: Making Software Performance Measurements Duration Performance Measurements From Address 109E File main(module)."/users/guest/demo/debug_env/hp64751/main.c" Symbolic Reference at interrupt_sim+8A To Address 1014 File main(module)."/users/guest/demo/debug_env/hp64751/main.c" Symbolic Reference at main.interrupt_sim Number of intervals 2550 Maximum Time 182927.360 us Minimum Time 82534.400 us Avg Time 99593.389 us Statistical summary - for 10 traces...

  • Page 293: Running Measurements And Creating Reports

    Chapter 8: Making Software Performance Measurements Running Measurements and Creating Reports Running Measurements and Creating Reports Several performance measurement tasks are the same whether you are making activity or duration measurements. This section describes how to: • Run performance measurements. •...

  • Page 294: To End Performance Measurements

    Chapter 8: Making Software Performance Measurements Running Measurements and Creating Reports Examples To run the performance measurement, enter the following command: performance_measurement_run 20 <RETURN> The command above causes 20 traces to occur. The SPMT processes the trace information after each trace, and the number of the trace being processed is shown on the status line.

  • Page 295: To Create A Performance Measurement Report

    Chapter 8: Making Software Performance Measurements Running Measurements and Creating Reports To create a performance measurement report • Use the perf32 command at the UNIX prompt. The perf32 report generator utility must be used to read the information in the "perf.out"...
  • Page 296 Chapter 8: Making Software Performance Measurements Running Measurements and Creating Reports Examples Now, to generate a report from the "perf.out" file, type the following on the command line to fork a shell and run the perf32 utility: !perf32 | more...

  • Page 297: Making Coordinated Measurements

    Making Coordinated Measurements...
  • Page 298 Measurement Bus (CMB), you can start and stop up to 32 emulators at the same time. You can use the analyzer in one HP 64700 to arm (that is, activate) the analyzers in other HP 64700 Card Cages or to cause emulator execution in other HP 64700 Card Cages to break into the monitor.
  • Page 299 The location of the CMB and BNC connectors on the HP 64700 rear panel is shown in the following figure. CMB Connector BNC Connector Signal Lines on the CMB There are three bi-directional signal lines on the CMB connector on the rear panel of the emulator.
  • Page 300 READY false and will hold it false until it is ready to resume running. When an emulator is reset, it also drives CMB READY false. EXECUTE The CMB EXECUTE line is low true. Any HP 64700 on the CMB can drive this line. It serves as a global interrupt and is processed by both the emulator and the analyzer.

  • Page 301: Setting Up For Coordinated Measurements

    RS-232C communications. Applying RS-232C signals to the CMB connector is likely to result in damage to the HP 64700 Card Cage. To use the CMB, you will need one CMB cable for the first two emulators and one additional cable for every emulator after the first two.
  • Page 302 Chapter 9: Making Coordinated Measurements Setting Up for Coordinated Measurements 1 Connect the cables to the HP 64700 CMB ports.

  • Page 303: To Connect To The Rear Panel Bnc

    * A modification must be performed by your HP Customer Engineer. Emulators using the CMB must use background emulation monitors. At least 3/4 of the HP 64700-Series emulators connected to the CMB must be powered up before proper operation of the entire CMB configuration can be assured.
  • Page 304 Chapter 9: Making Coordinated Measurements Setting Up for Coordinated Measurements 1 Connect one end of a 50 ohm coaxial cable with male BNC connectors to the HP 64700 BNC receptacle and the other end to the appropriate BNC receptacle on the other measuring instrument.

  • Page 305: Starting/Stopping Multiple Emulators

    Chapter 9: Making Coordinated Measurements Starting/Stopping Multiple Emulators Starting/Stopping Multiple Emulators When HP 64700 Card Cages are connected together via the Coordinated Measurement Bus (CMB), you can start and stop up to 32 emulators at the same time. These are called synchronous measurements.

  • Page 306: To Start Synchronous Measurements

    Chapter 9: Making Coordinated Measurements Starting/Stopping Multiple Emulators When you enter a normal trace command, trace at execute is disabled, and the analyzer ignores the CMB EXECUTE signal. Examples To enable synchronous measurements: specify run from 1e8h <RETURN> To trace when synchronous execution begins: specify trace after address main <RETURN>...

  • Page 307: Using Trigger Signals

    Using Trigger Signals The HP 64700 contains two internal lines, trig1 and trig2, over which trigger signals can pass from the emulator or analyzer to other HP 64700s on the Coordinated Measurement Bus (CMB) or other instruments connected to the BNC connector.
  • Page 308 Chapter 9: Making Coordinated Measurements Using Trigger Signals execution can break when a trigger signal is received from the CMB, BNC, or analyzer. You can use the trig2 line to make a connection between the analyzer and the CMB connector or BNC connector so that the analyzer can be armed (that is, enabled) when a trigger signal is received from the CMB or BNC connector.

  • Page 309: To Drive The Emulation Analyzer Trigger Signal To The Cmb

    Chapter 9: Making Coordinated Measurements Using Trigger Signals This section shows you how to: • Drive the emulation analyzer trigger signal to the CMB. • Drive the emulation analyzer trigger signal to the BNC connector. • Break emulator execution on signal from CMB. •...

  • Page 310: To Drive The Emulation Analyzer Trigger Signal To The Bnc Connector

    Chapter 9: Making Coordinated Measurements Using Trigger Signals To drive the emulation analyzer trigger signal to the BNC connector 1 Enter the modify configuration command. 2 Answer "yes" to the "Modify interactive measurement specification?" question. 3 Answer "receive" to the "Should BNC drive or receive Trig1?" question. You could also drive the emulation analyzer trigger to the BNC over the trig2 internal line by specifying that the BNC should receive trig2 and that the emulation analyzer should drive trig2.

  • Page 311: To Break Emulator Execution On Signal From Bnc

    Chapter 9: Making Coordinated Measurements Using Trigger Signals To break emulator execution on signal from BNC 1 Enter the modify configuration command. 2 Answer "yes" to the "Modify interactive measurement specification?" question. 3 Answer "drive" to the "Should BNC drive or receive Trig1?" question. You could also break emulator execution on a trigger signal from the BNC over the trig2 internal line by specifying that the BNC should drive trig2 and that the emulator break should receive trig2.

  • Page 312: To Arm The Emulation Analyzer On Signal From Bnc

    Chapter 9: Making Coordinated Measurements Using Trigger Signals To arm the emulation analyzer on signal from 1 Enter the modify configuration command. 2 Answer "yes" to the "Modify interactive measurement specification?" question. 3 Answer "drive" to the "Should BNC drive or receive Trig2?" question. 4 Answer "receive"...

  • Page 313: Setting X Resources

    Setting X Resources...
  • Page 314 Resources specifications in later files override those in earlier files. Files are read in the following order: The application defaults file. For example, /usr/lib/X11/app-defaults/HP64_Softkey when the operating system is HP-UX or /usr/openwin/lib/X11/app-defaults/HP64_Softkey when the operating system is SunOS.
  • Page 315 Chapter 10: Setting X Resources Resource specifications included in the command line with the -xrm option. System scheme files in directory /usr/hp64000/lib/X11/HP64_schemes. System-wide custom scheme files located in directory $XAPPLRESDIR/HP64_schemes. User-defined scheme files located in directory $HOME/.HP64_schemes (note the dot in the directory name). Scheme files group resource specifications for different displays, computing environments, and languages.

  • Page 316: To Modify The Graphical User Interface Resources

    Application Resources for Schemes Resource Values Description HP64_Softkey.platformScheme HP-UX Names the subdirectory for platform SunOS specific schemes. This resource should be (custom) set to the platform on which the X server is running (and displaying the Graphical User Interface) if it is different than the platform where the application is running.
  • Page 317 Chapter 10: Setting X Resources To modify the Graphical User Interface resources Commonly Modified Application Resources Resource Values Description HP64_Softkey.lines Specifies the number of lines in the main (min. 18) display area. HP64_Softkey.columns Specifies the number of columns, in (min. 80) characters, in the main display area.
  • Page 318 The HP64_Softkey file contains the default definitions for the graphical interface application’s X resources. For example, on an HP 9000 computer you can use the following command to copy the complete HP64_Softkey file to HP64_Softkey.tmp (note that the HP64_Softkey file is several hundred lines long): cp /usr/lib/X11/app-defaults/HP64_Softkey HP64_Softkey.tmp...
  • Page 319 !HP64_Softkey.columns: Save your changes and exit the editor. 3 If the RESOURCE_MANAGER property exists (as is the case with HP VUE — if you’re not sure, you can check by entering the xrdb -query command), use the xrdb command to add the resources to the RESOURCE_MANAGER property. For example: xrdb -merge -nocpp HP64_Softkey.tmp...

  • Page 320: To Use Customized Scheme Files

    3 Modify the $HOME/.HP64_schemes/<platform>/Softkey.<scheme> file. For example, you could modify the "$HOME/.HP64_schemes/HP-UX/Softkey.MyColor" file to change the defined foreground and background colors. Also, since the scheme file name is different than the default, you could comment out various resource settings to cause general foreground and background color definitions to apply to the Graphical User Interface.
  • Page 321 For example, to use the "$HOME/.HP64_schemes/HP-UX/Softkey.MyColor" color scheme file you would set the "HP64_Softkey.colorScheme" resource to "MyColor":...

  • Page 322: To Set Up Custom Action Keys

    Chapter 10: Setting X Resources To set up custom action keys To set up custom action keys • Modify the "actionKeysSub.keyDefs" resource. The "actionKeysSub.keyDefs" resource defines a list of paired strings. The first string defines the text that should appear on the action key pushbutton. The second string defines the command that should be sent to the command line area and executed when the action key is pushed.

  • Page 323: To Set Initial Recall Buffer Values

    Chapter 10: Setting X Resources To set initial recall buffer values To set initial recall buffer values • Modify the "entries" resource for the particular recall buffer. There are six popup recall buffers present in the Graphical User Interface. The resources for these popup recall buffers are listed in the following table.
  • Page 324 Chapter 10: Setting X Resources To set initial recall buffer values Examples To set the initial values for the directory selection dialog box when the Graphical User Interface is used with 68340 emulators, modify the "*m68340*dirSelectSub.entries" resource: *m68340*dirSelectSub.entries: \ "$HOME" \ ".."...

  • Page 325: To Set Up Demos Or Tutorials

    Chapter 10: Setting X Resources To set up demos or tutorials To set up demos or tutorials You can add demos or tutorials to the Graphical User Interface by modifying the resources described in the following tables. Demo Related Component Resources Resource Value Description...
  • Page 326 Chapter 10: Setting X Resources To set up demos or tutorials Tutorial Related Component Resources Resource Value Description *enableTutorial False Specifies whether True Help→Tutorial appears in the pulldown menu. *tutorialPopupSub.indexFile ./Xtutorial/Index-topics Specifies the file containing the list of topic and file pairs. *tutorialPopup.textColumns Specifies the width, in characters, of the of the tutorial...
  • Page 327 Chapter 10: Setting X Resources To set up demos or tutorials 2 Create the demo or tutorial index file. Each line in the index file contains first a quoted string that is the name of the topic which appears in the index popup and second the name of the file that is raised when the topic is selected.

  • Page 329: Part 3 Reference

    Part 3 Reference Descriptions of the product in a dictionary or encyclopedia format.
  • Page 330 Part 3...

  • Page 331: Emulator/Analyzer Interface Commands

    Emulator/Analyzer Interface Commands...

  • Page 332: How Pulldown Menus Map To The Command Line

    Emulator/Analyzer Interface Commands This chapter describes the emulator/analyzer interface commands in alphabetical order. First, the syntax conventions are described and the commands are summarized. How Pulldown Menus Map to the Command Line The following table shows the items available in the pulldown menus and the command line commands to which they map.
  • Page 333 Chapter 11: Emulator/Analyzer Interface Commands Pulldown Command Line File→Context→Directory File→Context→Symbols File→Load→Emulator Config load configuration load <abs_file> File→Load→Executable File→Load→Program Only load <abs_file> nosymbols File→Load→Symbols Only load symbols store trace File→Store→Trace Data File→Store→Trace Spec store trace_spec File→Store→BBA Data bbaunload copy display to File→Copy→Display File→Copy→Memory copy memory to...
  • Page 334 Chapter 11: Emulator/Analyzer Interface Commands Pulldown Command Line Display→Context pwd, pws Display→Memory display memory Display→Memory→Mnemonic () display memory --EXPR-- mnemonic Display→Memory→Mnemonic at PC display memory mnemonic at_pc display memory mnemonic previous_display Display→Memory→Mnemonic Previous Display→Memory→Hex ()→bytes display memory --EXPR-- blocked bytes Display→Memory→Hex ()→words display memory --EXPR-- blocked words Display→Memory→Hex ()→long...
  • Page 335 Chapter 11: Emulator/Analyzer Interface Commands Pulldown Command Line Execution→Run→from PC Execution→Run→from () run from --EXPR-- Execution→Run→from Transfer Address run from transfer_address Execution→Run→from Reset run from reset Execution→Run→until () run until --EXPR-- Execution→Step Source→from PC step source Execution→Step Source→from () step source from --EXPR-- Execution→Step Source→from Transfer step source from transfer_address Address...

  • Page 336: How Popup Menus Map To The Command Line

    Chapter 11: Emulator/Analyzer Interface Commands Pulldown Command Line Settings→Source/Symbol Modes→Absolute set source off symbols off Settings→Source/Symbol Modes→Symbols set source off symbols on Settings→Source/Symbol Modes→Source set source on inverse_video on symbols on Mixed set source only inverse_video off symbols on Settings→Source/Symbol Modes→Source Only Settings→Display Modes→Source Only Settings→Pod Command Keyboard...
  • Page 337 Chapter 11: Emulator/Analyzer Interface Commands Symbols Display Popup Command Line Display Local Symbols display local_symbols_in --SYMB-- Display Parent Symbols display local_symbols_in --SYMB--, display global_symbols Cut Full Symbol Name Edit File Defining Symbol ! vi +<line> <file> ! no_prompt_before_exit Status Line Popup Command Line Remove Temporary Message Display Error Log...

  • Page 338: Syntax Conventions

    Chapter 11: Emulator/Analyzer Interface Commands Syntax Conventions Conventions used in the command syntax diagrams are defined below. Oval-shaped Symbols Oval-shaped symbols show options available on the softkeys and other commands that are available, but do not appear on softkeys (such as log_commands and wait). These appear in the syntax diagrams as: Rectangular-shaped Symbols Rectangular-shaped symbols contain prompts or references to other syntax...

  • Page 339: Commands

    Chapter 11: Emulator/Analyzer Interface Commands Commands Emulator/analyzer interface commands are summarized in the table below and described in the following pages. !UNIX_COMMAND display event_log modify memory bbaunload display global_symbols modify register break display local_symbols_in modify software_breakpoints cd (change directory) display memory name_of_module cmb_execute display pod_command...

  • Page 340: Bbaunld

    BBA information to a file. Then, you can generate reports based on the stored information. See Also Refer to the HP Branch Validator (BBA) User’s Guide for complete details on the bbaunload command syntax.

  • Page 341: Break

    Chapter 11: Emulator/Analyzer Interface Commands break break This command causes the emulator to leave user program execution and begin executing in the monitor. The behavior of break depends on the state of the emulator: running Break diverts the processor from execution of your program to the emulation monitor.

  • Page 342: Cmb_Execute

    Chapter 11: Emulator/Analyzer Interface Commands cmb_execute cmb_execute The cmb_execute command causes the emulator to emit an EXECUTE pulse on its rear panel Coordinated Measurement Bus (CMB) connector. All emulators connected to the CMB (including the one sending the CMB EXECUTE pulse) and configured to respond to this signal will take part in the measurement.

  • Page 343: Copy

    Chapter 11: Emulator/Analyzer Interface Commands copy copy Use this command with various parameters to save or print emulation and analysis information.
  • Page 344 Chapter 11: Emulator/Analyzer Interface Commands copy The copy command copies selected information to your system printer or listing file, or directs it to a UNIX process. Depending on the information you choose to copy, default values may be options selected for the previous execution of the display command. For example, if you display memory locations 10h through 20h, then issue a copy memory to myfile command, myfile will list only memory locations 10h through 20h.
  • Page 345 Chapter 11: Emulator/Analyzer Interface Commands copy FCODE The function code used to define the address space being referenced. See the syntax diagram for FCODE to see a list of the function codes available and for an explanation of those codes. <FILE>...
  • Page 346 This copies the information into a file without headings. pod_command This allows you to copy the most recent commands sent to the HP 64700 Series emulator/analyzer. printer This option specifies your system printer as the destination device for the copy command.
  • Page 347 Chapter 11: Emulator/Analyzer Interface Commands copy Examples copy local_symbols_in mod_name to printer <RETURN> copy local_symbols_in mod_name: to linenumfile <RETURN> copy memory start to printer <RETURN> copy memory 0 thru 100h , start thru +5 , 500H , target2 to memlist <RETURN> copy memory 2000h thru 204fh to memlist <RETURN>...

  • Page 348: Count

    Chapter 11: Emulator/Analyzer Interface Commands COUNT COUNT The analyzer trace depth is 1024 states. A state is a unique combination of address, data, and status values occurring on the emulation bus simultaneously. When counting is off, the analyzer can store 1024 states in the trace buffer. When counting is on, the analyzer can only store 512 states in the trace buffer.
  • Page 349 Chapter 11: Emulator/Analyzer Interface Commands COUNT Examples trace after START counting state LOOP2 <RETURN> trace counting time <RETURN> See Also The trace command.

  • Page 350: Display

    Chapter 11: Emulator/Analyzer Interface Commands display display This command displays selected information on your screen.
  • Page 351 Chapter 11: Emulator/Analyzer Interface Commands display You can use the <Up arrow>, <Down arrow>, <PREV>, and <NEXT> keys to view the displayed information. For software_breakpoints, data, memory, and trace displays you can use the <CTRL>g and <CTRL>f keys to scroll left and right if the information goes past the edge of the screen.
  • Page 352 Chapter 11: Emulator/Analyzer Interface Commands display global_symbols This command displays the global symbols defined for the current absolute file. Global symbols are symbols declared as global in the source file. They include procedure names, variables, constants, and file names. When the display global_symbols command is used, the listing will include the symbol name and its logical address.
  • Page 353 Chapter 11: Emulator/Analyzer Interface Commands display If the emulation session is continued from a previous session, the listing will include any previously defined breakpoints. The column marked "status" shows whether the breakpoint is pending, inactivated, or unknown. A pending breakpoint causes the processor to enter the emulation monitor upon execution of that breakpoint.
  • Page 354 Chapter 11: Emulator/Analyzer Interface Commands display <TYPE> Meaning byte Hex display of one 8-bit location. word Hex display of one 16-bit location. long Hex display of one 32-bit location. int8 Display of one 8-bit location as a signed integer using two’s complement notation.
  • Page 355 Chapter 11: Emulator/Analyzer Interface Commands display display registers <RETURN> display registers BASIC D2 <RETURN> display simulated_io <RETURN> display software_breakpoints <RETURN> display software_breakpoints offset_by 1000H <RETURN> See Also The copy, modify, set, and step command descriptions and the following pages which describe the display memory and display trace commands.

  • Page 356: Display Memory

    Chapter 11: Emulator/Analyzer Interface Commands display memory display memory This command displays the contents of the specified memory location or series of locations.
  • Page 357 Chapter 11: Emulator/Analyzer Interface Commands display memory The memory contents can be displayed in mnemonic, hexadecimal, or real number format. In addition, the memory addresses can be listed offset by a value, which allows the information to be easily compared to the program listing. When displaying memory mnemonic and stepping, the next instruction that will step is highlighted.
  • Page 358 Chapter 11: Emulator/Analyzer Interface Commands display memory FCODE The function code used to define the address space being referenced. See the syntax diagram for FCODE to see a list of the function codes available and for an explanation of those codes. long Displays memory in a 64-bit real number format or 32-bit long words when preceded by blocked or absolute.
  • Page 359 Chapter 11: Emulator/Analyzer Interface Commands display memory command. The comma is also a delimiter between values when specifying multiple addresses. Examples You can display memory in real number and mnemonic formats: display memory 2000h thru 202fh , 2100h real long <RETURN>...

  • Page 360: Display Trace

    Chapter 11: Emulator/Analyzer Interface Commands display trace display trace This command displays the contents of the trace buffer.
  • Page 361 Chapter 11: Emulator/Analyzer Interface Commands display trace Captured information can be presented as absolute hexadecimal values or in mnemonic form. The processor status values captured by the analyzer can be listed mnemonically or in hexadecimal or binary form. Addresses captured by the analyzer are physical addresses. The offset_by option subtracts the specified offset from the addresses of the executed instructions before listing the trace.
  • Page 362 Chapter 11: Emulator/Analyzer Interface Commands display trace depth <DEPTH#> This defines the number of states to be uploaded by the interface. Note that after you have changed the trace depth, execute the command wait measurement_complete before displaying the trace. Otherwise the new trace states will not be available.
  • Page 363 Chapter 11: Emulator/Analyzer Interface Commands display trace This option is also useful for displaying symbols and source lines in dynamically relocated programs. Note that when using the set source only command, the analyzer may operate more slowly than when using the set source on command. This is an operating characteristic of the analyzer: When you use the command set source on, and are executing only assembly language code (not high-level language code), no source lines are displayed.

  • Page 364: End

    Chapter 11: Emulator/Analyzer Interface Commands This command terminates the current emulation session. You can end the emulation session and keep the emulator in a locked state. The current emulation configuration is stored, so that you can continue the emulation session on reentry to the emulator. You can select another measurement system when ending the current session.
  • Page 365 Chapter 11: Emulator/Analyzer Interface Commands Examples end <RETURN> end release_system <RETURN> See Also The "Exiting the Emulator/Analyzer Interface" section in the "Using the Emulator/Analyzer Interface" chapter.

  • Page 366: Expr

    Chapter 11: Emulator/Analyzer Interface Commands --EXPR-- --EXPR-- An expression is a combination of numeric values, symbols, operators, and parentheses used to specify address, data, status, executed address, or any other value used in the emulation commands. The function of an expression (--EXPR--) is to let you define the address, data, status, or executed address expression that fits your needs.
  • Page 367 Chapter 11: Emulator/Analyzer Interface Commands --EXPR-- <NUMBER> This can be an integer in any base (binary, octal, decimal, or hexadecimal), or can be a string of characters enclosed with quotation marks. <OP> This represents an algebraic or logical operand and may be any of the following (in order of precedence): modulo multiplication...
  • Page 368 Chapter 11: Emulator/Analyzer Interface Commands --EXPR-- is the same as disp_buf thru disp_buf + 25 Examples 05fxh 0ffffh disp_buf + 5 symb_tbl + (offset / 2) start mod_name: line 15 end See Also The SYMB syntax description.

  • Page 369: Fcode

    Chapter 11: Emulator/Analyzer Interface Commands FCODE FCODE The function code is used to define the address space being referenced. Select the appropriate function code from those listed below. CPU space. Data space. none Causes the emulator to ignore the function code bits. Program space.
  • Page 370 Chapter 11: Emulator/Analyzer Interface Commands FCODE Examples To copy a portion of user data memory to a file: copy memory fcode ud 1000H thru 1fffH to mymem <RETURN> To modify a location in program memory: modify memory fcode p 5000h long to 12345678h <RETURN>...

  • Page 371: Forward

    Chapter 11: Emulator/Analyzer Interface Commands forward forward This command lets you forward commands to other HP 64700 interfaces that use the "emul700dmn" daemon process to coordinate actions between the interfaces. Sends messages to the Broadcast Message Server or BMS. <COMMAND>...

  • Page 372: Help

    Chapter 11: Emulator/Analyzer Interface Commands help help Displays information about system and emulation features during an emulation session. Typing help or ? displays softkey labels that list the options on which you may receive help. When you select an option, the system will list the information to the screen.
  • Page 373 Chapter 11: Emulator/Analyzer Interface Commands help copy reset stop_trace software_breakpoints registers expressions (--EXPR--) symbols (--SYMB--) specify cmb_execute wait pod_command bbaunload coverage performance_measurement_initialize performance_measurement_run performance_measurement_end...

  • Page 374: Load

    Chapter 11: Emulator/Analyzer Interface Commands load load This command transfers absolute files from the host computer into emulation or target system RAM. With other parameters, the load command can load emulator configuration files, trace records, trace specifications, or symbol files. The absolute file contains information about where the file is stored.
  • Page 375 Chapter 11: Emulator/Analyzer Interface Commands load FCODE The function code used to define the address space being referenced. See the syntax diagram for FCODE to see a list of the function codes available and for an explanation of those codes. <FILE>...

  • Page 376: Log_Commands

    Chapter 11: Emulator/Analyzer Interface Commands log_commands log_commands This command allows you to record commands that are executed during an emulation session. A command file is an ASCII file containing Softkey Interface commands. The interface can read a command file and execute its commands as if they were typed into the command line.
  • Page 377 Chapter 11: Emulator/Analyzer Interface Commands log_commands Examples log_commands to logfile <RETURN> log_commands off <RETURN> See Also The wait command.

  • Page 378: Modify

    Chapter 11: Emulator/Analyzer Interface Commands modify modify This command allows you to observe or change information specific to the emulator.
  • Page 379 Chapter 11: Emulator/Analyzer Interface Commands modify The modify command is used to: • Modify contents of memory (as integers, strings, or real numbers). • Modify the contents of the processor registers. • View or edit the current emulation configuration. • Modify the software breakpoints table.
  • Page 380 Chapter 11: Emulator/Analyzer Interface Commands modify FCODE The function code used to define the address space being referenced. See the syntax diagram for FCODE to see a list of the function codes available and for an explanation of those codes. keyboard_to_simio Lets the keyboard to interact with your program through the simulated I/O software.
  • Page 381 Chapter 11: Emulator/Analyzer Interface Commands modify Memory modifications of integer values use the currently set display memory mode. Byte is the default. Memory modifications of "real" values use the currently set display memory mode. Short is the default. permanent Sets a permanent breakpoint. The software breakpoint instruction remains in the program until the breakpoint is inactivated or removed.
  • Page 382 Chapter 11: Emulator/Analyzer Interface Commands modify string Modify memory values to the ASCII character string given by <STRING>. <STRING> Quoted ASCII string including special characters as follows: null newline horizontal tab backspace carriage return form feed backslash single quote \’ bit pattern \ooo (where ooo is an octal number) temporary...
  • Page 383 Chapter 11: Emulator/Analyzer Interface Commands modify modify software_breakpoints enable <RETURN> modify software_breakpoints set loop1 end , loop2 end , 0E40H <RETURN> modify software_breakpoints clear <RETURN> modify software_breakpoints set <RETURN> See Also The copy, display, load, store commands.

  • Page 384: Performance_Measurement_End

    Chapter 11: Emulator/Analyzer Interface Commands performance_measurement_end performance_measurement_end This command stores data previously generated by the performance_measurement_run command, in a file named "perf.out" in the current working directory. The file named "perf.out" is overwritten each time this command is executed. Current measurement data existing in the emulation system is not altered by this command.

  • Page 385: Performance_Measurement_Initialize

    Chapter 11: Emulator/Analyzer Interface Commands performance_measurement_initialize performance_measurement_initialize This command sets up performance measurements. The emulation system will verify whether a symbolic database has been loaded. If a symbolic database has been loaded, the performance measurement is set up with the addresses of all global procedures and static symbols. If a valid database has not been loaded, the system will default to a predetermined set of addresses, which covers the entire emulation processor address range.
  • Page 386 Chapter 11: Emulator/Analyzer Interface Commands performance_measurement_initialize <FILE> This represents a file you specify to supply user-defined address or time ranges to the emulator. global_symbols This option specifies that the performance measurement will be set up with the addresses of all global symbols and procedures in the source program. local_symbols_in This causes addresses of the local symbols to be used as the default ranges for the measurement.

  • Page 387: Performance_Measurement_Run

    Chapter 11: Emulator/Analyzer Interface Commands performance_measurement_run performance_measurement_run This command begins a performance measurement. This command causes the emulation system to reduce trace data contained in the emulation analyzer, which will then be used for analysis by the performance measurement software. The default is to process data presently contained in the analyzer.
  • Page 388 Chapter 11: Emulator/Analyzer Interface Commands performance_measurement_run Refer to the "Making Software Performance Measurements" chapter for examples of performance measurement specification and use.
  • Page 389 Chapter 11: Emulator/Analyzer Interface Commands pod_command pod_command Allows you to control the emulator through the direct HP 64700 Terminal Interface. The HP 64700 Card Cage contains a low-level Terminal Interface, which allows you to control the emulator’s functions directly. You can access this interface using pod_command.

  • Page 390: Pod_Command

    Chapter 11: Emulator/Analyzer Interface Commands pod_command The parameters are as follows: keyboard Enters an interactive mode where you can simply type Terminal Interface commands (unquoted) on the command line. Use display pod_command to see the results returned from the emulator. <POD_CMD>...

  • Page 391: Qualifier

    Chapter 11: Emulator/Analyzer Interface Commands QUALIFIER QUALIFIER The QUALIFIER parameter is used with trace only, trace prestore, TRIGGER, and trace counting to specify states captured during the trace measurement. You may specify a range of states or specific states to be captured. You can continue to "or"...
  • Page 392 Chapter 11: Emulator/Analyzer Interface Commands QUALIFIER data The value following this softkey is searched for on the lines that monitor the emulation processor’s data bus. --EXPR-- An expression is a combination of numeric values, symbols, operators, and parentheses, specifying an address, data, status value. See the EXPR syntax diagram for details.
  • Page 393 Chapter 11: Emulator/Analyzer Interface Commands QUALIFIER trace before status write <RETURN> trace about address 1000H status write <RETURN> See Also The trace command.

  • Page 394: Reset

    Chapter 11: Emulator/Analyzer Interface Commands reset reset This command suspends target system operation and reestablishes initial emulator operating parameters, such as reloading control registers. The reset signal is latched when the reset command is executed and released by either the run or break command. See Also The break and run commands.

  • Page 395: Run

    If the emulator is configured to participate in the READY signal on the CMB, then this emulator will release the READY signal so that it will go TRUE if all other HP 64700 emulators participating on that signal are also ready. See the cmb_execute command description.
  • Page 396 Chapter 11: Emulator/Analyzer Interface Commands FCODE The function code used to define the address space being referenced. See the syntax diagram for FCODE to see a list of the function codes available and for an explanation of those codes. from This specifies the address from which program execution is to begin.

  • Page 397: Sequencing

    Chapter 11: Emulator/Analyzer Interface Commands SEQUENCING SEQUENCING Lets you specify complex branching activity that must be satisfied to trigger the analyzer. Sequencing provides you with parameters for the trace command that let you define branching conditions for the analyzer trigger. You are limited to a total of seven sequence terms, including the trigger, if no windowing specification is given.
  • Page 398 Chapter 11: Emulator/Analyzer Interface Commands SEQUENCING <#TIMES> Prompts you for the number of times a qualifier must be found. then Allows you to add multiple sequence terms, each with its own qualifier and occurrence count. restart Selects global restart. If the analyzer finds the restart qualifier while searching for a sequence term, the sequencer is reset and searching begins for the first sequence term.

  • Page 399: Set

    Chapter 11: Emulator/Analyzer Interface Commands Controls the display format for the data, memory, register, software breakpoint, and trace displays. With the set command, you can adjust the display format results for...
  • Page 400 Chapter 11: Emulator/Analyzer Interface Commands various measurements, making them easier to read and interpret. Formatting of source lines, symbol display selection and width, and update after measurement can be defined to your needs. The display command uses the set command specifications to format measurement results for the display window.
  • Page 401 1 through 50 may be entered. source memory_only_ This provides a way to default the memory and trace displays to a setting that HP trace_on believes is the nicest possible formats for memory and trace displays. Parameters such as "source on/only", number of source lines to show, display width, and turning symbols on are all governed by this one selection.
  • Page 402 Chapter 11: Emulator/Analyzer Interface Commands This option prevents inclusion of source lines in the trace and memory mnemonic display lists. This option displays source program lines preceding actual processor instructions with which they correlate. This enables you to correlate processor instructions with your source program code.
  • Page 403 Chapter 11: Emulator/Analyzer Interface Commands source This allows you to specify the width (in columns) of the source lines in the memory mnemonic display. To adjust the width of the source lines in the trace display, increase the widths of the label and/or mnemonic fields. label This lets you specify the address width (in columns) of the address field in the trace list or label (symbols) field in any of the other displays.

  • Page 404: Specify

    Chapter 11: Emulator/Analyzer Interface Commands specify specify This command prepares a run or trace command for execution, and is used with the cmb_execute command. When you precede a run or trace command with specify, the system does not execute your command immediately. Instead, it waits until until an EXECUTE signal is received from the Coordinated Measurement Bus or until you enter a cmb_execute command.
  • Page 405 Chapter 11: Emulator/Analyzer Interface Commands specify The parameters are as follows: disable This option turns off the specify condition of the run process. from --EXPR-- This is used with the specify run from command. An expression is a combination of numeric values, symbols, operators, and parentheses, specifying a memory address.

  • Page 406: Step

    Chapter 11: Emulator/Analyzer Interface Commands step step The step command allows sequential analysis of program instructions by causing the emulation processor to execute a specified number of assembly instructions or source lines. You can display the contents of the processor registers, trace memory, and emulation or target memory after each step command.
  • Page 407 Chapter 11: Emulator/Analyzer Interface Commands step The parameters are as follows: --EXPR-- An expression is a combination of numeric values, symbols, operators, and parentheses specifying a memory address. See the EXPR syntax diagram. FCODE The function code used to define the address space being referenced. See the syntax diagram for FCODE to see a list of the function codes available and for an explanation of those codes.

  • Page 408: Stop_Trace

    Chapter 11: Emulator/Analyzer Interface Commands stop_trace stop_trace This command terminates the current trace and stops execution of the current measurement. The analyzer stops searching for trigger and trace states. If trace memory is empty (no states acquired), nothing will be displayed. See Also The trace command.

  • Page 409: Store

    Chapter 11: Emulator/Analyzer Interface Commands store store This command lets you save the contents of specific memory locations in an absolute file. You also can save trace memory contents in a trace file. The store command creates a new file with the name you specify, if there is not already an absolute file with the same name.
  • Page 410 Chapter 11: Emulator/Analyzer Interface Commands store memory This causes selected memory locations to be stored in the specified HP64000 format file with a .X extension. thru This allows you to specify that ranges of memory be stored. Use this in the store memory command to separate memory locations from the file identifier.

  • Page 411: Symb

    Chapter 11: Emulator/Analyzer Interface Commands --SYMB-- --SYMB--...
  • Page 412 Chapter 11: Emulator/Analyzer Interface Commands --SYMB-- This parameter is a symbolic reference to an address, address range, file, or other value. Symbols may be: • Combinations of paths, filenames, and identifiers defining a scope, or referencing a particular identifier or location (including procedure entry and exit points).
  • Page 413 Chapter 11: Emulator/Analyzer Interface Commands --SYMB-- The parameters are as follows: entry_exit_range The range of addresses beginning with the entry point and ending with the return instruction. The entry point is the address used by other files when they call this procedure.
  • Page 414 SRU assigns an identifier and tags it with type procedure. prospecial Prospecial symbols are symbols that were created by the HP SRU (such as entry, exit, and return). They are derived symbols, not intended for the product user.
  • Page 415 Chapter 11: Emulator/Analyzer Interface Commands --SYMB-- Examples The following short C code example should help illustrate how symbols are maintained by SRU and referenced in your emulation commands. File /users/dave/control.c: int *port_one; main () int port_value; port_ptr = port_one; port_value = 10; process_port (port_ptr, port_value);...
  • Page 416 Chapter 11: Emulator/Analyzer Interface Commands --SYMB-- The symbol tree as built by SRU might appear as follows, depending on the object module format and compiler used: Note that SRU does not build tree nodes for variables that are dynamically allocated on the stack at run-time, such as i and j within the delay () procedure.
  • Page 417 Here are some examples of referencing different symbols in the above programs: control.c:main control.c:port_one porthand.c:utils.c:delay The last example above only works with IEEE-695 object module format; the HP object module format does not support referencing of include files that generate program code. porthand.c:process_port.i porthand.c:process_port.BLOCK_1.i...
  • Page 418 Chapter 11: Emulator/Analyzer Interface Commands --SYMB-- and made a reference to symbol i2, the retrieval utilities attempt to find a symbol called porthand.c:process_port.BLOCK_1.i2 which would not be found. The symbol utilities would then strip BLOCK_1 from the current working symbol, yielding porthand.c:process_port.i2 which is a valid symbol.
  • Page 419 Chapter 11: Emulator/Analyzer Interface Commands sync_sim_registers sync_sim_registers The sync_sim_registers command synchronizes the 68340’s system integration module (SIM) registers to the emulator’s CF_SIM registers. The parameters are as follows: from_68340_to_conf Copies the microprocessor’s SIM registers into the emulator’s CF_SIM registers. to_68340_from_conf Copies the emulator’s CF_SIM registers into the microprocessor’s SIM registers.

  • Page 420: Trace

    Chapter 11: Emulator/Analyzer Interface Commands trace trace This command allows you to trace program execution using the emulation analyzer. The options shown can be executed once for each trace command. Refer to the COUNT, QUALIFIER, SEQUENCING, TRIGGER, and WINDOW diagrams for details on setting up a trace.
  • Page 421 This option allows you to specify the external trigger as a trace qualifier, for coordinating measurements between multiple HP 64700s, or an HP 64700 and another instrument. Before arm_trig2 can appear as an option, you must modify the emulation configuration interactive measurement specification.
  • Page 422 Chapter 11: Emulator/Analyzer Interface Commands trace on_halt When using this option, the analyzer will continue to capture states until the emulation processor halts or until a stop_trace command is executed. When this option is used, the break_on_trigger, repetitively, and TRIGGER options cannot be included in the command.
  • Page 423 Chapter 11: Emulator/Analyzer Interface Commands trace Examples trace after 1000H <RETURN> trace only address range 1000H thru 1004H <RETURN> trace after address 1000H occurs 2 only address range 1000H thru 1004H break_on_trigger <RETURN> See Also The copy trace, display trace, load trace, load trace_spec, specify trace, store trace, and store trace_spec commands.

  • Page 424: Trigger

    Chapter 11: Emulator/Analyzer Interface Commands TRIGGER TRIGGER This parameter lets you define where the analyzer will begin tracing program information during a trace measurement. A trigger is a QUALIFIER. When you include the occurs option, you can specify the trigger to be a specific number of occurrences of a QUALIFIER (see the QUALIFIER syntax diagram).
  • Page 425 Chapter 11: Emulator/Analyzer Interface Commands TRIGGER Examples trace after MAIN <RETURN> trace after 1000H then data 5 <RETURN> Also see the trace command examples. See Also The trace command. Also, refer to the "Making Coordinated Measurements" chapter.

  • Page 426: Wait

    Chapter 11: Emulator/Analyzer Interface Commands wait wait This command allows you to present delays to the system. The wait command can be an enhancement to a command file, or to normal operation at the main emulation level. Delays allow the emulation system and target processor time to reach a certain condition or state before executing the next emulation command.
  • Page 427 Chapter 11: Emulator/Analyzer Interface Commands wait The parameters are as follows: measurement This causes the system to pause until a pending measurement completes (a trace _complete data upload process completes), or until a <CTRL>c signal is received. If a measurement is not in progress, the wait command will complete immediately. This causes the system to wait for a <CTRL>c signal or for a pending measurement to complete.

  • Page 428: Window

    Chapter 11: Emulator/Analyzer Interface Commands WINDOW WINDOW Lets you select which states are stored by the analyzer. WINDOW allows you to selectively toggle analyzer operation. When enabled, the analyzer will recognize sequence terms, trigger terms, and will store states. When disabled, the analyzer is effectively off, and only looks for a particular enable term.
  • Page 429 Chapter 11: Emulator/Analyzer Interface Commands WINDOW See Also The trace command and the SEQUENCING and QUALIFIER syntax descriptions.

  • Page 431: Error Messages

    Error Messages...
  • Page 432 Error Messages This chapter contains a list of error messages that may occur while operating the emulator and analyzer. The error log records error messages received during the emulation session. You may want to display the error log to view the error messages. Sometimes several messages will be displayed for a single error to help you locate a problem quickly.

  • Page 433: Graphical/Softkey Interface Messages - Unnumbered

    Graphical/Softkey Interface Messages - Unnumbered Address range too small for request - request truncated Cause: Too small of an address range is specified in a modify memory command. Action: Specify a larger memory range. Cannot create module file: Cause: Insufficient disk space for the module file. Action: Check disk space under /usr/hp64000.
  • Page 434 Cause: The host system could not continue the previous emulation session because it could not load the continue file. Action: Try again. If the failure continues, call your HP Service Representative. Continuing previous session, continue file loaded Cause: This is a status message. An emulation session which was ended earlier with the end command has been restarted.
  • Page 435 (performance verification) command on the emulator to verify that it is functioning properly. Also, verify proper software installation. If loading default configuration still fails, then call your HP 64000 representative. <CONFIGURATION FILENAME> does not exist Cause: The configuration file you are trying to load does not exist.
  • Page 436 Cause: Communication between the emulator and the host system to continue the emulation session failed. Action: Check the data communication switch settings on the rear panel of the HP 64700 series emulator. If necessary, refer to the HP 64700 Installation/Service Guide.
  • Page 437 Emul700dmn version incompatible with this product Cause: The emulation session could not begin because the version of the HP 64700 emulator daemon executable on host system is not compatible with the version of the Softkey Interface you are using.
  • Page 438 Error in configuration process Error starting configuration process Cause: Unexpected configuration error. Action: Verify proper software installation and call your HP 64000 representative. Fatal error from function <ADDRESS OF FUNCTION> Cause: This is an unexpected fatal system error. Action: Cycle power on the emulator and start again. If this is a persistent problem, call your HP 64000 representative.
  • Page 439 Cause: A user abort occurred while attempting to connect via LAN. Action: Possibly connecting to an emulator many miles away, be patient. HP 64700 I/O error; power down detected Cause: The emulator power was cycled. Action: Do not do this during a user interface session; this may force the user interface to end immediately.
  • Page 440 Chapter 12: Error Messages Graphical/Softkey Interface Messages - Unnumbered Illegal status combination Cause: You tried to specify combinations of status qualifiers in expressions incorrectly when entering commands. Action: Refer to the "Emulator/Analyzer Interface Commands" chapter for information about syntax of commands. Illegal symbol name Cause: You tried to specify incorrect symbol names when entering commands.
  • Page 441 Chapter 12: Error Messages Graphical/Softkey Interface Messages - Unnumbered Insufficient emulation memory, memory map may be incomplete Cause: You can map only the amount of emulation memory available in your emulator. Trying to map additional unavailable memory may cause information to be missing from your memory map.
  • Page 442 Chapter 12: Error Messages Graphical/Softkey Interface Messages - Unnumbered Joining session already in progress, user interface defaulted Cause: When operating the emulator in multiple windows, a new emulation session is "joined" to a current session. In this case, the new session used the user interface default selections.
  • Page 443 Chapter 12: Error Messages Graphical/Softkey Interface Messages - Unnumbered Memory block list unreadable Memory range overflow Cause: A modify memory command is attempted that would cross physical 0. Action: Limit the modify memory command to not overflow physical 0 or break the command into two separate modify commands.
  • Page 444 Chapter 12: Error Messages Graphical/Softkey Interface Messages - Unnumbered No valid trace data Cause: You tried to store trace data before a trace was completed. Action: Wait until valid trace data is available before attempting to store a trace. Not a valid trace file - load aborted Cause: You tried to load a file.TR that was not created by the emulation session.
  • Page 445 Chapter 12: Error Messages Graphical/Softkey Interface Messages - Unnumbered Perfinit - error in input file line <LINE NUMBER> invalid symbol You included a "label" file name with your "performance_measurement_initialize" command, and that file contains an invalid symbol. Action: Edit the file and correct the invalid symbol. Perfinit - error in input file line <NUMBER>...
  • Page 446 Chapter 12: Error Messages Graphical/Softkey Interface Messages - Unnumbered Performance tool must be initialized Cause: You tried to make a performance measurement when the Software Performance Measurement Tool (SPMT) was not initialized. Action: The Software Performance Measurement Tool (SPMT) must be initialized before making performance measurements on your software.
  • Page 447 Cause: The emulator was started using a new emulation session, and the user interface was set to default selections. Action: Call your HP Service Representative. Status unknown, run "emul700 -l <LOGICAL NAME>" Cause: The host system cannot determine the status of the emulator.
  • Page 448 Example: display trace symbols on. Timeout in emul700dmn communication Cause: The host system could not start the emulation session because the HP 64700 emulator process ran out of time before the emulator could start. Action: You must press end_release_system to exit this emulation session completely;...
  • Page 449 Unexpected message from emul700dmn Cause: The host system could not start the emulation session because of an unexpected message from the HP 64700 emulator process command. Action: You must press end_release_system to exit this emulation session completely; then start a new session. Make sure the host system is operating...

  • Page 450: Graphical/Softkey Interface Messages - Numbered

    Chapter 12: Error Messages Graphical/Softkey Interface Messages - Numbered Graphical/Softkey Interface Messages - Numbered These numbered messages can occur because of various problems with the emulator/analyzer. 10315 Logical emulator name unknown; not found in 64700tab file Cause: This message may occur while trying to start up the emulator. It indicates that the emulator name specified could not be found in the 64700tab.net or /etc/hosts files.
  • Page 451 Cause: There may be characters dropped in the information returned from the emulator. Action: Ignore this message unless it becomes frequent. If it becomes frequent, you may have a fatal error; call your HP 64700 representative. 10351 Exceeded maximum 64700 command line length Cause: Your command is longer than 240 characters.
  • Page 452 Chapter 12: Error Messages Graphical/Softkey Interface Messages - Numbered Action: Upgrade the interface software of product firmware. 10360 Analyzer limitation; all range resources in use Analyzer limitation; all pattern resources in use Analyzer limitation; all expression resources in use Cause: Your trace specification would use more than the maximum number of resources available to the analyzer.

  • Page 453: Terminal Interface Messages

    Chapter 12: Error Messages Terminal Interface Messages Terminal Interface Messages This section contains descriptions of error messages that can occur while using the Terminal Interface. The error messages are listed in numerical order, and each description includes the cause of the error and the action you should take to remedy the situation.
  • Page 454 Chapter 12: Error Messages Terminal Interface Messages Action: You must break the emulator’s execution into the monitor before you can enter the command. Emulator is in the reset state Cause: You have entered a command that requires the emulator to be running in the monitor (for example, displaying registers).
  • Page 455 Chapter 12: Error Messages Terminal Interface Messages Stack is in emulation ROM Cause: Your stack pointer pointed to a location in memory mapped as emulation ROM; you then attempted to run or step the emulation processor. The emulator was unable to access the stack to complete the transition from the monitor to the user program or vice versa.

  • Page 456: 68340 Emulator Messages

    Chapter 12: Error Messages Terminal Interface Messages Monitor failure; halted Cause: The monitor is unable to run because the processor is halted (due to an external halt line or a halt instruction). Action: Release the external halt and retry the operation. If the processor halted due to a halt instruction, try the reset command, then retry the operation.
  • Page 457 Chapter 12: Error Messages Terminal Interface Messages cannot fit into one 4 Kbyte range, you must map one of the ranges to single-port emulation memory. Dual ported memory in use by foreground monitor Cause: You attempted to map an address range to the 4 Kbyte block of dual-port emulation memory when it has already been allocated to the foreground monitor.
  • Page 458 Chapter 12: Error Messages Terminal Interface Messages cs0 can be used on one term only Cause: You attempted to map a second address range for global chip select operation. Only one address range can be mapped for this purpose. Action: You must remove the current mapper term that is assigned the cs0 attribute before you can map a different range for global chip select operation.
  • Page 459 Chapter 12: Error Messages Terminal Interface Messages Supervisor stack pointer is odd or uninitialized Supervisor stack is located in emulation ROM Supervisor stack is located in guarded memory Cause: You are using a foreground monitor, and you have attempted to run or step when the stack pointer contains an odd value or when the stack pointer contains an address that is mapped as emulation ROM or guarded memory.
  • Page 460 Chapter 12: Error Messages Terminal Interface Messages Unable to set trace vector to <TRACE_ENTRY_address>; vector table write failed Cause: In order to step when using a foreground monitor, the trace vector must contain the address of the monitor program’s TRACE_ENTRY label (which equals the monitor base address plus 800H).
  • Page 461 Cause: You have attempted to modify the MBAR or CF_MBAR register with a value that masks supervisor data space by setting bit 6. The HP 64751 emulator requires an address space to access 68340 SIM registers and, therefore, doesn’t let you set bit 6 in the MBAR or CF_MBAR register.

  • Page 462: General Emulator And System Messages

    68340 probe. Fuse F1 blown on HP64748C ABG Control Board Cause: The emulator detects a blown fuse on the HP 64748C ABG Control Board. Action: Contact your Hewlett-Packard Representative. General Emulator and System Messages...
  • Page 463 Records expected: %s; records received: %s Cause: The HP 64700 received a different number of records than it expected to receive during a transfer operation. Action: Retry the transfer. If the failure is repeated, make sure that the data communications parameters are set correctly on the host and on the HP 64700.
  • Page 464 Action: Retry the transfer. Make sure you are using the correct command options for both the host and the HP 64700. The data communications parameters need to be set correctly for both devices. Also, if you are in a remote location from the host, it is possible that line noise may cause the failure.
  • Page 465 Chapter 12: Error Messages Terminal Interface Messages Action: Run performance verification (Terminal Interface pv command), and check target system. Undefined software breakpoint: %s Cause: The emulator has encountered a software breakpoint in your program that was not inserted with the modify software_breakpoints set command. Action: Remove the breakpoint instructions in your code before assembly and link.
  • Page 466 Chapter 12: Error Messages Terminal Interface Messages READY is false, it indicates that one or more of the instruments participating in the measurement is running in the monitor. Action: None, information only. Write to ROM break Cause: This status message will be printed if you have enabled breaks on writes to ROM and the emulation processor attempted a write to a memory location mapped as ROM.
  • Page 467 Chapter 12: Error Messages Terminal Interface Messages trig1 break Cause: This status message will be displayed if you use the break_on_trigger syntax of the trace command and the analyzer has found the trigger condition while tracing a program run. The emulator is broken to the monitor. trig2 break Cause: This status message will be displayed if you have used the internal trig2 line to connect the analyzer trigger output to the emulator break input and the...
  • Page 468 Chapter 12: Error Messages Terminal Interface Messages Configuration aborted Cause: Occurs when a <CTRL>c is entered while emulator configuration items are being set. Configuration failed; setting unknown: %s=%s Cause: Target condition or system failure. Action: Check target system, and run performance verification (Terminal Interface pv command).
  • Page 469 ROM, possibly because the emulator was left in an unknown state or because of a hardware failure. Action: Initialize the emulator or cycle power. Then reenter the command. If the same failure occurs, call your HP sales and service office.
  • Page 470 Action: Initialize the emulator or cycle power, then re-enter the command. If the same failure occurs, call your HP sales and service office. Break condition configuration aborted Cause: Occurs when <CTRL>c is entered during the configuration of break conditions.
  • Page 471 Chapter 12: Error Messages Terminal Interface Messages Breakpoint code already exists: %s Cause: You attempted to insert a breakpoint; however, there was already a software breakpoint instruction at that location which was not already in the breakpoint table. Action: Your program code is apparently using the same instructions as used by the software breakpoints feature.
  • Page 472 Chapter 12: Error Messages Terminal Interface Messages Stepping aborted; number steps completed: %d Cause: This message is displayed if a break was received during a step command with a step count greater than zero. The break could have been due to any of the break conditions or a <CTRL>c break.
  • Page 473 Chapter 12: Error Messages Terminal Interface Messages Action: In most cases, the problem results from the emulator’s inability to break to the monitor to perform the operation. See message 608. Emulation memory access failed Cause: System failure. Action: Run performance verification (Terminal Interface pv command). Request access to guarded memory: %s Cause: The address or address range specified in the command included addresses within a range mapped as guarded memory.
  • Page 474 Invalid firmware for emulation subsystem Cause: This error occurs when the HP 64700 system controller determines that the emulation firmware (ROM) is invalid. Action: This message is not likely to occur unless you have upgraded the ROMs in your emulator.

  • Page 475: Analyzer Messages

    Chapter 12: Error Messages Terminal Interface Messages Lab firmware auxiliary subsystem; product address: %s Cause: This message should never occur. It shows that you have an unreleased firmware version of the auxiliary subsystem. Analyzer Messages 1105 Unable to delete label; used by emulation analyzer: <label> Cause: This error occurs when you attempt to delete an emulation trace label which is currently being used as a qualifier in the emulation trace specification or is currently specified in the emulation trace format.

  • Page 477: Specifications And Characteristics

    Specifications and Characteristics...

  • Page 478: Emulator Specifications And Characteristics

    • Environmental characteristics. Electrical This section describes the electrical characteristics of the HP 64751 68340 Emulator and the HP 64700 Card Cage. Electrical Characteristics of the HP 64751 Emulator The emulator requires some control signals and power supply in order to run.
  • Page 479 Capacitance, V = 0 V, T = 25°C, f = 1 MHz — Load Capacitance A0-A31, R/W, SIZ0-SIZ1, FC0-FC3 — All Other — AC Characteristics. The AC characteristics of the HP 64751 emulator’s active probe are listed in the following tables.
  • Page 480 Chapter 13: Specifications and Characteristics Emulator Specifications and Characteristics AC Electrical Specifications (64751-66508 and higher active probe board numbers) — Clock Timing MC68340 25.16 MHz HP 64751 Num. Characteristic Symbol Unit System Frequency (See Note) 25.16 25.16 Crystal Frequency XTAL On-Chip VCO System Frequency 0.13...
  • Page 481 Chapter 13: Specifications and Characteristics Emulator Specifications and Characteristics AC Electrical Specifications (64751-66508 and higher active probe board numbers) — Read and Write Cycles (Vcc = 5.0 Vdc +/-5%; GND = 0 Vdc; T to T MC68340 25.16 MHz HP 64751 Num.
  • Page 482 Chapter 13: Specifications and Characteristics Emulator Specifications and Characteristics AC Electrical Specifications (64751-66508 and higher active probe board numbers) — Read and Write Cycles (Vcc = 5.0 Vdc +/-5%; GND = 0 Vdc; T to T MC68340 25.16 MHz HP 64751 Num.
  • Page 483 Chapter 13: Specifications and Characteristics Emulator Specifications and Characteristics AC Electrical Specifications (64751-66508 and higher active probe board numbers) — Read and Write Cycles (Vcc = 5.0 Vdc +/-5%; GND = 0 Vdc; T to T MC68340 25.16 MHz HP 64751 Num.
  • Page 484 Chapter 13: Specifications and Characteristics Emulator Specifications and Characteristics AC Electrical Specifications (64751-66508 and higher active probe board numbers) — Read and Write Cycles (Vcc = 5.0 Vdc +/-5%; GND = 0 Vdc; T to T MC68340 25.16 MHz HP 64751 Num.
  • Page 485 Chapter 13: Specifications and Characteristics Emulator Specifications and Characteristics AC Electrical Specifications (64751-66506 and lower active probe board numbers) — Clock Timing MC68340 16.78 MHz HP 64751 Num. Characteristic Symbol Unit System Frequency (See Note) 16.78 16.78 Crystal Frequency XTAL On-Chip VCO System Frequency 0.13...
  • Page 486 Chapter 13: Specifications and Characteristics Emulator Specifications and Characteristics AC Electrical Specifications (64751-66506 and lower active probe board numbers) — Read and Write Cycles (Vcc = 5.0 Vdc +/-5%; GND = 0 Vdc; T to T MC68340 16.78 MHz HP 64751 Num.
  • Page 487 Chapter 13: Specifications and Characteristics Emulator Specifications and Characteristics AC Electrical Specifications (64751-66506 and lower active probe board numbers) — Read and Write Cycles (Vcc = 5.0 Vdc +/-5%; GND = 0 Vdc; T to T MC68340 16.78 MHz HP 64751 Num.
  • Page 488 Chapter 13: Specifications and Characteristics Emulator Specifications and Characteristics AC Electrical Specifications (64751-66506 and lower active probe board numbers) — Read and Write Cycles (Vcc = 5.0 Vdc +/-5%; GND = 0 Vdc; T to T MC68340 16.78 MHz HP 64751 Num.
  • Page 489 Chapter 13: Specifications and Characteristics Emulator Specifications and Characteristics AC Electrical Specifications (64751-66506 and lower active probe board numbers) — Read and Write Cycles (Vcc = 5.0 Vdc +/-5%; GND = 0 Vdc; T to T MC68340 16.78 MHz HP 64751 Num.

  • Page 490: Physical

    Chapter 13: Specifications and Characteristics Emulator Specifications and Characteristics Electrical Characteristics of the HP 64700 The electrical characteristics of the HP 64700 communication ports are as follows. Communications Serial Port RS-232-C DCE or DTE to 38.4 Kbaud. RS-422 DCE to 460.8 Kbaud.
  • Page 491 Width 325 mm (12.8 in.) Height 173 mm (6.8 in.) Length 389 mm (15.3 in.) Emulator Weight HP 64751 8.2 kg (18 lb) Cable Length Emulator to approximately 914 mm (3 ft). target system Probe Dimensions 92 mm (3.625 in.) width x 16 mm (0.626 in.) height x 159 mm (6.25 in.) length...

  • Page 492: Environmental

    Chapter 13: Specifications and Characteristics Emulator Specifications and Characteristics Environmental Temperature Operating 0°C to +55°C (+32°F to 131°F) Non-operating -40°C to +70°C (-40°F to 158°F) Altitude Operating 4 600m (15 000 ft) Non-operating 15 300m (50 000 ft). Relative Humidity 15% to 95%.
  • Page 493 Part 4 Concept Guide Topics that explain concepts and apply them to advanced tasks.
  • Page 494 Part 4...
  • Page 495 Concepts...
  • Page 496 Concepts This chapter provides conceptual information on the following topics: • X resources and the Graphical User Interface.
  • Page 497 Chapter 14: Concepts X Resources and the Graphical User Interface X Resources and the Graphical User Interface This section contains more detailed information about X resources and scheme files that control the appearance and operation of the Graphical User Interface. This section: •...
  • Page 498 Chapter 14: Concepts X Resources and the Graphical User Interface Class Names or Instance Names Can Be Used When specifying resource names, you can use either instance names or class names. For example, a "Done" pushbutton may have an instance name of "done" and a class name of "XmPushButton".
  • Page 499 Chapter 14: Concepts X Resources and the Graphical User Interface Specific Names Override General Names A more specific resource specification will override a more general one when both apply to a particular widget or application. The names for the application and the main window widget in HP64_Softkey applications have been chosen so that you may specify custom resource values that apply in particular situations: Apply to ALL HP64_Softkey applications:...
  • Page 500 Load Order Resource specifications are loaded from the following places in the following order: The application defaults file. For example, /usr/lib/X11/app-defaults/HP64_Softkey when the operating system is HP-UX or /usr/openwin/lib/X11/app-defaults/HP64_Softkey when the operating system is SunOS. The $XAPPLRESDIR/HP64_Softkey file. (The XAPPLRESDIR environment variable defines a directory containing system-wide custom application defaults.)
  • Page 501 This resource should be set to the platform on which the X server is running (and displaying the Graphical User Interface) if it is different than the platform where the application is running. Values can be: HP-UX, SunOS, pc-xview, or a custom platform scheme directory name.
  • Page 502 Chapter 14: Concepts X Resources and the Graphical User Interface HP64_Softkey.sizeScheme: Names the size scheme file which defines the fonts and the spacing used. Values can be: Large, Small, or a custom scheme file name. HP64_Softkey.inputScheme: Names the input scheme file which specifies mouse and keyboard operation. Values can be: Input, or a custom scheme file name.
  • Page 503 You can modify scheme files by copying them to the directory for user-defined schemes and changing the resource specifications in the file. For example, if you wish to modify the color scheme, and your platform is HP-UX, you can copy the /usr/hp64000/lib/X11/HP64_schemes/HP-UX/Softkey.Color file to $HOME/.HP64_schemes/HP-UX/Softkey.Color and modify its resource...
  • Page 505 Part 5 Installation Guide Instructions for installing and configuring the product.
  • Page 506 Part 5...
  • Page 507 Installation...
  • Page 508 Minimum HP 9000 Hardware and System Requirements The following is a set of minimum hardware and system recommendations for operation of the Graphical User Interface on HP 9000 Series 300/400 and Series 700 workstations. HP-UX For Series 9000/300 and Series 9000/400 workstations, the minimum supported version of the operating system is 7.03 or later.
  • Page 509 Chapter 15: Installation From here, you should proceed to the section titled "Installation for HP 9000 Hosted Systems" for instructions on how to install, verify, and start the Graphical User Interface on HP 9000 systems. Minimum Sun SPARCsystem Hardware and System Requirements The following is a set of minimum hardware and system recommendations for operation of the Graphical User Interface on Sun SPARCsystem workstations.
  • Page 510 Flat-blade screwdriver. Installation overview The steps in the installation process are: Connect the HP 64751 emulator probe to the HP 64748C emulator control card. Install cards into the HP 64700 card cage. Install emulation memory modules on the emulator probe.
  • Page 511 To avoid damage to the emulator cards, follow these guidelines: • If possible, work at a static-free workstation. • Handle the boards only by the edges; do not touch components or traces. • Use a grounding wrist strap that is connected to the HP 64700’s chassis.
  • Page 512 Installing Hardware Step 1. Connect the Emulator Probe Cables Three ribbon cables connect the HP 64748C emulation control card to the HP 64751 68340 emulator probe. The shortest cable connects from J1 of the emulation control card to J3 of the emulator probe. The medium length cable connects from J2 of the emulation control card to J2 of the emulator probe.
  • Page 513 Chapter 15: Installation Installing Hardware 2 When inserting cable connectors into the sockets, press inward on the connector clips so that they hook into the sockets as shown.
  • Page 514 Chapter 15: Installation Installing Hardware 3 Connect the other ends of the cables to the emulator probe.
  • Page 515 1 Use a ground strap when removing or installing boards into the HP 64700 Card Cage to reduce the chances of damage to the circuit cards from static discharge. A jack on the rear panel of the HP 64700 Card Cage is provided for this purpose.
  • Page 516 Chapter 15: Installation Installing Hardware 2 Turn the thumb screw and remove the top cover by sliding the cover toward the rear and up.
  • Page 517 Chapter 15: Installation Installing Hardware 3 Remove the side cover by unsnapping the two latches and lifting off. 4 Remove the card supports.
  • Page 518 Chapter 15: Installation Installing Hardware 5 First, completely loosen the four egress thumb screws. To remove emulator cards, insert a flat blade screwdriver in the access hole and eject the emulator cards by rotating the screwdriver.
  • Page 519 6 Insert a screw driver into the third slot of the right side of the front bezel, push to release catch, and pull the right side of the bezel about one half inch away from the front of the HP 64700. Then, do the same thing on the left side of the bezel.
  • Page 520 Chapter 15: Installation Installing Hardware 7 Lift the bezel panel to remove. Be careful not to put stress on the power switch extender. 8 If you’re removing an existing analyzer card that provides external analysis, remove the right angle adapter board by turning the thumb screws counter-clockwise.
  • Page 521 9 To remove the analyzer card, insert a flat blade screwdriver in the access hole and eject the analyzer card by rotating the screwdriver. Do not remove the system control board. This board is used in all HP 64700 emulation and analysis systems.
  • Page 522 Installing Hardware 10 Install HP 64704A and HP 64748C boards. The HP 64704A is installed in the slot next to the system controller board. The HP 64748C is installed in the second slot from the bottom of the HP 64700. These boards are identified with labels that show the model number and the serial number.
  • Page 523 Chapter 15: Installation Installing Hardware 11 Connect the +5 V power cable to the connector in the HP 64700 front panel.
  • Page 524 Chapter 15: Installation Installing Hardware 12 To reinstall the front bezel, be sure that the bottom rear groove of the front bezel is aligned with the lip as shown below.
  • Page 525 Chapter 15: Installation Installing Hardware 13 Install the card supports. 14 To install the side cover, insert the side cover into the tab slots and fasten the two latches.
  • Page 526 Chapter 15: Installation Installing Hardware 15 Install the top cover in reverse order of its removal, but make sure that the side panels of the top cover are attached to the side clips on the frame.
  • Page 527 Chapter 15: Installation Installing Hardware Step 3. Install emulation memory modules on emulator probe 1 Remove plastic rivets that secure the plastic cover on the top of the emulator probe, and remove the cover.
  • Page 528 2 Determine the placement of the emulation memory modules. Three types of modules may be installed: 256 Kbyte (HP 64171A or HP 64172A), 1 Mbyte (HP 64171B or HP 64172B), and 4 Mbyte (HP 64173A). Any type of module may be installed in either bank.
  • Page 529 Chapter 15: Installation Installing Hardware 3 Install emulation memory modules on emulator probe. There is a cutout on one side of the memory modules so that they can only be installed one way. To install memory modules, place the memory module into the socket groove at an angle. Firmly press the memory module into the socket to make sure that it is completely seated.
  • Page 530 Chapter 15: Installation Installing Hardware 4 Replace the plastic cover, and insert new plastic rivets (supplied with the emulator) to secure the cover.
  • Page 531 Chapter 15: Installation Installing Hardware Step 4. Plug the emulator probe into the demo target system 1 With HP 64700 power OFF, connect the emulator probe cables to the demo target system.
  • Page 532 Chapter 15: Installation Installing Hardware 2 Connect the power supply wires from the emulator to the demo target system. The 3-wire cable has 1 power wire and 2 ground wires. When attaching the 3-wire cable to the demo target system, make sure the connector is aligned properly so that all three pins are connected.
  • Page 533 The HP 64700B automatically selects the 115 Vac or 220 Vac range. In the 115 Vac range, the HP 64700B will draw a maximum of 345 W and 520 VA. In the 220 Vac range, the HP 64700B will draw a maximum of 335 W and 600 VA.
  • Page 534 Coco Brown * Part number shown for plug is industry identifier for plug only. Number shown for cable is HP part number for complete cable including plug. ** These cords are included in the CSA certification approval for the equipment.
  • Page 535 8120-4754 90/230 * Part number shown for plug is industry identifier for plug only. Number shown for cable is HP part number for complete cable including plug. ** These cords are included in the CSA certification approval for the equipment.
  • Page 536 The line switch is a push button located at the lower left hand corner of the front panel. To turn ON power to the HP 64700, push the line switch button in to the ON (1) position. The power light at the...
  • Page 537 Connecting the HP 64700 to a Computer or LAN Refer to the HP 64700 Series Installation/Service Guide for instructions on connecting the HP 64700 to a host computer (via RS-422 or RS-232) or LAN and setting the HP 64700’s configuration switches. (RS-422 and RS-232 are only...
  • Page 538 Installing HP 9000 Software Installing HP 9000 Software This section shows you how to install the Graphical User Interface on HP 9000 workstations. These instruction also tell you how not to install the Graphical User Interface if you want to use just the conventional Softkey Interface.
  • Page 539 /etc/update at the HP-UX prompt. 6 When the HP-UX update utility main screen appears, confirm that the source and destination devices are correct for your system. Refer to the information on updating HP-UX in your HP-UX documentation if you need to modify these values.
  • Page 540 X window manager (if you are not currently running an X server). If you plan to run the Motif Window Manager (mwm), or similar window manager, continue with Step 3a of these instructions. If you plan to run HP VUE, skip to Step 3b of these instructions.
  • Page 541 Step 3b. Start HP VUE If you are running the X server under HP VUE and have not started HP VUE, do so now. HP VUE is a window manager for the X Window system. The X server is executing underneath HP VUE.
  • Page 542 -s /users/team/usr/hp64000 /usr/hp64000 If you do not wish to establish a symbolic link, you can set the HP64000 variable to the full path that contains the HP 64000 software. Again, if you installed relative to /users/team, you would enter...
  • Page 543 3 Set the PATH environment variable to include the usr/hp64000/bin directory by entering PATH=$PATH:$HP64000/bin; export PATH Including usr/hp64000/bin in your PATH relieves you from prefixing HP 64700 executables with the directory path. 4 Set the MANPATH environment variable to include the usr/hp64000/man and...
  • Page 544 Chapter 15: Installation Installing Sun SPARCsystem Software Installing Sun SPARCsystem Software This section shows you how to install the Graphical User Interface on Sun SPARCsystem workstations. These instructions also tell you how not to install the Graphical User Interface if you want to use just the conventional Softkey Interface. This section shows you how to: Install the software from the media.
  • Page 545 Chapter 15: Installation Installing Sun SPARCsystem Software Step 2. Start the X server and OpenWindows If you are not already running the X server, do so now. The X server is required to run the Graphical User Interface because it is an X application. •...
  • Page 546 Consult the OpenWindows documentation for an explanation of the DISPLAY environment variable. 2 Set the HP64000 environment variable. For example, if you installed the HP 64000 software relative to the root directory, "/", you would enter setenv HP64000 /usr/hp64000 If you installed the software relative to a directory other than the root directory, it is strongly recommended that you use a symbolic link to make the software appear to be under /usr/hp64000.
  • Page 547 Chapter 15: Installation Installing Sun SPARCsystem Software 4 Set the MANPATH environment variable to include the usr/hp64000/man and usr/hp64000/contrib/man directories by entering setenv MANPATH ${MANPATH}:${HP64000}/man setenv MANPATH ${MANPATH}:${HP64000}/contrib/man Including these directories in your MANPATH variable lets you access the on-line "man"...
  • Page 548 Chapter 15: Installation Installing Sun SPARCsystem Software Step 5. Map your function keys If you are using the conventional Softkey Interface, map your function keys by following the steps below. 1 Copy the function key definitions by typing: cp $HP64000/etc/ttyswrc ~/.ttyswrc This creates key mappings in the .ttyswrc file in your $HOME directory.
  • Page 549 1 Display the 64700tab.net file by entering more /usr/hp64700/etc/64700tab.net at the HP-UX prompt. 2 Page through the file until you find the emulator you are going to use. This step will require some matching of information to an emulator, but it should not be difficult to determine which emulator you want to address.
  • Page 550 1 Apply power to the emulator you wish to access after making sure the emulator is connected to the LAN or to your host system. On the HP 64700 Series Emulator, the power switch is located on the front panel near the bottom edge. Push the switch in to turn power on to the emulator.
  • Page 551 Chapter 15: Installation Verifying the Installation Graphical User Interface. Otherwise, emul700 starts the conventional Softkey Interface. You should include an ampersand ("&") with the command to start the Graphical User Interface as a background process. Doing so frees the terminal window where you started the interface so that the window may still be used.
  • Page 552 Chapter 15: Installation Verifying the Installation...
  • Page 553 Chapter 15: Installation Verifying the Installation Step 3. Exit the Graphical User Interface 1 Position the mouse pointer over the pulldown menu named "File" on the menu bar at the top of the interface screen. 2 Press and hold the command select mouse button until the File menu appears. 3 While continuing to hold the mouse button down, move the mouse pointer down the menu to the "Exit"...
  • Page 555 Installing/Updating Emulator Firmware...
  • Page 556 HP 64751A. However, if you ordered the HP 64751A and the HP 64748C separately, or if you are using a HP 64748C that has been used previously with a different emulator probe, you must download the correct firmware into the emulation control card.
  • Page 557 • Enter the progflash -v <emul_name> <products ...> command. The progflash command downloads code from files on the host computer into Flash EPROM memory in the HP 64700. The -v option means "verbose". It causes progress status messages to be displayed during operation.
  • Page 558 2 em80960 i80960 3 em68340 m68340 Number of Emulator to Update? (intr (usually cntl C or DEL) to abort) To update firmware in the HP 64700 that contains the 68340 emulator, enter "3". Product 1 64700 2 64703/64704/64706/64740 3 64744...
  • Page 559 Code start 280000H (should equal control ROM start) Code size 2348CH (must be less than control ROM size) Finishing up... Rebooting HP64700... Flash programming SUCCEEDED You could perform the same update as in the previous example with the following command: $ progflash -v em68340 64751 <RETURN>...
  • Page 560 To display current firmware version information • Use the Terminal Interface ver command to view the version information for firmware currently in the HP 64700. When using the Graphical User Interface or Softkey Interface, you can enter Terminal Interface commands with the pod_command command. For example: display pod_command <RETURN>...
  • Page 561 HP 64700 that will not boot up. Repeat the firmware update process. If the HP 64700 is connected to the LAN in this situation and you are unable to connect to the HP 64700 after the power glitch, try repeating the firmware update...
  • Page 563 Glossary access mode Specifies the types of cycles used to access target system memory locations. For example a "byte" access mode tells the monitor program to use load/store byte instructions to access target memory. analyzer An instrument that captures data on signals of interest at discreet periods.
  • Page 564 Glossary modify the contents of processor registers, target system memory, and I/O resources. foreground The mode in which the emulator is executing the user program. In other words, the mode in which the emulator operates as the target microprocessor would. global restart When the same secondary branch condition is used for all terms in the analyzer’s sequencer, and secondary branches are always back to the first term.
  • Page 565 Glossary trace A collection of states captured on the emulation bus (in terms of the emulation bus analyzer) or on the analyzer trace signals (in terms of the external analyzer) and stored in trace memory. trigger The captured analyzer state about which other captured states are stored. The trigger state specifies when the trace measurement is taken.
  • Page 567 237 altitude, operating and non-operating environments, 492 ambiguous address error message, 141 analyzer, 563 arming other HP 64700 Series analyzers, 5 breaking emulator execution into the monitor, 4, 244 breaking execution of other HP 64700 Series emulators, 5...
  • Page 568 237 using the, 222 analyzer status occurrence left information, 226 sequence term information, 226 app-defaults directory HP 9000 computers, 500 Sun SPARCsystem computers, 500 application resource See X resource arm information, 225 arm_trig2, in trace command, 421 background, 123, 563...
  • Page 569 29.5 kg, 491 powering OFF the HP 64700, 53 protect emulator against static discharge, 52 rear panel, do not stand HP 64700 on, 515 characteristics, emulator, 478-492 characterization of memory, 135 chip selects, access emulation memory with, 134...
  • Page 570 Index executing commands, 91 help, 94 keyboard use of, 95-97 on-line help, 97 recalling commands with dialog box, 94 turning on or off, 90, 317 command paste mouse button, 29 Command Recall dialog box operation, 86 command select mouse button, 29 commands, 95 combining on a single command line, 95 completion, 95...
  • Page 571 Index context changing directory in configuration window, 116 changing directory in emulator/analyzer window, 172 changing symbol, 173 displaying directory from configuration window, 117 displaying directory from emulator/analyzer window, 172 displaying symbol, 172 coordinated measurements, 307 break_on_trigger syntax of the trace command, 307 definition, 298 copy command, 343-347 breakpoints, 215...
  • Page 572 Index data values, 204-205 adding items to the existing display, 205 clearing the display and adding a new item, 205 copying to a file, 215 displaying, 204 data values, displaying, 38 decimal numbers, 231 default trace command, 224 default trace display, returning to, 263 demo target system, 478 demos, setting up, 325-327 depth of the trace, 230...
  • Page 573 Index memory, 356-359 memory mnemonic, 33, 199 pod_command, 352 registers, 192-197, 352 simulated_io, 217, 352 software_breakpoints, 352 status, 224, 353 symbols, 163 trace, 228, 360-363 display mode, 563 display trace, 250-263 about line number, 252 absolute format, 255 count absolute/relative, 261 default, 263 dequeued, 251 disassemble from line number, 253...
  • Page 574 Index selecting, 287 standard deviation, 290 trace command setup, 285 edit command line entry area with popup menu, 93 command line entry area with pushbuttons, 92 file, 212, 317 file at address, 212, 317 file at program counter, 212 file at symbol from symbols screen, 212 file from memory display screen, 212 8-bit memory, substituting emulation memory for, 134 electrical characteristics of the emulator, 478...
  • Page 575 Index status lines, predefined values for, 235 using the, 154 weight, 491 emulator configuration break processor on write to ROM, 150 clock selection, 119 exiting the configuration interface, 118 load command, 374 loading from file, 118 modify command, 379 modifying a configuration section, 113 monitor entry after, 120 starting the configuration interface, 111 storing, 115...
  • Page 576 Index Entry Buffer Recall dialog box, 27, 83 multi-window copy-and-paste from, 84 multi-window copy-and-paste to, 81 operation, 83 recall button, 27 recalling entries, 83 symbol width and copy-and-paste to, 81 text entry, 80 with action keys, 83, 85 with pulldown menus, 83 Entry Buffer Recall dialog box operation, 86 environment variables (UNIX) HP64KPATH, 102...
  • Page 577 Index fast termination mode, 134 file breakpoints screen to, 215 data values screen to, 215 display area to, 215 editing, 212 editing at address, 212 editing at program counter, 212 editing at symbol from symbols screen, 212 editing from memory display screen, 212 emulator configuration, 115 emulator configuration load, 118 emulator status screen to, 216...
  • Page 578 89 on-line, 97 softkey driven information, 97 help index, displaying, 89 hexadecimal numbers, 232 HP 64700 Operating Environment, minimum version, 509 HP 9000 700 series Motif libraries, 508 HP-UX minimum version, 508 installing software, 538-543 minimum system requirements overview, 508...
  • Page 579 218 keyboard_to_simio, modify command, 380 label scheme, 316, 320, 502 LANG environment variable, 502 LD_LIBRARY_PATH environment variable, 547 libraries, Motif for HP 9000/700, 508 line numbers (source file), symbol display, 165 line numbers (trace) disassembling from, 253 displaying about, 252...
  • Page 580 Index lines in main display area, 317-318 list, trace, 228 load command, 374-375 absolute files, 160 configuration, 374 trace, 265-266, 375 trace_spec, 265, 375 local symbols, 232 copy command, 345 display command, 165, 352 initializing the performance measurement with, 273 to file, 216 locked, end command option, 72 log_commands command, 376-377...
  • Page 581 124 foreground monitor filename, 129 foreground or background, 123-132 function of, 123 selecting, 123-132 selecting entry after configuration, 120 Motif, HP 9000/700 requirements, 508 mouse buttons, 29 choosing menu items, 76-77 multi-window copy-and-paste from entry buffer, 84...
  • Page 582 262 on-line help, 97 on_halt, trace command option, 243 only, trace command storage qualifier, 240 operating system HP 64700 Series minimum version, 509 HP-UX minimum version, 508 SunOS minimum version, 509 operators, 232 overlapping addresses, memory mapping, 141...
  • Page 583 385-386 performance_measurement_run command, 387-388 physical characteristics of the emulator, 490 pin extender, 60 platform HP 9000 memory needs, 508 HP 9000 minimum performance, 508 SPARCsystem memory needs, 509 SPARCsystem minimum performance, 509 platform scheme, 316, 501 plug-in, 52...
  • Page 584 Index choosing with mouse, 76-77 pushbutton select mouse button, 29 QUALIFIER, in trace command, 391-393 qualifiers, 235 count, 242 prestore, 241 simple trigger, 237 storage, 240 RAM, mapping emulation or target, 135 READY, CMB signal, 299 real-time execution, 564 real-time runs commands not allowed during, 120 commands which will cause break, 121 restricting emulator to, 120...
  • Page 585 Index resource See X resource RESOURCE_MANAGER property, 500 restart term, 245, 247 restrict to real time runs, 120 target system dependency, 121 mapping emulation or target, 135 writes to, 135 RS-422, host computer interface card, 5 run command, 174, 395-396 from reset, 175 scheme files (for X resources), 315, 501 color scheme, 316, 320, 502...
  • Page 586 Index softkeys, 95 software installation for HP 9000, 538-543 installation for SPARCsystems, 544-548 software breakpoints, 179-191 clearing, 189 clearing all, 191 copy command, 346 deactivating, 186 display command, 352 enable/disable, 181 modify command, 381 opcode locations, 184, 186 permanent, setting, 184...
  • Page 587 Index restoring the current measurement, 274, 288 run, 387-388 running, 293 trace command setup, 271 trace display depth, 271 source lines set command, 401 symbol display, 165 trace display, 257 trace display, number of, 257 source/symbol modes, setting, 206 SPARCsystems installing software, 544-548 minimum system requirements overview, 509 SunOS minimum version, 509...
  • Page 588 --SYMB-- syntax, 411-418 trace display, 259 sync_sim_registers command, 419 synchronous measurements, 305 syntax conventions, 338 system requirements HP 64700 minimum version, 509 HP 9000 overview, 508 HP-UX minimum version, 508 OSF/Motif HP 9000/700 requirements, 508 SPARCsystem overview, 509 SunOS minimum version, 509...
  • Page 589 Index terminal emulation window, opening, 216 time range file format (SPMT measurements), 287 trace, 565 at EXECUTE, 305 copy command, 346 depth of, 230 display command, 360-363 displaying the, 228 halting the, 227 listing the, 228 listing to file, 215 load command, 375 loading, 265-266 on_halt, 243...
  • Page 590 Index source line inclusion, 257 symbol information inclusion, 259 width of columns, 260 trace display, setting the source/symbol modes, 206 trace signals (emulation analyzer), 233 trace status display, 224 trace_spec load command, 375 store command, 410 tracing background operation, 151 tram, memory characterization, 135 transfer address, 175 trigger, 565...
  • Page 591 Index opening additional emulator/analyzer, 69 running the emulator/analyzer interface in multiple, 65 terminal emulation, opening, 216 workstation HP 9000 memory needs, 508 HP 9000 minimum performance, 508 SPARCsystem memory needs, 509 SPARCsystem minimum performance, 509 write to ROM break, 150...
  • Page 592 Index X Window System, 65 XEnv_68k_except symbol and effect on breakpoints, 181...
  • Page 593 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 594 No other warranty is expressed or implied. HP specifically disclaims the implied warranties of merchantability and fitness for a particular purpose.
  • Page 595 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.
  • Page 596 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 597 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 598 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.

This manual is also suitable for:

6834064704

Table of Contents