Page 1 Agilent Test & Measurement website, www.tm.agilent.com. HP References in this Manual This manual may contain references to HP or Hewlett-Packard. Please note that Hewlett-Packard's former test and measurement, semiconductor products and chemical analysis businesses are now part of Agilent Technologies. We have made no changes to this manual copy.
Page 2 User’s Guide for the Graphical User Interface HP 64782 MC6833x Emulation/Analysis...
Page 3 Hewlett-Packard Company. The information contained in this document is subject to change without notice. HP is a trademark of Hewlett-Packard Company. OSF/Motif and Motif are trademarks of the Open Software Foundation in the U.S. and other countries.
Page 4 Printing History New editions are complete revisions of the manual. The date on the title page changes only when a new edition is published. A software code may be printed before the date; this indicates the version level of the software product at the time the manual was issued. Many product updates and fixes do not require manual changes, and manual corrections may be done without accompanying product changes.
Page 5 The HP 64703 Emulation Bus Analyzer meets this requirement. The HP 64703 Emulation Bus Analyzer also has an an external analyzer that captures up to 16 channels of data external to the emulator. You can also use the HP 64704 or HP 64794 Emulation Bus Analyzer which has 80 channels;...
Page 6 With the HP 64700 Card Cage, You Can ... • Use the RS-422 capability of the serial port and an RS-422 interface card on the host computer (HP 98659 for the HP 9000 Series 300) to provide upload/download rates of up to 230.4K baud. •...
Page 7 In This Book This book documents the Graphical User Interface and the Softkey Interface when used with the HP 64782 6833x emulators and the HP 64703/4 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 8: Table Of Contents
Part 2 User’s Guide 2 Plugging into a Target System Plugging the Emulator into a Target System 52 3 Starting and Exiting HP 64700 Interfaces Starting and Exiting HP 64700 Interfaces 54 Starting the Emulator/Analyzer Interface 55 To start the emulator/analyzer interface 55...
Page 9 To display the status of emulators 57 To unlock an interface that was left locked by another user 58 Opening Other HP 64700 Interface Windows 59 To open additional emulator/analyzer windows 59 To open the high-level debugger interface window 60...
Page 10 Using Pod Commands 89 To display the pod commands screen 90 To use pod commands 90 Forwarding Commands to Other HP 64700 Interfaces 91 To forward commands to the high-level debugger 92 To forward commands to the software performance analyzer 92...
Page 11 Contents To access context sensitive (f1) help 103 To exit the configuration interface 103 To load an existing configuration file 103 Modifying the General Items and Monitor Setup 104 When Modifying the Microprocessor Clock Source 105 When Restricting the Emulator to Real-time Runs 105 Reconfiguring the Emulator Copy of the SIM Registers 107 To define values for the emulator copy of the SIM registers 108 Mapping Memory 109...
Page 12 Contents 6 Using the Emulator Using the Emulator 134 Using the EMSIM Registers 135 To view the SIM register differences 138 To synchronize to the 6833x SIM registers 139 To synchronize to the EMSIM registers 139 To restore default values in the EMSIM registers 139 Loading and Storing Absolute Files 140 To load absolute files 140 To load absolute files without symbols 141...
Page 13 Contents To step assembly-level instructions 158 To reset the emulation processor 159 Using Execution Breakpoints 160 Setting execution breakpoints in RAM 161 Using temporary and permanent breakpoints 161 To enable execution breakpoints To disable an execution breakpoint To set a permanent breakpoint 164 To set a temporary breakpoint To clear an execution breakpoint To clear all execution breakpoints 168...
Page 14 Contents To set the display modes 181 Using System Commands 183 To set UNIX environment variables 183 To display the name of the emulation module 183 To display the event log 184 To display the error log 184 To edit files 185 To copy information to a file or printer 188 To open a terminal emulation window 189 Using Simulated I/O 190...
Page 15 Contents To enter a range in a trace expression To trigger on a number of occurrences of some state 213 To break emulator execution on the analyzer trigger 214 To count states or time To define a storage qualifier To define a prestore qualifier To trace activity leading up to a program halt 219 To capture a continuous stream of program execution no matter how large your program 219...
Page 16 Contents Saving and Restoring Trace Data and Specifications To store a trace specification To store trace data 251 To load a trace specification To load trace data 253 8 Making Software Performance Measurements Making Software Performance Measurements 256 Activity Performance Measurements 257 To set up the trace command for activity measurements 260 To initialize activity performance measurements 261 To interpret activity measurement reports 265...
Page 17 Contents Configuring the External Analyzer 294 To control the external analyzer with the emulator/analyzer interface 296 To specify the threshold voltage 296 To specify the external analyzer mode 297 To specify the slave clock mode 298 To define labels for the external analyzer signals 301 10 Making Coordinated Measurements Making Coordinated Measurements 304 Setting Up for Coordinated Measurements 307...
Page 18 Contents 11 Setting X Resources Setting X Resources 322 To modify the Graphical User Interface resources 324 To use customized scheme files 328 To set up custom action keys 330 To set initial recall buffer values 331 To set up demos or tutorials 332 Part 3 Reference 12 Emulator/Analyzer Interface Commands Emulator/Analyzer Interface Commands 338...
Page 19 Contents FCODE 383 forward 384 help 385 load 387 log_commands 389 modify 390 modify configuration 391 modify keyboard_to_simio 392 modify memory 393 modify register 396 modify SIM registers 397 performance_measurement_end 399 performance_measurement_initialize 400 performance_measurement_run 402 pod_command 403 QUALIFIER 405 RANGE 407 reset 409 run 410 SEQUENCING 412...
Page 20 Part 5 Installation Guide 15 Installation Installation 510 Connecting the HP 64700 to a Computer or LAN 512 Installing HP 9000 Software 513 Step 1. Install the software from the media 513 Step 2. Set the necessary environment variables 514 Step 3.
Page 21 Contents Verifying the Installation 523 Step 1. Determine the logical name of your emulator 523 Step 2. Start the interface with the emul700 command 524 Step 3. Exit the Graphical User Interface 525 16 Installing/Updating Emulator Firmware Installing/Updating Emulator Firmware 528 To update emulator firmware with "progflash"...
Page 22: Part 1 Quick Start Guide
Part 1 Quick Start Guide...
Page 23 Part 1 A one-glance overview of the product and a few task instructions to help you get comfortable.
Page 24: Getting Started
Getting Started...
Page 25: The Emulator/Analyzer Interface - At A Glance
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 26 Getting Started Menu Bar. Provides pulldown menus from which you select commands. When menu items are not applicable, they appear half-bright and do not respond to mouse clicks. Action Keys. User-defined pushbuttons. You can label these pushbuttons and define the action to be performed. Entry Buffer.
Page 27 Getting Started • Softkey pushbuttons. Clicking on these pushbuttons, or pressing softkeys, places the command in the command line entry area. You can press and hold the select mouse button to access the Command Line popup menu. • Command buttons (includes command recall button). The command Return button is the same as pressing the carriage return key —...
Page 28 The following table describes the generic mouse button names and shows the default mouse button bindings. Mouse Button Bindings and Description Generic Bindings for Bindings for Description Button HP 9000 Sun SPARCsystem Name (SunOS or Solaris) paste left left Paste from the display area to the entry buffer.
Page 29 Getting Started The following tables show the default keyboard bindings. Keyboard Key Bindings Sun SPARCsystem Generic Key Name HP 9000 (SunOS or Solaris) menu select extend char extend char insert insert char insert char delete delete char delete char left-arrow...
Page 30 Getting Started The Softkey Interface The emulator/analyzer interface can also be the Softkey Interface which is provided for several types of terminals, terminal emulators, and bitmapped displays. When using the Softkey Interface, commands are entered from the keyboard. Figure 2 Display area.
Page 31 Getting Started Display area. Can show memory, data values, analyzer traces, registers, breakpoints, status, simulated I/O, global symbols, local symbols, pod commands (the emulator’s underlying Terminal Interface), error log, or display log. You can use the UP ARROW, DOWN ARROW, PAGE UP, and PAGE DOWN cursor keys to scroll or page up or down the information in the active window.
Page 32: The Getting Started Tutorial
• The HP 64782B-H emulator and HP 64703/4 analyzer are installed into the HP 64700 Card Cage, the HP 64700 is connected to the host computer, and the Graphical User Interface software has been installed as outlined in the "Installation" chapter.
Page 33: 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 34: Step 2: Display The Program In Memory
Getting Started Step 2: Display the program in memory Step 2: Display the program in memory 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".
Page 35: Step 3: Run From The Transfer Address
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 Figure 4...
Page 36: Step 4: Step High-Level Source Lines
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. To step a source line from the current program counter, click on the Step Source action key.
Page 37: Step 5: Display The Previous Mnemonic Display
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 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 38: Step 6: Run Until An Address
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 39: Step 7: Display Data Values
Getting Started Step 7: Display data values Step 7: Display data values 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). Click on the Disp Var () action key.
Page 40: Step 8: Display Registers
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 Figure 8...
Page 41: Step 9: Step Assembly-Level Instructions
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. Or, using the command line, enter: step Figure 9...
Page 42: Step 10: Trace The Program
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. When one of these states matches the "trigger state"...
Page 43 Getting Started Step 10: Trace the program To view the captured states, choose Display→Trace. Or, using the command line, enter: display trace Figure 10 The default display mode settings cause source lines and symbols to appear in the trace list. Captured states are numbered in the left-hand column of the trace list.
Page 44: Step 11: Display Memory At An Address In A Register
Getting Started Step 11: Display memory at an address in a register Step 11: Display memory at an address in a register Click on the Disp @REG action key. Or, using the command line, enter the name of the command file: mematreg A command file dialog box appears (or a prompt appears in the command line).
Page 45: Step 12: Patch Assembly Language Code
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. With "main" still in the entry buffer, click on the Run Xfer til () action key.
Page 46 Getting Started Step 12: Patch assembly language code Figure 13 Exit out of the editor, saving your changes. The file you just edited is assembled, and the patch main menu appears. Type "a" and press <RETURN> to apply the patch. Figure 14...
Page 47 Getting Started Step 12: Patch assembly language code Notice in the emulator/analyzer interface that the instruction at address "main" has changed. 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 48 Getting Started Step 12: Patch assembly language code Click on the Patch () action key again. A window running the vi editor again appears. Suppose you want to patch the demo program so that the proc_spec_init() function is called before the init_system() function.
Page 49: Step 13: Exit The Emulator/Analyzer Interface
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...
Page 50: Part 2 User's Guide
Part 2 User’s Guide...
Page 51 Part 2 A complete set of task instructions and problem-solving guidelines, with a few basic concepts.
Page 52: Plugging Into A Target System
Plugging into a Target System...
Page 53: Plugging The Emulator Into A Target System
That manual describes connecting these emulators to a target system using an AMP 132-pin connector, a PQFP (plastic quad flat pack) cable, or a 132-pin to PQFP adapter. • M68331—Model HP 64782B • M68332—Model HP 64782C • M68334—Model HP 64782E •...
Page 54: Starting And Exiting Hp 64700 Interfaces
Starting and Exiting HP 64700 Interfaces...
Page 55: Starting And Exiting Hp 64700 Interfaces
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 56: Starting The Emulator/Analyzer Interface
"Installation" chapter), you can start the interface with the emul700 <emul_name> command. The "emul_name" is the logical emulator name given in the HP 64700 emulator device table (/usr/hp64000/etc/64700tab.net). It may also be the LAN address. If you are running a window system on your host computer (for example, the X Window System), you can run the interface in up to 10 windows.
Page 57 To start the emulator/analyzer interface for the 6833x emulator: $ emul700 em6833x The "em6833x" in the command above is the logical emulator name given in the HP 64700 emulator device table file (/usr/hp64000/etc/64700tab.net). # Blank lines rest of each line after a ’#’ character are ignored.
Page 58: To Start The Interface Using The Default Configuration
Starting and Exiting HP 64700 Interfaces To start the interface using the default configuration To start the interface using the default configuration • Use the emul700 -d <emul_name> command. In the emul700 -d <emul_name> command, the -d option says to use the default configuration.
Page 59: To Unlock An Interface That Was Left Locked By Another User
Starting and Exiting HP 64700 Interfaces To unlock an interface that was left locked by another user Examples To list, verbosely, the status of the emulator whose logical name is "em6833x": $ emul700 -lv em6833x The information may be similar to: em6833x - m6833x running;...
Page 60: 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 61: To Open The High-Level Debugger Interface Window
Starting and Exiting HP 64700 Interfaces To open the high-level debugger interface window 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 62: Exiting Hp 64700 Interfaces
Exiting HP 64700 Interfaces There are several options available when exiting the HP 64700 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 63: To Exit A Debug/Emulation Session
Starting and Exiting HP 64700 Interfaces To exit a debug/emulation session 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 64 Entering Commands...
Page 65: Entering Commands
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 66: 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: • Choose a pulldown menu item using the mouse. • Choose a pulldown menu item using the keyboard. •...
Page 67: 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". Type the character in lower case only.)
Page 68 Entering Commands To choose a pulldown menu item using the keyboard • To move down one menu item within a menu, press the down-arrow key. • To move up one menu item within a menu, press the up-arrow key. • To choose a menu item, type the character in the menu item label that is underlined.
Page 69: To Choose Popup Menu Items
Entering Commands To choose popup menu items To choose popup menu items 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.) Press and hold the select mouse button.
Page 70 Entering Commands To copy-and-paste to the entry buffer highlight in a given direction when it discovers a delimiting character not determined to be part of the string. A common delimiter would, of course, be a space. When you press and hold the mouse button and drag the pointer to highlight text, the interface copies all highlighted text to the entry buffer when you release the mouse button.
Page 71 Entering Commands To copy-and-paste to the entry buffer 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. A mouse click causes the interface to expand the highlight to include...
Page 72: To Recall Entry Buffer Values
Entering Commands To recall entry buffer values 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 73: To Copy-And-Paste From The Entry Buffer To The Command Line Entry Area
Entering Commands To copy-and-paste from the entry buffer to the command line entry area To copy-and-paste from the entry buffer to the command line entry area Place text to be pasted into the command line in the entry buffer text area.
Page 74: To Use Dialog Boxes
Entering Commands To use dialog boxes Several action keys are predefined when you first start the Graphical User Interface. You can use the predefined action keys, but you’ll really appreciate action keys when you define and use your own. Action keys are defined by setting an X resource. Refer to the chapter "Setting X Resources"...
Page 75 Entering Commands To use dialog boxes 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. A single click on a file name from either list highlights the file name and...
Page 76 Entering Commands To use dialog boxes To use the Directory Selection dialog box: Label informs you of the type of list displayed. A list of predefined or previously accessed directories. A single click on a directory name from the list highlights the name and copies it to the text area.
Page 77: To Access Help Information
Entering Commands To access help information To access help information Display the Help Index by choosing Help→General Topic... or Help→Command Line..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 78: 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. Additionally, the graphical interface makes the softkey labels pushbuttons so commands may be entered using the mouse.
Page 79: To Enter A Command
Entering Commands To enter a command Turns display of the command line area "on" or "off." On means that the command line is displayed and you can use the softkey label pushbuttons, the command return and recall pushbuttons, and the cursor pushbuttons for command line editing.
Page 80: To Edit The Command Line Using The Command Line Pushbuttons
Entering Commands To edit the command line using the command line pushbuttons 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 81: To Recall Commands
Entering Commands To recall commands Command Line popup menu appears; choose Clear to End of Line from the menu. • To position the cursor and insert characters at the cursor location: position the mouse pointer in a non-text area of the command line entry area;...
Page 82: To Get Help About The Command Line
Entering Commands To get help about the command line If you exit the emulation/analysis session with the interface "locked", commands in the recall buffer are saved and will be present when you restart the interface. You can predefine entries for the Command Recall dialog box and define the maximum number of entries by setting X resources (refer to the "Setting X Resources"...
Page 83: 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. The command line also provides command completion.
Page 84: To Recall Commands
Entering Commands To recall commands 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...
Page 85: To Access On-Line Help Information
Entering Commands To access on-line help information 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 86: 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 87 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 88 Entering Commands To access on-line help information 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," is passed to &VALUE1 and the remaining parameters "0ffffh,"...
Page 89: To Start Logging Commands To A Command File
Entering Commands To start logging commands to a command file 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 90: 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. Because some pod commands can cause the interface to become out-of-sync with the emulator, or even cause the interface to terminate abnormally, they must be used with care.
Page 91: To Display The Pod Commands Screen
Entering Commands To display the pod commands screen 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 92: 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 93: To Forward Commands To The High-Level Debugger
Entering Commands To forward commands to the high-level debugger To forward commands to the high-level debugger • Enter the forward debug "<command string>" command using the command line. Examples To send the "Program Run" command to the debugger: forward debug "Program Run" Or, since only the capitalized key is required: forward debug "P R"...
Page 94 Configuring the Emulator...
Page 95: Configuring The Emulator
Configuring the Emulator This chapter describes how to configure the emulator. You must map memory whenever you use the emulator. When you plug the emulator into a target system, you must configure the emulator so that it operates correctly in the target system. The configuration tasks are grouped into the following sections: •...
Page 96: 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. • Modify a configuration section. • Apply configuration changes to the emulator. •...
Page 97: To Start The Configuration Interface
Configuring the Emulator To start 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 top-level dialog box (see the following example) is displayed.
Page 98 Configuring the Emulator To start the configuration interface Examples The 6833x emulator configuration interface top-level dialog box is shown below. The menu bar. Clicking on one of these lines selects a particular configuration section. Clicking this button loads configuration changes into the emulator.
Page 99: To Modify A Configuration Section
Configuring the Emulator To modify a configuration section To modify a configuration section Start the emulator configuration interface. Click on a section name in the configuration interface top-level dialog box. Use the section dialog box to make changes to the configuration. As soon as you change a configuration option, the change is recorded (as seen by the "Changes Not Loaded"...
Page 100: If Apply To Emulator Fails
Configuring the Emulator If apply to emulator fails If apply to emulator fails Choose Display→Failed Apply Info from the pulldown menu in the top-level configuration interface window. A window containing the following information about the failed configuration is opened: • Chip select information from the emsim (emulator) resister set.
Page 101: To Store Configuration Changes To A File
Configuring the Emulator To store configuration changes to a file To store configuration changes to a file • Choose File→Store... from the pulldown menu in the top-level configuration interface window, and use the file selection dialog box to name the configuration file. •...
Page 102: To Change The Configuration Directory Context
Configuring the Emulator To change the configuration directory context To change the configuration directory context • Choose File→Directory... from the pulldown menu in the top-level configuration interface window, and use the directory selection dialog box to specify the new directory. The directory context specifies the directory to which configuration files are stored and from which they are loaded.
Page 103: To Access Help Topics
Configuring the Emulator To access help topics To access help topics • Choose Help→General Topic... from the pulldown menu in the top-level configuration interface window, click on a topic in the selection dialog box, and click the "OK" button. Figure 17 Displays help on main items.
Page 104: To Access Context Sensitive (F1) Help
Configuring the Emulator To access context sensitive (f1) help To access context sensitive (f1) help • Place the mouse pointer over the item you’re interested in, and press the f1 key. • Choose Help→On Item... from the pulldown menu in the top-level configuration interface window.
Page 105: Modifying The General Items And Monitor Setup
Modifying the General Items and Monitor Setup To modify the general configuration items, first start the configuration interface and access the "General Items/Monitor Setup" configuration section (refer to the previous "Using the Configuration Interface" section). Figure 18 To access information about the configuration items, use the online help button or press f1 to show context-sensitive help on an individual item.
Page 106: When Modifying The Microprocessor Clock Source
Configuring the Emulator When Modifying the Microprocessor Clock Source When Modifying the Microprocessor Clock Source In normal mode, if you are using the emulator in ACT mode, you must use an external target system clock. The external target system clock must be an oscillator unless you are using the emulator in ACT mode, in which case the external target system clock may be a crystal.
Page 107 Configuring the Emulator When Restricting the Emulator to Real-time Runs The following commands are not allowed when runs are restricted to real-time and the emulator is running the user program: • Display/modify registers. • Display/modify target system memory. • Load/store target system memory. •...
Page 108: Reconfiguring The Emulator Copy Of The Sim Registers
Reconfiguring the Emulator Copy of the SIM Registers To modify the general configuration items, first start the configuration interface and access the "Reconfigure Internal Registers" configuration section (refer to the previous "Using the Configuration Interface" section). Figure 19 To access information about the configuration items, use the online help button or press f1 to show context-sensitive help on an individual item.
Page 109: To Define Values For The Emulator Copy Of The Sim Registers
Configuring the Emulator To define values for the emulator copy of the SIM registers To define values for the emulator copy of the SIM registers • Click on the register field and enter the desired value. Then apply the changes to the emulator. Refer to the "Using the EMSIM Registers"...
Page 110: Mapping Memory
Mapping Memory If you are using the emulator in ACT mode, emulation memory cannot be used; therefore, this section is not applicable. Because the emulator can use target system memory or emulation memory (or both) in Normal mode, it is necessary to map ranges of memory so that the emulator knows where to direct its accesses.
Page 111 Configuring the Emulator To define values for the emulator copy of the SIM registers Figure 20 This section shows you how to: • Add memory map entries. • Modify memory map entries. • Delete memory map entries. • Characterize unmapped ranges. •...
Page 112: To Add Memory Map Entries
Configuring the Emulator To add memory map entries To add memory map entries • Choose Map→Add New Entry from the pulldown menu in the memory map window. • Press and hold the select mouse button and choose Add New Entry from the popup menu.
Page 113 Configuring the Emulator To add memory map entries The first two methods of mapping memory ranges give you the following dialog box. Figure 21 Subtract or add the address increment value. The starting address of The end address is the range to be added. changed by the same amount, thereby moving The ending address of...
Page 114 Configuring the Emulator To add memory map entries Examples Consider the following section summary from the linker load map output listing. SECTION SUMMARY --------------- SECTION ATTRIBUTE START LENGTH ALIGN ABSOLUTE DATA 00000000 0000002F 00000030 0 (BYTE) NORMAL 00000030 00000030 00000000 2 (WORD) NORMAL CODE 00000400...
Page 115 Configuring the Emulator To add memory map entries Using the command line (choose Settings→Command Line from the pulldown menu in the memory map window), enter the following commands to map memory for the above program. delete all <addr> 0 thru 4fffh emulation rom 7000h thru 8fffh emulation ram 0b000h thru 16fffh emulation ram The resulting memory mapper screen is shown below.
Page 116: To Modify Memory Map Entries
Configuring the Emulator To modify memory map entries To modify memory map entries • Choose Map→Modify Entry from the pulldown menu in the memory map window and select the entry number from the cascade menu. • Position the mouse pointer over the entry you wish to modify, press and hold the select mouse button and choose Modify Entry from the popup menu.
Page 117: To Delete Memory Map Entries
Configuring the Emulator To delete memory map entries To delete memory map entries • Choose Map→Delete Entry from the pulldown menu in the memory map window and select the entry number from the cascade menu. • Position the mouse pointer over the entry you wish to delete, press and hold the select mouse button and choose Delete Entry from the popup menu.
Page 118: To Map Memory Ranges That Use Function Codes
Configuring the Emulator To map memory ranges that use function codes To map memory ranges that use function codes • Specify function codes with address ranges when mapping memory. The function code can be: • None • supervisor • supervisor program •...
Page 119 Configuring the Emulator To map memory ranges that use function codes When you do this, be sure that all address ranges not mapped (that is, the "other" memory mapper term) are mapped as target RAM. When "other" is mapped as guarded, guarded memory access errors (from the attempt to load the absolute file sections that are outside the specified function code range) can prevent the absolute file sections that are inside the specified function range from being loaded.
Page 120 Configuring the Emulator To map memory ranges that use function codes After the configuration is saved, display memory at 1000H by entering the following command (using the command line): display memory 1000h blocked bytes Notice that an "ambiguous address" error occurs because the "sp" function code was not included with the address.
Page 121: Setting The Debug/Trace Options
Setting the Debug/Trace Options To set the debug/trace options, you must start the configuration interface and access the "Debug/Trace Options" configuration section (refer to the "Using the Configuration Interface" section). Figure 22 To access information about the configuration items, use the online help button or press f1 to show context-sensitive help on an individual item.
Page 122: When Configuring The Trace Mode
Configuring the Emulator When Configuring the Trace Mode When Configuring the Trace Mode "Background" specifies that the analyzer trace only background cycles. This is rarely a useful setting for user program debugging. "Both" specifies that the analyzer trace both foreground and background cycles.
Page 123: Setting Simulated I/O
Setting Simulated I/O To set the debug/trace options, you must start the configuration interface and access the "Simulated I/O " configuration section (refer to the "Using the Configuration Interface" section). Figure 23 To access information about the configuration items, use the online help button or press f1 to show context-sensitive help on an individual item.
Page 124: Verifying The Emulator Configuration
Verifying the Emulator Configuration The 6833x emulator lets you display information about emulator configuration and processor SIM programming. You can also display information about inconsistencies found in the emulator configuration. This section shows you how to: • Display information about chip selects. •...
Page 125 Configuring the Emulator To display information about chip selects The following table reflects the current values in the sim (processor) register set. Select Assign Base Size Mode Byte Strb DSACK Space IPL AVEC ------ ------ ------- ---- ----- ----- ----- ---- ------ ----- ------ ---- CSBOOT 16-bit 000000H 1M async both both...
Page 126: To Display Information About Bus Interface Ports
Configuring the Emulator To display information about bus interface ports To display information about bus interface ports • Choose Display→Configuration Info→Bus Interface Ports (SIM) or Display→Configuration Info→Bus Interface Ports (Emulator SIM) from either the configuration interface the emulator/analyzer interface pulldown menu. •...
Page 127: To Display Information About The Memory Map
Configuring the Emulator To display information about the memory map To display information about bus interface ports from the emsim (emulator) register set, choose Display→Configuration Info→Bus Interface Ports (Emulator SIM) from either the configuration interface the emulator/analyzer interface pulldown menu. The following table reflects the current values in the emsim register set that relate to the external bus interface.
Page 128 Configuring the Emulator To display information about the memory map Examples To display information about the memory map and its correlation with RAM, choose Display→Configuration Info→Memory Map from either the configuration interface the emulator/analyzer interface pulldown menu. Notice the entry labeled "info". Ranges with this label do not take up mapper resources;...
Page 129: To Display Information About The Reset Mode Configuration
Configuring the Emulator To display information about the reset mode configuration To display information about the reset mode configuration • Choose Display→Configuration Info→Reset Mode Value from either the configuration interface the emulator/analyzer interface pulldown menu. • Using the emulator/analyzer interface command line, enter the display configuration_info reset_mode command.
Page 130: To Display Assembly Language Instructions For Setting Up The Sim
Configuring the Emulator To display assembly language instructions for setting up the SIM To display assembly language instructions for setting up the SIM • Choose Display→Configuration Info→Initialization Source Code from either the configuration interface the emulator/analyzer interface pulldown menu. • Using the emulator/analyzer interface command line, enter the display configuration_info init_source_code command.
Page 131: To Check For Configuration Inconsistencies
Configuring the Emulator To check for configuration inconsistencies MOVE.W #$0000,($0a58,A0) ;set csbr3 MOVE.W #$0000,($0a5a,A0) ;set csor3 MOVE.W #$0000,($0a5c,A0) ;set csbr4 MOVE.W #$0000,($0a5e,A0) ;set csor4 MOVE.W #$ffeb,($0a60,A0) ;set csbr5 MOVE.W #$783f,($0a62,A0) ;set csor5 MOVE.W #$0804,($0a64,A0) ;set csbr6 MOVE.W #$38f0,($0a66,A0) ;set csor6 MOVE.W #$0804,($0a68,A0) ;set csbr7...
Page 132 Configuring the Emulator To check for configuration inconsistencies Examples To check for inconsistencies between the configuration and the EMSIM registers, choose Display→Configuration Info→Diagnostics from either the configuration interface the emulator/analyzer interface pulldown menu. !STATUS 170! CS0 is set for block size of 1M byte but A19 is not available !STATUS 170! CS0 is DS qualified and SIZx not available;...
Page 134 Using the Emulator...
Page 135: Using The Emulator
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 emulation copy of the SIM (emsim) registers. • Loading and storing absolute files. •...
Page 136: Using The Emsim Registers
The SIM can be programmed or configured in a variety of ways to suit the need of various systems. The HP 64782 emulator contains circuitry that accommodates the flexibility of the SIM and maintains consistent emulation features. Figure 24...
Page 137 Using the Emulator In the previous figure, there is a block labeled DE-SIM module. It receives as inputs from the 6833x: • Port C which can be BR, BG, BGACK, FC0-2, and A19-23 or CS0-10. • CSBOOT. • SIZ0,1. The DE-SIM module provides as outputs: •...
Page 138 Using the Emulator The default programming of the DE-SIM matches the reset values of the 6833x SIM (refer to the Motorola MC6833x User’s Manual for specific values). If desired, the programming of the DE-SIM can be transferred into the 6833x SIM with the sync_sim_registers to_6833x_from_config command.
Page 139: To View The Sim Register Differences
Using the Emulator To view the SIM register differences To view the SIM register differences • Choose Display→SIM Register Differences from the emulator/analyzer interface pulldown menu. • Using the emulator/analyzer interface command line, enter the sync_sim_registers difference command. Note that PORTE and PORTF check only output pins. Any registers that are the same are not displayed.
Page 140: To Synchronize To The 6833X Sim Registers
Using the Emulator To synchronize to the 6833x SIM registers CSOR6 = 0000 EMCSBR6 = 0066 CSBR7 = 0000 EMCSBR7 = 7700 CSOR7 = 0000 EMCSBR7 = 0077 CSBR8 = 0000 EMCSBR8 = 8800 CSOR8 = 0000 EMCSBR8 = 0088 CSBR9 = 0000 EMCSBR9...
Page 141: 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 142: To Load Absolute Files Without Symbols
Using the Emulator To load absolute files without symbols Examples To load the demo program absolute file and the configuration file, enter the following commands: load configuration Config.EA load ecs.x To load only portions of the absolute file that reside in target system RAM: load user_mem absfile To load only portions of the absolute file that reside in emulation memory: load emul_mem absfile...
Page 143: To Store Memory Contents Into Absolute Files
Using the command line, enter the store memory <expression> 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 144: 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 145: To Display Global Symbols
Using the Emulator To display global symbols 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. If there is more than a screen full of information, you can use the up arrow, down arrow, <NEXT>, or <PREV>...
Page 146: To Display Local Symbols
Using the Emulator To display local 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 147 Using the Emulator To display local symbols Examples To use the Symbols Display popup menu: View the local symbols associated with the highlighted symbol by choosing this menu item.
Page 148 Using the Emulator To display local symbols Using the command line: To display local symbols in a module: display local_symbols_in update_sys To display local symbols in a procedure: display local_symbols_in update_sys.save_points...
Page 149 Using the Emulator To display local symbols To display address ranges associated with the high-level source line numbers: display local_symbols_in update_sys."update_sys.c":...
Page 150: To Display A Symbol's Parent Symbol
Using the Emulator To display a symbol’s parent symbol 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 151: To Copy-And-Paste A Full Symbol Name To The Entry Buffer
Using the Emulator To copy-and-paste a full symbol name to the entry buffer 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 152: 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. Unless you have changed directories since beginning the emulation session, the current directory context is that of the directory from which you started the interface.
Page 153: To Display The Current Directory And Symbol Context
Using the Emulator To display the current directory and symbol context 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 154: To Change The Current Working Symbol Context
Using the Emulator To change the current working symbol context To change the current working symbol context • Choose File→Context→Symbols and use the dialog box to select the new working symbol context. • Using the command line, enter the cws <symbol_context> command.
Page 155: 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 156: To Run Programs From An Address
Using the Emulator To run programs from an address 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 920H: run from 920h...
Page 157: To Run Programs Until An Address
Using the Emulator To run programs until an address To run programs until an address • When displaying memory in mnemonic format, position the mouse pointer over the line that you want to run until; then press and hold the select mouse button and choose Run Until from the popup menu. •...
Page 158: To Stop (Break From) User Program Execution
Using the Emulator To stop (break from) user program execution To stop (break from) user program execution • Choose Execution→Break. • Using the command line, enter the break command. This command generates a break to the background monitor. Software breakpoints and the run until command allow you to stop execution at particular points in the user program.
Page 159: To Step Assembly-Level Instructions
Using the Emulator To step assembly-level instructions To step through instructions associated with high-level source lines at address "main": step source from main To step assembly-level instructions • Choose Execution→Step Instruction and select one of the items from the cascade menu. •...
Page 160: To Reset The Emulation Processor
Using the Emulator To reset the emulation processor To reset the emulation processor • Choose Execution→Reset. • Using the command line, enter the reset command. The reset command causes the processor to be held in a reset state until a break, run, or step command is entered.
Page 161: Using Execution Breakpoints
Using Execution Breakpoints Breakpoints allow you to stop target program execution at a particular address and transfer control to the emulation monitor. Suppose your system crashes when it executes in a certain area of your program. You can set a breakpoint in your program at a location just before the crash occurs.
Page 162: Setting Execution Breakpoints In Ram
Using the Emulator Setting execution breakpoints in RAM Setting execution breakpoints in RAM When you set an execution breakpoint in RAM, the emulator will place a breakpoint instruction (BKPT) at the address you specified, and then read that address to ensure that the BKPT instruction is there. The program instruction that was replaced by BKPT is saved by the emulator.
Page 163: To Enable Execution Breakpoints
Using the Emulator To enable execution breakpoints To enable execution breakpoints • Choose Breakpoints→Enable. • Inside the breakpoints list display, press and hold the select mouse button and then choose Enable/Disable Software Breakpoints from the popup menu. • Using the command line, enable breakpoints with: modify software_breakpoints enable You must enable breakpoints before you can set, inactivate, or clear any breakpoints.
Page 164: To Disable An Execution Breakpoint
Using the Emulator To disable an execution breakpoint To disable an execution breakpoint • Choose Breakpoints→Enable again. The Breakpoints→Enable selection is a switch. • Inside the breakpoints list display, press and hold the select mouse button and then choose Enable/Disable Software Breakpoints from the popup menu.
Page 165: To Set A Permanent Breakpoint
Using the Emulator To set a permanent breakpoint To set a permanent breakpoint • When displaying memory in mnemonic format, position the mouse pointer over the program line where you wish to set the breakpoint 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 166: To Set A Temporary Breakpoint
Type in the absolute or symbolic address of the breakpoint you want to set in the entry buffer. Then choose Breakpoints→Temporary(), ( or choose Breakpoints→Set() if your version of HP 64700 system firmware is less than A.04.00). • Choose Breakpoints→Set All to set all existing breakpoints in the breakpoint table.
Page 167: To Clear An Execution Breakpoint
Using the Emulator To clear an execution breakpoint Examples Set a new breakpoint at get_targets: modify software_breakpoints set update_sys.get_targets Reenable all existing breakpoints: modify software_breakpoints set To clear an execution breakpoint • Type in the name of the breakpoint you want to clear in the entry buffer.
Page 168 Using the Emulator To clear an execution breakpoint Examples To clear a breakpoint using the breakpoints display popup menu: Bring up the menu and choose this item to clear the highlighted breakpoint. To clear an existing breakpoint at get_targets: modify software_breakpoints clear update_sys.get_targets To clear all existing breakpoints: modify software_breakpoints clear...
Page 169: To Clear All Execution Breakpoints
Using the Emulator To clear all execution breakpoints To clear all execution 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 170 Using the Emulator To display the status of all execution breakpoints The status of a breakpoint can be: temporary Which means the temporary breakpoint has been set but not encountered during program execution. These breakpoints are removed when the breakpoint is encountered. permanent Which means the permanent breakpoint is active.
Page 171: Displaying And Modifying Registers
Displaying and Modifying Registers This section describes tasks related to displaying and modifying emulation processor registers. Within the interface, related registers are grouped into a class. For example, the <BASIC> register class includes general registers, such as the PC, ST, USP, SSP, and data and address registers.
Page 172: To Modify Register Contents
Using the Emulator To modify register contents To modify register contents • Choose Modify→Register... 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 173: 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. This section shows you how to: •...
Page 174: To Display Memory In Mnemonic Format
Using the Emulator To display memory in mnemonic format 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 175: To Display Memory In Hexadecimal Format
Using the Emulator To display memory in hexadecimal format 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>...
Page 176: To Display Memory In Real Number Format
Using the Emulator To display memory in real number format To display memory in blocked byte format: display memory ascii_old_data blocked bytes 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 177: To Display Memory At An Address
Using the Emulator To display memory at an address Examples To display memory in 64-bit real number format: display memory real long To display memory at an address • Place an absolute or symbolic address in the entry buffer; then, choose Display→Memory→At ().
Page 178: To Display Memory Repetitively
Using the Emulator To display memory repetitively 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. This command is ignored if the last memory display command was a mnemonic display.
Page 179: 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 180: To Clear The Data Values Display And Add A New Item
Using the Emulator To clear the data values display and add a new item 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 181: 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 182: To Set The Display Modes
Using the Emulator To set the display modes 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". Clicking toggles whether symbolic information is displayed.
Page 183 Using the Emulator To set the display modes 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 184: Using System Commands
Using System Commands With the Softkey Interface system commands, you can: • Set UNIX environment variables while in the Softkey Interface. • Display the name of the emulation module. • Display the event log. • Display the error log. To set UNIX environment variables •...
Page 185: To Display The Event Log
Using the Emulator To display the event log Examples To display the name of your emulation module: name_of_module The name of the emulation module is displayed on the status line. To display the event log • Choose Display→Event Log. • Position the mouse pointer on the status line, press and hold the select mouse button, and then choose Display Event Log from the popup menu.
Page 186: To Edit Files
Using the Emulator To edit files 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; then, choose File→Edit→At () Location.
Page 187 Using the Emulator To edit files Examples To edit a file that defines a symbol: Choosing the Edit File Defining Symbol menu item brings up a terminal window with an edit session open on the file where the highlighted symbol is defined.
Page 188 Using the Emulator To edit files To edit a file at a source line: Choosing the Edit Source menu item brings up a terminal window with an edit session open on the file where the highlighted source line exists.
Page 189: To Copy Information To A File Or Printer
Using the Emulator To copy information to a file or printer 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. •...
Page 190: To Open A Terminal Emulation Window
Using the Emulator To open a terminal emulation window 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 191: 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 192: To Use Simulated I/O Keyboard Input
Using the Emulator To use simulated I/O keyboard input 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 193: Using Basis Branch Analysis
Using Basis Branch Analysis Basis branch analysis (BBA) is provided by the HP Branch Validator product. This product is used to analyze the testing of your programs, create more complete test suites, and quantify your level of testing. The HP Branch Validator records branches executed in a program and generates reports that provide information about program execution during testing.
Page 194 Using the Emulation Analyzer...
Page 195: Using The Emulation Analyzer
Using the Emulation Analyzer This chapter describes tasks you may wish to 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. •...
Page 196: 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 197: To Start A Trace Measurement
Using the Emulation Analyzer To start a trace measurement To start a trace measurement • Choose Trace→Everything. • Using the command line, enter: trace When you use the trace command without any options, the analyzer begins recording processor bus cycles immediately, and continues until the trace buffer is filled.
Page 198: To Stop A Trace Measurement
Using the Emulation Analyzer To stop a trace measurement To stop a trace measurement • Choose Trace→Stop. • Using the command line, enter: stop_trace You must use this command to stop a trace started with a Trace→Until Stop command (refer to "To trace activity leading up to a program halt" later in this chapter).
Page 199 The next column shows the count information (time is counted by default). "Relative" indicates that each count is relative to the previous state. If your analyzer card contains external analysis (for example, HP 64703), the next column shows the data captured on the external trace signals.
Page 200: To Display The Trace Status
Using the Emulation Analyzer To display the trace status Note that when a trigger condition is found but not enough states are captured to fill trace memory, the status line will show the trace is still running. You can display all but the last captured state in this situation; you must halt the trace to display the last captured state.
Page 201 Using the Emulation Analyzer To display the trace status the message "Arm not received" or "Arm received" is displayed. The display indicates if the arm condition happened any time since the most recent trace started, even if it happened after the trace was halted or became complete. (The "Making Coordinated Measurements"...
Page 202: To Change The Trace Depth
Using the Emulation Analyzer To change the trace depth To change the trace depth • Choose Trace→Display Options... and in the dialog box, enter the desired trace unload depth in the field beside Unload Depth. Then click the OK or Apply pushbutton. •...
Page 203: To Modify The Last Trace Command Entered
Using the Emulation Analyzer To modify the last trace command entered To modify the last trace command entered • Choose Trace→Trace Spec... and use the dialog box to select and edit a trace command. • Using the command line, enter the trace modify_command command.
Page 204: To Position The Trace Display On Screen
Using the Emulation Analyzer To position the trace display on screen Also, this command is useful when you load a trace specification from a file. (See "To load a trace specification" in this chapter.) To position the trace display on screen •...
Page 205: 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). Also, you can prestore states.
Page 206 Using the Emulation Analyzer To position the trace display on screen Don’t care digits may be included in binary, octal, or hexadecimal numbers and they are represented by the letters X or x. A zero must precede any numerical value that begins with an "X". Symbols A symbol database is built when the absolute file is loaded into the emulator.
Page 207 Using the Emulation Analyzer To position the trace display on screen Emulation Analyzer Trace Signals When you qualify states, you specify values that should be found on the analyzer trace signals. The emulation analyzer trace signals are described in the table that follows. Emulation Analyzer Trace Signals Trace Analyzer...
Page 208 Using the Emulation Analyzer To position the trace display on screen Emulation Analyzer Trace Signals Trace Analyzer Signal Signal Signals Channel # Name Description bit 8 ch 56 DSACK0 These are processor DSACK signals, which may be bit 9 ch 57 DSACK1 configured as I/O pins.
Page 209 Using the Emulation Analyzer To position the trace display on screen 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 monitor the emulation processor’s address bus.
Page 210: To Specify A Trigger And Set The Trigger Position
Using the Emulation Analyzer To specify a trigger and set the trigger position To specify a trigger and set the trigger position • Enter a trigger state specification in the entry buffer; then, choose Trace→After (), Trace→About (), or Trace→Before (). •...
Page 211 Using the Emulation Analyzer To specify a trigger and set the trigger position 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 set source on inverse_video on symbols on...
Page 212: To Use Address, Data, And Status Values In Trace Expressions
Using the Emulation Analyzer To use address, data, and status values in trace expressions To use address, data, and status values in trace expressions • Enter the value(s) desired in the entry buffer (such as address 1000h). Then Choose Trace→After(), Trace→Before(), or Trace→About(), as desired.
Page 213: To Enter A Range In A Trace Expression
Using the Emulation Analyzer To enter a range in a trace expression To enter a range in a trace expression • Use the command-line rules (described below) to create your expression in the entry buffer. Then Choose Trace→After(), Trace→Before(), or Trace→About(), as desired. •...
Page 214: To Trigger On A Number Of Occurrences Of Some State
Using the Emulation Analyzer To trigger on a number of occurrences of some state You can use the logical or operator to combine the range term with several state qualifiers. See the examples. Examples Store only the accesses to the demo program’s current_humid location: trace only range current_humid thru +1h Store only bus cycles where data is in the range 6h..26h or is 29h: trace only data range 6h thru 26h or data 29h...
Page 215: To Break Emulator Execution On The Analyzer Trigger
Using the Emulation Analyzer To break emulator execution on the analyzer trigger To break emulator execution on the analyzer trigger • Enter a trigger state specification in the entry buffer; then, choose Trace→Until (). • When displaying memory in mnemonic format, position the mouse pointer over the program line which you wish to trace before, press and hold the select mouse button and choose Trace Until from the popup menu.
Page 216 Using the Emulation Analyzer To count states or time <bus_state> represents a combination of address, data and status expressions that must be matched to satisfy the trigger qualifier. • To count all states in the trace, enter: trace counting anystate •...
Page 217: To Define A Storage Qualifier
Using the Emulation Analyzer To define a storage qualifier Examples To count occurrences of a particular bus state in the trace (this requires the 1K analyzer speed to be set to "Slow" in configuration): trace counting state address 10h Count all states in the trace: trace counting anystate Count time in the trace: trace counting time...
Page 218: To Define A Prestore Qualifier
Using the Emulation Analyzer To define a prestore qualifier sequencer or trigger specification, any states given there are shown in the trace list even if they don’t meet the storage qualifier. Examples Trace only address 10h: trace only address 10h Trace only data value 0ffh: trace only data 0ffh Trace only write operations...
Page 219 Using the Emulation Analyzer To define a prestore qualifier You use the prestore qualifier to save states that are related to other routines that you’re tracing. For example, you might be tracing a subprogram, and want to see which program called it. You can specify calls be prestored and that entries to the subprogram be stored.
Page 220: To Trace Activity Leading Up To A Program Halt
Using the Emulation Analyzer To trace activity leading up to a program halt To trace activity leading up to a program halt • Choose Trace→Until Stop. • Using the command line, trace on a program halt by entering: trace on_halt The above commands cause the analyzer to continuously fill the trace buffer until you issue a Trace→Stop or stop_trace command.
Page 221 Using the Emulation Analyzer To capture a continuous stream of program execution no matter how large your program Choose Trace→Display Options ..., and in the dialog box, enter 0 or the total depth of your deep analyzer trace memory in the entry field beside Unload Depth.
Page 222 Using the Emulation Analyzer To capture a continuous stream of program execution no matter how large your program Note that "trng addr=<addr>..<addr>" means define an address range for the analyzer; "tsto !r" means store all trace activity except activity occurring in the defined address range.
Page 223 Using the Emulation Analyzer To capture a continuous stream of program execution no matter how large your program Resume the program run from the point where it was interrupted when the emulator broke to the monitor with the command run. Wait until the notation "trig1 break"...
Page 224: 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. Also, the analyzer’s sequencer allows you to trace "windows"...
Page 225: To Trigger After A Sequence Of States
Using the Emulation Analyzer To trigger after a sequence of states To trigger after a sequence of states • Create your first specification form on the command line. That will enter the proper format in the Trace Specification Selection dialog box.
Page 226 Using the Emulation Analyzer To trigger after a sequence of states 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 227: To Specify A Global Restart State
Using the Emulation Analyzer To specify a global restart state To specify a global restart state • Create your first specification form on the command line. That will enter the proper format in the Trace Specification Selection dialog box. Obtain the dialog box by choosing Trace→Trace Spec... You can click on your specification in the dialog box, edit it if desired, and click OK.
Page 228 Using the Emulation Analyzer To specify a global restart state To set up this sequencing trace specification, enter the following trace command. trace find_sequence save_points then interrupt_sim restart proc_specific trigger about do_sort only data 4e56h set source off 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"...
Page 229: To Trace "Windows" Of Program Execution
Using the Emulation Analyzer To trace "windows" of program execution To trace "windows" of program execution • Create your first specification form on the command line. That will enter the proper format in the Trace Specification Selection dialog box. Obtain the dialog box by choosing Trace→Trace Spec... You can click on your specification in the dialog box, edit it if desired, and click OK.
Page 230 Using the Emulation Analyzer To trace "windows" of program execution Examples In the demo program, suppose you are only interested in the execution that occurs within the switch statement of the "combsort" function. You could specify source line number 229 as the window enable state and the source line number of the next statement (line number 241) as the window disable state.
Page 231: To Specify Both Sequencing And Windowing
Using the Emulation Analyzer To specify both sequencing and windowing To specify both sequencing and windowing • Create your first specification form on the command line. That will enter the proper format in the Trace Specification Selection dialog box. Obtain that dialog box by choosing Trace→Trace Spec... You can click on your specification in the dialog box, edit it if desired, and click OK.
Page 232: Displaying The Trace List
Displaying the Trace List The trace list is your view of the analyzer’s record of processor bus activity. You can specify what is shown in the trace list to make it easier to find the information of interest. For example, you can display symbol information where available, or source lines from the high-level languages used to write the target system program.
Page 233 Using the Emulation Analyzer To specify both sequencing and windowing Examples To use the Trace Options dialog box: Click to select the desired format of trace disassembly. Click to select the way that absolute status information is shown in the trace list. Click to select count reference: Relative (to preceding state), or Absolute (to trigger).
Page 234 Using the Emulation Analyzer To specify both sequencing and windowing Examples To use the trace list popup menu: Click to begin trace disassembly from the selected line, moving that line to the top of the display. Click to open an edit window into the source file that contains the address of the selected line.
Page 235: To Display The Trace About A Line Number
Using the Emulation Analyzer To display the trace about a line number To display the trace about a line number • Choose Trace→Display Options... and in the dialog box, enter the desired trace list line number in the field beside Move to Line. Then click the OK or Apply pushbutton.
Page 236: To Move Through The Trace List
Using the Emulation Analyzer To move through the trace list To move through the trace list • Use the scroll bar at the right of the display to scroll up and down. Use the arrows at the bottom of the display (if any) to scroll left and right.
Page 237 Using the Emulation Analyzer To disassemble the trace list • To control where trace list disassembly starts, enter: display trace disassemble_from_line_number <LINE #> <LINE #> is a line number corresponding to a state in the trace list. Disassembly of instruction data means that you will see instructions as they would appear in an assembly language program listing.
Page 238: To Specify Trace Disassembly Options
Using the Emulation Analyzer To specify trace disassembly options To specify trace disassembly options • Selection of disassembly options is not supported in pulldowns of the Graphical User Interface. By default, the Graphical User Interface selects high_word and all_cycles. Use the command line if you need to specify trace disassembly using other options.
Page 239: To Specify Trace Dequeueing Options
Using the Emulation Analyzer To specify trace dequeueing options Examples Show only instruction cycles in the trace list starting at line 40: display trace disassemble_from_line_number 40 instructions_only Show all bus cycles in the trace list: display trace disassemble_from_line_number 40 all_cycles To specify trace dequeueing options •...
Page 240 Using the Emulation Analyzer To specify trace dequeueing options Once the dequeuer has been started on the correct opcode, it will continue to disassemble correctly unless an unusual condition causes it to misinterpret the data. By specifying the first instruction state for disassembly and the number of the first operand cycle for that instruction, you can resynchronize the disassembly.
Page 241: To Display The Trace Without Disassembly
Using the Emulation Analyzer To display the trace without disassembly To display the trace without disassembly • Choose Trace→Display Options... and in the dialog box, select Data Format Absolute. You can select Hex, Binary, or Mnemonic format for display of status information. Then click the OK or Apply pushbutton.
Page 242 Using the Emulation Analyzer To display the trace without disassembly Examples Display the trace list without instruction disassembly and with status information in binary format: Choose Trace→Display Options... and in the dialog box, select Data Format Absolute. Select Status Format Binary. Then click the OK or Apply pushbutton.
Page 243: To Display Symbols In The Trace List
Using the Emulation Analyzer To display symbols in the trace list To display symbols in the trace list • Choose Settings→Source/Symbol Modes→Symbols, or choose Settings→Display Modes ..., and in the dialog box, click on Symbolic Addresses. In the Field Widths area of the dialog box, you can select the widths of the Label Field and Symbols in Mnemonic Field to control the display space allocated to the symbols.
Page 244: To Display Source Lines In The Trace List
Using the Emulation Analyzer To display source lines in the trace list The Settings→Source/Symbol Modes..., Settings→Display Modes..., or set symbols command remains in effect until you enter a new Settings→Source/Symbol Modes..., Settings→Display Modes..., or set symbols command with different options. Refer to Chapter 6, "Using the Emulator", for details of how to set up and use the Display Modes dialog box.
Page 245: To Change The Column Width
Using the Emulation Analyzer To change the column width To change the column width • Choose Settings→Display Modes..., and select desired widths for information in the trace list by using the dialog box. Refer to the "Examples" page under "To display symbols in the trace list", earlier in this chapter for details of how to use the dialog box.
Page 246: To Select The Type Of Count Information In The Trace List
Using the Emulation Analyzer To select the type of count information in the trace list Example Set the width of the address label column to 30 characters and the width of the mnemonic column to 50 characters: set width label 30 mnemonic 50 To select the type of count information in the trace list •...
Page 247 Using the Emulation Analyzer To select the type of count information in the trace list Examples Count time and store only each iteration of the update_sys symbol in the demo program (if using the 1K analyzer, make sure the clock speed is set to "Slow"...
Page 248: To Offset Addresses In The Trace List
Using the Emulation Analyzer To offset addresses in the trace list To offset addresses in the trace list • Choose Trace→Display Options... and in the dialog box, enter the desired offset value in the field beside Address Offset. Then click the OK or Apply pushbutton.
Page 249: To Reset The Trace Display Defaults
Using the Emulation Analyzer To reset the trace display defaults To reset the trace display defaults • Choose Settings→Display Modes... Then in the dialog box, click on Default All Settings, and click the OK pushbutton. This leaves the trace display in the "source intermixed and symbols on" mode. •...
Page 250: To Display Program Memory Associated With A Trace List Line
Using the Emulation Analyzer To display program memory associated with a trace list line Examples Set the depth of the trace memory to 256 states: Choose Trace→Display Options... and in the dialog box, enter 256 in the field beside Unload Depth. Then click the OK or Apply pushbutton. Set the depth of the trace to 1024 states: display trace depth 1024 To display program memory associated with a trace...
Page 251: Saving And Restoring Trace Data And Specifications
Saving and Restoring Trace Data and Specifications The emulator/analyzer can save your trace data and trace specifications in a file for later use. This can help you record measurement results that you can use for comparison with other tests, and it is useful to automate measurements.
Page 252: To Store Trace Data
Using the Emulation Analyzer To store trace data commands that you want to make every time your target system program is modified. You can store each trace command in a separate file and recall it later using the load trace_spec command. Example Store a trace specification to a file: store trace_spec tspec.TS...
Page 253: To Load A Trace Specification
Using the Emulation Analyzer To load a trace specification To load a trace specification • Choose File→Load→Trace Spec... In the dialog box, click on the name of the trace specification you want to load (placing it in the Load Trace Specification box). Then click OK. •...
Page 254: To Load Trace Data
Using the Emulation Analyzer To load trace data To load trace data • Choose File→Load→Trace Data... In the dialog box, click on the name of the trace data file (file of trace memory content) you want to load (placing it in the Load Trace Data box). Then click OK. •...
Page 256: Making Software Performance Measurements
Making Software Performance Measurements...
Page 257: Making Software Performance Measurements
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...
Page 258: 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 259 Making Software Performance Measurements data Address Range 6007AH thru 603A5H Memory Activity State Percent Rel = 30.51 Abs = 30.51 Mean = 156.20 Sdv = 31.87 Time Percent Rel = 28.09 Abs = 28.09 Program Activity State Percent Rel = 0.18 Abs = 0.18...
Page 260 Making Software Performance Measurements Graph of Program Activity relative time percents >= 1 prog 99.84% ************************************************** Summary Information for 10 traces Memory Activity State count Relative count 5120 Mean sample 170.67 Mean Standard Dv 29.30 95% Confidence 12.28% Error tolerance Time count Relative Time - Us 2221.20...
Page 261: To Set Up The Trace Command For Activity Measurements
Making Software Performance Measurements To set up the trace command for activity measurements To set up the trace command for activity measurements Specify a trace display depth of 512. Trace after any state, store all states, and count time. Before you initialize and run performance measurements, the current trace command (in other words, the last trace command entered) must be properly set up.
Page 262: To Initialize Activity Performance Measurements
Making Software Performance Measurements To initialize activity performance measurements To initialize activity performance measurements • Use the performance_measurement_initialize command. After you set up the trace command, you must tell the SPMT the address ranges on which you wish to make activity measurements. This is done by initializing the performance measurement.
Page 263 Making Software Performance Measurements To initialize activity performance measurements Address range files may contain program symbols (procedure name or static), user defined address ranges, and comments. An example address range file is shown below. # Any line which starts with a # is a comment. # All user’s labels must be preceded by a "|".
Page 264 Making Software Performance Measurements To initialize activity performance measurements Initialization with Local Symbols When the performance_measurement_initialize command is entered with the local_symbols_in option and a source file name, the symbols associated with that source file become the address ranges for which activity is measured.
Page 265 Making Software Performance Measurements To initialize 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 266: To Interpret Activity Measurement Reports
Making Software Performance Measurements To interpret activity measurement reports 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 267 Making Software Performance Measurements To interpret activity measurement reports 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. mean Average number of states in the range per trace. Sum of squares of states in the range per trace.
Page 268 Making Software Performance Measurements To interpret activity measurement reports 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.
Page 269 Making Software Performance Measurements To interpret activity measurement reports Label set_outputs Address Range 1784H thru 1814H Memory Activity State Percent Rel = 30.28 Abs = 25.00 Mean = 128.00 Sdv = 227.46 Time Percent Rel = 30.45 Abs = 25.45 Program Activity State Percent Rel =...
Page 270 Making Software Performance Measurements To interpret activity measurement reports Address Range 10B0H thru 110AH Memory Activity State Percent Rel = 9.75 Abs = 8.05 Mean = 41.20 Sdv = 116.63 Time Percent Rel = 9.45 Abs = 7.90 Program Activity State Percent Rel = 12.39...
Page 271 Making Software Performance Measurements To interpret activity measurement reports Memory Activity State Percent Rel = 3.84 Abs = 3.17 Mean = 16.25 Sdv = 72.67 Time Percent Rel = 3.86 Abs = 3.23 Program Activity State Percent Rel = 3.70 Abs = 3.19 Mean =...
Page 272 Making Software Performance Measurements To interpret activity measurement reports Mean = 0.00 Sdv = 0.00 Time Percent Rel = 0.00 Abs = 0.00 Program Activity State Percent Rel = 0.00 Abs = 0.00 Mean = 0.00 Sdv = 0.00 Time Percent Rel = 0.00...
Page 273 Making Software Performance Measurements To interpret activity measurement reports Program Activity State Percent Rel = 0.00 Abs = 0.00 Mean = 0.00 Sdv = 0.00 Time Percent Rel = 0.00 Abs = 0.00 save_points Address Range 189CH thru 1980H Memory Activity State Percent Rel = 0.00...
Page 274 Making Software Performance Measurements To interpret activity measurement reports set_outputs 28.97% *************** update_system 28.99% *************** read_conditions 11.59% ****** strcpy8 12.39% ****** interrupt_sim 5.97% write_hdwr 5.79% proc_specific 3.70% combsort 1.90% Graph of Program Activity relative time percents >= 1 set_outputs 29.28% *************** update_system 29.29%...
Page 275 Making Software Performance Measurements To interpret activity measurement reports The measurements for each label are printed in descending order according to the amount of activity. You can see that the set_outputs function has the most activity. Also, you can see that no activity is recorded for several of the functions.
Page 276: 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 277: To Set Up The Trace Command For Duration Measurements
Making Software Performance Measurements To set up the trace command for duration measurements When measuring a recursive function, module duration will be measured between the last recursive call and the true end of the recursive execution. This will affect the accuracy of the measurement. 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.
Page 278 Making Software Performance Measurements To set up the trace command for duration measurements trace after module_name start or module_name end only module_name start or module_name end counting time 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 279: To Initialize Duration Performance Measurements
Making Software Performance Measurements To initialize 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. This is done by initializing the performance measurement.
Page 280 Making Software Performance Measurements To initialize duration performance measurements 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 20.1 ms 40 ms 40.1 ms 80 ms 80.1 ms 160 ms 160.1 ms 320 ms...
Page 281: To Interpret Duration Measurement Reports
Making Software Performance Measurements To interpret duration measurement reports 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. The information you will see in duration measurement reports is described below.
Page 282 Making Software Performance Measurements To interpret duration measurement reports 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 283 Making Software Performance Measurements To interpret duration measurement reports Examples Consider the following duration measurement report (generated with the commands shown): display trace depth 512 trace after interrupt_sim start or interrupt_sim end only interrupt_sim start or interrupt_sim end counting time performance_measurement_initialize duration performance_measurement_run 10 performance_measurement_end...
Page 284 Making Software Performance Measurements To interpret duration measurement reports 10.1 ms 20 ms 0.00% 20.1 ms 40 ms 0.00% 40.1 ms 80 ms 100.00% ************************************************** 80.1 ms 160 ms 0.00% 160.1 ms 320 ms 0.00% 320.1 ms 640 ms 0.00% 640.1 ms 1.2 s 0.00% From Address...
Page 285 Making Software Performance Measurements To interpret duration measurement reports Two sets of information are given in the duration measurement report: module duration and module usage. The first set is the "module usage" measurement. Module usage measurements show how much time is spent outside the module of interest; they indicate how often the module is used.
Page 286: 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. • End performance measurements. • Create a performance measurement report. To run performance measurements •...
Page 287: To End Performance Measurements
Making Software Performance Measurements To end performance measurements Examples To run the performance measurement, enter the following command: performance_measurement_run 20 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 288: To Create A Performance Measurement Report
Making Software Performance Measurements To create a performance measurement report Examples To cause the processed trace information to be dumped to the "perf.out" file: performance_measurement_end 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 289 Making Software Performance Measurements To create a performance measurement report Options -h, -s, -p, and -m affect the contents of reports generated for activity measurements. These options have no effect on the contents of reports generated for duration (time interval) measurements. Examples Now, to generate a report from the "perf.out"...
Page 290: Using The External State Analyzer
Using the External State Analyzer...
Page 291: Using The External State Analyzer
Using the External State Analyzer The HP 64703A analyzer provides an external analyzer with 16 external trace channels. These trace channels allow you to capture activity on signals external to the emulator, typically other target system signals. The external analyzer may be configured as an extension to the emulation analyzer, as an independent state analyzer, or as an independent timing analyzer.
Page 292: Setting Up The External Analyzer
Setting Up the External Analyzer This section assumes you have already connected the external analyzer probe to the HP 64700 Card Cage. Before you can use the external analyzer, you must: • Connect the external analyzer probe to the target system.
Page 293 Using the External State Analyzer To connect the external analyzer probe to the target system 2 Attach grabbers to probe wires. Each of the 18 probe wires has a signal and a ground connection. Each probe wire is labeled for easy identification. Thirty-six grabbers are provided for the signal and ground connections of each of the 18 probe wires.
Page 294 Using the External State Analyzer To connect the external analyzer probe to the target system Turn OFF target system power before connecting analyzer probe wires to C A U T I O N the target system. The probe grabbers are difficult to handle with precision, and it is extremely easy to short the pins of a chip (or other connectors which are close together) with the probe wire while trying to connect it.
Page 295: Configuring The External Analyzer
Configuring the External Analyzer After you have assembled the external analyzer probe and connected it to the emulator and target system, the next step is to configure the external analyzer. The external analyzer is a versatile instrument, and you can configure it to suit your needs.
Page 296 Using the External State Analyzer To connect the external analyzer probe to the target system Figure 25 If you’re using the Softkey Interface from a terminal or terminal emulation window, you don’t get a dialog box from which to choose configuration sections;...
Page 297: To Control The External Analyzer With The Emulator/Analyzer Interface
Using the External State Analyzer To control the external analyzer with the emulator/analyzer interface "External Analyzer" section, answer "yes" to the "Modify external analyzer configuration?" question. This section describes how to: • Specify whether the emulation emulator/analyzer interface should control the external analyzer.
Page 298: To Specify The External Analyzer Mode
Using the External State Analyzer To specify the external analyzer mode through 15 and the K clock). You can specify a threshold voltage for each of these groups. The default threshold voltages are specified as TTL which translates to 1.40 volts.
Page 299: To Specify The Slave Clock Mode
Using the External State Analyzer To specify the slave clock mode To specify the slave clock mode Choose "yes" for the "Should emulation control the external bits" configuration option. Choose "State" for the "External analyzer mode" configuration option. Choose "Off", "Mixed", or "Demux" for the "Slave clock mode for external bits"...
Page 300 Using the External State Analyzer To specify the slave clock mode more than one slave clock has appeared since the last master clock, only the first slave data will be available to the analyzer (see the figure below). Figure 27 Choose "demux"...
Page 301 Using the External State Analyzer To specify the slave clock mode Figure 28 If no slave clock has appeared since the last master clock, the data on the lower 8 bits of the pod will be the same as the upper 8 bits. If more than one slave clock has appeared since the last master clock, only the first slave data will be available to the analyzer.
Page 302: To Define Labels For The External Analyzer Signals
Using the External State Analyzer To define labels for the external analyzer signals If the "mixed" or "true demultiplexing" slave clock modes are selected, choose "None", "rising", "falling", or "Both" for the "Edges of J (K,L,M) clock used for slave clock" configuration options. Four configuration options are present when you select either the "mixed"...
Page 304: Making Coordinated Measurements
Making Coordinated Measurements...
Page 305: Making Coordinated Measurements
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 306 Making Coordinated Measurements The location of the CMB and BNC connectors on the HP 64700 rear panel is shown in the following figure. Figure 29 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 307 CMB 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 308: Setting Up For Coordinated Measurements
C A U T I O N by some computer systems for 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 309 Making Coordinated Measurements To connect the Coordinated Measurement Bus (CMB) 1 Connect the cables to the HP 64700 CMB ports.
Page 310: 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 311 To connect to the rear panel BNC 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 312: 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. This section describes how to: •...
Page 313: To Start Synchronous Measurements
Making Coordinated Measurements To start synchronous measurements Examples To enable synchronous measurements: specify run from 1e8h To trace when synchronous execution begins: specify trace after address main To start synchronous measurements • Enter the cmb_execute command. The cmb_execute command will cause the EXECUTE line to be pulsed, thereby initiating a synchronous measurement.
Page 314: 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 315 You can use the trig1 or trig2 line to make a connection between the analyzer and the CMB connector or BNC connector so that, when the analyzer finds its trigger condition, a trigger signal is driven on the HP 64700’s Coordinated Measurement Bus (CMB) or BNC connector. This can also be done for the external analyzer when it is configured as an independent state or timing analyzer.
Page 316 Making Coordinated Measurements To disable synchronous measurements Figure 31 If you’re using the Softkey Interface from a terminal or terminal emulation window, you don’t get a dialog box from which to choose configuration sections; however, you have access to the same configuration options through a series of configuration questions.
Page 317: To Drive The Emulation Analyzer Trigger Signal To The Cmb
Making Coordinated Measurements To drive the emulation analyzer trigger signal to the CMB • Arm the emulation analyzer on signal from CMB. • Arm the emulation analyzer on signal from BNC. • Arm the emulation analyzer on external analyzer trigger. •...
Page 318: To Drive The External Analyzer Trigger Signal To The Bnc Connector
Making Coordinated Measurements To drive the external analyzer trigger signal to the BNC connector To drive the external analyzer trigger signal to the BNC connector Choose "receive" for the "Should BNC drive or receive Trig2" configuration option. Choose "drive" for the "Should External Analyzer drive or receive Trig2"...
Page 319: To Arm The Emulation Analyzer On Signal From Cmb
Making Coordinated Measurements To arm the emulation analyzer on signal from CMB breaks. However, if trig1 is used to cause the break and trig2 is used to drive the CMB TRIGGER, TRIGGER will stay true until the trace is halted or until the next trace starts.
Page 320: To Arm The External Analyzer On Signal From Cmb
Making Coordinated Measurements To arm the external analyzer on signal from CMB To arm the external analyzer on signal from CMB Choose "drive" for the "Should CMBT drive or receive Trig2" configuration option. Choose "receive" for the "Should External Analyzer drive or receive Trig2"...
Page 322 Setting X Resources...
Page 323: Setting X Resources
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 in HP-UX or /usr/openwin/lib/X11/app-defaults/HP64_Softkey in SunOS. The $XAPPLRESDIR/HP64_Softkey file. (The XAPPLRESDIR environment variable defines a directory containing system-wide custom application defaults.)
Page 324 Setting X Resources 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. This chapter shows you how to: •...
Page 325: To Modify The Graphical User Interface Resources
Application Resources for Schemes Resource Values Description HP64_Softkey.platformScheme HP-UX Names the subdirectory for platform specific SunOS schemes. This resource should be set to the (custom) 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 326 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. HP64_Softkey.enableCmdline True Specifies whether the command line area is...
Page 327 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 328 Save your changes and exit the editor. 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.
Page 329: To Use Customized Scheme Files
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 330 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": HP64_Softkey.colorScheme: MyColor...
Page 331: To Set Up Custom Action Keys
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 332: To Set Initial Recall Buffer Values
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. The window manager resource "*transientDecoration"...
Page 333: To Set Up Demos Or Tutorials
Setting X Resources To set up demos or tutorials Examples To set the initial values for the directory selection dialog box when the Graphical User Interface is used with 6833x emulators, modify the "*m6833x*dirSelectSub.entries" resource: *m6833x*dirSelectSub.entries: \ "$HOME" \ ".." \ "/users/project1"...
Page 334 Setting X Resources To set up demos or tutorials Tutorial Related Component Resources Resource Value Description *enableTutorial False Specifies whether Help→Tutorial True 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 topic list...
Page 335 Setting X Resources To set up demos or tutorials 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 336: Part 3 Reference
Part 3 Reference...
Page 337 Part 3 Descriptions of the product in a dictionary or encyclopedia format.
Page 338: Emulator/Analyzer Interface Commands
Emulator/Analyzer Interface Commands...
Page 339: Emulator/Analyzer Interface Commands
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 Pulldown menu items and corresponding softkey commands are shown below. Pulldown Command Line File→Context→Directory...
Page 340 Emulator/Analyzer Interface Commands Pulldown Command Line File→Log→Playback <command file> File→Log→Record log_commands to File→Log→Stop log_commands off File→Emul700→High-Level Debugger File→Emul700→Performance Analyzer File→Emul700→Emulator/Analyzer File→Emul700→Timing Analyzer File→Emul700→SPA for VRTXsa File→Emul700→SPA for VRTX File→Edit→File ! vi <file> ! no_prompt_before_exit File→Edit→At () Location ! vi +<line> <file> ! no_prompt_before_exit File→Edit→At PC Location ! vi +<line>...
Page 341 Emulator/Analyzer Interface Commands Pulldown Command Line Display→Configuration Info display configuration_info Display→Configuration Info→Diagnostics display configuration_info diagnostics Display→Configuration Info→Chip Selects display configuration_info sim_chip_selects (SIM) Display→Configuration Info→Chip Selects display configuration_info emsim_chip_selects (Emulator SIM) Display→Configuration Info→Bus Interface display configuration_info bus_interface_ports Ports (SIM) Display→Configuration Info→Bus Interface display configuration_info embus_interface_ports Ports (Emulator SIM) Display→Configuration Info→Memory Map...
Page 342 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 343 Emulator/Analyzer Interface Commands Pulldown Command Line Trace→Display display trace Trace→Display Options display trace Trace→Trace Spec N/A (browses recall buffer for trace commands) Trace→After () trace after STATE Trace→Before () trace before STATE Trace→About () trace about STATE Trace→Only () trace only STATE Trace→Only () Prestore trace only STATE prestore anything Trace→Again...
Page 344 Emulator/Analyzer Interface Commands How Popup Menus Map to the Command Line The following tables show the items available in the popup menus and the command line commands to which they map. Mnemonic Memory Display Popup Command Line Set/Clear Software Breakpoint modify software_breakpoints set/clear --EXPR-- Edit Source ! vi +<line>...
Page 345 Emulator/Analyzer Interface Commands Status Line Popup Command Line Remove Temporary Message Command Line On/Off (toggles command line) Display Error Log display error_log Display Event Log display event_log Command Line Popup Command Line Position Cursor, Replace Mode <INSERT CHAR> key (when in insert mode) Position Cursor, Insert Mode <INSERT CHAR>...
Page 346 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 diagrams.
Page 347: Commands
Commands Emulator/analyzer Softkey 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 modify tags cmb_execute display pod_command name_of_module <command file>...
Page 348: Bbaunld
Emulator/Analyzer Interface Commands bbaunld bbaunld This command is available when the HP Branch Validator product is installed. This basis branch analyzer (BBA) product is used to analyze the testing of your programs, create more complete test suites, and quantify your level of testing.
Page 349: Break
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 350: Cmb_Execute
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 351: Copy
Emulator/Analyzer Interface Commands copy copy Use this command with various parameters to save or print emulation and analysis information. The copy command copies selected information to your system printer or listing file, or directs it to an UNIX process.
Page 352 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.
Page 353 Emulator/Analyzer Interface Commands copy printer This option specifies your system printer as the destination device for the copy command. Before you can specify the printer as the destination device, you must define PRINTER as a shell variable. For example, you could enter the text shown below after the "$"...
Page 354: Copy Local_Symbols_In
Emulator/Analyzer Interface Commands copy local_symbols_in copy local_symbols_in This command lets you copy local symbols contained in a source file and relative segments (program, data, or common) to the selected destination. Local symbols are symbols that are children of the particular file or symbol defined by --SYMB--, that is, they are defined in that file or scope.
Page 355: Copy Memory
Emulator/Analyzer Interface Commands copy memory copy memory This command copies the contents of a memory location or series of locations to the specified output. The memory contents are copied in the same format as specified in the last display memory command. Contents of memory can be displayed if program runs are not restricted to real-time.
Page 356 Emulator/Analyzer Interface Commands copy memory The parameters are as follows: --EXPR-- An expression is a combination of numeric values, symbols, operators, and parentheses, specifying a memory address or offset value. 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 357: Copy Registers
Emulator/Analyzer Interface Commands copy registers copy registers This command copies the contents of the processor registers to a file or printer. The copy register process does not occur in real-time. The emulation system must be configured for nonreal-time operation to list the registers while the processor is running.
Page 358: Copy Trace
Emulator/Analyzer Interface Commands copy trace copy trace This command copies the contents of the trace buffer to a file or to the printer. Trace information is copied in the same format as specified in the last display trace command. Initial values are the same as specified by the last display trace command. The parameters are as follows: from_line_number This specifies the trace list line number from which copying will begin.
Page 359: Display
Emulator/Analyzer Interface Commands display display This command displays selected information on your screen. 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 360 Emulator/Analyzer Interface Commands display local_symbols_in This option lets you display all the children of a given symbol. See the --SYMB-- syntax page and the Symbolic Retrieval Utilities User’s Guide for details on symbol hierarchy. memory This option allows you to display the contents of memory. pod_command This option lets you display the output of previously executed emulator pod commands.
Page 361: Display Configuration_Info
Emulator/Analyzer Interface Commands display configuration_info display configuration_info This command displays information about emulator configuration and processor SIM programming. You can also display diagnostic information about inconsistencies found in the emulator configuration.
Page 362 Emulator/Analyzer Interface Commands display configuration_info The parameters are as follows: diagnostics Checks all parts of the emulator configuration and reports any inconsistencies. It identifies errors that result from inconsistencies between related configuration values. These errors should be resolved in order for the emulator to operate correctly.
Page 363 Emulator/Analyzer Interface Commands display configuration_info Examples display configuration_info diagnostics display configuration_info memory_map See Also The sync_sim_registers and modify configuration commands. Also, see the "Verifying the Emulator Configuration" section in the "Configuring the Emulator" chapter.
Page 364: Display Data
Emulator/Analyzer Interface Commands display data display data This command can display the values of simple data types in your program. Using this command can save you time; otherwise, you would need to search through memory displays for the location and value of a particular variable. The address, identifier, and data value of each symbol may be displayed.
Page 365 Emulator/Analyzer Interface Commands display data Symbols are normally set off until you give the command set symbols on. Otherwise, only the address, data type, and value of the data item will be displayed. The parameters are as follows: A leading comma allows you to append additional expressions to the previous display data command.
Page 366 Emulator/Analyzer Interface Commands display data Examples display data Msg_A thru +17 char , Stack long set symbols on set width label 30 display data , Msg_B thru +17 char , Msg_Dest thru +17 char See Also The copy data and set commands.
Page 367: Display Global_Symbols
Emulator/Analyzer Interface Commands display global_symbols 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 368: Display Local_Symbols_In
Emulator/Analyzer Interface Commands display local_symbols_in display local_symbols_in This command displays the local symbols in a specified source file and their relative segment (program, data, or common). Local symbols of --SYMB-- are the ones which are children of the file and/or scope specified by --SYMB--.
Page 369: Display Memory
Emulator/Analyzer Interface Commands display memory display memory This command displays the contents of the specified memory location or series of locations. The memory contents can be displayed in mnemonic, hexadecimal, or real number format. In addition, the memory addresses can be listed offset by a...
Page 370 Emulator/Analyzer Interface Commands display memory 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. The memory mnemonic display autopages to the new address if the next PC goes outside the currently displayed address range.
Page 371 Emulator/Analyzer Interface Commands display memory mnemonic This causes the memory listing to be formatted in assembly language instruction mnemonics with associated operands. When specifying mnemonic format, you should include a starting address that corresponds to the first byte of an operand to ensure that the listed mnemonics are correct. If set source only is on, you will see only the high level language statements and corresponding line numbers.
Page 372 Emulator/Analyzer Interface Commands display memory Examples You can display memory in real number and mnemonic formats: display memory 2000h thru 202fh , 2100h real long display memory 400h mnemonic set symbols on set source on display memory main mnemonic See Also The copy memory, modify memory, set, and store memory commands.
Page 373: Display Registers
Emulator/Analyzer Interface Commands display registers display registers This command displays the current contents of the emulation processor registers. If a step command just executed, the mnemonic representation of the last instruction is also displayed, if the current display is the register display. This process does not occur in real-time.
Page 374: Display Simulated_Io
Emulator/Analyzer Interface Commands display simulated_io display simulated_io This command displays information written to the simulated I/O display buffer. After you have enabled polling for simulated I/O during the emulation configuration process, six simulated I/O addresses can be defined. You then define files used for standard input, standard output, and standard error.
Page 375 Emulator/Analyzer Interface Commands display software_breakpoints display software_breakpoints This command displays the currently defined software breakpoints and their status. 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.
Page 376: Display Trace
Emulator/Analyzer Interface Commands display trace display trace This command displays the contents of the trace buffer. 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.
Page 377 Emulator/Analyzer Interface Commands display trace 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. With an appropriate entry for offset, each instruction in the listed trace will appear as it does in the assembled or compiled program listing.
Page 378 Emulator/Analyzer Interface Commands display trace --EXPR-- An expression is a combination of numeric values, symbols, operators, and parentheses, specifying an offset value to be subtracted from the addresses traced by the emulation analyzer. See the EXPR syntax diagram. external binary Displays the external analyzer trace list in binary format.
Page 379 Emulator/Analyzer Interface Commands display trace status binary Lists absolute status information in binary form. Lists absolute status information in hexadecimal form. mnemonic Lists absolute status information in mnemonic form. Examples display trace count absolute display trace absolute status binary display trace mnemonic See Also The copy trace, store trace, and set commands.
Page 380: End
The emulation system is released for other users. If you do not release the emulation system when ending, others cannot access it. Examples end release_system See Also The "Exiting the Emulator/Analyzer Interface" section in the "Starting and Exiting HP 64700 Interfaces" chapter.
Page 381: Expr
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 382 Emulator/Analyzer Interface Commands --EXPR-- is only valid when "C" appears on the status line, which indicates a valid expression has been defined. <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>...
Page 383 Emulator/Analyzer Interface Commands --EXPR-- Note that when a thru softkey has been entered, a <+ EXPR> prompt appears. This saves you from tedious repeated entry of long symbols and expressions. For example: disp_buf thru +25 is the same as disp_buf thru disp_buf + 25 Examples 05fxh 0ffffh...
Page 384: Fcode
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. Data space. none Causes the emulator to ignore the function code bits. Program space. Supervisor space.
Page 385: Forward
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> An ASCII string, enclosed in quotes, that is the command to be forwarded to the named interface.
Page 386: Help
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 387 Emulator/Analyzer Interface Commands help 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 388: Load
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. The memory map specifies that the locations of the file are in user (target system) memory or emulation memory.
Page 389 Emulator/Analyzer Interface Commands load emul_mem Loads only those portions of the absolute file that reside in memory ranges mapped as emulation memory. FCODE Specifies the address space where the file will be loaded. fg_mon Loads a foreground monitor. <FILE> This represents the absolute file to be loaded into either target system memory, emulation memory (.X files are assumed), or the trace memory (.TR files are assumed).
Page 390: Log_Commands
Emulator/Analyzer Interface Commands log_commands log_commands This command allows you to record commands that are executed during an emulation session. Commands executed during an emulation session are stored in a file until this feature is turned off. This is a handy method for creating command files. To execute the saved commands after the file is closed, type the filename on the command line.
Page 391: Modify
Emulator/Analyzer Interface Commands modify modify This command allows you to observe or change information specific to the emulator. The modify command is used to: • Modify contents of memory (as integers, strings, or real numbers). • Modify the contents of the processor registers. •...
Page 392: Modify Configuration
Emulator/Analyzer Interface Commands modify configuration modify configuration This command allows you to view and edit the current emulation configuration items. The configuration questions are presented in sequence with either the default response, or the previously entered response. You can select the currently displayed response by pressing <RETURN>.
Page 393: Modify Keyboard_To_Simio
Emulator/Analyzer Interface Commands modify keyboard_to_simio modify keyboard_to_simio This command allows the keyboard to interact with your program through the simulated I/O software. When the keyboard is activated for simulated I/O, its normal interaction with emulation is disabled. The emulation softkeys are blank and the suspend softkey is displayed on your screen.
Page 394: Modify Memory
Emulator/Analyzer Interface Commands modify memory modify memory This command lets you modify the contents of selected memory locations. You can modify the contents of individual memory locations to individual values. Or, you can modify a range of memory to a single value or a sequence of values.
Page 395 Emulator/Analyzer Interface Commands modify memory A range of memory can be modified such that the content of each location in the range is changed to the single specified value, or to a single or repeated sequence. This type of memory modification is done by entering the limits of the memory range to be modified (--EXPR-- thru --EXPR--) and the value or list of values (--EXPR--, ...
Page 396 Emulator/Analyzer Interface Commands modify memory backspace carriage return form feed backslash single quote \’ bit pattern \ooo (where ooo is an octal number) thru This option lets you specify a range of memory locations to be modified. This lets you specify values to which the selected memory locations will be changed.
Page 397: Modify Register
Emulator/Analyzer Interface Commands modify register modify register This command allows you to modify the contents of the emulation processor internal registers. The entry you specify for <REGISTER> determines which register is modified. Individual fields of control registers may be modified. Register modification cannot be performed during real-time operation of the emulation processor.
Page 398: Modify Sim Registers
Emulator/Analyzer Interface Commands modify SIM registers modify SIM registers The 6833x SIM is configured through the registers in the SIM register class; these registers control how the 6833x uses external signal lines to access memory. The emulator’s DE-SIM module is configured through the registers in the EMSIM register class.
Page 399 Emulator/Analyzer Interface Commands modify SIM registers If desired, the programming of the DE-SIM can be transferred into the 6833x SIM with the sync_sim_registers to_6833x_from_config command. This happens automatically each time a break to the monitor from emulation reset occurs. This ensures that the 6833x is prepared to properly access memory when a program is downloaded to the emulator.
Page 400: Performance_Measurement_End
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 401 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.
Page 402 Emulator/Analyzer Interface Commands performance_measurement_initialize The parameters are as follows: activity This option causes the performance measurement process to operate as though an option is not specified. duration This option sets the measurement mode to "duration." Time ranges will default to a predetermined set (unless a user-defined file of time ranges is specified).
Page 403: Performance_Measurement_Run
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. The parameters are as follows: <COUNT>...
Page 404: Pod_Command
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 405 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> Prompts you for a Terminal Interface command as a quoted string. Enter the command in quotes and press <RETURN>.
Page 406: Qualifier
Emulator/Analyzer Interface Commands QUALIFIER QUALIFIER The QUALIFIER parameter is used with trace only, trace prestore, and TRIGGER to specify states captured during the trace measurement. You may specify a range of states (RANGE) or specific states (STATE) to be captured. You can continue to "or" states until the analyzer resources are depleted.
Page 407 Emulator/Analyzer Interface Commands QUALIFIER Examples trace only address mod_name:read_input trace only address range mod_name:read_input thru output trace only address range mod_name:clear thru read_input See Also The trace command.
Page 408: Range
Emulator/Analyzer Interface Commands RANGE RANGE The RANGE parameter allows you to specify a condition for the trace measurement, made up of one or more values. The range option can be used for state qualifier labels. Range can only be used once in a trace measurement. Refer to the "Qualifying Trigger and Store Conditions"...
Page 409 Emulator/Analyzer Interface Commands RANGE range This indicates a range of addresses to be specified (--EXPR-- thru --EXPR--). status The value following this softkey is searched for on the lines that monitor other emulation processor signals. thru This indicates that the following address expression is the upper address in a range.
Page 410: Reset
Emulator/Analyzer Interface Commands reset reset This command suspends target system operation and re-establishes 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 411: 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 412 Emulator/Analyzer Interface Commands The parameters are as follows: address Specifies an address for a temporary register breakpoint that will be programmed into one of the processor’s two breakpoint registers. Up to two addresses may be specified. --EXPR-- An expression is a combination of numeric values, symbols, operators, and parentheses, specifying a memory address.
Page 413: Sequencing
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 414 Emulator/Analyzer Interface Commands SEQUENCING occurs Selects the number of times a particular qualifier must be found before the analyzer proceeds to the next sequence term or the trigger term. This option is not available when trace windowing is in use. See the WINDOW syntax pages.
Page 415: Set
Emulator/Analyzer Interface Commands...
Page 416 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 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.
Page 417 Emulator/Analyzer Interface Commands langinfo In certain languages, you may have symbols with the same names but different types. For example, in IEEE695, you may have a file named main.c and a procedure named main. SRU would identify these as main(module) and main(procedure).
Page 418 Emulator/Analyzer Interface Commands <NUMSRC> This prompts you for the number of source lines to be displayed. Values in the range 1 through 50 may be entered. source This displays source lines of memory. memory This option prevents inclusion of source lines in the trace and memory mnemonic display lists.
Page 419 Emulator/Analyzer Interface Commands <VALUE> Specifies the logical value to which a particular UNIX environment variable is to be set. width This allows you to specify the width (in columns) of the source lines in the source 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.
Page 420: Specify
Emulator/Analyzer Interface Commands specify specify This command prepares a 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 421 Emulator/Analyzer Interface Commands specify 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. 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 422: State
Emulator/Analyzer Interface Commands STATE STATE This parameter lets you specify a trigger condition as a unique combination of address, data, status, and executed address values. The STATE option is part of the QUALIFIER parameter to the trace command, and allows you to specify a condition for the trace measurement. Refer to the "Qualifying Trigger and Store Conditions"...
Page 423 Emulator/Analyzer Interface Commands STATE The parameters are as follows: address This specifies that the expression following is an address value. This is the default, and is therefore not required on the command line when specifying an address expression. This lets you specify a combination of status and expression values when status is specified in the state specification.
Page 424: Step
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 425 Emulator/Analyzer Interface Commands step If the from address option (defined by --EXPR-- or transfer_address) is omitted, stepping begins at the next program counter address. The parameters are as follows: --EXPR-- An expression is a combination of numeric values, symbols, operators, and parentheses specifying a memory address.
Page 426: Stop_Trace
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 427: Store
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 428 Emulator/Analyzer Interface Commands store 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. trace This option causes the current trace data to be stored in the specified file with a .TR extension.
Page 429: Symb
Emulator/Analyzer Interface Commands --SYMB-- --SYMB--...
Page 430 Emulator/Analyzer Interface Commands --SYMB-- This parameter is a symbolic reference to an address, address range, file, or other value. Note that if no default file was defined by executing the command display local_symbols_in --SYMB--, or with the cws command, a source file name (<FILE>) must be specified with each local symbol in a command line.
Page 431 Emulator/Analyzer Interface Commands --SYMB-- The parameters are as follows: <FILENAME> This is an UNIX path specifying a source file. If no file is specified, and the identifier referenced is not a global symbol in the executable file that was loaded, then the default file is assumed (the last absolute file specified by a display local_symbols_in command).
Page 432 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 433 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 434 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 Notice how you can reference different variables with matching identifiers by specifying the complete scope.
Page 435 Emulator/Analyzer Interface Commands --SYMB-- If a symbol search with the current working symbol prefix is unsuccessful, the last scope on the current working symbol is stripped. The symbol you specified is then retested with the modified current working symbol. Note that this does not change the actual current working symbol.
Page 436: Sync_Sim_Registers
Emulator/Analyzer Interface Commands sync_sim_registers sync_sim_registers This command synchronizes the 6833x’s system integration module (SIM) registers to the emulator’s EMSIM registers. The parameters are as follows: from_6833x Copies the microprocessor’s SIM registers into the emulator’s EMSIM _to_config registers. to_6833x Copies the emulator’s EMSIM registers into the microprocessor’s SIM _from_config registers.
Page 437: Trace
Emulator/Analyzer Interface Commands trace trace This command allows you to trace program execution using the emulation analyzer. Note that the options shown can be executed once for each trace command. Refer to the TRIGGER and QUALIFIER diagrams for details on setting up a trace.
Page 438 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 439 Emulator/Analyzer Interface Commands trace selectively saved by using trace only to enter the specific events to be saved. When this is used, only the indicated states are stored in the trace memory. See the QUALIFIER syntax. repetitively This initiates a new trace after the results of the previous trace are displayed. The trace will continue until a stop_trace or a new trace command is issued.
Page 440: Trigger
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 441 Emulator/Analyzer Interface Commands TRIGGER Examples trace after MAIN trace after 1000H then data 5 See Also The trace command and examples. Also, refer to the "Making Coordinated Measurements" chapter.
Page 442: Wait
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 443 Emulator/Analyzer Interface Commands wait Note that a wait command in a command file will cause execution of the command file to pause until a <CTRL>c signal is received, if <CTRL>c is defined as the interrupt signal. Subsequent commands in the command file will not execute while the command file is paused.
Page 444: Window
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 446: Error Messages
Error Messages...
Page 447 Error Messages This chapter alphabetically lists and describes the error messages displayed on the interface status line and in the error log. 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 448 Error Messages <LOGICAL NAME>: End, released Cause: This is a status message. The emulation session is being exited with the end release_system command. When the session has ended, the emulator is released, meaning that others can access and use it. When you restart the emulation session later, the new session will use all default settings.
Page 449 Error Messages Analyzer Break (613) Cause: Status message. Analyzer limitation; all range resources in use Analyzer limitation; all pattern resources in use Analyzer limitation; all expression resources in use (10360) Cause: Your trace specification would use more than the maximum number of resources available to the analyzer.
Page 450 Error Messages Break failed (602) Cause: The break command was unable to break the emulator to the monitor. Action: Determine why the break failed, then correct the condition and retry the command. See message 608. Breakpoint code already exists: %s (667) Cause: You attempted to insert a breakpoint;...
Page 451 Action: Ignore this message unless it becomes frequent. If it becomes frequent, you may have a fatal error; call your HP 64700 representative. Cannot lock emulator; failure in obtaining the accessid Cannot lock emulator; failure in <ERRNO MSG>...
Page 452 Error Messages Cannot start. Ending previous session, try again Cause: The host system could not start a new emulation session, and is ending the previous session. Action: After the previous session has ended, try starting a new emulation session. If that fails, try "emul700 -u <logical name>" to unlock the emulator and cycle power, if needed.
Page 453 Error Messages CMB execute; run started (693) Cause: This status message is displayed when you are making coordinated measurements. The CMB /EXECUTE pulse has been received; the emulation processor started running at the address specified by the specify run command. Action: None;...
Page 454 Continue load failed 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.
Page 455 (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. Count out of bounds: %s (318) Cause: You specified an occurrence count less than 1 or greater than 65535.
Page 456 Error Messages CS%s is configured for fast termination; max clock is 8 MHz (171) Cause: This is a status message output by the display configuration_info diagnostics command. Whenever chip selects are programmed for fast termination (-1 wait state) and are used to select emulation memory, the operating clock rate must be limited.
Page 457 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 458 Emul700dmn queue failure Emul700dmn error in file operation Emul700dmn queue full Cause: The HP 64700 emulator daemon process command was too large for the host system to process. 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 459 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. Action: Make sure the software has been properly installed. Then try starting the emulator again.
Page 460 Error in configuration process Error starting configuration process Cause: Unexpected configuration error. Action: Verify proper software installation and call your HP 64000 representative. Exceeded maximum 64700 command line length (10351) Cause: Your command is longer than 240 characters.
Page 461 Action: Write down the sequence of commands which caused the error. Cycle power on the emulator and re-enter the commands. If the error repeats, call your local HP Sales and Service office for assistance. File could not be opened Cause: You tried to store or load trace data to a file with incorrect permission.
Page 462 If you are unsuccessful, make sure that the data communications parameters are set correctly on the host and on the HP 64700, then retry the operation. Guarded memory access break (614) Cause: This message is displayed if the emulation processor attempts to read or write memory mapped as guarded.
Page 463 Error Messages 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. HP64700 I/O channel busy; communications timed out Cause: The communications channel is in use for an unusually long period of time by another command.
Page 464 Incompatible compatibility table entry (206) Cause: The emulation firmware (ROM) is not compatible with the analysis or system firmware in your HP 64700 system. Action: The ROMs in your emulator must be compatible with each other for your emulation system to work correctly. Contact your Hewlett-Packard Representative.
Page 465 Invalid address: %s (146) Cause: You specified an invalid address value as an argument to one of the HP 64782 specific commands. For example, you may have specified digits that don’t correspond to the base specified, or you forgot to precede a hexadecimal letter digit with a number (even zero (0)).
Page 466 Error Messages Invalid analysis subsystem; product address: %s (902) Cause: This error occurs when the HP 64700 system controller determines that the analysis firmware (ROM) is invalid. Action: This message is not likely to occur unless you have upgraded the ROMs in your emulator.
Page 467 Error Messages Invalid option or operand: %s (148) Cause: You have specified incorrect option(s) to a command. %s, if printed, indicates the incorrect option(s). Action: Re-enter the command with the correct syntax. Refer to the on-line help information. Invalid trigger duration: <duration> (2031) Cause: This error occurs when you attempt to specify an external timing trigger duration which is in the valid range but is not a multiple of 10 ns.
Page 468 Error Messages Joining session already in progress, continue file loaded Cause: This is a status message. When operating the emulator in multiple windows, a new emulation session is "joined" to a current session. In this case, the new session was able to continue because the continue file loaded properly.
Page 469 Error Messages Load completed with errors Cause: While loading a file into the emulator, one or more events occurred that caused errors during the load process. Action: Use the display error_log command to view any errors. You may need to modify the configuration and map memory before you load the file again. If the problem persists, make sure the host system and emulator are operating properly, and that you are trying to load an acceptable file.
Page 470 Message overflow (151) Cause: The display configuration_info diagnostics command may emit more messages than the HP 64700 will allow (16). This status message occurs when there are more than 16 messages. Need %s or chip select for map entry #%d (174) Cause: This error message is a result of the display configuration_info diagnostics command.
Page 471 Error Messages Negated patterns not allowed in timing (2030) Cause: This error occurs when you attempt to specify a "not equals" expression when defining the external timing trigger. You can only specify labels which equal patterns (of 1’s, 0’s, or X’s). Action: Do not attempt to specify negated timing patterns.
Page 472 Normal emulation mode not allowed with HP 64782A (155) Cause: The HP 64782A emulator, which supports only ACT mode, does not allow you to configure the emulator for the Normal mode. Not a valid trace file - load aborted Cause: You tried to load a file.TR that was not created by the emulation...
Page 473 Error Messages Number of chip select function codes limited to 4 (166) Cause: This status message occurs when you specify more than 4 chip select function codes when mapping an address range. Only the first 4 chip selects will be allowed. Number of lines not in range: 1 <= valid lines <= 50 Cause: You tried to enter a number of lines that was outside the range from 1 to 50.
Page 474 Error Messages Perfinit - error in input file line <NUMBER> Cause: You included an input file name with your "performance_measurement_initialize" command, and that file contains a syntax error. Action: Edit the file and correct the syntax error. Perfinit - File could not be opened Cause: You specified a file as an option to "performance_measurement_initialize", and the file you specified could not be found or opened by SPMT software.
Page 475 Error Messages Period not in 1/2/5 sequence: <period> (2021) Cause: This error message occurs when the external timing sample period is not in a 1/2/5 sequence; for example, 10ns, 20ns, 50ns, 100ns, 200ns, 500ns, 1us, 2us, 5us, etc. Some examples of invalid sample period specifications are: 12ns, 18ns, 25ns, 60ns, 80ns, etc.
Page 476 HP 64700. Action: Retry the transfer operation. If the failure is repeated, make sure that both your host and the HP 64700 data communications parameters are configured correctly. Records expected: %s; records received: %s (401) Cause: The HP 64700 received a different number of records than it expected to receive during a transfer operation.
Page 477 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 478 Action: Retry the transfer. If it fails again, make sure that the data communications parameters are set correctly on the host and on the HP 64700. Also make sure that you are using the correct command options, both on the HP 64700 and on the host.
Page 479 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 480 Error Messages Step count must be 1 through 999 Cause: You tried to use a step count greater than 999. Action: Use a step count less than 1000. Step display failed (688) Cause: System failure or target condition. Action: Check memory mapping and configuration questions. Stepping aborted;...
Page 481 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; then start a new session. Make sure the host system is operating...
Page 482 Error Messages Trace error during CMB execute (692) Cause: System failure. Action: Run performance verification (Terminal Interface pv command). Trace file not found Cause: You tried to load trace data file that does not exist. Action: Find the correct name and path of the trace data file and try again. Transfer failed to start (413) Cause: Communication link or transfer protocol incorrect.
Page 483 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 re-enter the command. If the same failure occurs, call your HP sales and service office.
Page 484 Error Messages Unable to delete label; used by emulation analyzer: <label> (1105) 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. Action: You stop the trace or must change the trace command before you can delete the label.
Page 485 Error Messages Unable to redefine label; used by emulation analyzer: <label> (1108) Cause: This error occurs when you attempt to redefine an emulation trace label which is currently used as a qualifier in the emulation trace specification. Action: You stop the trace or must change the trace command before you can redefine the label.
Page 486 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 487 Error Messages Unknown expression type Cause: While entering your command, you included an unknown expression type. Action: See the EXPR command syntax for more information about expressions. Then try entering your command again with a known expression type. Unload trace data failed Cause: An unexpected error occurred while waiting for a trace to be completed.
Page 488 Error Messages Write to ROM break (612) 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. Action: None (except troubleshooting your program).
Page 490 Part 4 Concept Guide...
Page 491 Part 4 Topics that explain concepts and apply them to advanced tasks.
Page 492 Concepts...
Page 493 Concepts This chapter provides conceptual information on the following topics: • X resources and the Graphical User Interface. • Concepts of the EMSIM and EMRAM...
Page 494 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: • Describes the X Window concepts surrounding resource specification. •...
Page 495 Concepts 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". To set the background color for a hypothetical "Done"...
Page 496 Concepts 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: HP64_Softkey*<resource>: <value>...
Page 497 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 498 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. HP64_Softkey.colorScheme: Names the color scheme file.
Page 499 Concepts 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. The actual scheme file names take the form: "Softkey.<value>".
Page 500 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 specifications.
Page 501 Concepts of the EMSIM and EMRAM The 6833x processors provide an array of on-chip peripherals which are configured and used via memory mapped registers. These registers directly control many aspects of the external operation of the processor. The most notable of these on-chip peripherals is the SIM (System Integration Module). For example, address bits A19 through A23 can be configured as either address bits, chip select control signals, or discrete output port signals.
Page 502 Concepts The emulator has been designed to ensure that the emulation-bus analyzer and the emulation memory system will have access to the equivalent of the internal processor 24-bit address bus, function codes, and size information. The external bus decoder circuitry can recreate these signals for all possible combinations of processor pin usage that make sense to the target system.
Page 503 Concepts automatically; the user can manually transfer the EMSIM to the SIM or the SIM to the EMSIM or display their differences at any time. Concepts of the EMRAM Most members of the 6833x family of processors have one or more internal RAM modules.
Page 504 Concepts Concepts of Show Cycles Typically when the processor accesses internal resources (either the Module Control Block, or internal RAM) the bus cycles are not available external to the processor. These bus cycles can be made available by enabling a feature of the 6833x processor called show cycles.
Page 505 Concepts EMSIM/EMRAM Utility Command Modify→SIM Registers This capability lets the user compare and transfer register values between the SIM and EMSIM register sets. Note even though the word "sim" is used in the command, all operations also include the RAM and EMRAM register sets. Modify→SIM Registers→Copy Emulator SIM to Processor SIM This transfers the current values of the EMSIM registers into the SIM registers.
Page 506 Concepts Display→Configuration Info→Chip Selects (Emulator SIM) This displays chip selects in the EMSIM (emulator) register set in a table. Use this to see how the EMSIM registers have configured the chip select pins of the emulation copy. Display→Configuration Info→Bus Interface Ports (SIM) This displays bus interface ports in the SIM (processor) register set in a table.
Page 508 Part 5 Installation Guide...
Page 509 Part 5 Instructions for installing and configuring the product.
Page 510 Installation...
Page 511 These installation tasks are described in the following sections: • Where to find information on connecting the HP 64700 to a computer or LAN. • Installing HP 9000 software.
Page 512 Installation 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 (SunOS or Solaris) workstations. SunOS The Graphical User Interface software is designed to run on a Sun SPARCsystem with SunOS version 4.1 or 4.1.1 or greater, and Solaris version 2.3.
Page 513 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...
Page 514 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 515 /etc/update at the HP-UX prompt. 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 516 /users/team, you would enter ln -s /users/team/usr/hp64000 /usr/hp64000 If you installed the HP 64000 software relative to the root directory, "/", or established a symbolic link to /usr/hp64000, then you would enter HP64000=/usr/hp64000; export HP64000...
Page 517 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 4a of these instructions. If you plan to run HP VUE, skip to Step 4b of these instructions.
Page 518 Step 4b. 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 519 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.
Page 520 Installation Step 2. Start the X server and OpenWindows 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 521 -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; also set the LD_LIBRARY_PATH variable to the directory containing run-time libraries used by the HP 64000 products.
Page 522 Installation Step 4. Verify the software installation Step 4. Verify the software installation A number of product filesets were installed on your system during the software installation process. Due to the complexity of installing on NFS mounted file systems, a script that verifies and customizes these products was also installed.
Page 523 Installation Step 5. Map your function keys Add the following to your .profile or .login file: stty erase ^H setenv KEYMAP sun The erase character needs to be set to backspace so that the Delete key can be used for "delete character." If you want to continue using the F1 key for HELP, you can use use F2-F9 for the Softkey Interface.
Page 524 64700tab.net file is placed in the directory as part of the installation process. Display the 64700tab.net file by entering more /usr/hp64700/etc/64700tab.net at the HP-UX prompt. 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 525 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 526 Installation Step 3. Exit the Graphical User Interface Example Suppose you have discovered that the logical name for a 6833x emulator connected to the LAN is "em6833x". To start the Graphical User Interface and begin communicating with that emulator, enter (assuming your $PATH includes $HP64000/bin) emul700 em6833x After a few seconds, the Graphical User Interface Emulator/Analyzer window...
Page 528 Installing/Updating Emulator Firmware...
Page 529 The floppies are for users that do not have hosted interface software.) Before you can update emulator firmware, you must have already installed the emulator into the HP 64700, connected the HP 64700 to a host computer or LAN, and installed the emulator/analyzer interface and HP B1471 software as described in the "Installation"...
Page 530 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 531 2 em80960 i80960 3 em6833x m6833x Number of Emulator to Update? (intr (usually cntl C or DEL) to abort) To update firmware in the HP 64700 that contains the 6833x emulator, enter "3". Product 1 64700 2 64703/64704/64706/64740 3 64744...
Page 532 Installing/Updating Emulator Firmware To update emulator firmware with "progflash" To update the HP 64782 6833x emulator firmware, enter "4". Enable progress messages? [y/n] (y) To enable status messages, enter "y". Checking System firmware revision... Mainframe is a 64700B Reading configuration from ’/usr/hp64000/inst/update/64782.cfg’...
Page 533 System RAM:1 Mbyte HP64782C Motorola 68332 Emulator Version: A.03.00 Control: HP 64748C Emulation Control Board Speed: 20.1 MHz Memory: 1024 Kbytes BANK 0: HP 64171B (35 ns) or HP 64172B (20 ns) 1 MByte Memory Module HP64740 Emulation Analyzer Version: A.02.02 13Mar91...
Page 534 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 with the HP 64700 connected to an RS-232 or...
Page 536 Glossary Specifies the types of cycles used to access target system memory locations. access mode For example a "byte" access mode tells the monitor program to use load/store byte instructions to access target memory. An instrument that captures data on signals of interest at discreet periods. analyzer The emulator mode in which foreground operation is suspended so the background...
Page 537 Individual levels of the sequencer. The HP 64705A analyzer provides 8 sequence terms sequence terms. The part of the analyzer that allows it to search for a certain sequence of sequencer states before triggering.
Page 538 Glossary Occurs when the analyzer finds the primary or secondary branch state sequencer specified at a certain level and begins searching for the states specified at branch another level. The microprocessor system which the emulator plugs into. target system A collection of states captured on the emulation bus (in terms of the trace emulation bus analyzer) or on the analyzer trace signals (in terms of the external analyzer) and stored in trace memory.
Page 540 25 copying to a file, 188 analyzer, 535 Command Recall dialog box, 26 disabling execution breakpoints, 163 arming other HP 64700 Series analyzers, Command Recall dialog box, operation, displaying and seeing their status, 168-169 breaking emulator execution into the...
Page 541 Index recalling commands with dialog box, 80 copy command, 350-352 adding items to the existing display, turning on or off, 77, 325 configuration info, 351 command paste mouse button, 27 data, 351 clearing the display and adding a new item, Command Recall dialog box operation, 73 display, 351 command select mouse button, 27...
Page 542 Index registers, 170, 372 number of intervals, 280 modifying a configuration section, 98 simulated_io, 190, 192, 373 recursion considerations, 275 restrict to real-time runs, 105-106 software_breakpoints, 374 selecting, 278-279 starting the configuration interface, status, 359 standard deviation, 281 96-97 symbols, 143 trace command setup, 276-277 storing, 100 trace, 197-200, 375-378...
Page 543 117 configuration, 294 need for separately linked modules, HP 98659 RS-422 Interface Card, 5 general description, 4 HP-UX, minimum version, 510 labels, 296, 301 functions, step over, 173 HP64KPATH, UNIX environment variable,...
Page 544 LD_LIBRARY_PATH environment variable, block size, 109 multiple commands, 82 function code specification, 117-119 multiple emulator start/stop, 5 libraries, Motif for HP 9000/700, 510 overlaid addresses, 117 line numbers (source file), symbol display, using emulation memory in place of target, 118...
Page 545 407 how to set, 164 RANGE, in trace command, 407-408 platform READY, CMB signal, 305 HP 9000 memory needs, 510 scheme files (for X resources), 323, 497 real-time runs, 536 HP 9000 minimum performance, 510 color scheme, 324, 328, 498...
Page 546 518 --SYMB-- syntax, 428-434 softkeys, 82 minimum system requirements overview, symbol context software changing, 153 installation for HP 9000, 513 SunOS minimum version, 511 displaying, 152 installation for SPARCsystems, 518 specify command, 419-420 symbol file, loading, 143 software breakpoints...
Page 547 Index SPARCsystem overview, 511 starting, 196 store command, 427 SunOS minimum version, 511 stopping, 197 tracing background operation, 121 store command, 427 tram, memory characterization, 111 storing data, 251 transfer address, 155 Trace Specification Selection dialog box, trigger, 537 target memory condition, 209-210 loading absolute files, 140 trigger position, 209-210...
Page 548 Index workstation HP 9000 memory needs, 510 HP 9000 minimum performance, 510 SPARCsystem memory needs, 511 SPARCsystem minimum performance, write to ROM break, 120 X client, 322 X resource, 322 $XAPPLRESDIR directory, 496 $XENVIRONMENT variable, 497 .Xdefaults file, 496 /usr/hp64000/lib/X11/HP64_schemes,...
Page 550 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 551 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 552 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 553 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.
Page 554 HP. For products returned to HP for warranty service, Buyer shall prepay shipping charges to HP and HP shall pay shipping charges to return the product to Buyer. However, Buyer shall pay all shipping charges, duties, and taxes for products returned to HP from another country.

HP 64782 User Manual

Part 1 Quick Start Guide

1 Getting Started

Part 2 User's Guide

2 Plugging into a Target System

3 Starting and Exiting HP 64700 Interfaces

5 Configuring the Emulator

6 Using the Emulator

7 Using the Emulation Analyzer

8 Making Software Performance Measurements

9 Using the External State Analyzer

10 Making Coordinated Measurements

11 Setting X Resources

Part 3 Reference

12 Emulator/Analyzer Interface Commands

Quick Links

Related Manuals for HP 64782

Summary of Contents for HP 64782