Page 1 Graphical User Interface User’s Guide MC68360/68EN360 Emulator/Analyzer (HP 64780A)
Page 2 Notice Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Page 3 Printing History New editions are complete revisions of the manual. Many product updates and fixes do not require manual changes, and manual corrections may be done without accompanying product changes. Therefore, do not expect a one-to-one correspondence between product updates and manual revisions. Edition 1 B3091-97000, December 1993 Edition 2...
Page 4 The emulator plugs into the modular HP 64700 instrumentation card cage and offers 80 channels of processor bus analysis with the HP 64794A or HP 64704A emulation-bus analyzer. Up to eight megabytes of emulation memory may be installed on the probe. High performance download is achieved through the use of an optional LAN or RS-422 interface.
Page 5 Background and foreground monitors • Simulated I/O with workstation interfaces • Consumes IEEE-695, HP-OMF, Motorola S-Records, and Extended Tek Hex File formats directly. (Symbols are available with IEEE-695 and HP-OMF formats.) • Multiprocessor emulation – synchronous start of 32 emulation sessions –...
Page 6 In This Book This manual shows you how to use the HP 64780A emulator through its Graphical User Interface for the MC68360 microprocessor. It is divided into the following parts: Part 1 contains the Quick Start Guide. It shows you how to quickly become productive with the emulation system.
Page 7: Table Of Contents
Contents Part 1 Quick Start Guide 1 Getting Started The Emulator/Analyzer Interface — At a Glance The Softkey Interface Softkey Interface Conventions The Graphical User Interface Graphical User Interface Conventions The Getting Started Tutorial Step 1. Start the demo Step 2: Display the program in memory Step 3: Run from the transfer address Step 4: Step high-level source lines Step 5: Display the previous mnemonic display...
Page 8 Step 3. Turn ON power Plugging into the Motorola QUADS Target System To connect the emulator to the Motorola QUADS 3 Starting and Exiting HP 64700 Interfaces Starting the Emulator/Analyzer Interface To start the emulator/analyzer interface To start the interface using the default configuration...
Page 9 To playback (execute) a command file Using Pod Commands To display the pod commands screen To use pod commands Forwarding Commands to Other HP 64700 Interfaces To forward commands to the high level debugger To forward commands to the software performance analyzer...
Page 10 Contents 5 Configuring the Emulator Using the Configuration Interface To start the configuration interface To modify a configuration section To apply configuration changes to the emulator If apply to emulator fails To store configuration changes to a file To change the configuration directory context To display the configuration context To access help topics To access help for a configuration item in a dialog box...
Page 11 Contents Using Symbols To load symbols To display global symbols To display local symbols To display a symbol’s parent symbol To copy-and-paste a full symbol name to the entry buffer Using Context Commands To display the current directory and symbol context To change the directory context To change the current working symbol context Executing User Programs...
Page 12 Contents Displaying and Modifying Memory To display memory To display memory in mnemonic format To return to the previous mnemonic display To display memory in hexadecimal format To display memory at an address To display memory repetitively To modify memory Displaying Data Values To display data values To clear the data values display and add a new item...
Page 13 Contents Using Basis Branch Analysis To store BBA data to a file 7 Using the Emulation-Bus Analyzer Power of the Emulation-Bus Analyzer Making Simple Trace Measurements To start a trace measurement To stop a trace measurement To display the trace list To display the trace status To change the trace depth To modify the last trace command entered...
Page 14 Contents Making Complex Trace Measurements To use address, data, and status values in trace expressions To enter a range in a trace expression To use the sequencer To specify a restart term To specify trace windowing To specify both sequencing and windowing To count states or time To define a storage qualifier To define a prestore qualifier...
Page 15 Contents 9 Making Coordinated Measurements Setting Up for Coordinated Measurements To connect the Coordinated Measurement Bus (CMB) To connect to the rear panel BNC Starting/Stopping Multiple Emulators To enable synchronous measurements To start synchronous measurements To disable synchronous measurements Using Trigger Signals To drive the emulation analyzer trigger signal to the CMB To drive the emulation analyzer trigger signal to the BNC connector To break emulator execution on signal from CMB...
Page 16 Contents Part 3 Reference 10 Setting X Resources To modify Graphical User Interface resources To use customized scheme files To set up custom action keys To set initial recall buffer values To set up demos or tutorials 11 Emulator/Analyzer Interface Commands How Pulldown Menus Map to the Command Line How Pop-up Menus Map to the Command Line Syntax Conventions...
Page 17 Contents log_commands modify modify configuration modify keyboard_to_simio modify memory modify register modify software_breakpoints performance_measurement_end performance_measurement_initialize performance_measurement_run pod_command QUALIFIER RANGE reset SEQUENCING specify STATE step stop_trace store --SYMB-- sync_sim_registers trace TRIGGER wait WINDOW 12 Emulator Error Messages Emulator error messages xvii...
Page 18 Contents Part 4 Concept Guide 13 Concepts of the EMSIM and EMRAM Concepts of the EMSIM and EMRAM Concepts of the EMRAM Concepts of Show Cycles EMSIM/EMRAM Utility Command xviii...
Page 19 Contents Part 5 Installation and Service Guide 14 Installation Connecting the HP 64700 to a Computer or LAN Installing HP 9000 Software Step 1. Install the software from the media Step 2. Verify the software installation Step 3a. Start the X server and the Motif Window Manager (mwm) Step 3b.
Page 21: Part 1 Quick Start Guide
Part 1 Quick Start Guide...
Page 22 Part 1 Quick Start Guide In This Part This part describes how to quickly become productive with the emulation system.
Page 23: Getting Started
Getting Started...
Page 24: The Emulator/Analyzer Interface - At A Glance
Chapter 1: Getting Started The Emulator/Analyzer Interface — At a Glance When an X Window System that supports OSF/Motif interfaces is running on the host computer, the emulator/analyzer interface is the Graphical User Interface which provides pull-down and pop-up menus, point and click setting of breakpoints, cut and paste, on-line help, customizable action keys and pop-up recall buffers, etc.
Page 25: Softkey Interface Conventions
Chapter 1: Getting Started Status line. Displays the emulator and analyzer status. Also, when error and status messages occur, they are displayed on the status line in addition to being saved in the error log. Command line. Commands are entered on the command line by pressing softkeys (or by typing them in) and executed by pressing the Return key.
Page 26: The Graphical User Interface
Chapter 1: Getting Started The Graphical User Interface Menu bar Action keys Entry buffer Entry buffer recall button. Display area. Scroll bar. Status line. Command line. Command line entry area. Softkey pushbuttons Command buttons. Includes command Cursor buttons for command line area recall button.
Page 27 Chapter 1: Getting Started Entry Buffer. Wherever you see "()" in a pulldown menu, the contents of the entry buffer are used in that command. You can type values into the entry buffer, or you can cut and paste values into the entry buffer from the display area or from the command line entry area.
Page 28: Graphical User Interface Conventions
Chapter 1: Getting Started The command Recall button allows you to recall previous or predefined commands. When you click on the command Recall button, a dialog box appears that allows you to select a command. • Cursor buttons for command line area control. Allow you to move the cursor in the command line entry area forward or backward, clear to the end of the command line, or clear the whole command line entry area.
Page 29 Mouse Button Bindings and Description Bindings: Generic Button Name Description HP 9000 SPARCsystem paste left left Paste from the display area to the entry buffer. command paste middle...
Page 30 Chapter 1: Getting Started The following tables show the default keyboard bindings. Keyboard Key Bindings Generic Key Name HP 9000 Sun SPARCsystem menu select extend char extend char insert insert char insert char delete delete char delete char left-arrow left arrow...
Page 31: The Getting Started Tutorial
• The HP 64780 emulator and 80-channel 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 Chapter 14, "Installation."...
Page 32: Step 1. Start The Demo
"platformScheme" resource setting in the "Xdefaults.emul" file. For example, if the Graphical User Interface will be run on a HP 9000 computer and displayed on a Sun SPARCsystem computer, change the platform scheme to "SunOS".
Page 33: Step 2: Display The Program In Memory
Chapter 1: Getting Started Step 2: Display the program in memory Step 2: Display the program in memory 1 If the symbol "main" is not already in the entry buffer, move the mouse pointer to the entry buffer (notice the flashing I-beam cursor) and type in "main". 2 Choose Display→Memory→Mnemonic ().
Page 34: Step 3: Run From The Transfer Address
Chapter 1: Getting Started Step 3: Run from the transfer address Step 3: Run from the transfer address The transfer address is the entry address defined by the software development tools and included with the program’s symbol information. • Click on the Run Xfer til () action key. Or, using the command line, enter: run from transfer_address until main <RETURN>...
Page 35: Step 4: Step High-Level Source Lines
Chapter 1: Getting Started Step 4: Step high-level source lines Step 4: Step high-level source lines You can step through the program by high-level source lines. The emulator executes as many instructions as are associated with the high-level program source lines.
Page 36: Step 5: Display The Previous Mnemonic Display
Chapter 1: Getting Started Step 5: Display the previous mnemonic display Step 5: Display the previous mnemonic display • Click on the Disp Src Prev action key. Or, using the command line, enter: display memory mnemonic previous_display <RETURN> This command is useful, for example, when you have stepped into a function that you do not wish to look at—you can display the previous mnemonic display and run until the source line that follows the function call.
Page 37: Step 6: Run Until An Address
Chapter 1: Getting Started Step 6: Run until an address Step 6: Run until an address When displaying memory in mnemonic format, a selection in the pop-up menu lets you run from the current program counter address until a specific source line. •...
Page 38: Step 7: Display Data Values
Chapter 1: Getting Started Step 7: Display data values Step 7: Display data values 1 Position the mouse pointer over "num_checks" in the source line that reads "num_checks++;" and click the paste mouse button (notice "num_checks" is cut and pasted into the entry buffer). 2 Click on the Disp Var () action key.
Page 39: Step 8: Display Registers
Chapter 1: Getting Started Step 8: Display registers Step 8: Display registers You can display the contents of the processor registers. • Choose Display→Registers→BASIC. Or, using the command line, enter: display registers <RETURN>...
Page 40: Step 9: Step Assembly Level Instructions
Chapter 1: Getting Started Step 9: Step assembly-level instructions Step 9: Step assembly-level instructions You can step through the program one instruction at a time. • To step one instruction from the current program counter, click on the Step Asm action key.
Page 41: Step 10: Trace The Program
Chapter 1: Getting Started Step 10: Trace the program Step 10: Trace the program When the analyzer traces program execution, it looks at the data on the emulation processor’s bus and control signals at each clock cycle. The information seen at a particular clock cycle is called a state.
Page 42 Chapter 1: Getting Started Step 10: Trace the program 5 To view the captured states, choose Display→Trace. Or, using the command line, enter: display trace <RETURN> The default display mode settings cause source lines and symbols to appear in the trace list.
Page 43: Step 11: Display Memory At An Address In A Register
Chapter 1: Getting Started Step 11: Display memory at an address in a register Step 11: Display memory at an address in a register 1 Click on the Disp @REG action key. Or, using the command line, enter the name of the command file: mematreg <RETURN>...
Page 44: Step 12: Exit The Emulator/Analyzer Interface
• To exit the emulator/analyzer interface and release the emulator, choose File→Exit→Released. Or, using the command line, enter: end release_system <RETURN> Solving Problems If you encounter problems when using the emulator/analyzer, refer to the chapter titled "Solving Problems" in the MC68360 Emulator/Analyzer Installation/Service/Terminal Interface Manual.
Page 45: Part 2 Using The Emulator
Part 2 Using The Emulator...
Page 46: Making Measurements
Chapter 2, "Plugging into a Target System," tells you how to correctly connect the emulation probe into a target system. Chapter 3, "Starting and exiting HP 64700 Interfaces," tells you how to get the desired interface on screen. Chapter 4, “Entering Commands,” tells you how to use the commands and features of the Graphical User Interface and Softkey Interface.
Page 47: Plugging Into A Target System
Plugging into a Target System...
Page 48 Plugging into the Motorola QUADS target system. Before attempting to run the emulator, ensure that you have selected the proper clock module and installed it in the emulator probe. The details of clock module selection are discussed in the MC68360 Emulator/Analyzer (HP 64789A) Installation/Service/Terminal Interface manual.
Page 49: Connecting The Emulator To The Target System
Chapter 2: Plugging into a Target System Connecting the Emulator to the Target System Connecting the Emulator to the Target System The 68360 emulator probe plugs into a PGA through-hole socket that is soldered into the target system. There are three ways of connecting the 68360 emulator probe to a target system: •...
Page 50: Step 1. Turn Off Power
HP 64700 power is OFF before removing or installing the emulator probe into the target system. Do not turn HP 64700 power OFF while the emulator is plugged into a target system whose power is ON. 1 If the emulator is currently plugged into a different target system, turn that target system’s power OFF.
Page 51: Step 2. Connect The Probe To The Target System
Chapter 2: Plugging into a Target System Connecting the Emulator to the Target System Step 2. Connect the probe to the target system CAUTION Possible Damage to the Emulator Probe. A pin extender is included with the emulator probe. Do not use the probe without a pin extender installed. Replacing a broken pin extender is much less expensive than replacing other pieces.
Page 52: Step 3. Turn On Power
Chapter 2: Plugging into a Target System Connecting the Emulator to the Target System Step 3. Turn ON power 1 Turn emulator power ON. 2 Turn target system power ON.
Page 53: Plugging Into The Motorola Quads Target System
Chapter 2: Plugging into a Target System Plugging into the Motorola QUADS Target System Plugging into the Motorola QUADS Target System This section shows you how to: • Connect the emulator to the Motorola QUADS board. The Motorola QUADS board gives you an opportunity to plug the emulator into a target system that contains one 68360 master chip, and one 68360 slave chip.
Page 54: To Connect The Emulator To The Motorola Quads
Ensure that the default clock module is plugged in. The default clock module must be installed in the emulator probe in order for the 68360 emulator to work with the Quads board. Refer to the Hewlett-Packard MC68360 Emulator/Analyzer Installation/Service/Terminal Interface User’s Guide for details.
Page 55 Chapter 2: Plugging into a Target System Plugging into the Motorola QUADS Target System...
Page 56 Chapter 2: Plugging into a Target System Plugging into the Motorola QUADS Target System 3 Turn ON power. First turn on the emulator power. Then turn target system power 4 You will need to select three configuration items for the emulator. With the Graphical User Interface on screen, choose Modify→Emulator Config...
Page 57 "Sync $MBAR" (in the previous procedure) to pick the master registers. Press the "Pick Chip 360" Action Key. From the Available MC68360 Slaves Browser Window, select HP64MBAR360_1 and click Done. Press the "Set Chip ()" Action Key. This identifies the chip that will be controlled and viewed in the interface.
Page 58 Chapter 2: Plugging into a Target System Plugging into the Motorola QUADS Target System 12 Select pepar from the Register List in the Browser Window and click Done. 13 Press the "Reg 360 ()" Action Key. A Browser Window opens. It shows the contents of the slave processor’s pepar registers.
Page 59: Starting And Exiting Hp 64700 Interfaces
Starting and Exiting HP 64700 Interfaces...
Page 60 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 61: Starting The Emulator/Analyzer Interface
Chapter 3: Starting and Exiting HP 64700 Interfaces Starting the Emulator/Analyzer Interface Starting the Emulator/Analyzer Interface Before starting the emulator/analyzer interface, the emulator and interface software must have already been installed as described in Chapter 14, "Installation". This section describes how to: •...
Page 62: To Start The Interface Using The Default Configuration
Chapter 3: Starting and Exiting HP 64700 Interfaces Starting the Emulator/Analyzer Interface Examples To start the emulator/analyzer interface for the 68360 emulator: $ emul700 em68360 <RETURN> The "em68360" in the command above is the logical emulator name given in the HP 64700 emulator device table file (/usr/hp64000/etc/64700tab.net).
Page 63: To Run A Command File On Interface Startup
Chapter 3: Starting and Exiting HP 64700 Interfaces Starting the Emulator/Analyzer Interface To run a command file on interface startup • Use the emul700 -c <cmd_file> <emul_name> command. You can cause command files to be run upon starting the interface by using the -c <cmd_file>...
Page 64: To Unlock An Interface That Was Left Locked By Another User
Chapter 3: Starting and Exiting HP 64700 Interfaces Starting the Emulator/Analyzer Interface Or, the information may be similar to: em68360 - m68360 running; user = guest@myhost description: M68360 emulation, 512K bytes emul mem user interfaces: xdebug, xemul, xperf, skemul, sktiming internet address: 21.17.9.143...
Page 65: 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 66: To Open The High Level Debugger Interface Window
Chapter 3: Starting and Exiting HP 64700 Interfaces Opening Other HP 64700 Interface Windows window must complete before the command entered in the second window can start. The status lines and the event log displays are updated in all windows.
Page 67: Exiting Hp 64700 Interfaces
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 68: To Exit A Debug/Emulation Session
Chapter 3: Starting and Exiting HP 64700 Interfaces Exiting HP 64700 Interfaces To exit a debug/emulation session • To exit the interface, save your configuration to a temporary file, and lock the emulator so that it cannot be accessed by other users, choose File→Exit→Locked.
Page 69: Entering Commands
Entering Commands...
Page 70 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 71: Using Menus, The Entry Buffer, And Action Keys
Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys Using Menus, the Entry Buffer, and Action Keys This section describes the tasks you perform when using the Graphical User Interface to enter commands. This section describes how to: •...
Page 72: To Choose A Pulldown Menu Item Using The Mouse (Method 1)
Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To choose a pulldown menu item using the mouse (method 1) 1 Position the mouse pointer over the name of the menu on the menu bar. 2 Press and hold the command select mouse button to display the menu. 3 While continuing to hold down the mouse button, move the mouse pointer to the desired menu item.
Page 73: To Choose A Pulldown Menu Item Using The Mouse (Method 2)
• To initially display a pulldown menu, press and hold the menu select key (for example, the "Extend char" key on a HP 9000 keyboard) and then type the underlined character in the menu label on the menu bar. (For example, "f" for "File".
Page 74 Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys • To move left to another pulldown menu after having initially displayed a menu, press the left-arrow key. • To move down one menu item within a menu, press the down-arrow key. •...
Page 75: To Choose Pop-Up Menu Items
Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To choose pop-up menu items 1 Move the mouse pointer to the area whose pop-up menu you wish to access. (If a pop-up menu is available, the mouse pointer changes from an arrow to a hand.) 2 Press and hold the select mouse button.
Page 76: To Place Values Into The Entry Buffer Using The Keyboard
Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To place values into the entry buffer using the keyboard 1 Position the mouse pointer within the text entry area. (An "I-beam" cursor will appear.) 2 Enter the text using the keyboard. To clear the entry buffer text area from beginning until end, press the <Ctrl>u key combination.
Page 77 Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys Because the interface displays absolute addresses as hex values, any copied and pasted string that can be interpreted as a hexadecimal value (that is, the string contains only numbers 0 through 9 and characters "a" through "f") automatically has an "h"...
Page 78 Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys Example To paste the symbol "num_checks" into the entry buffer from the interface display area, position the mouse pointer over the symbol and then click the paste mouse button.
Page 79: To Recall Entry Buffer Values
Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To recall entry buffer values • Position the mouse pointer over the Recall button just to the right of the entry buffer text area, click the mouse button to bring up the Entry Buffer Recall dialog box, and then choose a string from that dialog box.
Page 80: To Copy-And-Paste From The Entry Buffer To The Command Line Entry Area
Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To copy-and-paste from the entry buffer to the command line entry area 1 Place text to be pasted into the command line in the entry buffer text area. You may do that by: •...
Page 81: To Use The Action Keys
Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To use the action keys 1 If the action key uses the contents of the entry buffer, place the desired information in the entry buffer. 2 Position the mouse pointer over the action key and click the action key. Action keys are user-definable pushbuttons that perform interface or system functions.
Page 82 Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys Entry Buffer Recall You can recall a previously used entry buffer text string, a predefined entry buffer text string, or a newly entered entry buffer string, to the entry buffer text area. Command Recall You can recall a previously executed command, a predefined command, or a newly entered command, to the...
Page 83 Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys Examples To use the File Selection dialog box: The file filter selects specific files. A list of filter-matching files from the current directory. A list of files previously accessed during the emulation session.
Page 84 Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To use the Directory Selection dialog box: Label informs you of the type of list displayed. A list of predefined or previously accessed directories. A single click on a directory name from the list highlights the name and copies...
Page 85: To Access Help Information
Chapter 4: Entering Commands Using Menus, the Entry Buffer, and Action Keys To access help information • Help available in the help index: 1 Display the Help Index by choosing Help→General Topic... or Help→Command Line..2 Choose a topic of interest from the Help Index. The Help Index lists topics covering operation of the interface as well other information about the interface.
Page 86: Using The Command Line With The Mouse
Chapter 4: Entering Commands Using the Command Line with the Mouse Using the Command Line with the Mouse When using the Graphical User Interface, the command line portion of the interface gives you the option of entering commands in the same manner as they are entered in the Softkey Interface.
Page 87: To Enter A Command
Chapter 4: Entering Commands Using the Command Line with the Mouse 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. Off means the command line is not displayed and you use only the pulldown menus and the action keys to control the interface.
Page 88: To Edit The Command Line Using The Command Line Pushbuttons
Chapter 4: Entering Commands Using the Command Line with the Mouse choices and action keys are supplied with the needed carriage return as part of the command.) To edit the command line using the command line pushbuttons • To clear the command line, click the Clear pushbutton. •...
Page 89: To Edit The Command Line Using The Command Line Pop-Up Menu
Chapter 4: Entering Commands Using the Command Line with the Mouse To edit the command line using the command line pop-up menu • To clear the command line: position the mouse pointer within the Command Line entry area; press and hold the select mouse button until the Command Line pop-up menu appears;...
Page 90: To Recall Commands
Chapter 4: Entering Commands Using the Command Line with the Mouse To recall commands 1 Click the pushbutton labeled Recall in the Command Line to display the dialog box. 2 Choose a command from the buffer list. (You can also enter a command directly into the text entry area of the dialog box.) Because all command entry methods in the interface —...
Page 91: Using The Command Line With The Keyboard
Chapter 4: Entering Commands Using the Command Line with the Keyboard Using the Command Line with the Keyboard When using the command line with the keyboard, you enter commands by pressing softkeys whose labels appear at the bottom of the screen. Softkeys provide for quick command entry, and minimize the possibility of errors.
Page 92: To Recall Commands
Chapter 4: Entering Commands Using the Command Line with the Keyboard To recall commands • Press <CTRL>r or <CTRL>b. The most recent 20 commands you enter are stored in a buffer and may be recalled by pressing <CTRL>r. Pressing <CTRL>b cycles forward through the recall buffer.
Page 93: To Access On-Line Help Information
Chapter 4: Entering Commands Using the Command Line with the Keyboard To access on-line help information • Use the help or ? commands. To access the command line’s on-line help information, type either help or ? on the command line. You will notice a new set of softkeys. By pressing one of these softkeys and <RETURN>, you can display information on that topic.
Page 94: Using Command Files
Chapter 4: Entering Commands Using Command Files Using Command Files You can execute a series of commands that have been stored in a command file. You can create command files by logging commands while using the interface or by using an editor on your host computer. Once you create a command file, you can execute the file in the emulation environment by typing the name of the file on the command line and pressing <RETURN>.
Page 95 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 96 Chapter 4: Entering Commands Using Command Files When you execute CMDFILE, you will be prompted with: Define command file parameter [&ADDR] To pass the parameter, enter the address of the first memory location to be modified. You will then be prompted for &VALUE1. If you enter, for example, "0,-1,20, 0ffffh, 4+5*4", the first parameter "0,-1,20,"...
Page 97: To Start Logging Commands To A Command File
Chapter 4: Entering Commands Using Command Files characters for shell commands which are double quotes ("), single quotes (’), and the backslash symbol (\). For example, the following three lines are treated as a single shell command. The two hidden line feeds are ignored because they are inside the two single quotes (’): !awk ’/$/ { blanks++ } END { print blanks }...
Page 98: To Playback (Execute) A Command File
Chapter 4: Entering Commands Using Command Files To playback (execute) a command file • Choose File→Log→Playback and use the dialog box to select the name of the command file you wish to execute. • Using the command line, enter the name of the command file and press <RETURN>.
Page 99: Using Pod Commands
Chapter 4: Entering Commands Using Pod Commands Using Pod Commands Pod commands are Terminal Interface commands. The Terminal Interface is the low-level interface that resides in the firmware of the emulator. A pod command used in the Graphical User Interface bypasses the interface and goes directly to the emulator.
Page 100: To Display The Pod Commands Screen
Chapter 4: Entering Commands Using Pod Commands To display the pod commands screen • Choose Display→Pod Commands. The pod commands screen displays the results of pod (Terminal Interface) commands. To set the interface to use pod commands, choose Settings→Pod Command Keyboard. To use pod commands •...
Page 101: 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 102: To Forward Commands To The Software Performance Analyzer
Chapter 4: Entering Commands Forwarding Commands to Other HP 64700 Interfaces To forward commands to the software performance analyzer • Enter the forward perf "<command string>" command using the command line. Examples To send the "profile" command to the software performance analyzer:...
Page 103: Configuring The Emulator
Configuring the Emulator...
Page 104 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 105: Using The Configuration Interface
Chapter 5: Configuring the Emulator Using the Configuration Interface Using the Configuration Interface This section shows you how to modify, store, and load configurations using the emulator configuration interface. This section shows you how to: • Start the configuration interface. •...
Page 106: To Start The Configuration Interface
Chapter 5: Configuring the Emulator Using the Configuration Interface To start the configuration interface • Choose Modify→Emulator Config... from the emulator/analyzer interface pulldown menu. • Using the command line, enter the modify configuration command. The configuration interface top-level dialog box (see the following example) is displayed.
Page 107 Chapter 5: Configuring the Emulator Using the Configuration Interface Examples The 68360 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 any configuration changes into the emulator.
Page 108: To Modify A Configuration Section
Chapter 5: Configuring the Emulator Using the Configuration Interface To modify a configuration section 1 Start the emulator configuration interface. 2 Click on a section name in the configuration interface top-level dialog box. 3 Use the section dialog box to make changes to the configuration. If you are using the Softkey Interface: The configuration questions in the "General Items"...
Page 109 Chapter 5: Configuring the Emulator Using the Configuration Interface Most configuration sections provide dialog boxes similar to the following. The dialog for this section has been opened Applies configuration changes to the emulator Configuration options in this section Closes the Cancels all changes since Presents emulator dialog box...
Page 110: To Apply Configuration Changes To The Emulator
Chapter 5: Configuring the Emulator Using the Configuration Interface As soon as you change a configuration option, the change is recorded (as seen by the "Changes Not Loaded" message in the top level dialog). To apply configuration changes to the emulator •...
Page 111: If Apply To Emulator Fails
Chapter 5: Configuring the Emulator Using the Configuration Interface 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: •...
Page 112: To Store Configuration Changes To A File
Chapter 5: Configuring the Emulator Using the Configuration Interface 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 113: To Change The Configuration Directory Context
Chapter 5: Configuring the Emulator Using the Configuration Interface 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 114: To Access Help Topics
Chapter 5: Configuring the Emulator Using the Configuration Interface 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. To access help for a configuration item in a dialog box •...
Page 115: To Exit The Configuration Interface
Chapter 5: Configuring the Emulator Using the Configuration Interface To exit the configuration interface • Choose File→Exit... from the pulldown menu in the top-level configuration interface window (or type <CTRL>x). If configuration changes have not been stored to a file, a confirmation dialog box appears, giving you the options of: storing, exiting without storing, or canceling the exit.
Page 116: Verifying The Emulator Configuration
Chapter 5: Configuring the Emulator Verifying the Emulator Configuration Verifying the Emulator Configuration The 68360 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: •...
Page 117: To Display Information About Bus Interface Ports
Chapter 5: Configuring the Emulator Verifying the Emulator Configuration Other information from the option register. 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 or the emulator/analyzer interface pulldown menu. •...
Page 118: To Display Information About The Reset Mode Configuration
Chapter 5: Configuring the Emulator Verifying the Emulator Configuration To display information about the reset mode configuration • Choose Display→Configuration Info→Reset Mode Value from either the configuration interface or the emulator/analyzer interface pulldown menu. • Using the emulator/analyzer interface command line, enter the display configuration_info reset_mode command.
Page 119: To Display Information About The Present Clock Input Mode
• Using the emulator/analyzer interface command line, enter the display configuration_info clock_mode command. The clock mode depends on the clock module installed in the emulation probe. Refer to the Hewlett-Packard MC68360 Emulator/Analyzer Installation/Service/Terminal Interface User’s Guide for details. To display assembly language instructions for setting up the SIM •...
Page 120: To Check For Configuration Inconsistencies
Chapter 5: Configuring the Emulator Verifying the Emulator Configuration To check for configuration inconsistencies • Choose Display→Configuration Info→Diagnostics from either the configuration interface or the emulator/analyzer interface pulldown menu. • Using the emulator/analyzer interface command line, enter the display configuration_info diagnostics command. This command: •...
Page 121: To Verify The Emulator Configuration
Chapter 5: Configuring the Emulator Verifying the Emulator Configuration To verify the emulator configuration 1 Choose Display→Configuration Info→Memory Map from either the configuration interface or the emulator/analyzer interface pulldown menu to display information about the memory map and its correlation with chip selects, internal module register block, and RAM.
Page 123: Using The Emulator
Using the Emulator...
Page 124 "Solving Problems" in the MC68360 emulator/Analyzer Installation/Service/Terminal Interface Manual. Ensure that you are using the appropriate clock module for the system you are probing. Details of clock module selection are also discussed in the MC68360 emulator/Analyzer Installation/Service/Terminal Interface Manual.
Page 125: Using The Emsim Registers
The default programming of the EMSIM register set matches the reset values of the 68360 SIM (refer to the Motorola MC68360 User’s Manual for specific values).
Page 126 Chapter 6: Using the Emulator Using the EMSIM Registers There are three places where 68360 SIM registers are kept: the target 68360, the emulator 68360, and the emulator configuration file. At any given time during a run of program, the content of the SIM and EMSIM registers will likely be different, and they may both be different from the content of the configuration file.
Page 127: To View The Sim Register Differences
Chapter 6: Using the Emulator Using the EMSIM Registers 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. A list will appear. It will show only registers having different values between the SIM and EMSIM.
Page 128: To Synchronize To The Emsim Registers
Chapter 6: Using the Emulator Using the EMSIM Registers To synchronize to the EMSIM registers • Choose Modify→SIM Registers→Copy Emulator SIM to Processor SIM from the emulator/analyzer interface pulldown menu. • Using the emulator/analyzer interface command line, enter the sync_sim_registers to_68360_from_config command.
Page 129: To Assign An Mbar Value For The M68360 Register Set
Chapter 6: Using the Emulator Using the EMSIM Registers To assign an MBAR value for the M68360 register • Press the "Sync $MBAR" Action Key. The emulator will read the value of the MBAR register in the target 68360 processor and record the value for use in defining the 68360 register set in the emulator.
Page 130: 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 131: To Load Absolute Files Without Symbols
To store memory contents into absolute files • Using the command line, enter the store memory command. You can store emulation or target system memory contents into HP format absolute files on the host computer. Absolute files are stored in the current directory. If no extension is given for the absolute file name, it is given a ".X"...
Page 132: Using Symbols
Chapter 6: Using the Emulator Using Symbols Using Symbols If symbol information is present in the absolute file, it is loaded along with the absolute file (unless you use the nosymbols option). Both global symbols and symbols that are local to a program module can be displayed. Long symbol names can be truncated in the symbols display;...
Page 133: To Display Global Symbols
Chapter 6: Using the Emulator Using Symbols Examples To load symbols from the demo program: load symbols ecs.x <RETURN> To display global symbols • Choose Display→Global Symbols. • Using the command line, enter the display global_symbols command. Listed are: address ranges associated with a symbol, the segment the symbol is associated with, and the offset of that symbol within the segment.
Page 134: To Display Local Symbols
Chapter 6: Using the Emulator Using Symbols To display local symbols • When displaying symbols, position the mouse pointer over a symbol on the symbol display screen and click the select mouse button. • When displaying symbols, position the mouse pointer over the symbol, press and hold the select mouse button, and choose Display Local Symbols from the pop-up menu.
Page 135 Chapter 6: Using the Emulator Using Symbols Examples To use the Symbols Display pop-up menu: View the local symbols associated with the highlighted symbol by choosing this menu item.
Page 136 Chapter 6: Using the Emulator Using Symbols Using the command line: To display local symbols in a module: display local_symbols_in update_sys <RETURN> To display local symbols in a procedure: display local_symbols_in update_sys.save_points <RETURN>...
Page 137 Chapter 6: Using the Emulator Using Symbols To display address ranges associated with the high-level source line numbers: display local_symbols_in update_sys."update_sys.c": <RETURN>...
Page 138: To Display A Symbol's Parent Symbol
Chapter 6: Using the Emulator Using Symbols To display a symbol’s parent symbol • When displaying symbols, position the mouse pointer over the symbol, press and hold the select mouse button, and choose Display Parent Symbols from the pop-up menu. Examples View the parent symbol associated...
Page 139: To Copy-And-Paste A Full Symbol Name To The Entry Buffer
Chapter 6: Using the Emulator Using Symbols To copy-and-paste a full symbol name to the entry buffer • When displaying symbols, position the mouse pointer over the symbol, press and hold the select mouse button, and choose Cut Full Symbol Name from the pop-up menu.
Page 140: Using Context Commands
Chapter 6: Using the Emulator Using Context Commands Using Context Commands The commands in this section display and control the directory and symbol contexts for the interface. Directory context. The current directory context is the directory accessed by all system references for files—primarily load, store, and copy commands—if no explicit directory is mentioned.
Page 141: To Display The Current Directory And Symbol Context
Chapter 6: Using the Emulator Using Context Commands To display the current directory and symbol context • Choose Display→Context. • Using the command line, enter the pwd and pws commands. The current directory and working symbol contexts are displayed, and also the name of the last executable file from which symbols were loaded.
Page 142: To Change The Directory Context
Chapter 6: Using the Emulator Using Context Commands To change the directory context • Choose File→Context→Directory and use the dialog box to select a new directory. • Using the command line, enter the cd <directory> command. The Directory Selection dialog box contains a list of directories accessed during the emulation session as well as any predefined directories present at interface startup.
Page 143: Executing User Programs
Chapter 6: Using the Emulator Executing User Programs Executing User Programs You can use the emulator to run programs, break program execution into the monitor, step through the program by high-level source lines or by assembly language instructions, and reset the emulation processor. When displaying memory in mnemonic format, a highlighted bar shows the current program counter address.
Page 144: To Run Programs From An Address
Chapter 6: Using the Emulator Executing User Programs To run programs from an address • Position the mouse pointer in the entry buffer and enter the address you want to run from; then, choose Execution→Run→from (). • Using the command line, enter the run from <address> command. Examples To run from address 920H: run from 920h <RETURN>...
Page 145: To Run Programs From Soft Reset
Chapter 6: Using the Emulator Executing User Programs To run programs from soft reset • Choose Execution→Run→from Soft Reset. • Using the command line, enter the run from soft_reset command. The run from soft reset command pulses the RESETS line to the processor to force a soft reset.
Page 146: To Stop (Break From) User Program Execution
Chapter 6: Using the Emulator Executing User Programs 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 147: To Step Assembly-Level Instructions
Chapter 6: Using the Emulator Executing User Programs Examples To step through instructions associated with the high-level source lines at the current program counter: step source <RETURN> To step through instructions associated with high-level source lines at address "main": step source from main <RETURN> To step assembly-level instructions •...
Page 148: To Reset The Emulation Processor
Chapter 6: Using the Emulator Executing User Programs 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 149: Using Software Breakpoints
Note Version A.04.00 or greater of the HP 64700 system firmware provides support for permanent as well as temporary breakpoints. If your version of HP 64700 system firmware is less than A.04.00, only temporary breakpoints are supported.
Page 150: To Display The Breakpoints List
Chapter 6: Using the Emulator Using Software Breakpoints • Re-activate a breakpoint. • Clear a breakpoint. • Clear all breakpoints. To display the breakpoints list • Choose Display→Breakpoints or Breakpoints→Display. • Using the command line, enter the display software_breakpoints command. The breakpoints display shows the address and status of each breakpoint currently defined.
Page 151: To Enable/Disable Breakpoints
Chapter 6: Using the Emulator Using Software Breakpoints program execution. Both temporary and permanent breakpoints can be inactivated (and restored) using the breakpoints display pop-up menu. pending Which means the temporary breakpoint has been set but not encountered during program execution. When encountered, these breakpoints are inactivated but retained in the breakpoints list.
Page 152 Chapter 6: Using the Emulator Using Software Breakpoints The run-time library provided with the 68360 C Cross Compiler uses software breakpoints to interrupt program execution when exceptions (for example, divide by zero) are encountered. If software breakpoints are disabled, exception processing may result in "access to guarded memory"...
Page 153: To Set A Permanent Breakpoint
• Using the command line, enter the modify software_breakpoints set <address> permanent command. Permanent breakpoints are available if your version of HP 64700 system firmware is A.04.00 or greater. The breakpoints feature must be enabled before individual breakpoints can be set.
Page 154 Chapter 6: Using the Emulator Using Software Breakpoints Examples To set permanent breakpoints using the mnemonic memory display pop-up menu: Click this line to set a breakpoint. Click this line to clear a breakpoint. (Asterisks mark set breakpoints.) Bring up menu and choose this item to set (or clear) a breakpoint on the...
Page 155: To Set A Temporary Breakpoint
• Place an absolute or symbolic address in the entry buffer; then, choose Breakpoints→Temporary () (or Breakpoints→Set () if your version of HP 64700 system firmware is less than A.04.00). • Using the command line, enter the modify software_breakpoints set <address>...
Page 156: To Deactivate A Breakpoint
Chapter 6: Using the Emulator Using Software Breakpoints To deactivate a breakpoint • When displaying breakpoints, position the mouse pointer over the line displaying the active breakpoint and click the select mouse button. Or, press and hold the select mouse button and choose Set/Inactivate Breakpoint from the pop-up menu. A deactivated breakpoint remains in the breakpoint list and can be re-activated later.
Page 157 Chapter 6: Using the Emulator Using Software Breakpoints Examples To re-activate breakpoints using the breakpoints display pop-up menu: Change status with a mouse click on this line (menu and highlight do not appear). Choose this menu item to change the state of the highlighted breakpoint.
Page 158: To Clear A Breakpoint
Chapter 6: Using the Emulator Using Software Breakpoints To clear a breakpoint • When displaying memory in mnemonic format, position the mouse pointer over the program line at which you wish to clear a currently set breakpoint (notice the asterisk at the left of the line) and click the select mouse button. Or, press and hold the select mouse button and choose Set/Clear Software Breakpoint from the pop-up menu.
Page 159 Chapter 6: Using the Emulator Using Software Breakpoints Examples To clear a software breakpoint using the breakpoints display pop-up menu: Bring up the menu and choose this item to clear the highlighted breakpoint.
Page 160: To Clear All Breakpoints
Chapter 6: Using the Emulator Using Software Breakpoints To clear all breakpoints • When displaying breakpoints, position the mouse pointer within the Breakpoints Display screen, press and hold the select mouse button, and choose Clear (delete) All Breakpoints from the pop-up menu. •...
Page 161: Displaying And Modifying Registers
Chapter 6: Using the Emulator Displaying and Modifying Registers Displaying and Modifying Registers This section describes tasks related to displaying and modifying emulation processor registers. You can display the contents of an individual register or of all the registers. To display register contents •...
Page 162: Obtaining Mnemonic Displays Of The 68360 Registers Using The Action Keys
Chapter 6: Using the Emulator Displaying and Modifying Registers Obtaining mnemonic displays of the 68360 registers using the Action Keys • To set up to display registers for the emulated 68360, use the "Sync $MBAR" Action Key. • To obtain a record of the present contents of all SIM60 and CPM registers in one listing, press the "Reg 360 All"...
Page 163 Chapter 6: Using the Emulator Displaying and Modifying Registers The following expanded display of the pepar register was obtained from the SIM60/CMP Register Browser Window by placing pepar in the entry buffer and clicking the action key labeled Reg 360 (): CREATED: Fri Mar 31 11:39:27 1995 >addr=0x00001016 pepar=0x0000 Name...
Page 164: To Modify Register Contents
Chapter 6: Using the Emulator Displaying and Modifying Registers 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 165: To Modify Registers Using The Action Keys
Chapter 6: Using the Emulator Displaying and Modifying Registers To modify registers using the Action Keys • To modify the content of a SIM60 or CPM register, press the "Pick Reg 360" Action Key. Within the appropriate browser window, click on the name of the register to be modified.
Page 166: Displaying And Modifying Memory
Chapter 6: Using the Emulator Displaying and Modifying Memory Displaying and Modifying Memory You can display and modify the contents of memory in hexadecimal formats and in real number formats. You can also display the contents of memory in assembly language mnemonic format.
Page 167: To Display Memory In Mnemonic Format
Chapter 6: Using the Emulator Displaying and Modifying Memory To display memory in mnemonic format • To display memory at a particular address, place an absolute or symbolic address in the entry buffer; then, choose Display→Memory→Mnemonic (), or, using the command line, enter the display memory <address>...
Page 168: To Display Memory In Hexadecimal Format
Chapter 6: Using the Emulator Displaying and Modifying Memory To display memory in hexadecimal format • Place an absolute or symbolic address in the entry buffer; then, choose Display→Memory→Hex () and select the size from the cascade menu. • Using the command line, enter the display memory <address> blocked <size> command.
Page 169: To Display Memory At An Address
Chapter 6: Using the Emulator Displaying and Modifying Memory To display memory in blocked byte format: display memory ascii_old_data blocked bytes <RETURN> To display memory at an address • Place an absolute or symbolic address in the entry buffer; then, choose Display→Memory→At ().
Page 170: To Display Memory Repetitively
Chapter 6: Using the Emulator Displaying and Modifying Memory To display memory repetitively • Choose Display→Memory→Repetitively. • Using the command line, enter the display memory repetitively command. The memory display is constantly updated. The format is specified by the last memory display command.
Page 171: Displaying Data Values
Chapter 6: Using the Emulator Displaying Data Values Displaying Data Values The data values display lets you view the contents of memory as data types. You can display data values in the following formats: bytes 8-bit integers unsigned 8-bit integers chars words 16-bit integers...
Page 172: To Clear The Data Values Display And Add A New Item
Chapter 6: Using the Emulator Displaying Data Values To clear the data values display and add a new item • Place an absolute or symbolic address in the entry buffer; then, choose Display→Data Values→New () and select the data type from the cascade menu. •...
Page 173: Changing The Interface Settings
Chapter 6: Using the Emulator Changing the Interface Settings Changing the Interface Settings This section shows you how to: • Set the source/symbol modes. • Set the display modes. To set the source/symbol modes • To display assembly language mnemonics with absolute addresses, choose Settings→Source/Symbol Modes→Absolute, or, using the command line, enter the set source off symbols off command.
Page 174: To Set The Display Modes
Chapter 6: Using the Emulator Changing the Interface Settings To set the display modes • Choose Settings→Display Modes... to open the display modes dialog box. Press and hold the select mouse button and drag the mouse to select "Source Only", "Source Mixed", or "Off".
Page 175 Chapter 6: Using the Emulator Changing the Interface Settings Source/Symbols View Source in Memory specifies whether source lines are included, mixed with assembly code, or excluded from mnemonic memory displays. Source in Trace specifies whether source lines are included, mixed with stored states, or excluded from trace displays.
Page 176: Using System Commands
Chapter 6: Using the Emulator 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. •...
Page 177: To Display The Name Of The Emulation Module
Chapter 6: Using the Emulator Using System Commands To display the name of the emulation module • Using the command line, enter the name_of_module command. While operating your emulator, you can verify the name of the emulation module. This is also the logical name of the emulator in the emulator device file. Examples To display the name of your emulation module: name_of_module <RETURN>...
Page 178: To Display The Error Log
Chapter 6: Using the Emulator Using System Commands To display the error log • Choose Display→Error Log. • Position the mouse pointer on the status line, press and hold the select mouse button, and then choose Display Error Log from the pop-up menu. •...
Page 179 Chapter 6: Using the Emulator Using System Commands The interface will choose the "vi" editor as its default editor, unless you specify another editor by setting an X resource. Refer to the Chapter 10, "Setting X Resources" for more information about setting this resource. You must load symbols before most commands will work because symbol information is needed to be able to locate the files.
Page 180 Chapter 6: Using the Emulator Using System Commands Examples To edit a file that defines a symbol: Choosing this menu item brings up a terminal window with an edit session open on the file where the highlighted symbol is defined.
Page 181 Chapter 6: Using the Emulator Using System Commands To edit a file at a source line: Choosing this menu item brings up a terminal window with an edit session open on the file where the highlighted source line exists.
Page 182: To Copy Information To A File Or Printer
Chapter 6: Using the Emulator Using System Commands To copy information to a file or printer • Choose File→Copy, select the type of information from the cascade menu, and use the dialog box to select the file or printer. • Using the command line, enter the copy command. ASCII characters are copied to the file or printer.
Page 183 Chapter 6: Using the Emulator Using System Commands Registers ... Copies the current values of the BASIC register class to a file. To copy the contents of the other register classes, first display the registers in that class, and then use the File→Copy→Display ... command. Breakpoints ...
Page 184: To Save Peripheral Register Settings To A File
Chapter 6: Using the Emulator Using System Commands To save peripheral register settings to a file 1 Press the "Pick Util" Action Key. 2 In the browser window, highlight save68360registers and click Done. 3 Press the "Run Util()" Action Key. 4 Type the desired directory/filename to contain register values in the Define command file parameter dialog box, and click OK.
Page 185: To Remove All Temporary Files
Chapter 6: Using the Emulator Using System Commands To remove all temporary files 1 Press the "Pick Util" Action Key. 2 In the browser window, highlight clean68360util and click Done. 3 Press the "Run Util()" Action Key. To generate boot code for configuring the SIM60 unit 1 Press the "Boot Code"...
Page 186: Using Emulator Support For The M68360 Companion Mode
Chapter 6: Using the Emulator Using emulator support for the M68360 Companion Mode Using emulator support for the M68360 Companion Mode This section shows you how to use the M68360 action keys to develop products that use the M68360 Companion Mode. Through the action keys, you can perform such actions as viewing registers, configuring registers, developing boot code, and running programs.
Page 187: Tasks You May Wish To Perform When Using The M68360 Companion Mode
Chapter 6: Using the Emulator Using emulator support for the M68360 Companion Mode Tasks you may wish to perform when using the M68360 companion Mode The following paragraphs show you how to perform typical development operations supported in the action keys of the M68360 Graphical User Interface. For further details, refer to the help screen available by pressing the "**Help 360**"...
Page 188 Chapter 6: Using the Emulator Using emulator support for the M68360 Companion Mode • To assign a new base address to contain the register set of an M68360 chip, press the "Pick Util" Action Key. In the Utilities Selection browser window, highlight assign68360chip, and click Done.
Page 189: For More Information
• Refer to the file named README040360 in the directory $HP64000/inst/emul/64780A/compmode to see files developed to support companion mode use of an HP 64780 M68360 or HP 64783 M68040 emulator system. This file can easily be modified to support M68360 companion mode with...
Page 190: Using Simulated I/O
Chapter 6: Using the Emulator Using Simulated I/O Using Simulated I/O Simulated I/O is a feature of the emulator/analyzer interface that lets you use the same keyboard and display that you use with the interface to provide input to programs and display program output. To use simulated I/O, your programs must communicate with the simulated I/O control address and the buffer locations that follow it.
Page 191: To Use Simulated I/O Keyboard Input
Chapter 6: Using the Emulator Using Simulated I/O Examples A message tells you whether the display is open or closed. You can modify the configuration to enable status messages. To use simulated I/O keyboard input • To begin using simulated I/O input, choose Settings→Simulated IO Keyboard. •...
Page 192: Using Basis Branch Analysis
This section shows you how to: • Store BBA data to a file. Refer to the HP Branch Validator (BBA) User’s Guide for complete details on the BBA product and how it works. To store BBA data to a file •...
Page 193: Using The Emulation-Bus Analyzer
Using the Emulation-Bus Analyzer How to record program execution in real-time...
Page 194: Power Of The Emulation-Bus Analyzer
Also, trace specifications and trace data can be stored to files and loaded from files. If you encounter problems when using the emulator/analyzer, refer to the chapter titled "Solving Problems" in the MC68360 Emulator/Analyzer Installation/Service/Terminal Interface Manual.
Page 195: Making Simple Trace Measurements
Chapter 7: Using the Emulation-Bus Analyzer Making Simple Trace Measurements Making Simple Trace Measurements You can make simple records of the processor’s bus activity using just a few analyzer commands. When you set up the analyzer to record processor bus activity, you are preparing to make a trace measurement.
Page 196: To Start A Trace Measurement
If you are using the deep analyzer, the depth of the trace list buffer depends on whether or not you installed memory modules on the analyzer card, and the capacity of the memory modules installed. Refer to the Hewlett-Packard MC68360 Emulator/Analyzer Installation/Service/Terminal Interface Guide for details. If you are using the 1K analyzer, the trace list buffer is 512 or 1024 states deep (depending on whether or not you turn on the state/time count).
Page 197: To Stop A Trace Measurement
Chapter 7: Using the Emulation-Bus Analyzer Making Simple Trace Measurements 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 198 Chapter 7: Using the Emulation-Bus Analyzer Making Simple Trace Measurements Whether source lines, disassembled trace states, or symbols are included in the display depends on the modes you choose with the Settings→Source/Symbols Modes or Settings→Display Modes pulldown menu items. Example A simple trace list resembles:...
Page 199: To Display The Trace Status
Chapter 7: Using the Emulation-Bus Analyzer Making Simple Trace Measurements To display the trace status • Choose Display→Status. • Using the command line, display the trace status with the display status command. When you complete a trace measurement, you’ll want to see the results. The commands above show the current emulator and analyzer status.
Page 200: To Change The Trace Depth
In the deep analyzer, the maximum number of trace states depends on whether or not you installed memory modules in the analyzer card, and the capacity of the memory modules. Refer to the Hewlett-Packard MC68360 Emulator/Analyzer Installation/Service/Terminal Interface Guide for details. In the 1K analyzer, the maximum number of trace states is 1024 when counting is turned off, and 512 otherwise.
Page 201: To Modify The Last Trace Command Entered
Chapter 7: Using the Emulation-Bus Analyzer Making Simple Trace Measurements 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: trace modify_command The Trace Specification Selection dialog box contains a list of trace specifications executed during the emulation session as well as any predefined trace specifications present at interface startup.
Page 202: To Define A Simple Trigger Qualifier
Chapter 7: Using the Emulation-Bus Analyzer Making Simple Trace Measurements To define a simple trigger qualifier • Enter your trigger qualifier (such as, address 1000h) in the entry buffer. Then in the menu bar, click on: Trace→After(), Trace→Before(), or Trace→About(). •...
Page 203: To Specify A Trigger And Set The Trigger Position
Chapter 7: Using the Emulation-Bus Analyzer Making Simple Trace Measurements To capture a trace of activity both preceding and following the write_hdwr symbol in the update_sys module, place update_sys.write_hdwr in the entry buffer and choose Trace→About(), or on the commad line, enter: trace about long_aligned update_sys.write_hdwr To specify a trigger and set the trigger position •...
Page 204: To Define A Simple Storage Qualifier
Chapter 7: Using the Emulation-Bus Analyzer Making Simple Trace Measurements When you enter a trace about command, the trigger state (line 0) is normally labeled “about”. However, if there are three or fewer states before the trigger, the trigger state is labeled “after”, and if there are three or fewer states after the trigger, the trigger state is labeled “before”.
Page 205: If You Are Having Problems Tracing
Chapter 7: Using the Emulation-Bus Analyzer Making Simple Trace Measurements If you are having problems tracing • Check the emulator configuration. Choose Modify→Emulator Config..Then in the Emulator Pod Settings dialog box: • You may need to select Clock 01 Drive to Target = Buffered. •...
Page 206: Displaying The Trace List
Chapter 7: Using the Emulation-Bus Analyzer 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.
Page 207 Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List 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...
Page 208 Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List Examples To use the trace list pop-up 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...
Page 209: To Disassemble The Trace List
Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List To disassemble the trace list • Choose Trace→Display Options... and in the dialog box, select Data Format Mnemonic. Then click the OK or Apply pushbutton. • Use the mouse to place the cursor on a line in the trace list where you want disassembly to begin.
Page 210: To Specify Trace Disassembly Options
Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List Examples To disassemble instruction data in the trace list starting at line 40: Place the cursor on line 40, press the select mouse button, and click on Disassemble From in the pop-up menu. Or, using the command line, enter: display trace disassemble_from_line_number 40 To specify trace disassembly options...
Page 211 Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List Normally, the MC68360 presents the trace list data as it was stored by the analyzer. That is, all bus cycles are shown, and disassembly starts with the most significant word of the data.
Page 212: To Specify Trace Dequeueing Options
Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List To specify trace dequeueing options • Choose Trace→Display Options... and in the dialog box, select Dequeue Enable. Then click the OK or Apply pushbutton. • Using the command line, enter commands as follows: •...
Page 213 Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List will need to include the low word option if the destination opcode is in the low word at the destination address. You may need to resynchronize alignment of operand cycles with the instruction at the branch address, using the align_data_from_line option.
Page 214: To Display The Trace Without Disassembly
Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List 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.
Page 215: To Display Symbols In The Trace List
Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List 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. Or, using the command line, enter: display trace absolute status binary Display the trace list without instruction disassembly and with status information in...
Page 216 Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List • To display only high level symbols, enter: set symbols high • To display only low level symbols, enter: set symbols low • To display all symbols (both high and low level), enter: set symbols all When you enable symbol display, addresses and operands are replaced by the symbols that correspond to those values.
Page 217: To Display Source Lines In The Trace List
Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List To display source lines in the trace list • Choose Settings→Source/Symbol Modes→Source Mixed or Settings→Source/Symbol Modes→Source Only . • Choose Settings→Display Modes..., and in the dialog box, click on Source in Trace and select either Source Mixed or Source Only from the submenu.
Page 218: To Change The Column Width
Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List 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 219: To Select The Type Of Count Information In The Trace List
Chapter 7: Using the Emulation-Bus Analyzer Displaying 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 220 Chapter 7: Using the Emulation-Bus Analyzer Displaying 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" in the configuration): Specify the trace for the emulator: trace only update_sys counting time...
Page 221: To Offset Addresses In The Trace List
Chapter 7: Using the Emulation-Bus Analyzer Displaying 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 222: To Reset The Trace Display Defaults
Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List 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"...
Page 223: To Display The Trace List Around A Specific Line Number
Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List To display the trace list around a specific 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 224: To Change The Number Of States Available For Display
Refer to the Hewlett-Packard MC68360 Emulator/Analyzer Installation/Service/Terminal Interface Guide for details. If you are using the 1K analyzer, the trace list buffer is 512 or 1024 states deep (depending on whether or not you turn on the state/time count).
Page 225: To Display Program Memory Associated With A Trace List Line
Chapter 7: Using the Emulation-Bus Analyzer Displaying the Trace List To display program memory associated with a trace list line • Using the mouse, place the cursor on the line in the trace list where you want to see the associated content of program memory. Then press the select mouse button, and click on Display Memory At in the trace list pop-up menu.
Page 226: Making Complex Trace Measurements
A sequence is a more complex specification that specifies a series of bus states that must be found to satisfy the trigger. This section tells you how to get the most out of the HP 64700 analyzer by using trigger and sequence specifications. It also describes additional measurement tools to help you get more information from the trace.
Page 227 Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements Q q O o Octal (example: 377o or 377q). D d (default) Decimal (example: 2048d or 2048). Hexadecimal (example: 0a7fh). You must precede any hexadecimal number that begins with an A, B, C, D, E, or F with a zero. Don’t care digits may be included in binary, octal, or hexadecimal numbers.
Page 228 Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements Values, symbols, and operators may be used together in analysis specification expressions. For example, if the local symbol exists, the following is a valid expression: module.c:symb+0b67dh&0fff00h However, you cannot add two symbols unless one of them is an EQU type symbol. Emulation-Bus Analyzer Trace Signals The emulation-bus analyzer has 80 channels available for capturing information: 64 of those channels are used for the instruction bus and data bus, and the...
Page 229 Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements synthesized signals, and are collectively called the status lines. You can use status values as trigger or storage qualifiers. For example, you may want to capture processor reads to a certain address, but not processor writes. You can use a status value to qualify only processor read cycles to the memory location.
Page 230: To Use Address, Data, And Status Values In Trace Expressions
Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements 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 231: To Enter A Range In A Trace Expression
(The Terminal Interface does allow this type of measurement, though there is still only one range term. Refer to the Hewlett-Packard MC68360 Emulator/Analyzer Installation/Service/Terminal Interface Guide for details.) Since address is the default range type, you can omit the address keyword. You can’t omit the data or status keywords if those are the bus parts you want to...
Page 232: To Use The Sequencer
Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements 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 To use the sequencer •...
Page 233: To Specify A Restart Term
Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements To specify a restart term • 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...
Page 234: To Specify Trace Windowing
Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements To specify trace windowing • 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...
Page 235: To Specify Both Sequencing And Windowing
Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements 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...
Page 236: To Count States Or Time
512 states. If you disable the counter in the 1K analyzer, using the trace counting off command, maximum trace depth is 1024 states. When using the 1K analyzer, the MC68360 emulator defaults to counting off. To count states or time, you must configure the analyzer clocks correctly. See "To configure the analyzer clock"...
Page 237: To Define A Storage Qualifier
Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements 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 address 10h Count all states in the trace: trace counting anystate Count time in the trace: trace counting time...
Page 238: To Define A Prestore Qualifier
Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements Examples Trace only address 10h: trace only address 10h Trace only data value 0ffh: trace only data 0ffh Trace only write operations trace only status write To define a prestore qualifier •...
Page 239: To Trace Activity Leading Up To A Program Halt
Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements Store-qualify writes to the variable, and use prestore to capture the instructions that caused those writes to occur (perhaps by prestoring program reads). Examples Specify a prestore qualifier: trace prestore address not range gen_ascii_data thru gen_ascii_data end status prog and read only long_aligned gen_ascii_data Disable prestore qualification:...
Page 240: To Modify The Trace Specification
Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements To modify the trace specification • Choose Trace→Trace Spec... You can recall, modify, and enter your trace specification in the dialog box. • Using the command line, enter: trace modify_command Then use the command line editing features to change the trace command specifications.
Page 241: To Repeat The Previous Trace Command
Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements Example Recall the last trace command with Trace→Trace Spec..., or by entering: trace modify_command Then edit the trace command as you desire. To repeat the previous trace command • Choose Trace→Again. •...
Page 242: To Capture A Continuous Stream Of Program Execution No Matter How Large Your Program
Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements To capture a continuous stream of program execution no matter how large your program The following example can be performed in emulation systems using the deep analyzer (it cannot be done with the 1K analyzer). It shows you how to capture all of the execution of your target program.
Page 243 Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements of trig1 may be ignored until the critical routine is completed (when using a foreground monitor). 3 If you are using a foreground monitor, enter the following additional pod commands to prevent the trace memory from capturing monitor execution. The following example commands will obtain this result in some emulators: Settings→Pod Command Keyboard trng addr=<address range occupied by your monitor>...
Page 244 Chapter 7: Using the Emulation-Bus Analyzer Making Complex Trace Measurements Note that when you set a delay specification using tgout -c or tgout -t (trigger output delay before trace complete/after trigger), the trace will indicate complete as soon as the analyzer has captured the state specified, even though the entire trace memory has not been filled.
Page 245: Saving And Restoring Trace Data And Specifications
Chapter 7: Using the Emulation-Bus Analyzer 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 246: To Store Trace Data
Chapter 7: Using the Emulation-Bus Analyzer Saving and Restoring Trace Data and Specifications Example Store a trace specification to a file: store trace_spec tspec.TS To store trace data • Choose File→Store→Trace Data... In the dialog box, select an existing filename or specify a new filename to contain the present trace memory content.
Page 247: To Load A Trace Specification
Chapter 7: Using the Emulation-Bus Analyzer Saving and Restoring Trace Data and Specifications 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).
Page 248: To Load Trace Data
Chapter 7: Using the Emulation-Bus Analyzer Saving and Restoring Trace Data and Specifications 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).
Page 249: Making Software Performance Measurements
Making Software Performance Measurements...
Page 250 The SPMT allows you to make some of the measurements that are possible with the HP 64708 Software Performance Analyzer and its Graphical User Interface (HP B1487). The SPMT post-processes information from the analyzer trace list. When you end a performance measurement, the SPMT dumps the post-processed information to a binary file, which is then read using the perf32 report generator utility.
Page 251: Activity Performance Measurements
Chapter 8: Making Software Performance Measurements Activity Performance Measurements Activity Performance Measurements Activity measurements are measurements of the number of accesses (reads or writes) within an address range. The SPMT shows you the percentage of analyzer trace states that are in the specified address range, as well as the percentage of time taken by those states.
Page 252 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Program Activity State Percent Rel = 0.18 Abs = 0.18 Mean = 0.90 Sdv = 0.88 Time Percent Rel = 0.16 Abs = 0.16 stack Address Range 40000H thru 43FFFH Memory Activity State Percent Rel = 11.72...
Page 253: To Set Up The Trace Command For Activity Measurements
Chapter 8: Making Software Performance Measurements Activity Performance Measurements Time count Relative Time - Us 2221.20 Absolute Totals Absolute count - state 5120 Absolute count - time - Us 2221.20 This section describes how to: • Set up the trace command for activity measurements. •...
Page 254: To Initialize Activity Performance Measurements
Chapter 8: Making Software Performance Measurements Activity Performance Measurements Examples To specify a trace depth of 512: display trace depth 512 <RETURN> To trace after any state, store all states, and count time: trace counting time <RETURN> To initialize activity performance measurements •...
Page 255 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Initialization with User Defined Ranges You can specifically give the SPMT address ranges to use by placing the information in a file and entering the file name in the performance_measurement_initialize command. Address range files may contain program symbols (procedure name or static), user defined address ranges, and comments.
Page 256 Chapter 8: Making Software Performance Measurements Activity Performance Measurements You can also use the local_symbols_in option with procedure symbols; this allows you to measure activity related to the symbols defined in a single function or procedure. Restoring the Current Measurement The performance_measurement_initialize restore command allows you to restore old performance measurement data from the perf.out file in the current directory.
Page 257 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Examples Suppose the "addr_ranges" file contains the names of all the functions in the "ecs" demo program loop: combsort do_sort gen_ascii_data get_targets graph_data interrupt_sim proc_specific read_conditions save_points set_outputs strcpy8 update_system write_hdwr Since these labels are program symbols, you do not have to specify the address range associated with each label;...
Page 258: To Interpret Activity Measurement Reports
Chapter 8: Making Software Performance Measurements Activity Performance Measurements To interpret activity measurement reports • View the performance measurement report. Activity measurements are measurements of the number of accesses (reads or writes) within an address range. The reports generated for activity measurements show you the percentage of analyzer trace states that are in the specified address range, as well as the percentage of time taken by those states.
Page 259 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Standard Deviation Deviation from the mean of state count. The following equation is used to calculate standard deviation: Where: Number of traces in the measurement. Average number of states in the range per trace. mean Sum of squares of states in the range per trace.
Page 260 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Error Tolerance and Confidence Level An approximate error may exist in displayed information. Error tolerance for a level of confidence is calculated using the mean of the standard deviations and the mean of the means. Error tolerance gives an indication of the stability of the information.
Page 261 Chapter 8: Making Software Performance Measurements Activity Performance Measurements 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 262 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Address Range 101EH thru 10A8H Memory Activity State Percent Rel = 6.15 Abs = 5.08 Mean = 26.00 Sdv = 114.41 Time Percent Rel = 5.96 Abs = 4.98 Program Activity State Percent Rel = 5.97...
Page 263 Chapter 8: Making Software Performance Measurements Activity Performance Measurements State Percent Rel = 0.47 Abs = 0.39 Mean = 2.00 Sdv = 5.30 Time Percent Rel = 0.49 Abs = 0.41 Program Activity State Percent Rel = 0.70 Abs = 0.61 Mean = 3.10...
Page 264 Chapter 8: Making Software Performance Measurements Activity Performance Measurements 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 265 Chapter 8: Making Software Performance Measurements Activity Performance Measurements write_hdwr 5.86% proc_specific 3.73% combsort 1.80% Summary Information for 20 traces Memory Activity State count Relative count 8455 Mean sample 30.20 Mean Standard Dv 75.44 95% Confidence 116.98% Error tolerance Time count Relative Time - Us 3500.92 Program Activity...
Page 266: Duration Performance Measurements
Chapter 8: Making Software Performance Measurements Duration Performance Measurements Duration Performance Measurements Duration measurements provide a best-case/worst-case characterization of code execution time. These measurements record execution times that fall within a set of specified time ranges. The analyzer trace command is set up to store only the entry and exit states of the module to be measured (for example, a C function or Pascal procedure).
Page 267: To Set Up The Trace Command For Duration Measurements
Chapter 8: Making Software Performance Measurements Duration Performance Measurements If a module is entered at the normal point, and then exited by a point other than the defined exit point, the entry point will be ignored. It will be judged the same as any other unused prefetch, and no time-duration measurement will be made.
Page 268 Chapter 8: Making Software Performance Measurements Duration Performance Measurements CAUTION The previous command depends on the generation of correct exit address symbols by the software development tools. trace after module_name start or module_name end only module_name start or module_name end counting time <RETURN>...
Page 269: To Initialize Duration Performance Measurements
Chapter 8: Making Software Performance Measurements Duration Performance Measurements To initialize duration performance measurements • Use the performance_measurement_initialize command with the duration option. After you set up the trace command, you must tell the SPMT the time ranges to be used in the duration measurement.
Page 270 Chapter 8: Making Software Performance Measurements Duration Performance Measurements When no user defined time range file is specified, the following set of default time ranges are used. 1 us 10 us 10.1 us 100 us 100.1 us 500 us 500.1 us 1 ms 1.001 ms 5 ms 5.001 ms 10 ms 10.1 ms 20 ms...
Page 271: To Interpret Duration Measurement Reports
Chapter 8: Making Software Performance Measurements Duration Performance Measurements To interpret duration measurement reports • View the performance measurement report. Duration measurements provide a best-case/worst-case characterization of code execution time. These measurements record execution times that fall within a set of specified time ranges.
Page 272 Chapter 8: Making Software Performance Measurements Duration Performance Measurements Standard Deviation Deviation from the mean of time. The following equation is used to calculate standard deviation: Where: Number of intervals. Average time. mean Sum of squares of time in the intervals. sumq Error Tolerance and Confidence Level An approximate error may exist in displayed information.
Page 273 Chapter 8: Making Software Performance Measurements Duration Performance Measurements Mean of the means (i.e., mean of the average times in each time range). Examples Consider the following duration measurement report (generated with the commands shown): display trace depth 512 <RETURN> trace after interrupt_sim start or interrupt_sim end only interrupt_sim start or interrupt_sim end counting time <RETURN>...
Page 274 Chapter 8: Making Software Performance Measurements Duration Performance Measurements From Address 101E File main(module)."/users/guest/demo/debug_env/hp64749/main.c" Symbolic Reference at main.interrupt_sim To Address 10A8 File main(module)."/users/guest/demo/debug_env/hp64749/main.c" Symbolic Reference at interrupt_sim+8A Number of intervals 2550 Maximum Time 342343.680 us Minimum Time 52.320 us Avg Time 36987.751 us Statistical summary - for 10 traces...
Page 275: Running Measurements And Creating Reports
Chapter 8: Making Software Performance Measurements Running Measurements and Creating Reports Running Measurements and Creating Reports Several performance measurement tasks are the same whether you are making activity or duration measurements. This section describes how to: • Run performance measurements. •...
Page 276: To End Performance Measurements
Chapter 8: Making Software Performance Measurements Running Measurements and Creating Reports Examples To run the performance measurement, enter the following command: performance_measurement_run 20 <RETURN> The command above causes 20 traces to occur. The SPMT processes the trace information after each trace, and the number of the trace being processed is shown on the status line.
Page 277: To Create A Performance Measurement Report
Chapter 8: Making Software Performance Measurements Running Measurements and Creating Reports To create a performance measurement report • Use the perf32 command at the UNIX prompt. The perf32 report generator utility must be used to read the information in the "perf.out"...
Page 278 Chapter 8: Making Software Performance Measurements Running Measurements and Creating Reports Examples Now, to generate a report from the "perf.out" file, type the following on the command line to fork a shell and run the perf32 utility: !perf32 | more...
Page 279: Making Coordinated Measurements
Making Coordinated Measurements...
Page 280 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 281 The location of the CMB and BNC connectors on the HP 64700 rear panel is shown in the following figure. CMB Connector BNC Connector Signal Lines on the CMB There are three bi-directional signal lines on the CMB connector on the rear panel of the emulator.
Page 282 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 283: Setting Up For Coordinated Measurements
RS-232C communications. Applying RS-232C signals to the CMB connector is likely to result in damage to the HP 64700 Card Cage. To use the CMB, you will need one CMB cable for the first two emulators and one additional cable for every emulator after the first two.
Page 284 Chapter 9: Making Coordinated Measurements Setting Up for Coordinated Measurements 1 Connect the cables to the HP 64700...
Page 285: 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 286 Chapter 9: Making Coordinated Measurements Setting Up for Coordinated Measurements 1 Connect one end of a 50 ohm coaxial cable with male BNC connectors to the HP 64700 BNC receptacle and the other end to the appropriate BNC receptacle on the other measuring instrument.
Page 287: Starting/Stopping Multiple Emulators
Chapter 9: Making Coordinated Measurements Starting/Stopping Multiple Emulators Starting/Stopping Multiple Emulators When HP 64700 Card Cages are connected together via the Coordinated Measurement Bus (CMB), you can start and stop up to 32 emulators at the same time. These are called synchronous measurements.
Page 288: To Start Synchronous Measurements
Chapter 9: Making Coordinated Measurements Starting/Stopping Multiple Emulators When you enter a normal trace command, trace at execute is disabled, and the analyzer ignores the CMB EXECUTE signal. Examples To enable synchronous measurements: specify run from 1e8h <RETURN> To trace when synchronous execution begins: specify trace after address main <RETURN>...
Page 289: 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 290 Chapter 9: Making Coordinated Measurements Using Trigger Signals You can use the trig1 or trig2 line to make a connection between the emulator break input and the CMB connector, BNC connector, or analyzer so that program execution can break when a trigger signal is received from the CMB, BNC, or analyzer.
Page 291 Chapter 9: Making Coordinated Measurements Using Trigger Signals 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 292: To Drive The Emulation Analyzer Trigger Signal To The Cmb
Chapter 9: Making Coordinated Measurements Using Trigger Signals To drive the emulation analyzer trigger signal to the CMB • Choose "receive" for the "Should CMBT drive or receive Trig1" configuration option. You could also drive the emulation analyzer trigger to the CMB over the trig2 internal line by specifying that the CMBT should receive trig2 and that the emulation analyzer should drive trig2.
Page 293: To Break Emulator Execution On Signal From Cmb
Chapter 9: Making Coordinated Measurements Using Trigger Signals To break emulator execution on signal from CMB • Choose "drive" for the "Should CMBT drive or receive Trig1" configuration option. You could also break emulator execution on a trigger signal from the CMB over the trig2 internal line by specifying that the CMB should drive trig2 and that the emulator break should receive trig2.
Page 294: To Arm The Emulation Analyzer On Signal From Cmb
Chapter 9: Making Coordinated Measurements Using Trigger Signals To arm the emulation analyzer on signal from 1 Choose "drive" for the "Should CMBT drive or receive Trig2" configuration option. 2 Choose "receive" for the "Should Analyzer drive or receive Trig2" configuration option.
Page 295: Part 3 Reference
Part 3 Reference...
Page 296 Chapter 12, "Emulator Error Messages," lists each of the messages that you may see while using the MC68360 emulator/analyzer, and describes conditions that may cause the message to appear, and suggests actions you can take to correct problems indicated by the messages.
Page 297: Setting X Resources
Setting X Resources...
Page 298 Resources specifications in later files override those in earlier files. Files are read in the following order: 1 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. 2 The $XAPPLRESDIR/HP64_Softkey file. (The XAPPLRESDIR environment variable defines a directory containing system-wide custom application defaults.)
Page 299 Chapter 10: Setting X Resources 6 System scheme files in directory /usr/hp64000/lib/X11/HP64_schemes. 7 System-wide custom scheme files located in directory $XAPPLRESDIR/HP64_schemes. 8 User-defined scheme files located in directory $HOME/.HP64_schemes (note the dot in the directory name). Scheme files group resource specifications for different displays, computing environments, and languages.
Page 300: To Modify Graphical User Interface Resources
Application Resources for Schemes Resource Values Description HP64_Softkey.platformScheme HP-UX Names the subdirectory for platform SunOS specific schemes. This resource should be (custom) set to the platform on which the X server is running (and displaying the Graphical User Interface) if it is different than the platform where the application is running.
Page 301 Chapter 10: Setting X Resources To modify Graphical User Interface resources Commonly Modified Application Resources Resource Values Description HP64_Softkey.lines Specifies the number of lines in the main (min. 18) display area. HP64_Softkey.columns Specifies the number of columns, in (min. 80) characters, in the main display area.
Page 302 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 303 !HP64_Softkey.columns: Save your changes and exit the editor. 3 If the RESOURCE_MANAGER property exists (as is the case with HP VUE — if you’re not sure, you can check by entering the xrdb -query command), use the xrdb command to add the resources to the RESOURCE_MANAGER property. For example: xrdb -merge -nocpp HP64_Softkey.tmp...
Page 304: To Use Customized Scheme Files
3 Modify the $HOME/.HP64_schemes/<platform>/Softkey.<scheme> file. For example, you could modify the "$HOME/.HP64_schemes/HP-UX/Softkey.MyColor" file to change the defined foreground and background colors. Also, since the scheme file name is different than the default, you could comment out various resource settings to cause general foreground and background color definitions to apply to the Graphical User Interface.
Page 305 For example, to use the "$HOME/.HP64_schemes/HP-UX/Softkey.MyColor" color scheme file you would set the "HP64_Softkey.colorScheme" resource to "MyColor":...
Page 306: To Set Up Custom Action Keys
Chapter 10: Setting X Resources To set up custom action keys To set up custom action keys • Modify the "actionKeysSub.keyDefs" resource in the $HP64000/lib/X11/app-defaults/HP64_Softkey file. The "actionKeysSub.keyDefs" resource defines a list of paired strings. The first string defines the text to appear on the action key pushbutton. The second string defines the command that will be sent to the command line area and executed when the action key is pressed.
Page 307: To Set Initial Recall Buffer Values
Chapter 10: Setting X Resources To set initial recall buffer values To set initial recall buffer values • Modify the "entries" resource for the particular recall buffer. There are six pop-up recall buffers present in the Graphical User Interface. The resources for these pop-up recall buffers are listed in the following table.
Page 308 Chapter 10: Setting X Resources To set initial recall buffer values Examples To set the initial values for the directory selection dialog box when the Graphical User Interface is used with a 68360 emulator, modify the "*m68360*dirSelectSub.entries" resource: *m68360*dirSelectSub.entries: \ "$HOME"...
Page 309: To Set Up Demos Or Tutorials
Chapter 10: Setting X Resources To set up demos or tutorials To set up demos or tutorials You can add demos or tutorials to the Graphical User Interface by modifying the resources described in the following tables. Demo Related Component Resources Resource Value Description...
Page 310 Chapter 10: Setting X Resources To set up demos or tutorials Tutorial Related Component Resources Resource Value Description *enableTutorial False Specifies whether True Help→Tutorial appears in the pulldown menu. *tutorialPopupSub.indexFile ./Xtutorial/Index-topics Specifies the file containing the list of topic and file pairs. *tutorialPopup.textColumns Specifies the width, in characters, of the of the tutorial...
Page 311 Chapter 10: Setting X Resources To set up demos or tutorials 2 Create the demo or tutorial index file. Each line in the index file contains first a quoted string that is the name of the topic which appears in the index pop-up and second the name of the file that is raised when the topic is selected.
Page 313: Emulator/Analyzer Interface Commands
Emulator/Analyzer Interface Commands...
Page 314: How Pulldown Menus Map To The Command Line
Emulator/Analyzer Interface Commands This chapter describes the emulator/analyzer interface commands in alphabetical order. First, the syntax conventions are described and the commands are summarized. How Pulldown Menus Map to the Command Line The following table shows the items available in the pulldown menus and the command line commands to which they map.
Page 315 Chapter 11: 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→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 316 Chapter 11: Emulator/Analyzer Interface Commands Pulldown Command Line display configuration_info Display→Configuration Info 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_ports Display→Configuration Info→Bus Interface Ports (SIM) Display→Configuration Info→Bus Interface display configuration_info embus_interface_ports Ports (Emulator SIM) Display→Configuration Info→Memory Map...
Page 317 Chapter 11: Emulator/Analyzer Interface Commands Pulldown Command Line Modify→Emulator Config modify configuration Modify→Memory modify memory Modify→Memory at () modify memory --EXPR-- modify register Modify→Register Modify→SIM Registers→Copy Processor sync_sim_registers from_68360_to_config SIM to Emulator SIM Modify→SIM Registers→Copy Emulator sync_sim_registers to_68360_from_config SIM to Processor SIM Modify→SIM Registers→Default Emulator sync_sim_registers default_config Execution→Run→from PC...
Page 318 Chapter 11: Emulator/Analyzer Interface Commands Pulldown Command Line display trace Trace→Display 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 STATE Trace→Only () Trace→Only () Prestore trace only STATE prestore anything...
Page 319: How Pop-Up Menus Map To The Command Line
Chapter 11: Emulator/Analyzer Interface Commands How Pop-up Menus Map to the Command Line The following tables show the items available in the pop-up menus and the command line commands to which they map. Mnemonic Memory Display Pop-up Command Line Set/Clear Software Breakpoint modify software_breakpoints set/clear --EXPR-- Edit Source ! vi +<line>...
Page 320 Chapter 11: Emulator/Analyzer Interface Commands Status Line Pop-up 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 Pop-up Command Line Position Cursor, Replace Mode <INSERT CHAR> key (when in insert mode) Position Cursor, Insert Mode <INSERT CHAR>...
Page 321: Syntax Conventions
Chapter 11: Emulator/Analyzer Interface Commands Syntax Conventions Conventions used in the command syntax diagrams are defined below. Oval-shaped Symbols Oval-shaped symbols show options available on the softkeys and other commands that are available, but do not appear on softkeys (such as log_commands and wait).
Page 322: Commands
Chapter 11: Emulator/Analyzer Interface Commands Commands Emulator/analyzer interface commands are summarized in the table below and described in the following pages. !UNIX_COMMAND display error_log modify memory bbaunload display event_log modify register break display global_symbols modify software_breakpoints cd (change directory) display local_symbols_in name_of_module cmb_execute display memory...
Page 323: Break
Chapter 11: Emulator/Analyzer Interface Commands break break This command causes the emulator to leave user program execution and begin executing in the monitor. The behavior of break depends on the state of the emulator: running Break diverts the processor from execution of your program to the emulation monitor.
Page 324: Bbaunld
BBA information to a file. Then, you can generate reports based on the stored information. See Also Refer to the HP Branch Validator (BBA) User’s Guide for complete details on the bbaunload command syntax.
Page 325: Cmb_Execute
Chapter 11: Emulator/Analyzer Interface Commands cmb_execute cmb_execute The cmb_execute command causes the emulator to emit an EXECUTE pulse on its rear panel Coordinated Measurement Bus (CMB) connector. All emulators connected to the CMB (including the one sending the CMB EXECUTE pulse) and configured to respond to this signal will take part in the measurement.
Page 326: Copy
Chapter 11: 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 327 Chapter 11: Emulator/Analyzer Interface Commands copy Depending on the information you choose to copy, default values may be options selected for the previous execution of the display command. For example, if you display memory locations 10h through 20h, then issue a copy memory to myfile command, myfile will list only memory locations 10h through 20h.
Page 328 Chapter 11: Emulator/Analyzer Interface Commands copy pod_command This allows you to copy the most recent commands sent to the HP 64700 Series emulator/analyzer. printer This option specifies your system printer as the destination device for the copy command. Before you can specify the printer as the destination device, you must define PRINTER as a shell variable.
Page 329: Copy Local_Symbols_In
Chapter 11: 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 330: Copy Memory
Chapter 11: 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.
Page 331 Chapter 11: 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 332: Copy Registers
Chapter 11: 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 333: Copy Trace
Chapter 11: 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.
Page 334: Display
Chapter 11: 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 335 Chapter 11: Emulator/Analyzer Interface Commands display event_log This option displays the recorded list of events. global_symbols This option lets you display a list of all global symbols in memory. 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.
Page 336: Display Configuration_Info
Chapter 11: Emulator/Analyzer Interface Commands display configuration_info display configuration_info The display configuration_info command displays information about emulator configuration and processor SIM programming. You can also display diagnostic information about inconsistencies found in the emulator configuration. The parameters are as follows: diagnostics Checks all parts of the emulator configuration and reports any inconsistencies.
Page 337 Display the present mode of clock for the 68360 target system. This mode is set by installation of a clock module in the clock module socket on the emulation probe. Refer to the Hewlett-Packard MC68360 Installation/Service/Terminal Interface User’s Guide manual for details.
Page 338 Chapter 11: Emulator/Analyzer Interface Commands display configuration_info Examples display configuration_info diagnostics <RETURN> display configuration_info memory_map <RETURN> See Also The sync_sim_registers and modify configuration commands. Also, see the "Verifying the Emulator Configuration" section in Chapter 5, "Configuring the Emulator".
Page 339: Display Data
Chapter 11: Emulator/Analyzer Interface Commands display data display data The display data 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 340 Chapter 11: 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 341 Chapter 11: Emulator/Analyzer Interface Commands display data Examples display data Msg_A thru +17 char , Stack long <RETURN> set symbols on <RETURN> set width label 30 <RETURN> display data , Msg_B thru +17 char , Msg_Dest thru +17 char <RETURN> See Also The copy data and set commands.
Page 342: Display Global_Symbols
Chapter 11: 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 343: Display Local_Symbols_In
Chapter 11: Emulator/Analyzer Interface Commands display local_symbols_in display local_symbols_in 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 344: Display Memory
Chapter 11: Emulator/Analyzer Interface Commands display memory display memory This command displays the contents of the specified memory location or series of locations.
Page 345 Chapter 11: Emulator/Analyzer Interface Commands display memory The memory contents can be displayed in mnemonic, hexadecimal, or real number format. In addition, the memory addresses can be listed offset by a value, which allows the information to be easily compared to the program listing. When displaying memory mnemonic and stepping, the next instruction that will step is highlighted.
Page 346 Chapter 11: Emulator/Analyzer Interface Commands display memory FCODE The function code used to define the address space being referenced. See the syntax diagram for FCODE to see a list of the function codes available and for an explanation of those codes. long Displays memory in a 64-bit real number format or 32-bit long words when preceded by blocked or absolute.
Page 347 Chapter 11: Emulator/Analyzer Interface Commands display memory command. The comma is also a delimiter between values when specifying multiple addresses. Examples You can display memory in real number and mnemonic formats: display memory 2000h thru 202fh , 2100h real long <RETURN>...
Page 348: Display Registers
Chapter 11: 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 349: Display Simulated_Io
Chapter 11: 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 350: Display Software_Breakpoints
Chapter 11: 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 351: Display Trace
Chapter 11: 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 352 Chapter 11: Emulator/Analyzer Interface Commands display trace 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 353 Chapter 11: Emulator/Analyzer Interface Commands display trace external binary Displays the external analyzer trace list in binary format. <external This option displays a defined external analyzer label. _label> Displays the external analyzer trace list in hexadecimal format. Use this option to turn off the external trace list display. then This allows you to display multiple external analysis labels.
Page 354 Chapter 11: 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 <RETURN> display trace absolute status binary <RETURN> display trace mnemonic <RETURN>...
Page 355: 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 <RETURN> end release_system <RETURN> See Also The "Exiting the Emulator/Analyzer Interface" section in Chapter 3, "Starting and Exiting HP 64700 Interfaces".
Page 356: Expr
Chapter 11: Emulator/Analyzer Interface Commands --EXPR-- --EXPR-- An expression is a combination of numeric values, symbols, operators, and parentheses used to specify address, data, status, executed address, or any other value used in the emulation commands. The function of an expression (--EXPR--) is to let you define the address, data, status, or executed address expression that fits your needs.
Page 357 Chapter 11: Emulator/Analyzer Interface Commands --EXPR-- <NUMBER> This can be an integer in any base (binary, octal, decimal, or hexadecimal), or can be a string of characters enclosed with quotation marks. <OP> This represents an algebraic or logical operand and may be any of the following (in order of precedence): modulo multiplication...
Page 358 Chapter 11: 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...
Page 359: Fcode
Chapter 11: Emulator/Analyzer Interface Commands FCODE FCODE The function code is used to define the address space being referenced. Select the appropriate function code from those listed below. Data space. none Causes the emulator to ignore the function code bits. Program space.
Page 360 Chapter 11: Emulator/Analyzer Interface Commands FCODE Examples To copy a portion of user data memory to a file: copy memory fcode ud 1000H thru 1fffH to mymem <RETURN> To modify a location in program memory: modify memory fcode p 5000h long to 12345678h <RETURN>...
Page 361: Forward
Chapter 11: Emulator/Analyzer Interface Commands forward forward This command lets you forward commands to other HP 64700 interfaces that use the "emul700dmn" daemon process to coordinate actions between the interfaces. Sends messages to the Broadcast Message Server or BMS. <COMMAND>...
Page 362: Help
Chapter 11: Emulator/Analyzer Interface Commands help help Displays information about system and emulation features during an emulation session. Typing help or ? displays softkey labels that list the options on which you may receive help. When you select an option, the system will list the information to the screen.
Page 363 Chapter 11: Emulator/Analyzer Interface Commands help copy reset stop_trace software_breakpoints registers expressions (--EXPR--) symbols (--SYMB--) specify cmb_execute wait pod_command bbaunload coverage performance_measurement_initialize performance_measurement_run performance_measurement_end...
Page 364: Load
Chapter 11: Emulator/Analyzer Interface Commands load load This command transfers absolute files from the host computer into emulation or target system RAM. With other parameters, the load command can load emulator configuration files, trace records, trace specifications, or symbol files. The absolute file contains information about where the file is stored.
Page 365 Chapter 11: Emulator/Analyzer Interface Commands load The parameters are as follows: configuration This option specifies that a previously created emulation configuration file will be loaded into the emulator. You can follow this option with a file name. Otherwise the previously loaded configuration will be reloaded. emul_mem Loads only those portions of the absolute file that reside in memory ranges mapped as emulation memory.
Page 366: Log_Commands
Chapter 11: Emulator/Analyzer Interface Commands log_commands log_commands This command allows you to record commands that are executed during an emulation session. 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 367: Modify
Chapter 11: 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 368: Modify Configuration
Chapter 11: 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 369: Modify Keyboard_To_Simio
Chapter 11: 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 softkey labeled "suspend"...
Page 370: Modify Memory
Chapter 11: 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. Modify a series of memory locations by specifying the address of the first location in the series to be modified, and the values to which the contents of that location and successive locations are to be changed.
Page 371 Chapter 11: 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 372 Chapter 11: Emulator/Analyzer Interface Commands modify memory <STRING> Quoted ASCII string including special characters as follows: null newline horizontal tab backspace carriage return form feed backslash single quote \’ bit pattern \ooo (where ooo is an octal number) 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 373: Modify Register
Chapter 11: 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 374: Modify Software_Breakpoints
Chapter 11: Emulator/Analyzer Interface Commands modify software_breakpoints modify software_breakpoints This command changes the specification of software breakpoints. Software breakpoints provide a way to accurately stop the execution of your program at one or more instruction locations. When a software breakpoint is set, the instruction that is normally at that location is replaced with a TRAP instruction.
Page 375 Chapter 11: Emulator/Analyzer Interface Commands modify software_breakpoints The parameters are as follows: clear This option erases the specified breakpoint address. If no breakpoints are specified in the command, all currently specified breakpoints are cleared. disable This option turns off the software breakpoint capability. enable This option allows you to modify the software breakpoint specification.
Page 376: Performance_Measurement_End
Chapter 11: Emulator/Analyzer Interface Commands performance_measurement_end performance_measurement_end This command stores data previously generated by the performance_measurement_run command, in a file named "perf.out" in the current working directory. The file named "perf.out" is overwritten each time this command is executed. Current measurement data existing in the emulation system is not altered by this command.
Page 377: Performance_Measurement_Initialize
Chapter 11: Emulator/Analyzer Interface Commands performance_measurement_initialize performance_measurement_initialize This command sets up performance measurements. The emulation system will verify whether a symbolic database has been loaded. If a symbolic database has been loaded, the performance measurement is set up with the addresses of all global procedures and static symbols. If a valid database has not been loaded, the system will default to a predetermined set of addresses, which covers the entire emulation processor address range.
Page 378 Chapter 11: Emulator/Analyzer Interface Commands performance_measurement_initialize 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). <FILE> This represents a file you specify to supply user-defined address or time ranges to the emulator.
Page 379: Performance_Measurement_Run
Chapter 11: Emulator/Analyzer Interface Commands performance_measurement_run performance_measurement_run This command begins a performance measurement. This command causes the emulation system to reduce trace data contained in the emulation analyzer, which will then be used for analysis by the performance measurement software. The default is to process data presently contained in the analyzer.
Page 380: Pod_Command
Chapter 11: Emulator/Analyzer Interface Commands pod_command pod_command Allows you to control the emulator through the direct HP 64700 Terminal Interface. The HP 64700 Card Cage contains a low-level Terminal Interface, which allows you to control the emulator’s functions directly. You can access this interface using pod_command.
Page 381: Pod_Command
Chapter 11: Emulator/Analyzer Interface Commands pod_command The parameters are as follows: keyboard Enters an interactive mode where you can simply type Terminal Interface commands (unquoted) on the command line. Use display pod_command to see the results returned from the emulator. <POD_CMD>...
Page 382: Qualifier
Chapter 11: 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.
Page 383 Chapter 11: Emulator/Analyzer Interface Commands QUALIFIER Examples trace only address mod_name:read_input <RETURN> trace only address range mod_name:read_input thru output <RETURN> trace only address range mod_name:clear thru read_input <RETURN> See Also The trace command.
Page 384: Range
Chapter 11: 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.
Page 385 Chapter 11: Emulator/Analyzer Interface Commands RANGE This specifies that the analyzer search for the logical "not" of the specified range (this includes any addresses not in the specified 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.
Page 386: Reset
Chapter 11: Emulator/Analyzer Interface Commands reset reset This command suspends target system operation and reestablishes initial emulator operating parameters, such as reloading control registers. The reset signal is latched when the reset command is executed and released by either the run or break command. See Also The break and run commands.
Page 387: 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 388 Chapter 11: Emulator/Analyzer Interface Commands absolute file containing a transfer address has just been loaded, execution starts at that address. 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.
Page 389: Sequencing
Chapter 11: Emulator/Analyzer Interface Commands SEQUENCING SEQUENCING Lets you specify complex branching activity that must be satisfied to trigger the analyzer. Sequencing provides you with parameters for the trace command that let you define branching conditions for the analyzer trigger. You are limited to a total of seven sequence terms, including the trigger, if no windowing specification is given.
Page 390 Chapter 11: 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. <#TIMES>...
Page 391: Set
Chapter 11: Emulator/Analyzer Interface Commands...
Page 392 Chapter 11: Emulator/Analyzer Interface Commands Controls the display format for the data, memory, register, software breakpoint, and trace displays.With the set command, you can adjust the display format results for 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 393 Chapter 11: 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 394 Chapter 11: 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 option prevents inclusion of source lines in the trace and memory mnemonic display lists.
Page 395 Chapter 11: Emulator/Analyzer Interface Commands <VALUE> Specifies the logical value to which a particular UNIX environment variable is to be set. width source This allows you to specify the width (in columns) of the source lines in the memory mnemonic display. To adjust the width of the source lines in the trace display, increase the widths of the label and/or mnemonic fields.
Page 396: Specify
Chapter 11: Emulator/Analyzer Interface Commands specify specify This command prepares a run or trace command for execution, and is used with the cmb_execute command. When you precede a run or trace command with specify, the system does not execute your command immediately. Instead, it waits until until an EXECUTE signal is received from the Coordinated Measurement Bus or until you enter a cmb_execute command.
Page 397 Chapter 11: Emulator/Analyzer Interface Commands specify The parameters are as follows: disable This option turns off the specify condition of the run process. from --EXPR-- This is used with the specify run from command. An expression is a combination of numeric values, symbols, operators, and parentheses, specifying a memory address.
Page 398: State
Chapter 11: 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.
Page 399 Chapter 11: Emulator/Analyzer Interface Commands STATE The default STATE expression type is address. 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.
Page 400: Step
Chapter 11: Emulator/Analyzer Interface Commands step step The step command allows sequential analysis of program instructions by causing the emulation processor to execute a specified number of assembly instructions or source lines. You can display the contents of the processor registers, trace memory, and emulation or target memory after each step command.
Page 401 Chapter 11: 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 402: Stop_Trace
Chapter 11: Emulator/Analyzer Interface Commands stop_trace stop_trace This command terminates the current trace and stops execution of the current measurement. The analyzer stops searching for trigger and trace states. If trace memory is empty (no states acquired), nothing will be displayed. See Also The trace command.
Page 403: Store
Chapter 11: Emulator/Analyzer Interface Commands store store This command lets you save the contents of specific memory locations in an absolute file. You also can save trace memory contents in a trace file. The store command creates a new file with the name you specify, if there is not already an absolute file with the same name.
Page 404 Chapter 11: Emulator/Analyzer Interface Commands store memory This causes selected memory locations to be stored in the specified HP64000 format file with a .X extension. thru This allows you to specify that ranges of memory be stored. Use this in the store memory command to separate memory locations from the file identifier.
Page 405: Symb
Chapter 11: Emulator/Analyzer Interface Commands --SYMB-- --SYMB--...
Page 406 Chapter 11: 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 407 Chapter 11: 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 408 Chapter 11: Emulator/Analyzer Interface Commands --SYMB-- Examples The following short C code example should help illustrate how symbols are maintained by SRU and referenced in your emulation commands. File /users/dave/control.c: int *port_one; main () int port_value; port_ptr = port_one; port_value = 10; process_port (port_ptr, port_value);...
Page 409 Chapter 11: Emulator/Analyzer Interface Commands --SYMB-- The symbol tree as built by SRU might appear as follows, depending on the object module format and compiler used: Note that SRU does not build tree nodes for variables that are dynamically allocated on the stack at run-time, such as i and j within the delay () procedure.
Page 410 Here are some examples of referencing different symbols in the above programs: control.c:main control.c:port_one porthand.c:utils.c:delay The last example above only works with IEEE-695 object module format; the HP object module format does not support referencing of include files that generate program code. porthand.c:process_port.i porthand.c:process_port.BLOCK_1.i...
Page 411 Chapter 11: Emulator/Analyzer Interface Commands --SYMB-- For example, if you set the current working symbol as cws porthand.c:process_port.BLOCK_1 and made a reference to symbol i2, the retrieval utilities attempt to find a symbol called porthand.c:process_port.BLOCK_1.i2 which would not be found. The symbol utilities would then strip BLOCK_1 from the current working symbol, yielding porthand.c:process_port.i2 which is a valid symbol.
Page 412: Sync_Sim_Registers
Chapter 11: Emulator/Analyzer Interface Commands sync_sim_registers sync_sim_registers The sync_sim_registers command synchronizes the 68360’s system integration module (SIM) registers to the emulator’s EMSIM registers. The parameters are as follows: from_68360 Copies the microprocessor’s SIM registers into the emulator’s EMSIM registers. _to_config to_68360 Copies the emulator’s EMSIM registers into the microprocessor’s SIM registers.
Page 413: Trace
Chapter 11: 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. You can perform analysis tasks either by starting a program run and then specifying the trace parameters, or by specifying the trace parameters first and then initiating the program run.
Page 414 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 415 Chapter 11: Emulator/Analyzer Interface Commands trace QUALIFIER This determines which of the traced states will be stored or prestored in the trace memory for display upon completion of the trace. Events can be 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.
Page 416: Trigger
Chapter 11: Emulator/Analyzer Interface Commands TRIGGER TRIGGER This parameter lets you define where the analyzer will begin tracing program information during a trace measurement. A trigger is a QUALIFIER. When you include the occurs option, you can specify the trigger to be a specific number of occurrences of a QUALIFIER (see the QUALIFIER syntax diagram).
Page 417 Chapter 11: Emulator/Analyzer Interface Commands TRIGGER Examples trace after MAIN <RETURN> trace after 1000H then data 5 <RETURN> Also see the trace command examples. See Also The trace command. Also, refer to Chapter 9, "Making Coordinated Measurements".
Page 418: Wait
Chapter 11: Emulator/Analyzer Interface Commands wait wait This command allows you to present delays to the system. The wait command can be an enhancement to a command file, or to normal operation at the main emulation level. Delays allow the emulation system and target processor time to reach a certain condition or state before executing the next emulation command.
Page 419 Chapter 11: Emulator/Analyzer Interface Commands wait seconds This causes the system to pause for a specific number of seconds. <TIME> This prompts you for the number of seconds to insert for the delay. 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.
Page 420: Window
Chapter 11: Emulator/Analyzer Interface Commands WINDOW WINDOW Lets you select which states are stored by the analyzer. WINDOW allows you to selectively toggle analyzer operation. When enabled, the analyzer will recognize sequence terms, trigger terms, and will store states. When disabled, the analyzer is effectively off, and only looks for a particular enable term.
Page 421 Chapter 11: Emulator/Analyzer Interface Commands WINDOW Examples trace enable _rand disable 0ecch <RETURN> See Also The trace command and the SEQUENCING and QUALIFIER syntax descriptions.
Page 423: 12 Emulator Error Messages
Emulator Error Messages This chapter lists error and status messages that you may see when using the emulator. The causes of the messages are given along with actions you can take to overcome error conditions.
Page 424: Emulator Error Messages
Chapter 12: Emulator Error Messages Analyzer Break (Async_Stat 613) The emulator/analyzer interface provides feedback to the user through messages that are displayed on the STATUS line. The messages in this chapter are listed in alphabetical order. Some messages have error numbers assigned to them. These error numbers are shown in parenthesis at the end of the message text in this chapter.
Page 425 Chapter 12: Emulator Error Messages Ascii symbol download failed (Error 881) Ascii symbol download failed (Error 881) Cause: This error occurs because the system is out of memory. Action: You must either reduce the number of symbols to be loaded, or free up additional system space and try the download again.
Page 426 Chapter 12: Emulator Error Messages Break condition configuration aborted (Error 653) Break condition configuration aborted (Error 653) Cause: Occurs when <CTRL> c is entered during bc display. Break condition must be specified (Error 652) Cause: You tried to define a breakpoint without specifying the break condition to enable or disable.
Page 427 Chapter 12: Emulator Error Messages Breakpoint remove aborted (Error 669) Breakpoint remove aborted (Error 669) Cause: Occurs when <CTRL> c is entered when clearing a software breakpoint. Bus activity required to access emulation memory (Error 148) Cause: You entered a command that requires the emulator to access emulation memory, but there is no bus activity so the emulator cannot access emulation memory.
Page 428 Chapter 12: Emulator Error Messages Chip select 0 must have tcyc >=1 for map term 1 (Error 147) Chip select 0 must have tcyc >=1 for map term 1 (Error 147) Cause: You tried to enter a TCYC3-0 specification that is incompatible with the present maximum bus speed and memory type.
Page 429 Chapter 12: Emulator Error Messages Chip select 0 must have tcyc >=2 for map term 1 (Error 147) Chip select 0 must have tcyc >=2 for map term 1 (Error 147) Cause: You tried to enter a TCYC3-0 specification that is incompatible with the present maximum bus speed and memory type.
Page 430 Chapter 12: Emulator Error Messages Clock speed not available with current count qualifier (Error 1239) Clock speed not available with current count qualifier (Error 1239) Cause: This error occurs when you attempt to specify a fast (F) or very fast (VF) maximum qualified clock speed when the analyzer is counting time.
Page 431 Conflict between expected and received symbol information (Error 880) Cause: The information you supplied in a symbol definition is not what the HP 64700 expected to receive. Action: Make sure that all symbols in the symbol file are defined correctly. Verify that there are no spaces in the address definitions for the symbols in the symbol file being downloaded.
Page 432 Chapter 12: Emulator Error Messages Conflicting disassembler option: <option> (Error 1000) Conflicting disassembler option: <option> (Error 1000) Cause: This error occurs when you attempt to specify inverse assembly options that are not allowed with each other. Action: Do not use conflicting inverse assembly options in the same trace list command.
Page 433 Chapter 12: Emulator Error Messages Count qualifier not available with current clock speed (Error 1240) Count qualifier not available with current clock speed (Error 1240) Cause: This error occurs when you attempt to specify the “time” count qualifier when the current maximum qualified clock speed is fast (F) or very fast (VF). This error also occurs when you attempt to specify a “state”...
Page 434 Cause: The program has tried to access emulation memory configured as DRAM, which is not supported in emulation memory. Action: Refer to "If emulation memory addressing appears incorrect" in the "Solving Problems" chapter of the MC68360 Emulator/Analyzer (HP 64780A) Installation/Service/Terminal Interface User’s Guide. Emulation memory access failed (Error 702) Cause: This message is displayed if the emulator was unable to perform the requested operation on memory mapped to the target system.
Page 435 Chapter 12: Emulator Error Messages Emulator terminated hung bus cycle: 010000000@sp byte read (Error 167) Emulator terminated hung bus cycle: 010000000@sp byte read (Error 167) Cause: A hung bus cycle occurred during a memory access operation. This message indicates that the emulator detected the hung bus cycle and terminated it. Action: Retry the command that caused the hung bus cycle.
Page 436 Cause: The system has encountered an error from which it cannot recover. Action: Write down the sequence of commands that caused the error. Cycle power on the emulator and reenter the commands. If the error repeats, call your local HP Sales Office for assistance.
Page 437 Chapter 12: Emulator Error Messages Foreground monitor range(4Kbytes) not within map term 1 (Error 141) Foreground monitor range(4Kbytes) not within map term 1 (Error 141) Cause: You tried to allocate too small a space for map term 1 or you tried to place map term 1 in target memory when you were using a foreground monitor.
Page 438 Chapter 12: Emulator Error Messages Illegal width for symbol display: <width> (Error 1138) Illegal width for symbol display: <width> (Error 1138) Cause: This error occurs when the value specified for the trace format address field width is not valid. Action: Enter your command again, and specify the width of the address field for symbol display within the range of 4 to 55.
Page 439 Chapter 12: Emulator Error Messages Invalid address: <address> (Error 310) Invalid address: <address> (Error 310) You specified an invalid address value as an argument to a command (other than an analyzer command). 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 440 Chapter 12: Emulator Error Messages Invalid base: <base> (Error 319) Invalid base: <base> (Error 319) Cause: This error occurs if you have specified an invalid base when entering a command to change the format of the trace list. Action: Use the help screens to view the valid base options. Invalid clock channel: <name>...
Page 441 Invalid memory map attribute: <attribute> (Error 731) Cause: The only valid memory map attributes for the MC68360 emulator are Processor DSACKs, Target DSACKs, 32 Bit Emulation DSACKs, 16 Bit Emulation DSACKs, and 8 Bit Emulation DSACKs.
Page 442 Chapter 12: Emulator Error Messages Invalid number of arguments (Error 308) Invalid number of arguments (Error 308) Cause: You either entered too many options to a command or an insufficient number of options. Action: Reenter the command with correct syntax. Use online help by typing help <command>.
Page 443 Chapter 12: Emulator Error Messages Invalid question in ascii file; configuration aborted Invalid question in ascii file; configuration aborted Cause: A configuration file (filename.EA) being loaded into the emulator has at least one question that is not valid for this emulator. Action: Display the emulator error log to see which question(s) were invalid.
Page 444 Chapter 12: Emulator Error Messages Label not defined: <label> (Error 321) Label not defined: <label> (Error 321) Cause: You entered an analyzer expression in which the label was not present in the analyzer label list. For example, if the label list includes address, data, and status, you might have entered something such as lowerdata=24t.
Page 445 Message overflow (Status 153) 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. Missing option or operand (Error 313) Cause: You have omitted a required option to the command.
Page 446 Cause: You tried to add more mapper terms than are available for this emulator. For example, with the MC68360 emulator, there are only eight terms. If you had already defined memory types for these terms, then tried to map another term, you would see the above error message.
Page 447 Chapter 12: Emulator Error Messages Number must be a multiple of 1000H Number must be a multiple of 1000H Cause: A number other than a multiple of 1000H was entered for the base address of the foreground monitor during configuration. Action: Use a number that is a multiple of 1000H for the base address of the foreground monitor.
Page 448 Records expected: <number>; records received: <number> (Error 401) Cause: The HP 64700 received a different number of records than it expected to receive during a transfer operation. Action: Retry the transfer. If the failure is repeated, make sure the data communications parameters are set correctly on the host and on the HP 64700.
Page 449 Chapter 12: Emulator Error Messages Register access aborted (Error 630) Register access aborted (Error 630) Cause: Occurs when a <CTRL> c is entered during register display. Register class cannot be modified: <register class> (Error 637) Cause: You tried to modify a register class instead of an individual register. You can only modify individual registers.
Page 450 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, line noise may cause the failure.
Page 451 Action: Retry the transfer. If it fails again, make sure the data communications parameters are set correctly on the host and on the HP 64700. Also make sure you are using the correct command options, both on the HP 64700 and on the host.
Page 452 Chapter 12: Emulator Error Messages Stack pointer is odd (Error 80) Stack pointer is odd (Error 80) Cause: You tried to modify the stack pointer to an odd value and the emulator expects the stack to be aligned on a word boundary. Action: Modify the stack pointer to an even value.
Page 453 Chapter 12: Emulator Error Messages Symbol cannot contain wildcard in this context (Error 878) Symbol cannot contain wildcard in this context (Error 878) Cause: You tried to enter a global, local, or user symbol name using the wildcard (*) incorrectly. Action: When you enter the symbol name again, include the wildcard (*) at the end of the symbol.
Page 454 Chapter 12: Emulator Error Messages Trigger position changed to accomodate trig1, trig2 delay spec (Status 1203) Trigger position changed to accomodate trig1, trig2 delay spec (Status 1203) Cause: The terminal interface tgout (trigger output) command provides a delay feature that allows for driving of the trig1 and/or trig2 signals a specified number of states after trigger or before trace complete.
Page 455 Chapter 12: Emulator Error Messages Trigger position out of bounds: <bounds> (Error 1202) Trigger position out of bounds: <bounds> (Error 1202) Cause: This error occurs when you attempt to specify a number of lines to appear either before or after the trigger which is greater than the number of lines allowed. The <bounds>...
Page 456 Chapter 12: Emulator Error Messages Unable to modify trace vector to <value> for single stepping (Error 156) Unable to modify trace vector to <value> for single stepping (Error 156) Cause: You tried to single step, and the emulator detected the trace vector was not set properly and the emulator was unable to modify the vector table because it was not located in emulation memory or target RAM.
Page 457 Chapter 12: Emulator Error Messages Unable to load new memory map; old map reloaded (Error 725) Unable to load new memory map; old map reloaded (Error 725) Cause: There is not enough emulation memory left for this request. Action: Reduce the amount of emulation memory requested. Unable to modify register: <register>=<value>...
Page 458 Chapter 12: Emulator Error Messages Unable to reset (Error 640) Unable to reset (Error 640) Cause: Target condition or system failure. Action: Check target system, and run performance verification (pv command). Unable to run (Error 610) Cause: Run has failed for some reason. For example, this message will appear if the emulator cannot write to stack, which is required to run.
Page 459 Chapter 12: Emulator Error Messages Unmatched quote encountered (Error 820) Unmatched quote encountered (Error 820) Cause: In entering a string, such as with the echo command, you didn’t properly match the string delimiters (either ‘‘ or “”). For example, you might have entered echo “set S1 to off Action: Reenter the command and string, making sure to properly match opening and closing delimiters.
Page 461 Part 4 Concept Guide...
Page 462 Part 4 Concept Guide In This Part Part 4 of this book explains concepts and shows you how to apply them to advanced tasks.
Page 463 Concepts of the EMSIM and EMRAM...
Page 464 Chapter 13: Concepts of the EMSIM and EMRAM Concepts of the EMSIM and EMRAM This chapter provides conceptual information on the EMSIM and EMRAM...
Page 465: Concepts Of The Emsim And Emram
Chapter 13: Concepts of the EMSIM and EMRAM Concepts of the EMSIM and EMRAM The 68360 processor provides 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).
Page 466 Chapter 13: Concepts of the EMSIM and EMRAM 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 32-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 467: Concepts Of The Emram
Chapter 13: Concepts of the EMSIM and EMRAM Concepts of the EMRAM The 68360 processor has internal RAM modules. These internal RAM modules can be used like any other system RAM; that is, their memory hardware can be assigned to support any desired address range within the 68360 address space. The address range that a particular internal RAM module will support, and the qualifiers that might additionally be assigned to that address range are defined by the values contained within registers in the Memory Controller of the processor.
Page 468: Emsim/Emram Utility Command
Chapter 13: Concepts of the EMSIM and EMRAM The external-bus decoder within the emulator will automatically decode these "show" bus cycles if the following two conditions are met. Condition 1: Show cycles are enabled as described above. Condition 2: The /DS signal is available external to the processor. If the pin that carries the /DS signal is programmed as a portC I/O pin, the processor is not able to indicate a show cycle and the analyzer will not be able to display show cycles in a trace.
Page 469 Chapter 13: Concepts of the EMSIM and EMRAM Display→SIM Register Differences This shows current differences between the SIM registers and the EMSIM registers. This presents a list of all registers whose values are different between the SIM and the EMSIM. Use this to compare the programming between the SIM and EMSIM.
Page 470 This displays the present mode of clock for the 68360 target system. This mode is set by installation of a clock module in the clock module socket on the emulation probe. Refer to the Hewlett-Packard MC68360 Installation/Service/Terminal Interface User’s Guide for details.
Page 471 Part 5 Installation and Service Guide...
Page 472 The Hewlett-Packard M68360 Emulator/Analyzer Installation/Service/Terminal Interface User’s Guide shows you how to: • Connect the emulator into an MC68360 target system and overcome the differences between the specifications and characteristics of the target microprocessor and those of the emulator. •...
Page 473 Installation...
Page 474 Minimum HP 9000 Hardware and System Requirements The following is a set of minimum hardware and system recommendations for operation of the Graphical User Interface on HP 9000 Series 300/400 and Series 700 workstations. HP-UX For Series 9000/300 and Series 9000/400 workstations, the minimum supported version of the operating system is 7.03 or later.
Page 475 Chapter 14: 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 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.
Page 476: Connecting The Hp 64700 To A Computer Or Lan
Computer or LAN Refer to the HP 64700 Series Installation/Service Guide for instructions on connecting the HP 64700 to a host computer (via RS-422 or RS-232) or LAN and setting the HP 64700’s configuration switches. (RS-422 and RS-232 are only...
Page 477: Installing Hp 9000 Software
1 Install the software from the media. 2 Verify the software installation. 3 Start the X server and the Motif Window Manager (mwm), or start HP VUE. 4 Set the necessary environment variables. Step 1. Install the software from the media The tape that contains the Graphical User Interface software may contain several products.
Page 478 /etc/update at the HP-UX prompt. 6 When the HP-UX update utility main screen appears, confirm that the source and destination devices are correct for your system. Refer to the information on updating HP-UX in your HP-UX documentation if you need to modify these values.
Page 479: Step 2. Verify The Software Installation
X window manager (if you are not currently running an X server). If you plan to run the Motif Window Manager (mwm), or similar window manager, continue with Step 3a of these instructions. If you plan to run HP VUE, skip to Step 3b of these instructions.
Page 480: Step 3A. Start The X Server And The Motif Window Manager (Mwm)
Step 3b. Start HP VUE If you are running the X server under HP VUE and have not started HP VUE, do so now. HP VUE is a window manager for the X Window system. The X server is executing underneath HP VUE.
Page 481: Step 4. Set The Necessary Environment Variables
-s /users/team/usr/hp64000 /usr/hp64000 If you do not wish to establish a symbolic link, you can set the HP64000 variable to the full path that contains the HP 64000 software. Again, if you installed relative to /users/team, you would enter...
Page 482 3 Set the PATH environment variable to include the usr/hp64000/bin directory by entering PATH=$PATH:$HP64000/bin; export PATH Including usr/hp64000/bin in your PATH relieves you from prefixing HP 64700 executables with the directory path. 4 Set the MANPATH environment variable to include the usr/hp64000/man and...
Page 483: Installing Sun Sparcsystem Software
Chapter 14: Installation Installing Sun SPARCsystem Software Installing Sun SPARCsystem Software This section shows you how to install the Graphical User Interface on Sun SPARCsystem workstations. These instructions also tell you how not to install the Graphical User Interface if you want to use just the conventional Softkey Interface. This section shows you how to: 1 Install the software from the media.
Page 484: Step 2. Start The X Server And Openwindows
Chapter 14: Installation Installing Sun SPARCsystem Software Step 2. Start the X server and OpenWindows If you are not already running the X server, do so now. The X server is required to run the Graphical User Interface because it is an X application. Note that if you see windows on screen, skip this step.
Page 485 Consult the OpenWindows documentation for an explanation of the DISPLAY environment variable. 2 Set the HP64000 environment variable. For example, if you installed the HP 64000 software relative to the root directory, "/", you would enter setenv HP64000 /usr/hp64000 If you installed the software relative to a directory other than the root directory, it is strongly recommended that you use a symbolic link to make the software appear to be under /usr/hp64000.
Page 486: Step 4. Verify The Software Installation
Chapter 14: Installation Installing Sun SPARCsystem Software 4 Set the MANPATH environment variable to include the usr/hp64000/man and usr/hp64000/contrib/man directories by entering setenv MANPATH ${MANPATH}:${HP64000}/man setenv MANPATH ${MANPATH}:${HP64000}/contrib/man Including these directories in your MANPATH variable lets you access the on-line "man"...
Page 487: Step 5. Map Your Function Keys
Chapter 14: Installation Installing Sun SPARCsystem Software Step 5. Map your function keys If you are using the conventional Softkey Interface, map your function keys by following the steps below. 1 Copy the function key definitions by typing: cp $HP64000/etc/ttyswrc ~/.ttyswrc This creates key mappings in the .ttyswrc file in your $HOME directory.
Page 488: Verifying The Installation
1 Display the 64700tab.net file by entering more /usr/hp64700/etc/64700tab.net at the HP-UX prompt. 2 Page through the file until you find the emulator you are going to use. This step will require some matching of information to an emulator, but it should not be difficult to determine which emulator you want to address.
Page 489: Step 2. Start The Interface With The Emul700 Command
1 Apply power to the emulator you wish to access after making sure the emulator is connected to the LAN or to your host system. On the HP 64700 Series Emulator, the power switch is located on the front panel near the bottom edge. Push the switch in to turn power on to the emulator.
Page 490 Chapter 14: Installation Verifying the Installation You should include an ampersand ("&") with the command to start the Graphical User Interface as a background process. Doing so frees the terminal window where you started the interface so that the window may still be used. 5 Optionally start additional Graphical User Interface windows into the same emulation session by repeating the previous step.
Page 491 Chapter 14: Installation Verifying the Installation...
Page 492: Step 3. Exit The Graphical User Interface
Chapter 14: Installation Verifying the Installation Step 3. Exit the Graphical User Interface 1 Position the mouse pointer over the pulldown menu named "File" on the menu bar at the top of the interface screen. 2 Press and hold the command select mouse button until the File menu appears. 3 While continuing to hold the mouse button down, move the mouse pointer down the menu to the "Exit"...
Page 493: 15 Installing/Updating Emulator Firmware
Installing/Updating Emulator Firmware...
Page 494 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 Chapter 14, "Installation".
Page 495: To Update Emulator Firmware With "Progflash
• Enter the progflash -v <emul_name> <product> 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 496 2 em80960 i80960 3 em68360 m68360 Number of Emulator to Update? (intr (usually cntl C or DEL) to abort) To update firmware in the HP 64700 that contains the 68360, emulator, enter "3". Product 1 64700 2 64703/64704/64706/64740 3 64744...
Page 497 Chapter 15: Installing/Updating Emulator Firmware To update emulator firmware with "progflash" Config file path is /usr/hp64000/inst/update/64780.cfg System firmware revision required = A.03.00 ROM identifier address = 2FFFF0H Required hardware identifier = 1FF4H Control ROM start address = 280000H Control ROM size = 40000H Control ROM width = 16 Programming voltage control address = 2FFFFEH Programming voltage control value = FFFFH...
Page 498: To Display Current Firmware Version Information
To display current firmware version information • Use the Terminal Interface ver command to view the version information for firmware currently in the HP 64700. When using the Graphical User Interface or Softkey Interface, you can enter Terminal Interface commands with the pod_command command. For example: display pod_command <RETURN>...
Page 499: If There Is A Power Failure During A Firmware Update
HP 64700 that will not boot up. Repeat the firmware update process. If the HP 64700 is connected to the LAN in this situation and you are unable to connect to the HP 64700 after the power glitch, try repeating the firmware update...
Page 501 Glossary Absolute Count A count in the trace list count column that indicates the total count accumulated between the displayed state and the trigger state. Absolute File A file consisting of machine-readable instructions in which absolute addresses are used to store instructions, data, or both. These files are generated by the compiler/assembler/linker and are loaded into the emulator.
Page 502 A connector that provides a means for the emulator to drive/receive a trigger signal to/from an external device (such as a logic analyzer, oscilloscope, or HP 64000-UX system). Breakpoint A point at which emulator execution breaks from the target program and begins executing in the monitor.
Page 503 Glossary Command File A file containing a sequence of commands to be executed. Compatible Mode The compatible mode of the deep analyzer configures the analyzer to provide the same memory depth as the 1K analyzer: 1024 states deep when the analyzer is not configured to make a count of states or time during a measurement, and 512 states deep when the analyzer is configured to make a count of states or time during a measurement.
Page 504 Cross Trigger The situation in which the trigger condition of one analyzer is used to trigger another analyzer. Two signals internal to the HP 64700 can be connected through the BNC on the instrumentation card cage to allow cross-triggering between the emulation-bus analyzer and other analyzers.
Page 505 Glossary Downloading The process of transferring absolute files from a host computer into the emulator. Embedded Microprocessor System The microprocessor system which the emulator plugs into. Emulation-Bus Analyzer The internal analyzer that captures emulator bus cycle information synchronously with the processor’s clock signal. Emulation Monitor Program A program that is executed by the emulation processor which allows the emulation controller to access target system resources.
Page 506 Glossary Escape Sequence (transparent mode) A keyboard input consisting of a special sequence of characters, beginning with the escape character (1C hexadecimal). This sequence is used to access an emulator while in transparent mode. When using multiple emulators and transparent mode to access the different emulators, each one must be given a unique escape character.
Page 507 Host Computer A computer to which an HP 64700 Series emulator can be connected. A host computer may run interface programs which control the emulator. Host computers may also be used to develop programs to be downloaded into the emulator.
Page 508 Glossary Memory Mapper Term A number assigned to a specific address range in the memory map. Term numbers are consecutive. Memory Mapping Defining ranges of the processor address space as emulation RAM or ROM, target RAM or ROM, or guarded memory. Monitor Program A program executed by the emulation processor that allows the emulation system controller to access target system resources.
Page 509 Glossary Pass Through Mode See Transparent Mode. PC Interface A program that runs on the HP Vectra and IMB PC/AT compatible computers. This is a friendly interface used to operate an HP 64700 Series emulator. Performance Verification A program that tests the emulator to determine whether the emulation and analysis hardware is functioning properly.
Page 510 Glossary Primary Sequencer Branch Occurs when the analyzer finds the primary branch state specified at a certain level and begins searching for the states specified at the primary branch’s destination level. Qualifier A specification that must be met before an action can be taken by the analyzer.
Page 511 Glossary Remote Configuration The configuration in which an HP 64700 Series emulator is directly connected to a host computer via a single port. Commands are entered (typically from an interface program running on the host computer) and absolute code is downloaded into the emulator through that single port.
Page 512 An analyzer that measures execution of software modules, interaction between software modules, and usage of data points and I/O ports. Standalone Configuration The configuration in which a data terminal is used to control the HP 64700 Series emulator, and the emulator is not connected to a host computer.
Page 513 Storage that is present in the target system. Terminal Interface The command interface present inside the HP 64700 Series emulators that is used when the emulator is connected to a simple data terminal. This interface provides on-line help, command recall, macros, and other features which provide for easy command entry from a terminal.
Page 514 Glossary Trigger The condition that identifies a reference state within an analyzer trace measurement. Trigger also refers to the analyzer signal that becomes active when the trigger condition is found. Trigger signals called trig1 and trig2 are bidirectional signal lines that can be used to coordinate measurement activity between emulators and analyzers installed in the instrumentation card cage, and between instruments connected to the BNC on the rear panel of the card cage.
Page 515 Wait states are typically used when slower memory is implemented. Window A specified rectangular area of virtual space shown on the display in which data can be observed. 1K Analyzer The term "1K analyzer" refers to the HP 64704 Emulation-Bus Analyzer with 1K trace memory.
Page 517 Index absolute files, 344 loading, 110 loading without symbols, 111 storing memory contents into, 111 access size (target memory), 481 action keys, 6 custom, 286 getting 68360 register displays, 142 operation, 61 with command files, 286 with entry buffer, 59, 61 activity measurements (SPMT), 231-245 additional symbols for address, 239 confidence level, 240...
Page 518 BNC accepts only TTL voltage levels, 265 CMB 9-pin port is NOT for RS-232C, 263 do not use probe without pin extender, 31 powering OFF the HP 64700, 30 protect emulator against static discharge, 30 changing column width, 198...
Page 519 Index cmb_execute command, 268, 305 color scheme, 280, 284 columns in main display area, 281 command buttons, 7 command files, 346 other things to know about, 76 passing parameters, 75 command line, 7 Command Recall dialog box, 8 Command Recall dialog box, operation, 70 copy-and-paste to from entry buffer, 60 editing entry area with pop-up menu, 69 editing entry area with pushbuttons, 68...
Page 520 Index configuration context, displaying from configuration window, 93 configuration info copy command, 307 copying to a file, 162 display command, 316-318 configuration, emulator exiting the interface, 95 loading from file, 95 modifying a section, 88 starting the interface, 86 storing, 92 context changing directory in configuration window, 93 changing directory in emulator/analyzer window, 122...
Page 521 Index copy-and-paste (continued) symbol width, 57 to entry buffer, 56 copying breakpoints to a file, 163 configuration info to a file, 162 data values to a file, 162 display area to file, 162 emulator status to a file, 163 error log to file, 163 event log to file, 163 global symbols to file, 163 local symbols to file, 163...
Page 522 Index dialog box, trace options, 187 directory context changing in configuration window, 93 changing in emulator/analyzer window, 122 displaying from configuration window, 93 displaying from emulator/analyzer window, 121 Directory Selection dialog box operation, 61, 64 display area, 7 columns, 281 copying to a file, 162 lines, 281-282 display command, 314-315...
Page 523 Index display trace disassemble_from_line_number command, 189 align_data_from_line option, 192 options, 190 display trace mnemonic command, 189 display trace offset_by command, 201 displaying bit-field values of registers, 142 displays, copying, 307 don’t care digits, 207 don’t care number entries, 207 downloading absolute files, 110 duration measurements (SPMT), 246-254 average time, 251 confidence level, 252...
Page 524 Index emulator, 485 configuring the, 84 device table file, 12, 41-42 multiple start/stop, 267-268 plugging into a target system, 27 running from target reset, 124-125 using the, 104 emulator configuration exiting the configuration interface, 95 load command, 345 loading from file, 95 modify command, 348 modifying a configuration section, 88 starting the configuration interface, 86...
Page 525 Entry Buffer Recall dialog box operation, 62 environment variables (UNIX) HP64KPATH, 78 HP64KSYMBPATH, 386 PATH, 41 Softkey Interface, setting while in, 156 equates, 209 for MC68360, 209 error log copy command, 307 display command, 314 to file, 163 error messages, emulator, 403-439 event log, 45...
Page 526 SPMT measurement with, 235 to file, 163 halfbright, 67-68 hand pointer, 7, 55 hardware HP 9000 memory needs, 454 HP 9000 minimum performance, 454 HP 9000 minimums overview, 454 SPARCsystem memory needs, 455 SPARCsystem minimum performance, 455 SPARCsystem minimums overview, 455...
Page 527 65 hexadecimal number entries, 207 hexadecimal numbers, 207 high level interface, using pod commands within, 222 HP 64700 Operating Environment, minimum version, 455 HP 9000 700 series Motif libraries, 454 HP-UX minimum version, 454 installing software, 457-462...
Page 528 171 keyboard_to_simio, modify command, 349 label scheme, 280, 284 LD_LIBRARY_PATH environment variable, 466 libraries, Motif for HP 9000/700, 454 line numbers (source file), symbol display, 114 lines in main display area, 281-282 load command, 344-345 absolute files, 110...
Page 529 349 memory, 350-352 register, 144, 353 software_breakpoints, 354-355 module duration measurements (SPMT), 246 module usage measurements (SPMT), 246 Motif, HP 9000/700 requirements, 454 mouse buttons, 9 choosing menu items, 52-53 multi-window copy-and-paste from entry buffer, 60 copy-and-paste to entry buffer, 57...
Page 530 207 numerical values, 206 octal numbers, 207 offset addresses in trace list, 201 online help, 73 operating system HP 64700 Series minimum version, 455 HP-UX minimum version, 454 SunOS minimum version, 455 operators, 207 bitwise AND, 207 bitwise OR, 207 integer, 207 unary one’s complement, 207...
Page 531 See software performance measurements performance_measurement_end command, 356 performance_measurement_initialize command, 357-358 performance_measurement_run command, 359 pin extender, 31 platform HP 9000 memory needs, 454 HP 9000 minimum performance, 454 SPARCsystem memory needs, 455 SPARCsystem minimum performance, 455 platform scheme, 280 plug-in, 27...
Page 532 Index RAM/EMRAM concepts, 443-450 range resource, note on, 364 RANGE, in trace command, 364-365 READY, CMB signal, 261 recall buffer, 7 columns, 287 initial content, 287-288 lines, 287 recalling entries, 59 recall, command, 72 dialog box, 70 recursion in SPMT measurements, 246 registers 68360 register displays with action keys, 142 assigning a base address for 68360 registers, 109...
Page 533 Index scheme files (for X resources), 279 color scheme, 280, 284 custom, 284-285 input scheme, 280 label scheme, 280, 284 platform scheme, 280 size scheme, 280 scroll bar, 7 secondary branch expression, 491 select mouse button, 9 sequence definition, 206 sequencer (analyzer), 491 branch, 491 terms, 491...
Page 534 Index softkey pushbuttons, 7 softkeys, 71 software installation for HP 9000, 457-462 installation for SPARCsystems, 463-467 software breakpoints, 129-140 clearing, 138 clearing all, 140 copy command, 308 deactivating, 136 display command, 330 enable/disable, 131 modify command, 354-355 opcode locations, 133, 135...
Page 535 Index software performance measurements (continued) restoring the current measurement, 236, 250 run, 359 running, 255 trace command setup, 233 trace display depth, 233 solving problems, 24 source lines display in trace list, 197 set command, 374 symbol display, 114 source/symbol modes, setting, 153 SPARCsystems installing software, 463-467 minimum system requirements overview, 455...
Page 536 374 --SYMB-- syntax, 385-391 sync_sim_registers command, 392 synchronous measurements, 267 syntax conventions, 301 system requirements HP 64700 minimum version, 455 HP 9000 overview, 454 HP-UX minimum version, 454 OSF/Motif HP 9000/700 requirements, 454 SPARCsystem overview, 455 SunOS minimum version, 455...
Page 537 Index terminal interface, commands used in high level interface, 222 time range file format (SPMT measurements), 249 trace at EXECUTE, 267 continuous stream of execution, 222 copy command, 313 count states, 216 count time, 216 display command, 331-334 display status, 179 displaying count information, 199 displaying without disassembly, 194 introduction, 175-185...
Page 538 Index trace depth, how to change, 180 trace dequeueing,m specifying options, 192 trace disassembly, specifying options, 190 trace display depth, SPMT measurements, 233 source/symbol modes, 153 trace enable command, options, 214 trace expressions address values, 210 data values, 210 range, 211 status values, 210 trace find_sequence command, 212-213 trace list...
Page 539 47 opening additional emulator/analyzer, 45 running the emulator/analyzer interface in multiple, 41 terminal emulation, opening, 165 workstation HP 9000 memory needs, 454 HP 9000 minimum performance, 454 SPARCsystem memory needs, 455 SPARCsystem minimum performance, 455 X client, 278...
Page 541 This Hewlett-Packard system product is warranted against defects in materials and workmanship for a period of 90 days from date of installation. During the warranty period, HP will, at its option, either repair or replace products which prove to be defective.
Page 542 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 warrants that its software and firmware designated by HP for use with an instrument will execute its programming instructions when properly installed on that instrument.
Page 543 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 544 Keep Away From Live Circuits Operating personnel must not remove instrument covers. Component replacement and internal adjustments must be made by qualified maintenance personnel. Do not replace components with the power cable connected. Under certain conditions, dangerous voltages may exist even with the power cable removed. To avoid injuries, always disconnect power and discharge circuits before touching them.
Page 545 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 546 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.

This manual is also suitable for:

Mc68en360 64780a

HP MC68360 User Manual

Part 1 Quick Start Guide

1 Getting Started

Part 2 Using the Emulator

2 Plugging into a Target System

3 Starting and Exiting HP 64700 Interfaces

4 Entering Commands

5 Configuring the Emulator

6 Using the Emulator

7 Using the Emulation-Bus Analyzer

8 Making Software Performance Measurements

9 Making Coordinated Measurements

Part 3 Reference

10 Setting X Resources

11 Emulator/Analyzer Interface Commands

12 Emulator Error Messages

14 Installation

Quick Links

Related Manuals for HP MC68360

Summary of Contents for HP MC68360