Page 1 User’s Guide for the Graphical User Interface HP 64746 68302 Emulation/Analysis...
Page 2 Hewlett-Packard Company. The information contained in this document is subject to change without notice. HP is a trademark of Hewlett-Packard Company. Microtec is a registered trademark of Microtec Research Inc. OSF/Motif and Motif are trademarks of the Open Software Foundation in the U.S.
Page 3 Therefore, do not expect a one-to-one correspondence between product updates and manual revisions. Edition 1 64746-97001, August 1990 Edition 2 64746-97003, December 1990 Edition 3...
Page 4 The HP 64703 Emulation Bus Analyzer meets this requirement, and it has an external analyzer that captures up to 16 channels of external data. You can use the HP 64704 or HP 64794 Emulation Bus Analyzers which have 80 channels; however, these analyzers do not have external analysis channels.
Page 5 Start and stop up to 16 emulators at the same time (up to 32 if modifications are made). • Use the analyzer in one HP 64700 to arm (that is, activate) the analyzers in other HP 64700 card cages or to cause emulator execution in other HP 64700 card cages to break.
Page 6 In This Book This book documents the Graphical User Interface and the Softkey Interface when used with the HP 64746 68302 emulator and the HP 64703/704/706/794 analyzer. It is organized into five parts whose chapters are described below. Part 1. Quick Start Guide Chapter 1 quickly shows you how to use the emulator and analyzer.
Page 7: Table Of Contents
Contents Part 1 Quick Start Guide 1 Getting Started The Emulator/Analyzer Interface — At a Glance The Softkey Interface Softkey Interface Conventions The Graphical User Interface Graphical User Interface Conventions The Getting Started Tutorial Step 1. Start the demo Step 2: Display the program in memory Step 3: Run from the transfer address Step 4: Step high-level source lines Step 5: Display the previous mnemonic display...
Page 8 Contents Part 2 User’s Guide 2 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 To run a command file on interface startup To display the status of emulators...
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 4 Configuring the Emulator...
Page 10 Contents Modifying the General Configuration Items To select the emulator clock source To enable/disable entry into the monitor after configuration To restrict the emulator to real-time runs To turn OFF the restriction to real-time runs To select the inverse assembly syntax Selecting the Emulation Monitor Program To use the background monitor program To use a foreground monitor program...
Page 11 Contents 5 Plugging into a Target System Connecting the Emulator Probe Step 1. Turn OFF power Step 2. Connect the probe to the target system Step 3. Turn ON power If you need a PQFP connector Configuring the Emulator for In-Circuit Operation Step 1.
Page 12 Contents 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 To run programs from the current PC To run programs from an address To run programs from the transfer address To run programs from reset To run programs until an address...
Page 13 Contents Displaying Data Values To display data values To clear the data values display and add a new item To add items to the data values display Changing the Interface Settings To set the source/symbol modes To set the display modes Using System Commands To set UNIX environment variables To display the name of the emulation module...
Page 14 Contents Qualifying Trigger and Store Conditions To qualify the trigger state and position To trigger on a number of occurrences of some state To qualify states stored in the trace To prestore states before qualified store states To change the count qualifier To trace until the analyzer is halted To break emulator execution on the analyzer trigger Using the Sequencer...
Page 15 Contents Duration Performance Measurements To set up the trace command for duration measurements To initialize duration performance measurements To interpret duration measurement reports Running Measurements and Creating Reports To run performance measurements To end performance measurements To create a performance measurement report 9 Using the External State Analyzer Setting Up the External Analyzer To connect the external analyzer probe to the target system...
Page 16 Contents 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 drive the external analyzer trigger signal to the CMB To drive the external analyzer trigger signal to the BNC connector To break emulator execution on signal from CMB To break emulator execution on signal from BNC To break emulator execution on external analyzer trigger...
Page 17 Contents copy memory copy registers copy trace display display data display global_symbols display local_symbols_in display memory display registers display simulated_io display software_breakpoints display trace --EXPR-- FCODE forward help load 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...
Page 18 Contents trace TRIGGER wait WINDOW 13 Error Messages Graphical/Softkey Interface Messages - Unnumbered Graphical/Softkey Interface Messages - Numbered Terminal Interface Messages Emulator Messages 68302 Emulator Messages General Emulator and System Messages Analyzer Messages 14 Specifications and Characteristics Emulator Specifications and Characteristics Processor Compatibility Electrical Physical...
Page 19 Contents Part 5 Installation Guide 16 Installation Installing Hardware Step 1. Install Boards into the HP 64700 Card Cage Step 2. Apply power to the HP 64700 Connecting the HP 64700 to a Computer or LAN Installing HP 9000 Software Step 1.
Page 21: Part 1 Quick Start Guide
Part 1 Quick Start Guide...
Page 22 Part 1...
Page 23: Getting Started
Getting Started...
Page 24: The Emulator/Analyzer Interface - At A Glance
Chapter 1: Getting Started The Emulator/Analyzer Interface — At a Glance When an X Window System that supports OSF/Motif interfaces is running on the host computer, the emulator/analyzer interface is the Graphical User Interface which provides pull-down and pop-up menus, point and click setting of breakpoints, cut and paste, on-line help, customizable action keys and pop-up recall buffers, etc.
Page 25: Softkey Interface Conventions
Chapter 1: Getting Started Status line. Displays the emulator and analyzer status. Also, when error and status messages occur, they are displayed on the status line in addition to being saved in the error log. Command line. Commands are entered on the command line by pressing softkeys (or by typing them in) and executed by pressing the Return key.
Page 26: The Graphical User Interface
Chapter 1: Getting Started The Graphical User Interface Menu bar Action keys Entry buffer Entry buffer recall button. Display area. Scroll bar. Status line. Command line. Command line entry area. Softkey pushbuttons Command buttons. Includes command Cursor buttons for command line area recall button.
Page 27 Chapter 1: Getting Started Entry Buffer. Wherever you see "()" in a pulldown menu, the contents of the entry buffer are used in that command. You can type values into the entry buffer, or you can cut and paste values into the entry buffer from the display area or from the command line entry area.
Page 28: Graphical User Interface Conventions
Chapter 1: Getting Started The command Recall button allows you to recall previous or predefined commands. When you click on the command Recall button, a dialog box appears that allows you to select a command. • Cursor buttons for command line area control. Allow you to move the cursor in the command line entry area forward or backward, clear to the end of the command line, or clear the whole command line entry area.
Page 29 Mouse Button Bindings and Description Bindings: Generic Button Name Description HP 9000 SPARCsystem paste left left Paste from the display area to the entry buffer. command paste middle...
Page 30 Chapter 1: Getting Started The following tables show the default keyboard bindings. Keyboard Key Bindings Generic Key Name HP 9000 Sun SPARCsystem menu select extend char extend char insert insert char insert char delete delete char delete char left-arrow left arrow...
Page 31: The Getting Started Tutorial
• The HP 64746 emulator and HP 64703/704/706/794 analyzer are installed into the HP 64700 Card Cage, the HP 64700 is connected to the host computer, and the Softkey Interface software has been installed as outlined in the "Installation" chapter.
Page 32: Step 1. Start The Demo
"platformScheme" resource setting in the "Xdefaults.emul" file. For example, if the Graphical User Interface will be run on a HP 9000 computer and displayed on a Sun SPARCsystem computer, change the platform scheme to "SunOS".
Page 33: Step 2: Display The Program In Memory
Chapter 1: Getting Started Step 2: Display the program in memory Step 2: Display the program in memory 1 If the symbol "main" is not already in the entry buffer, move the mouse pointer to the entry buffer (notice the flashing I-beam cursor) and type in "main". 2 Choose Display→Memory→Mnemonic ().
Page 34: Step 3: Run From The Transfer Address
Chapter 1: Getting Started Step 3: Run from the transfer address Step 3: Run from the transfer address The transfer address is the entry address defined by the software development tools and included with the program’s symbol information. • Click on the Run Xfer til () action key. Or, using the command line, enter: run from transfer_address until main <RETURN>...
Page 35: Step 4: Step High-Level Source Lines
Chapter 1: Getting Started Step 4: Step high-level source lines Step 4: Step high-level source lines You can step through the program by high-level source lines. The emulator executes as many instructions as are associated with the high-level program source lines.
Page 36: Step 5: Display The Previous Mnemonic Display
Chapter 1: Getting Started Step 5: Display the previous mnemonic display Step 5: Display the previous mnemonic display • Click on the Disp Src Prev action key. Or, using the command line, enter: display memory mnemonic previous_display <RETURN> This command is useful, for example, when you have stepped into a function that you do not wish to look at—you can display the previous mnemonic display and run until the source line that follows the function call.
Page 37: Step 6: Run Until An Address
Chapter 1: Getting Started Step 6: Run until an address Step 6: Run until an address When displaying memory in mnemonic format, a selection in the popup menu lets you run from the current program counter address until a specific source line. •...
Page 38: Step 7: Display Data Values
Chapter 1: Getting Started Step 7: Display data values Step 7: Display data values 1 Position the mouse pointer over "num_checks" in the source line that reads "num_checks++;" and click the paste mouse button (notice "num_checks" is cut and pasted into the entry buffer). 2 Click on the Disp Var () action key.
Page 39: Step 8: Display Registers
Chapter 1: Getting Started Step 8: Display registers Step 8: Display registers You can display the contents of the processor registers. • Choose Display→Registers→basic. Or, using the command line, enter: display registers basic <RETURN>...
Page 40: Step 9: Step Assembly-Level Instructions
Chapter 1: Getting Started Step 9: Step assembly-level instructions Step 9: Step assembly-level instructions You can step through the program one instruction at a time. • To step one instruction from the current program counter, click on the Step Asm action key.
Page 41: Step 10: Trace The Program
Chapter 1: Getting Started Step 10: Trace the program Step 10: Trace the program When the analyzer traces program execution, it looks at the data on the emulation processor’s bus and control signals at each clock cycle. The information seen at a particular clock cycle is called a state.
Page 42 Chapter 1: Getting Started Step 10: Trace the program Notice that now the message on the status line is "Emulation trace complete". This shows the trigger state has been found and the analyzer trace memory has been filled. 5 To view the captured states, choose Display→Trace. Or, using the command line, enter: display trace <RETURN>...
Page 43: Step 11: Display Memory At An Address In A Register
Chapter 1: Getting Started Step 11: Display memory at an address in a register Step 11: Display memory at an address in a register 1 Click on the Disp @REG action key. Or, using the command line, enter the name of the command file: mematreg <RETURN>...
Page 44: Step 12: Patch Assembly Language Code
Step 12: Patch assembly language code The Patch () action key lets you patch code in your program. Note that the HP AxLS 68000 series assembler must be installed in order to use this action key; skip this step if the assembler is not installed.
Page 45 Chapter 1: Getting Started Step 12: Patch assembly language code Notice in the emulator/analyzer interface that the instruction at address "main" has changed. 4 Click on the Patch () action key again. A window running the vi editor again appears, allowing you to modify the patch code that was just created.
Page 46 Chapter 1: Getting Started Step 12: Patch assembly language code 5 Type "main+4 thru main+15" in the entry buffer. By entering an address range in the entry buffer (that is, <address> thru <address>) before clicking on the Patch () action key, you can modify a patch template file which allows you to insert as much or as little code as you wish.
Page 47: Step 13: Exit The Emulator/Analyzer Interface
Chapter 1: Getting Started Step 13: Exit the emulator/analyzer interface Step 13: Exit the emulator/analyzer interface • To exit the emulator/analyzer interface and release the emulator, choose File→Exit→Released. Or, using the command line, enter: end release_system <RETURN>...
Page 49: Part 2 User's Guide
Part 2 User’s Guide...
Page 50 Part 2...
Page 51: Starting And Exiting Hp 64700 Interfaces
Starting and Exiting HP 64700 Interfaces...
Page 52 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 53: Starting The Emulator/Analyzer Interface
If $HP64000/bin is specified in your PATH environment variable (as shown in the "Installation" chapter), you can start the interface with the emul700 <emul_name> command. The "emul_name" is the logical emulator name given in the HP 64700 emulator device table ($HP64000/etc/64700tab.net).
Page 54: To Start The Interface Using The Default Configuration
Chapter 2: Starting and Exiting HP 64700 Interfaces Starting the Emulator/Analyzer Interface Examples To start the emulator/analyzer interface for the 68302 emulator: $ emul700 em68302 <RETURN> The "em68302" in the command above is the logical emulator name given in the HP 64700 emulator device table file ($HP64000/etc/64700tab.net).
Page 55: To Run A Command File On Interface Startup
Chapter 2: 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 56: To Unlock An Interface That Was Left Locked By Another User
Chapter 2: Starting and Exiting HP 64700 Interfaces Starting the Emulator/Analyzer Interface Or, the information may be similar to: em68302 - m68302 running; user = guest@myhost description: M68302 emulation, w/internal analysis, 126Kbytes emul mem user interfaces: xdebug, xemul, xperf, skemul, sktiming internet address: 21.17.9.143...
Page 57: 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 58: To Open The High-Level Debugger Interface Window
Chapter 2: Starting and Exiting HP 64700 Interfaces Opening Other HP 64700 Interface Windows To open the high-level debugger interface window • Choose File→Emul700→High-Level Debugger ... under "Graphic Windows", or enter the emul700 -u xdebug <emul_name> command in another terminal emulation window.
Page 59: Exiting Hp 64700 Interfaces
Exiting HP 64700 Interfaces Exiting HP 64700 Interfaces There are several options available when exiting the HP 764700 interfaces. You can simply close one of the open interface windows, or you can exit the debug session by closing all the open windows. When exiting the debug session, you can lock the emulator so that you can continue later, or you can release the emulation system so that others may use it.
Page 60: To Exit A Debug/Emulation Session
Chapter 2: 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 61: Entering Commands
Entering Commands...
Page 62 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 63: Using Menus, The Entry Buffer, And Action Keys
Chapter 3: 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 64: To Choose A Pulldown Menu Item Using The Mouse (Method 1)
Chapter 3: 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 65: 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 66 Chapter 3: 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 67: To Choose Popup Menu Items
Chapter 3: Entering Commands Using Menus, the Entry Buffer, and Action Keys To choose popup menu items 1 Move the mouse pointer to the area whose popup menu you wish to access. (If a popup menu is available, the mouse pointer changes from an arrow to a hand.) 2 Press and hold the select mouse button.
Page 68: To Place Values Into The Entry Buffer Using The Keyboard
Chapter 3: 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 69 Chapter 3: Entering Commands Using Menus, the Entry Buffer, and Action Keys contains only numbers 0 through 9 and characters "a" through "f") automatically has an "h" appended. Note If you have multiple Graphical User Interface windows open, a copy-and-paste action in any window causes the text to appear in all entry buffers in all windows.
Page 70 Chapter 3: 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 71: To Recall Entry Buffer Values
Chapter 3: 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 72: To Copy-And-Paste From The Entry Buffer To The Command Line Entry Area
Chapter 3: 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 73: To Use The Action Keys
Chapter 3: 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 74 Chapter 3: Entering Commands Using Menus, the Entry Buffer, and Action Keys File Selection From the working directory, you can select an existing file name or specify a new file name. Entry Buffer Recall You can recall a previously used entry buffer text string, a predefined entry buffer text string, or a newly entered entry buffer string, to the entry buffer text area.
Page 75 Chapter 3: 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 76 Chapter 3: 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 77: To Access Help Information
Chapter 3: Entering Commands Using Menus, the Entry Buffer, and Action Keys To access help information 1 Display the Help Index by choosing Help→General Topic... or Help→Command Line..2 Choose a topic of interest from the Help Index. The Help Index lists topics covering operation of the interface as well other information about the interface.
Page 78: Using The Command Line With The Mouse
Chapter 3: 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 79: To Enter A Command
Chapter 3: Entering Commands Using the Command Line with the Mouse Off means the command line is not displayed and you use only the pulldown menus and the action keys to control the interface. The command line area begins just below the status line and continues to the bottom of the emulator/analyzer window.
Page 80: To Edit The Command Line Using The Command Line Pushbuttons
Chapter 3: Entering Commands Using the Command Line with the Mouse To edit the command line using the command line pushbuttons • To clear the command line, click the Clear pushbutton. • To clear the command line from the cursor position to the end of the line, click the Clear to end pushbutton.
Page 81: To Edit The Command Line Using The Command Line Popup Menu
Chapter 3: Entering Commands Using the Command Line with the Mouse To edit the command line using the command line popup menu • To clear the command line: position the mouse pointer within the Command Line entry area; press and hold the select mouse button until the Command Line popup menu appears;...
Page 82: To Recall Commands
Chapter 3: 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 83: Using The Command Line With The Keyboard
Chapter 3: 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 84: To Recall Commands
Chapter 3: Entering Commands Using the Command Line with the Keyboard To recall commands • Press <CTRL>r or <CTRL>b. The most recent 20 commands you enter are stored in a buffer and may be recalled by pressing <CTRL>r. Pressing <CTRL>b cycles forward through the recall buffer. Examples For example, to recall and execute the command prior to the last command: <CTRL>r <CTRL>r <RETURN>...
Page 85: To Access On-Line Help Information
Chapter 3: 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 86: Using Command Files
Chapter 3: 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 87 The only way to pass a parameter containing a space is to enclose the parameter in double quotes (") or single quotes (’). Thus, to pass the parameter HP 9000 to a command file, you can use either "HP 9000" or ’HP 9000’.
Page 88 Chapter 3: 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 89: To Start Logging Commands To A Command File
Chapter 3: 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 90: To Playback (Execute) A Command File
Chapter 3: 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 91: Using Pod Commands
Chapter 3: 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 92: To Display The Pod Commands Screen
Chapter 3: 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 93: 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 94: To Forward Commands To The Software Performance Analyzer
Chapter 3: 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 95: Configuring The Emulator
Configuring the Emulator...
Page 96 Configuring for Operation in the Target System After you plug the emulator into a target system and turn on power to the HP 64700, you need to configure the emulator so that it operates properly with your target system. Map memory. Because the emulator can use target system memory or emulation memory (or both), it is necessary to map ranges of memory so that the emulator knows where to direct its accesses.
Page 97 Chapter 4: Configuring the Emulator emulation memory to the target system causes wait states to be inserted on emulation memory accesses as they would be on target system memory accesses. You specify the synchronization of emulation memory by answering a configuration question to make the specification for all emulation memory and background monitor cycles.
Page 98 Chapter 4: Configuring the Emulator Is there circuitry in the target system that constantly monitors bus cycle execution (for example, memory refresh circuitry or a watchdog timer)? If so, you should drive background cycles to the target system. (Foreground monitor cycles appear at the target interface exactly as if they were bus cycles caused by a user program.) Should bus arbitration be allowed? Generally, the answer to this question will be "yes".
Page 99: Using The Configuration Interface
Chapter 4: 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 100: To Start The Configuration Interface
Chapter 4: Configuring the Emulator Using the Configuration Interface To start the configuration interface • Choose Modify→Emulator Config... from the emulator/analyzer interface pulldown menu. • Using the command line, enter the modify configuration command. The configuration interface main menu (see example below) is displayed. The configuration sections that are presented depend on the hardware and features of your particular emulator.
Page 101 Chapter 4: Configuring the Emulator Using the Configuration Interface Examples The 68302 emulator configuration interface main menu is shown below. Clicking on one of these lines selects a particular configuration section. Clicking this button presents the questions for the selected configuration section.
Page 102: To Modify A Configuration Section
Chapter 4: Configuring the Emulator Using the Configuration Interface To modify a configuration section 1 Start the emulator configuration interface. 2 Click on a section name in the configuration interface main menu, and click the "Modify Section" pushbutton. 3 Use the command line to answer the configuration questions. If you’re using the Softkey Interface: The configuration questions in the "General Items"...
Page 103 Chapter 4: Configuring the Emulator Using the Configuration Interface Each configuration section presents a window similar to the following. The menu bar. Configuration help text display area. Emulator status and error message line. Command line text entry area. Pushbutton softkeys. Command control and cursor control pushbuttons.
Page 104: To Store A Configuration
Chapter 4: Configuring the Emulator Using the Configuration Interface At the last question of a configuration section, you are asked if you wish to return to the main menu. You can click the "next_sec" softkey pushbutton to access the questions in the next configuration section. To recall a configuration question, click the "RECALL"...
Page 105: To Change The Configuration Directory Context
Chapter 4: Configuring the Emulator Using the Configuration Interface Do not modify configurations by editing the ".EA" files. Use the configuration CAUTION interface to modify and save configurations. For more information on how to use dialog boxes, refer to the "To use dialog boxes"...
Page 106: To Display The Configuration Context
Chapter 4: Configuring the Emulator Using the Configuration Interface To display the configuration context • When answering the configuration questions, choose Display→Context... from the pulldown menu. The current directory context and the current configuration files are displayed in a window. Click the "Done" pushbutton when you wish to close the window. To access help information •...
Page 107: To Exit The Configuration Interface
Chapter 4: Configuring the Emulator Using the Configuration Interface To exit the configuration interface • When answering the configuration questions, choose File→Exit... from the pulldown menu (or type <CTRL>x), and click "Yes" in the confirmation dialog box. • From the configuration interface main menu, click the "Exit Window" button, and click "Yes"...
Page 108: Modifying The General Configuration Items
Your target system clock must conform to the specifications for the 68302 microprocessor. The maximum clock speed with the HP 64746 emulator is 20 MHz. When an external clock is selected and the target system power is off, the status line will say "Slow clock".
Page 109: To Enable/Disable Entry Into The Monitor After Configuration
Chapter 4: Configuring the Emulator Modifying the General Configuration Items To enable/disable entry into the monitor after configuration • Answer "yes" or "no" to the "Enter monitor after configuration?". This question allows you to select whether the emulator will be running in the monitor or held in the reset state on completion of the emulator configuration.
Page 110: To Restrict The Emulator To Real-Time Runs
Chapter 4: Configuring the Emulator Modifying the General Configuration Items To restrict the emulator to real-time runs • Answer "yes" to the "Restrict to real-time runs?" question. CAUTION If your target system circuitry is dependent on constant execution of program code, you should restrict the emulator to real-time runs.
Page 111: To Turn Off The Restriction To Real-Time Runs
HP 64902 68000 C Cross Compiler HP 64870 68000/10/20 Assembler/Linker/Librarian The assembly language syntax used by the HP 64845 assembler does not use Motorola assembly language syntax. For example, you use brackets instead of parentheses around address registers and the PC in address register and program counter indirect address modes.
Page 112: Selecting The Emulation Monitor Program
Chapter 4: Configuring the Emulator Selecting the Emulation Monitor Program Selecting the Emulation Monitor Program In order to select the type of monitor program used by the emulator, you must first start the configuration interface and access the "Monitor Type" configuration section (refer to the previous "Using the Configuration Interface"...
Page 113 The monitor program named fmon68302.S should be assembled and linked with the HP 64845 68000/10 Cross Assembler/Linker, and the monitor named Mfmon68302.s should be assembled and linked with the HP 64870 assembler. You may customize the foreground monitor if necessary; however, you must...
Page 114 Chapter 4: Configuring the Emulator Selecting the Emulation Monitor Program system controller. Comments in the monitor program source file detail sections that cannot be changed. Comparison of Background and Foreground Monitor Programs Monitor Program Characteristic Background Foreground Takes up processor memory space Allows the emulator to respond to target system interrupts during monitor execution Can be customized...
Page 115: To Use The Background Monitor Program
Chapter 4: Configuring the Emulator Selecting the Emulation Monitor Program To use the background monitor program 1 Answer "background" to the "Monitor type?" question. 2 Answer "yes" to the "Reset map (change of monitor type requires map reset)?" question. 3 Re-map memory (see the following section on "Mapping Memory"). When you select the background monitor program, a memory overlay is created and the background monitor is loaded into that area.
Page 116: To Use A Foreground Monitor Program
(address ending in 000H or 800H) except 0H (since that’s the location of the vector table). If you are using the HP 64170 memory board with 1 Mbyte memory modules, the base address should be on an 8 Kbyte boundary. An ORG statement in the foreground monitor source file defines the base address.
Page 117 Examples The following examples of how to set up and use a foreground monitor program assume the HP 64870 or HP B1464 68000/08/10/20/302 Assembler/Linker/Librarian is installed on the host computer. To copy the foreground monitor program source file: $ cp $HP64000/monitor/Mfmon68302.s .
Page 118 Chapter 4: Configuring the Emulator Selecting the Emulation Monitor Program To assemble and link the monitor program, enter the following commands (which assume that $HP64000/bin is defined in the PATH environment variable): $ as68k -hL Mfmon68302.s > Mfmon68302.lis <RETURN> $ ld68k -hc Mfmon68302.k -L > Mfmon68302.map <RETURN> Where the "Mfmon68302.k"...
Page 119 Chapter 4: Configuring the Emulator Selecting the Emulation Monitor Program To modify the TRACE exception vector to point to the TRACE_ENTRY label in the monitor program (so that the emulator can single-step), enter the following commands using the command line: load symbols Mfmon68302 <RETURN>...
Page 120: Mapping Memory
1 Kbyte 2 Kbytes HP 64746, 512 Kbytes 1 Kbyte 1 Kbyte 2 Kbytes HP 64746 w/HP 64170 and HP 64171A 2 Kbytes 256 bytes 2 Kbytes memory modules (256 Kbytes each) HP 64746 w/HP 64170 and HP 64171B 8 Kbytes...
Page 121: To Map Memory Ranges
Chapter 4: Configuring the Emulator Mapping Memory Direct memory access (DMA) to emulation memory is not permitted. You should map all memory ranges used by your programs before loading programs into memory. Note that the internal memory space of the 68302 must be mapped as target RAM. The BAR and SCR registers (located at 0F0H and 0F4H in the exception vector table) may be mapped as emulation RAM, but you should use the register (not memory) command to modify or examine these locations.
Page 122 Chapter 4: Configuring the Emulator Mapping Memory Examples Consider the following section summary from the linker load map output listing. SECTION SUMMARY --------------- SECTION ATTRIBUTE START LENGTH ALIGN ABSOLUTE DATA 00000000 0000002F 00000030 0 (BYTE) NORMAL 00000030 00000030 00000000 2 (WORD) NORMAL CODE 00002000 00002BC6...
Page 123: To Characterize Unmapped Ranges
Chapter 4: Configuring the Emulator Mapping Memory Enter the following commands to map memory for the above program. delete all <RETURN> 0 thru 3ffh emulation ram <RETURN> 2000h thru 4fffh emulation rom <RETURN> 5000h thru 0ffffh emulation ram <RETURN> 0fff000h thru 0ffffffh target ram <RETURN> The resulting memory mapper screen is shown below.
Page 124: To Delete Memory Map Ranges
Chapter 4: Configuring the Emulator Mapping Memory To exit out of the memory mapper, enter: end <RETURN> To delete memory map ranges • Use the delete softkey to delete mapped ranges. Note that programs should be reloaded after deleting mapper terms. The memory mapper may re-assign blocks of emulation memory after the insertion or deletion of mapper terms.
Page 125: To Map Memory Ranges That Use Function Codes
Chapter 4: Configuring the Emulator Mapping Memory To map memory ranges that use function codes • Specify function codes with address ranges when mapping memory. Function code information lets you further characterize memory blocks as supervisor, user, supervisor program, supervisor data, user program, or user data space.
Page 126 Chapter 4: Configuring the Emulator Mapping Memory Examples Suppose you’re developing a system with the following characteristics: • Output port at 400 hex. • Supervisor program from 1000 through 1fff hex. • Supervisor data from 2000 through 2fff hex. • User program from 3000 through 3fff hex.
Page 127: Configuring The Emulator Pod
Chapter 4: Configuring the Emulator Configuring the Emulator Pod Configuring the Emulator Pod In order to configure the emulator pod, you must first start the configuration interface and access the "Emulator Pod Settings" configuration section (refer to the previous "Using the Configuration Interface" section). This section shows you how to: •...
Page 128: To Enable/Disable Bus Arbitration
Chapter 4: Configuring the Emulator Configuring the Emulator Pod To enable/disable bus arbitration • Answer "yes" to the "Enable bus arbitration?" question to enable target system bus arbitration; answer "no" to disable the target bus arbitration. Enabling and disabling bus master arbitration can be useful for isolating target system problems.
Page 129: To Specify The Analyzer's Response To Bus Arbitration
Chapter 4: Configuring the Emulator Configuring the Emulator Pod To specify the analyzer’s response to bus arbitration • Answer "disable", "enable", or "tag" to the "Arbitration analysis?" question. When DMA tracing is disabled, the analyzer will not capture any external or internal DMA, bus cycles.
Page 130: To Enable/Disable Emulation Memory Synchronization
Chapter 4: Configuring the Emulator Configuring the Emulator Pod To enable/disable emulation memory synchronization • Answer "yes" to the "Interlock emulator /DTACK with user /DTACK?" question to enable synchronization; answer "no" to disable synchronization. /DTACK interlock applies only to situations where the 68302 does not provide an internal /DTACK.
Page 131: To Enable/Disable /Berr Connection To Target System
Chapter 4: Configuring the Emulator Configuring the Emulator Pod To enable/disable /BERR connection to target system • Answer "yes" or "no" to the "Enable Bus Error connected to target system?" question. The emulator will always respond to the /BERR signal during target system memory cycles.
Page 132: To Enable/Disable Response To Target System Interrupts
Chapter 4: Configuring the Emulator Configuring the Emulator Pod To enable/disable response to target system interrupts • Answer "yes" to the "Respond to target system interrupts?" question to enable the emulator’s response; answer "no" to disable the emulator’s response. When enabled, the emulator responds to target system interrupts during foreground operation.
Page 133: To Set The Reset Value For The Supervisor Stack Pointer
Chapter 4: Configuring the Emulator Configuring the Emulator Pod To set the reset value for the Supervisor Stack Pointer • Enter an even address in response to the "Reset value of Supervisor Stack Pointer?" question. In order for the emulator to transition into the run state, to step, or to perform other functions after emulation reset, the supervisor stack pointer must be set to an appropriate value.
Page 134: To Set The Processor Data Bus Width
Chapter 4: Configuring the Emulator Configuring the Emulator Pod To set the processor data bus width • Answer "yes" to the "Data bus width 16 bits?" question to set 16-bit mode; answer "no" to set 8-bit mode. The data bus width setting only applies when operating the emulator out-of-circuit (that is, not connected to the target system).
Page 135: To Select /Iack7 Or Pb0
Chapter 4: Configuring the Emulator Configuring the Emulator Pod To select /IACK7 or PB0 • Answer "/IACK7" or "PB0" to the "/IACK7 pin is" question. When the /IACK7-PB0 pin is used as an interrupt acknowledge line, the emulator blocks emulator-generated level 7 interrupt acknowledges to the target system. When the /IACK7-PB0 pin is used as a port B peripheral pin, the emulator does not affect the PB0 line.
Page 136: To Stop Driving Background Cycles To The Target System
Chapter 4: Configuring the Emulator Configuring the Emulator Pod The function code specified can be: supr prog (FC2-FC0=110) supr data (FC2-FC0=101) user prog (FC2-FC0=010) user data (FC2-FC0=001) Choose a function code that will not cause target system hardware such as memory management units to behave in an unpredictable manner.
Page 137: To Specify /Dtack Sources For Chip Selects
Chapter 4: Configuring the Emulator Configuring the Emulator Pod To specify /DTACK sources for chip selects • Answer "internal" or "external" to the "/DTACK source for cs0? (cs1?, cs2?, cs3?)" questions. The 68302 chip selects can be configured either to generate the /DTACK signal internally or to use an externally supplied /DTACK.
Page 138: Setting The Debug/Trace Options
Chapter 4: Configuring the Emulator Setting the Debug/Trace Options Setting the Debug/Trace Options In order to set the debug/trace options, you must first start the configuration interface and access the "Debug/Trace Options" configuration section (refer to the previous "Using the Configuration Interface" section). This section shows you how to: •...
Page 139: To Specify Which Trap Instruction Is Used For Software Breakpoints
Chapter 4: Configuring the Emulator Setting the Debug/Trace Options To specify which TRAP instruction is used for software breakpoints • Enter a value in response to the "Trap number for software breakpoint (0..0FH)?" question. You can answer with values from 0 through 0FH to specify the particular TRAP instruction used for software breakpoints.
Page 140: To Include/Exclude Background States In The Trace
Chapter 4: Configuring the Emulator Setting the Debug/Trace Options To include/exclude background states in the trace • Answer "background" or "both" to the "Trace background or foreground operation?" question to include background states in the trace; answer "foreground" to exclude background states from the trace. Answering "background"...
Page 141: Plugging Into A Target System
Plugging into a Target System...
Page 142 Plugging the Emulator into a Target System This chapter contains information about plugging the emulator into target systems and configuring the emulator so that it operates correctly. • Connecting the Emulator Probe • Configuring the Emulator for In-Circuit Operation...
Page 143: Connecting The Emulator Probe
Chapter 5: Plugging into a Target System Connecting the Emulator Probe Connecting the Emulator Probe The 68302 emulator probe plugs into a PGA through-hole socket that is soldered into the target system. This section describes the steps you must perform when connecting the emulator to a target system: Turn OFF power.
Page 144: 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 145: Step 2. Connect The Probe To The Target System
The use of more than one pin extender is discouraged, unless it is necessary for mechanical clearance reasons, because pin extenders cause signal quality degradation. PGA sockets are available from HP as HP part number 1200-1318. A MacKenzie Technology PGA-100M-003B1-1324 socket should also be suitable.
Page 146 Chapter 5: Plugging into a Target System Connecting the Emulator Probe 1 Install the emulator probe into the target system socket. Be sure to orient the probe correctly. Pin A1 of the PGA matrix is at the notched corner of the probe. (Note that pin "A1" of the PGA matrix is signal "A14."...
Page 147: Step 3. Turn On Power
Chapter 5: Plugging into a Target System Connecting the Emulator Probe Step 3. Turn ON power 1 Turn emulator power ON. 2 Turn target system power ON.
Page 148: If You Need A Pqfp Connector
If your target system uses the MC68302FE surface mount (PQFP) package, you should order the following parts: • HP A2414 QFP Probe Adapter Assembly • Motorola MC22901PQFP132 dummy part The "dummy" part should be installed in place of the microprocessor on your target system.
Page 149: Configuring The Emulator For In-Circuit Operation
Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Configuring the Emulator for In-Circuit Operation Many users of the 68302 emulator encounter problems when first plugging the emulator into their target system. This section should help you avoid or quickly correct most of those problems.
Page 150: Step 1. Understand The Important Concepts
Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Step 1. Understand the important concepts There are a few basic concepts related to 68302 emulation that should be understood before you begin. Understanding these concepts will help you avoid the common startup problems.
Page 151 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation The Freeze Pin and the Background Monitor The 68302 has a hardware input pin called FRZ which can be used to "freeze" selected on-chip peripherals. When configured for the background monitor, the 68302 emulator will assert the FRZ pin during the entire time the emulator is running in the monitor.
Page 152: Step 2. Set Up Your Chip-Selects
Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Step 2. Set up your chip-selects The 68302 has 4 chip-selects, only one of which is enabled after a reset condition. Nearly all 68302 target systems rely on at least one chip-select for accesses to memory.
Page 153 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation For example, assuming you have the area from 0 through 01FFFFH mapped as emulation ROM and have already written your code to initialize the chip-select registers, you should load that code, set a breakpoint, and then run from a reset condition.
Page 154 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Failure to setup the chip-select registers is by far the most common cause of problems when using the 68302 emulator. If you remember that load, modify/display, step, and run commands often rely on valid chip-select settings, you can avoid most of the common mistakes made by users.
Page 155: Step 3. Reprogram Chip-Select Base Addresses
Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Step 3. Reprogram chip-select base addresses If you are not going to be changing the base address of chip-select 0 from address 0, or changing the base address registers of the other chip-selects after initial setup, you should skip this step.
Page 156 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation XDEF SWITCHED $400000 DC.L $10000 ; Stack begins at $0FFFE DC.L RESET-$400000 ; Reset initialization code DC.L BUS_ERROR DC.L ADDR_ERROR $400400 RESET MOVE.W #$0800,$F2 ; Set up the BAR for $800XXX MOVEA.L #$800000,A0 MOVE.W...
Page 157 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation target system will at reset. Now you can simply set a breakpoint, and then run from reset using the commands: modify software_breakpoints enable <RETURN> modify software_breakpoints set SWITCHED <RETURN> run from reset <RETURN>...
Page 158: Step 4. Know Your Interrupt Mode
Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Step 4. Know your interrupt mode If your target does not use dedicated mode interrupts, you can skip this step. One of the more common problems users encounter is not being able to break into the monitor (ERROR: break failed).
Page 159 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Method 2: Using Your Initialization Code to Set the Interrupt Mode Execute a small section of initialization code that sets the GIMR register to the proper value, and break into the monitor immediately after that using either a software or analysis breakpoint.
Page 160: Step 5. Decide Whether To Use The Foreground Monitor
Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Step 5. Decide whether to use the foreground monitor The default configuration for the 68302 emulator uses the background monitor. The background monitor is easier to use and usually requires no special setup. The foreground monitor offers you much more flexibility but also requires extra setup and sometimes requires more in-depth knowledge of your target system.
Page 161: Step 6. Set Up The Emulator For The Foreground Monitor
Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Step 6. Set up the emulator for the foreground monitor Skip this step if you have decided not to use the foreground monitor. Here are the steps you should follow if you choose to use the foreground monitor: 1 Choose an address for the monitor.
Page 162 $ ld68k -h -o Mfmon68302 Mfmon68302.o <RETURN> For the Microtec linker, use the command: $ lnk68k -h -o Mfmon68302 Mfmon68302.o <RETURN> You must use the -h option. This forces the output file to be an "HP OLS" file (.X Note extension) For the HP OLS Linker, use the command: $ lnk <RETURN>...
Page 163 6 Modify your emulator configuration to specify a foreground monitor and specify the address you chose and the filename you created (in this example the filename is Mfmon68302.X for the Microtec or HP AxLS linker). 7 Make sure that the address range 0FFF000H through 0FFFFFFH is mapped as "target RAM".
Page 164 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation • Use a command file to single step that first modifies memory location 24H to point to TRACE_ENTRY, then step. For example: modify memory 24H long to XXXXXXH <RETURN> step <RETURN>...
Page 165 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation If You Need Interrupts Serviced While Running in the Monitor By default, the foreground monitor leaves the Interrupt Mask of the 68302 at 7 after a "break" into the monitor. If you wish to have any interrupts other than level 7 interrupts serviced while the monitor is running, you must modify the monitor source code.
Page 166: Step 7. If You Use The 68302 Built-In Dram Refresh
Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Step 7. If you use the 68302 built-in DRAM refresh The 68302 has a special built-in function that allows for automatic refresh of DRAM with no additional target hardware. If your target system does not rely on this built-in feature of the 68302, you can skip this step.
Page 167: Step 8. Set Up The Dtack Signals
Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Step 8. Set up the DTACK signals Probably the least understood questions asked during the configuration process relate to the interlocking and source for the DTACK signal. Answering these questions correctly is easy once you know a little bit about your target system.
Page 168 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation your actual target. This is because an area mapped as emulation memory will always terminate with 0 wait states, even if it overlays an address where your target system inserts wait states.
Page 169: Step 9. If Emulator Status Shows Halted
Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Step 9. If emulator status shows HALTED Most users will encounter a status of "M68302--Halted" at one time or another. This almost always is caused by a double-bus fault, although under rare conditions it can be caused by the target asserting the "HALT"...
Page 170 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Here is an example where a "trace on_halt" command was used to find the cause of a double-bus fault: XDEF CS_INIT,GIMR_INIT DC.L $440000 ; Stack begins at $43FFFC DC.L $400 ;...
Page 171 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Looking at the trace we see: Trace List Depth=512 Offset=0 More data off screen Label: Address Opcode or Status w/ Source Lines time count Base: mnemonic relative ----- ------- ---------------------------------------------------...
Page 172 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Note In a case like this where there was no trigger, the emulator does not know which line in the trace to begin disassembly on. In this example you would need to issue the command: display trace disassemble_from_line_number -14 <RETURN>...
Page 173: Step 10. Choose The Correct Target Memory Access Size
Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Step 10. Choose the correct target memory access size Whenever the emulator accesses either target memory or an on-chip location, it uses the monitor program to do so. The monitor program will use either a "MOVE.B"...
Page 174: Step 11. Check Your Dtack Pullup Resistor
Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Step 11. Check your DTACK pullup resistor! It wouldn’t be fair to solve all these 68302 plug-in problems and not give the hardware engineer a chance to help out, so there’s one last thing you should check before you begin.
Page 175: If You Have Problems
Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation If you have problems Listed below are common problems and their most common causes: PROBLEM: You get "ERROR: Stepping failed" when trying to use "step" or "step from" command. Cause: This is most likely caused by an invalid stack.
Page 176 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Fix: Make sure the stack pointer is pointing to a legitimate address and that any chip-selects for that address are initialized. PROBLEM: You get "ERROR: Monitor failure; bus error" when trying to do a display, modify or load command.
Page 177 Chapter 5: Plugging into a Target System Configuring the Emulator for In-Circuit Operation Fix: Use the foreground monitor and include the necessary modifications. Refer to "Step 7. If you use the 68302 built-in DRAM refresh" for details on how to ensure proper DRAM refresh.
Page 179: Using The Emulator
Using the Emulator...
Page 180 Using the Emulator This chapter describes general tasks you may wish to perform while using the emulator. These tasks are grouped into the following sections: • Loading absolute files. • Using symbols. • Executing user programs (starting, stopping, stepping, and resetting the emulator).
Page 181: 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 182: 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 183: 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 184: 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 185: To Display Local Symbols
Chapter 6: Using the Emulator Using Symbols To display local symbols • When displaying symbols, position the mouse pointer over a symbol on the symbol display screen and click the select mouse button. • When displaying symbols, position the mouse pointer over the symbol, press and hold the select mouse button, and choose Display Local Symbols from the popup menu.
Page 186 Chapter 6: Using the Emulator Using Symbols Examples To use the Symbols Display popup menu: View the local symbols associated with the highlighted symbol by choosing this menu item.
Page 187 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 188 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 189: To Display A Symbol's Parent Symbol
Chapter 6: Using the Emulator Using Symbols To display a symbol’s parent symbol • When displaying symbols, position the mouse pointer over the symbol, press and hold the select mouse button, and choose Display Parent Symbols from the popup menu. Examples View the parent symbol associated...
Page 190: To Copy-And-Paste A Full Symbol Name To The Entry Buffer
Chapter 6: Using the Emulator Using Symbols To copy-and-paste a full symbol name to the entry buffer • When displaying symbols, position the mouse pointer over the symbol, press and hold the select mouse button, and choose Cut Full Symbol Name from the popup menu.
Page 191: 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 192: 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 193: To Change The Current Working Symbol Context
Chapter 6: Using the Emulator Using Context Commands You can predefine directories and set the maximum number of entries for the Directory Selection dialog box by setting X resources (see the "Setting X Resources" chapter). To change the current working symbol context •...
Page 194: 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 195: 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 196: To Run Programs Until An Address
Chapter 6: Using the Emulator Executing User Programs cycles of the /RESET signal). When the target system /RESET line becomes active and then inactive, the 68302 registers are initialized to their reset values. To run programs until an address • When displaying memory in mnemonic format, position the mouse pointer over the line that you want to run until;...
Page 197: 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 198: 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 199: 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 200: 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 201 Chapter 6: Using the Emulator Using Software Breakpoints Software breakpoints should not be set, cleared, enabled, or disabled while the CAUTION emulator is running user code. If any of these commands are entered while the emulator is running user code, and the emulator is executing code in the area where the breakpoint is being modified, program execution may be unreliable.
Page 202: To Display The Breakpoints List
Chapter 6: Using the Emulator Using Software 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 203: To Enable/Disable Breakpoints
Chapter 6: Using the Emulator Using Software Breakpoints To enable/disable breakpoints • Choose the Breakpoints→Enable toggle. • When displaying the breakpoint list, press and hold the select mouse button and then choose Enable/Disable Software Breakpoints from the popup menu. • Using the command line, enter the modify software_breakpoints enable or modify software_breakpoints disable command.
Page 204 Chapter 6: Using the Emulator Using Software Breakpoints Examples To enable software breakpoints using the breakpoints display popup menu: Bring up menu and choose this item to change states.
Page 205: 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 206: 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 207: To Set All Breakpoints
Chapter 6: Using the Emulator Using Software Breakpoints Note that software breakpoints only stop program execution at memory locations which contain instruction opcodes (not operands or data). When displaying memory in mnemonic format, asterisks (*) appear next to breakpoint addresses. An asterisk shows the breakpoint is active. Also, if assembly level code is being displayed, the disassembled instruction mnemonic at the breakpoint address will show the breakpoint instruction.
Page 208: To Re-Activate A Breakpoint
Chapter 6: Using the Emulator Using Software Breakpoints To re-activate a breakpoint • When displaying breakpoints, position the mouse pointer over the line displaying the inactivated breakpoint and click the select mouse button. Or, press and hold the select mouse button and choose Set/Inactivate Breakpoint from the popup menu. The "inactivated"...
Page 209 Chapter 6: Using the Emulator Using Software Breakpoints Examples To re-activate breakpoints using the breakpoints display popup menu: Change status with a mouse click on this line (menu and highlight do not appear). Choose this menu item to change the state of the highlighted breakpoint.
Page 210: To Clear A Breakpoint
Chapter 6: Using the Emulator Using Software Breakpoints To clear a breakpoint • When displaying memory in mnemonic format, position the mouse pointer over the program line at which you wish to clear a currently set breakpoint (notice the asterisk at the left of the line) and click the select mouse button. Or, press and hold the select mouse button and choose Set/Clear Software Breakpoint from the popup menu.
Page 211 Chapter 6: Using the Emulator Using Software Breakpoints Examples To clear a software breakpoint using the breakpoints display popup menu: Bring up the menu and choose this item to clear the highlighted breakpoint.
Page 212: To Clear All Breakpoints
Chapter 6: Using the Emulator Using Software Breakpoints To clear all breakpoints • When displaying breakpoints, position the mouse pointer within the Breakpoints Display screen, press and hold the select mouse button, and choose Clear (delete) All Breakpoints from the popup menu. •...
Page 213: Displaying And Modifying Registers
Chapter 6: Using the Emulator Displaying and Modifying Registers Displaying and Modifying Registers You can display and modify the contents of emulation processor registers. Most emulators have at least a BASIC class of registers. Some emulators have additional register classes whose register contents can be displayed and modified. Consult your emulator-specific Softkey Interface documentation for a definition of the register classes.
Page 214 Chapter 6: Using the Emulator Displaying and Modifying Registers <REGCLASS> <REGNAME> Description idma Function Code Register Channel Mode Register sapr Source Address Pointer dapr Destination Address Pointer Byte Count Register Channel Status Register interrupt gimr Global Interrupt Mode Register Interrupt Pending Register Interrupt Mask Register In-Service Register pcant...
Page 215 Chapter 6: Using the Emulator Displaying and Modifying Registers <REGCLASS> <REGNAME> Description scc1 scon1 SCC1 Configuration Register scm1 SCC1 Mode Register dsr1 SCC1 Data Synchronization Register scce1 SCC1 Event Register sccm1 SCC1 Mask Register SCC1 Status Register sccs1 scc2 scon2 SCC2 Configuration Register scm2 SCC2 Mode Register...
Page 216: To Display Register Contents
Chapter 6: Using the Emulator Displaying and Modifying Registers To display register contents • Choose Display→Registers. • Using the command line, enter the display registers command. When displaying registers, you can display classes of registers and individual registers.
Page 217: To Modify Register Contents
Chapter 6: Using the Emulator Displaying and Modifying Registers To modify register contents • Choose Modify→Registers... and use the dialog box to name the register and specify its value. Clicking the "Recall" pushbutton lets you select register names and values from predefined or previously specified entries.
Page 218: 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 219: 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 220: 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 221: To Display Memory In Real Number Format
Chapter 6: Using the Emulator Displaying and Modifying Memory To display memory in blocked byte format: display memory ascii_old_data blocked bytes <RETURN> To display memory in real number format • Place an absolute or symbolic address in the entry buffer; then, choose Display→Memory→Real () and select the size from the cascade menu.
Page 222: To Display Memory At An Address
Chapter 6: Using the Emulator Displaying and Modifying Memory Examples To display memory in 64-bit real number format: display memory real long <RETURN> To display memory at an address • Place an absolute or symbolic address in the entry buffer; then, choose Display→Memory→At ().
Page 223: 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 224: 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 225: 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 226: 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 227: 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 228 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 229: 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 230: 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 231: To Display The Error Log
Chapter 6: Using the Emulator Using System Commands To display the error log • Choose Display→Error Log. • Position the mouse pointer on the status line, press and hold the select mouse button, and then choose Display Error Log from the popup menu. •...
Page 232: To Edit Files
Chapter 6: Using the Emulator Using System Commands To edit files • Choose File→Edit→File and use the dialog box to specify the file name. • To edit a file based on an address in the entry buffer, place an address reference (either absolute or symbolic) in the entry buffer;...
Page 233 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 234 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 235: 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 236: To Open A Terminal Emulation Window
Chapter 6: Using the Emulator Using System Commands Status ... Copies the emulator/analyzer status display. Global Symbols ... Copies the global symbols. If symbols have not been loaded, this menu item is grayed-out and unresponsive. Local Symbols () ... Copies the local symbols from the symbol scope named (by an enclosing symbol) in the entry buffer.
Page 237: 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 238: 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 239: 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 241: Using The Emulation Analyzer
Using the Emulation Analyzer...
Page 242 Using the Emulation Analyzer This chapter describes tasks you may wish to perform while using the emulation analyzer. These tasks are grouped into the following sections: • The basics of starting, stopping, and displaying traces. • Qualifying trigger and store conditions. •...
Page 243: The Basics Of Starting, Stopping, And Displaying Traces
Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces The Basics of Starting, Stopping, and Displaying Traces This section describes the basic tasks that relate to starting and stopping trace measurements. When you start a trace measurement, the analyzer begins looking at the data on the emulation processor’s bus and control signals on each analyzer clock signal.
Page 244: To Start A Trace Measurement
Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces To start a trace measurement • Choose Trace→Everything. • Using the command line, enter the trace command. The trace command tells the analyzer to begin monitoring the states which appear on the trace signals.
Page 245 Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces Examples To display the trace status: display status <RETURN> The first line of the emulation trace status display shows the user trace has been "completed"; other possibilities are that the trace is still "running" or that the trace has been "halted".
Page 246 Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces The "States" line shows the number of states that have been stored (out of the number that is possible to store) and the line numbers that the stored states occupy. (The trigger state is always stored on line 0.) The "Sequence term"...
Page 247: To Stop A Trace Measurement
Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces To stop a trace measurement • Choose Trace→Stop. • Using the command line, enter the stop_trace command. You can, and most likely will, specify traces whose trigger or storage states are never found.
Page 248: To Display The Trace
Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces To display the trace • Choose Trace→Display or Display→Trace. • Using the command line, enter the display trace command. You can display captured trace data with the display trace command. The available options to the display trace command are described in the "Modifying the Trace Display"...
Page 249: To Position The Trace Display On Screen
The next column shows the count information (time is counted by default). "Relative" indicates that each count is relative to the previous state. If your analyzer card contains external analysis (for example, HP 64703), the next column shows the data captured on the external trace signals.
Page 250: To Change The Trace Depth
Chapter 7: Using the Emulation Analyzer The Basics of Starting, Stopping, and Displaying Traces To change the trace depth • Using the command line, enter the display trace depth command. The display trace depth command allows you to specify the number of states that are displayed.
Page 251: Qualifying Trigger And Store Conditions
Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions Qualifying Trigger and Store Conditions This section describes tasks relating to the qualification of trigger and storage states. You can trigger on, or store, specific states or specific values on a set of trace signals (which are identified by trace labels).
Page 252 Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions Hexadecimal (example: 0a7fh). You must precede any hexadecimal number that begins with an A, B, C, D, E, or F with a zero. Don’t care digits may be included in binary, octal, or hexadecimal numbers and they are represented by the letters X or x.
Page 253 Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions However, you cannot add two symbols unless one of them is an EQU type symbol. Emulation Analyzer Trace Signals When you qualify states, you specify values that should be found on the analyzer trace signals.
Page 254 The following sofkeys are available if you have an emulation analyzer that has 64 channels (for example, HP 64703 or HP 64704). The value following this softkey is searched for on the lines that monitor processor signals CS0 through CS3.
Page 255 Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions extra Combines the edma, pbclr, cs, pberr, grd, rom, pbio, and ipl softkeys. Some values you can specify following the extra softkey are: Value Description 0xxxx xxxx xxxx xx0xb BCLR active 0xxxx xxxx x0xx xxxxb BERR active...
Page 256: To Qualify The Trigger State And Position
Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions Predefined Values for Status Qualifiers When you specify status qualifiers for analyzer states (by pressing the status softkey), you will be given the following softkeys which are predefined values for the qualifiers. Softkey Value Description...
Page 257 Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions button and choose Trace After, Trace Before, or Trace About from the popup menu. • Using the command line, enter the trace after, trace about, or trace before commands. Tracing after the trigger state says states that occur after the trigger state should be saved;...
Page 258 Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions Examples Suppose you want to look at the execution of the demo program after the call of the "update_system()" function (main.c: line 101) occurs. To trigger on this address, enter: trace after address main."main.c": line 101 <RETURN>...
Page 259: To Trigger On A Number Of Occurrences Of Some State
Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions To trigger on a number of occurrences of some state • Use the occurs <#TIMES> after specifying the trigger state. When specifying a trigger state, you can include an occurrence count. The occurrence count specifies that the analyzer trigger on the Nth occurrence of some state.
Page 260: To Qualify States Stored In The Trace
Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions To qualify states stored in the trace • Enter a storage state specification in the entry buffer; then, choose Trace→Only (). • Using the command line, use the only option in the trace command. By default, all captured states are stored;...
Page 261: To Prestore States Before Qualified Store States
Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions To prestore states before qualified store states • Enter a storage state specification in the entry buffer; then, choose Trace→Only () Prestore. • Use the prestore option in the trace command. Prestore allows you to save up to two states which precede a normal store state.
Page 262: To Change The Count Qualifier
Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions To change the count qualifier • Use the counting option in the trace command. After initializing the analyzer, the default count qualifier is "time", which means that the time between states is saved. When time is counted, up to 512 states can be stored in the trace.
Page 263 Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions Examples Suppose you want to know how many loops of the program occur between calls of the "do_sort" function. To change the count qualifier to count a state that occurs once for each loop of the program, enter: trace only do_sort counting state main."main.c": line 101 <RETURN>...
Page 264: To Trace Until The Analyzer Is Halted
Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions To trace until the analyzer is halted • Choose Trace→Until Stop. • Using the command line, enter the trace on_halt command. The trace on_halt command allows you to prevent triggering. In other words, the trace runs until you enter the stop_trace command.
Page 265: To Break Emulator Execution On The Analyzer Trigger
Chapter 7: Using the Emulation Analyzer Qualifying Trigger and Store Conditions To break emulator execution on the analyzer trigger • Enter a trigger state specification in the entry buffer; then, choose Trace→Until (). • When displaying memory in mnemonic format, position the mouse pointer over the program line which you wish to trace before, press and hold the select mouse button and choose Trace Until from the popup menu.
Page 266: Using The Sequencer
Chapter 7: Using the Emulation Analyzer Using the Sequencer Using the Sequencer When you use the analyzer’s sequencer, you can specify traces that trigger on a series, or sequence, of states. You can specify a state which, when found, causes the analyzer to restart the search for the sequence of states.
Page 267 Chapter 7: Using the Emulation Analyzer Using the Sequencer Examples In the demo program, suppose you wish to trigger on the following sequence of events: the "save_points" function, the "interrupt_sim" function, and finally the "do_sort" function. Also, suppose you wish to store only opcode fetches of the assembly language LINK A6,#0 instruction (data values that equal 4E56H) to show function entry addresses.
Page 268: To Specify A Global Restart State
Chapter 7: Using the Emulation Analyzer Using the Sequencer To specify a global restart state • Use the restart option to the trace command. When using the analyzer’s sequencer, an additional sequence restart term is also allowed. This restart is a "global restart"; that is, it applies to all the sequence terms. The restart term is a state which, when captured before the analyzer has found the trigger state, causes the search for the sequence of states to start over.
Page 269: To Trace "Windows" Of Program Execution
Chapter 7: Using the Emulation Analyzer Using the Sequencer Notice in the preceding trace (you may have to press <PREV> in order to see the states captured prior to the trigger) that, in addition to states captured in the sequence, "sq adv" is also shown next to states which cause a sequencer restart. To trace "windows"...
Page 270 Chapter 7: Using the Emulation Analyzer Using the Sequencer If you wish to combine the windowing and sequencing functions of the analyzer, there are some restrictions: • Up to four sequence terms are available when windowing is in effect. • Global restart is not available when windowing is in effect.
Page 271: Modifying The Trace Display
Chapter 7: Using the Emulation Analyzer Modifying the Trace Display Modifying the Trace Display This section describes the options available when displaying trace lists. This section describes how to: • Display the trace about a line number. • Display the trace, disassembling from a line number. •...
Page 272: To Display The Trace About A Line Number
Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace about a line number • Use the <LINE #> option to the display trace command. The <LINE #> trace display option allows you to specify the line number to be centered in the display.
Page 273: To Display The Trace, Disassembling From A Line Number
Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace, disassembling from a line number • Use the disassemble_from_line_number option to the display trace command. The "disassemble_from_line_number" trace display option causes the inverse assembler to attempt to begin disassembling the trace information from the specified line number.
Page 274: To Display The Trace In Absolute Format
Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace in absolute format • Use the absolute option to the display trace command. The absolute trace display option allows you to display status information in absolute format (binary, hex, or mnemonic). The absolute status mnemonic display is the same as default mnemonic display, except that opcodes are not disassembled.
Page 275: To Display The Trace In Mnemonic Format
Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace in mnemonic format • Use the mnemonic option to the display trace command. The mnemonic trace display option allows you to display the trace information in mnemonic format (that is, opcodes and status).
Page 276: To Display The Trace With High-Level Source Lines
Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace with high-level source lines • Use the set source command. To include high-level source lines in the trace display, you must use the set command. The set command allows you to include symbolic information in trace, memory, register, and software breakpoint displays.
Page 277 Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To set the number of source lines to be displayed at 12: set source on number_of_source_lines 12 <RETURN> display trace <RETURN>...
Page 278: To Display The Trace With Symbol Information
Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace with symbol information The set symbols on/off command allows you to specify that address information be displayed in terms of program symbols. Examples To display the trace with symbol information: set source off symbols on <RETURN>...
Page 279: To Change Column Widths In The Trace Display
Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To change column widths in the trace display • Use the set width command. The set width command allows you to change the width of the address and mnemonic (or absolute) columns in the trace list. Values from one to 80 can be entered.
Page 280: To Display Time Counts In Absolute Or Relative Format
Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display time counts in absolute or relative format • Use the count option to the display trace command. Count information may be displayed two ways: relative (which is the default), or absolute.
Page 281: To Display The Trace With Addresses Offset
Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display the trace with addresses offset • Use the offset_by option to the display trace command. The offset_by trace display option allows you to cause the address information in the trace display to be offset by the amount specified.
Page 282: To Return To The Default Trace Display
Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To return to the default trace display • Use the set default command. The set default command allows you to return to the default display. Examples To return to the default trace display: set default <RETURN>...
Page 283: To Display External Analyzer Information
Chapter 7: Using the Emulation Analyzer Modifying the Trace Display To display external analyzer information • Use the external option to the display trace command. The external trace display option allows you to include data from the external analyzer in the trace list. External bits are displayed by default. If you do not wish to have the external bits information in the display, you can turn them off.
Page 284: Saving And Restoring Traces
Chapter 7: Using the Emulation Analyzer Saving and Restoring Traces Saving and Restoring Traces The emulator/analyzer interface allow you to save trace commands and trace lists. You can restore trace commands in order to set up the same trace specification. You can restore traces in order to view trace data captured in the stored trace.
Page 285: To Restore Trace Commands
Chapter 7: Using the Emulation Analyzer Saving and Restoring Traces To restore trace commands • Choose File→Load→Trace Spec. • Using the command line, enter the load trace_spec command. Trace commands that are restored will always work, even if symbols have been changed;...
Page 286: To Save Traces
Chapter 7: Using the Emulation Analyzer Saving and Restoring Traces To save traces • Choose File→Store→Trace Data. • Using the command line, enter the store trace command. You can save a trace to a trace file and reload it at a later time. The trace is saved in a file named "trcfile.TR"...
Page 287: To Restore Traces
Chapter 7: Using the Emulation Analyzer Saving and Restoring Traces To restore traces • Choose File→Load→Trace Data. • Using the command line, enter the load trace command. The restored trace depth is the depth specified when the trace was stored and cannot be increased.
Page 289: Making Software Performance Measurements
Making Software Performance Measurements...
Page 290 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 291: 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 292 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 293: To Set Up The Trace Command For Activity Measurements
Chapter 8: Making Software Performance Measurements Activity Performance Measurements Absolute count - state 5120 Absolute count - time - Us 2221.20 This section describes how to: • Set up the trace command for activity measurements. • Initialize activity performance measurements. •...
Page 294: 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 295 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 296 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 297 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 298: 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 299 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 300 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 301 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Label set_outputs Address Range 33D0H thru 3460H Memory Activity State Percent Rel = 42.02 Abs = 40.00 Mean = 204.80 Sdv = 257.34 Time Percent Rel = 42.18 Abs = 40.12 Program Activity State Percent Rel =...
Page 302 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Address Range 329AH thru 3322H Memory Activity State Percent Rel = 5.25 Abs = 5.00 Mean = 25.60 Sdv = 114.49 Time Percent Rel = 5.27 Abs = 5.01 Program Activity State Percent Rel = 5.12...
Page 303 Chapter 8: Making Software Performance Measurements Activity Performance Measurements State Percent Rel = 0.18 Abs = 0.18 Mean = 0.90 Sdv = 4.02 Time Percent Rel = 0.19 Abs = 0.18 Program Activity State Percent Rel = 0.22 Abs = 0.21 Mean = 1.10...
Page 304 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 Graph of Memory Activity relative state percents >= 1 set_outputs 42.02% *********************...
Page 305 Chapter 8: Making Software Performance Measurements Activity Performance Measurements Relative Time - Us 3230.68 Program Activity State count Relative count 10007 Mean sample 38.49 Mean Standard Dv 93.22 95% Confidence 113.41% Error tolerance Time count Relative Time - Us 3295.40 Absolute Totals Absolute count - state 10240...
Page 306: 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 307: 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 308 Chapter 8: Making Software Performance Measurements Duration Performance Measurements trace after module_name start or module_name end only module_name start or module_name end counting time <RETURN> Where "symbol_entry" and "symbol_exit" are symbols from the user program. Or, where "module_name" is the name of a C function or Pascal procedure (and is listed as a procedure symbol in the global symbol display).
Page 309: 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 310 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 311: 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 312 Chapter 8: Making Software Performance Measurements Duration Performance Measurements Standard Deviation Deviation from the mean of time. The following equation is used to calculate standard deviation: Where: Number of intervals. mean Average time. Sum of squares of time in the intervals. sumq Error Tolerance and Confidence Level An approximate error may exist in displayed information.
Page 313 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 314 Chapter 8: Making Software Performance Measurements Duration Performance Measurements From Address 2CC4 File main(module)."/users/patw/demo/debug_env/hp64746/main.c" Symbolic Reference at interrupt_sim+A2 To Address 2C22 File main(module)."/users/patw/demo/debug_env/hp64746/main.c" Symbolic Reference at main.interrupt_sim Number of intervals 2550 Maximum Time 79728.640 us Minimum Time 50892.800 us Avg Time 59438.028 us Statistical summary - for 10 traces...
Page 315: 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 316: 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 317: 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 318 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 319: Using The External State Analyzer
Using the External State Analyzer...
Page 320 Using the External State Analyzer The HP 64703A analyzer provides an external analyzer with 16 external trace channels. These trace channels allow you to capture activity on signals external to the emulator, typically other target system signals. The external analyzer may be configured as an extension to the emulation analyzer, as an independent state analyzer, or as an independent timing analyzer.
Page 321: Setting Up The External Analyzer
Setting Up the External Analyzer Setting Up the External Analyzer This section assumes you have already connected the external analyzer probe to the HP 64700 Card Cage. Before you can use the external analyzer, you must: • Connect the external analyzer probe to the target system.
Page 322: To Connect The External Analyzer Probe To The Target System
Chapter 9: Using the External State Analyzer Setting Up the External Analyzer To connect the external analyzer probe to the target system 1 Assemble the Analyzer Probe. The analyzer probe is a two-piece assembly, consisting of ribbon cable and 18 probe wires (16 data channels and the J and K clock inputs) attached to a connector. Either end of the ribbon cable may be connected to the 18 wire connector, and the connectors are keyed so they may only be attached one way.
Page 323 Chapter 9: Using the External State Analyzer Setting Up the External Analyzer 2 Attach grabbers to probe wires. Each of the 18 probe wires has a signal and a ground connection. Each probe wire is labeled for easy identification. Thirty-six grabbers are provided for the signal and ground connections of each of the 18 probe wires.
Page 324 Chapter 9: Using the External State Analyzer Setting Up the External Analyzer CAUTION Turn OFF target system power before connecting analyzer probe wires to the target system. The probe grabbers are difficult to handle with precision, and it is extremely easy to short the pins of a chip (or other connectors which are close together) with the probe wire while trying to connect it.
Page 325: Configuring The External Analyzer
Chapter 9: Using the External State Analyzer Configuring the External Analyzer Configuring the External Analyzer After you have assembled the external analyzer probe and connected it to the emulator and target system, the next step is to configure the external analyzer. The external analyzer is a versatile instrument, and you can configure it to suit your needs.
Page 326: To Control The External Analyzer With The Emulator/Analyzer Interface
Chapter 9: Using the External State Analyzer Configuring the External Analyzer To control the external analyzer with the emulator/analyzer interface 1 Enter the modify configuration command. 2 Answer "yes" to the "Modify external analyzer configuration?" question. 3 Answer the "Should emulation control the external bits?" question. Answer "yes"...
Page 327: To Specify The Threshold Voltage
Chapter 9: Using the External State Analyzer Configuring the External Analyzer To specify the threshold voltage 1 Enter the modify configuration command. 2 Answer "yes" to the "Modify external analyzer configuration?" question. 3 Answer "yes" to the "Should emulation control the external bits?" question. 4 Answer the "Threshold voltage for bits 0-7 and J clock?"...
Page 328: To Specify The External Analyzer Mode
Chapter 9: Using the External State Analyzer Configuring the External Analyzer To specify the external analyzer mode 1 Enter the modify configuration command. 2 Answer "yes" to the "Modify external analyzer configuration?" question. 3 Answer "yes" to the "Should emulation control the external bits?" question. 4 Answer the "External analyzer mode?"...
Page 329: To Specify The Slave Clock Mode
Chapter 9: Using the External State Analyzer Configuring the External Analyzer To specify the slave clock mode 1 Enter the modify configuration command. 2 Answer "yes" to the "Modify external analyzer configuration?" question. 3 Answer "yes" to the "Should emulation control the external bits?" question. 4 Answer "state"...
Page 330 Chapter 9: Using the External State Analyzer Configuring the External Analyzer If no slave clock has appeared since the last master clock, the data on the lower 8 bits of the pod will be latched at the same time as the upper 8 bits. If more than one slave clock has appeared since the last master clock, only the first slave data will be available to the analyzer (see the figure below).
Page 331 Chapter 9: Using the External State Analyzer Configuring the External Analyzer Answer "demux" to specify the true demultiplexing mode. In this mode, only the lower eight external channels (0-7) are used. The slave clock (as specified by your answers to the next four questions) latches these bits and the emulation clock samples the same channels again.
Page 332: To Define Labels For The External Analyzer Signals
Chapter 9: Using the External State Analyzer Configuring the External Analyzer If no slave clock has appeared since the last master clock, the data on the lower 8 bits of the pod will be the same as the upper 8 bits. If more than one slave clock has appeared since the last master clock, only the first slave data will be available to the analyzer.
Page 333 Chapter 9: Using the External State Analyzer Configuring the External Analyzer to extend past bit 15. Thus, the sum of the start bit number plus the width must not exceed 16. The "polarity?" question allows you to specify positive or negative logic for the external bits.
Page 335: Making Coordinated Measurements
Making Coordinated Measurements...
Page 336 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 337 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 338 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 339: 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 340 Chapter 10: Making Coordinated Measurements Setting Up for Coordinated Measurements 1 Connect the cables to the HP 64700 CMB ports.
Page 341: 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 342 Chapter 10: 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 343: Starting/Stopping Multiple Emulators
Chapter 10: 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 344: To Start Synchronous Measurements
Chapter 10: 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 345: 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 346 CMB connector or BNC connector so that, when the analyzer finds its trigger condition, a trigger signal is driven on the HP 64700’s Coordinated Measurement Bus (CMB) or BNC connector. This can also be done for the external analyzer when it is configured as an independent state or timing analyzer.
Page 347: To Drive The Emulation Analyzer Trigger Signal To The Cmb
Chapter 10: Making Coordinated Measurements Using Trigger Signals This section shows you how to: • Drive the emulation analyzer trigger signal to the CMB. • Drive the emulation analyzer trigger signal to the BNC connector. • Drive the external analyzer trigger signal to the CMB. •...
Page 348: To Drive The Emulation Analyzer Trigger Signal To The Bnc Connector
Chapter 10: Making Coordinated Measurements Using Trigger Signals To drive the emulation analyzer trigger signal to the BNC connector 1 Enter the modify configuration command. 2 Answer "yes" to the "Modify interactive measurement specification?" question. 3 Answer "receive" to the "Should BNC drive or receive Trig1?" question. You could also drive the emulation analyzer trigger to the BNC over the trig2 internal line by specifying that the BNC should receive trig2 and that the emulation analyzer should drive trig2.
Page 349: To Drive The External Analyzer Trigger Signal To The Bnc Connector
Chapter 10: Making Coordinated Measurements Using Trigger Signals To drive the external analyzer trigger signal to the BNC connector 1 Enter the modify configuration command. 2 Answer "yes" to the "Modify interactive measurement specification?" question. 3 Answer "receive" to the "Should BNC drive or receive Trig2?" question. 4 Answer "drive"...
Page 350: To Break Emulator Execution On Signal From Bnc
Chapter 10: Making Coordinated Measurements Using Trigger Signals To break emulator execution on signal from BNC 1 Enter the modify configuration command. 2 Answer "yes" to the "Modify interactive measurement specification?" question. 3 Answer "drive" to the "Should BNC drive or receive Trig1?" question. You could also break emulator execution on a trigger signal from the BNC over the trig2 internal line by specifying that the BNC should drive trig2 and that the emulator break should receive trig2.
Page 351: To Arm The Emulation Analyzer On Signal From Cmb
Chapter 10: Making Coordinated Measurements Using Trigger Signals To arm the emulation analyzer on signal from 1 Enter the modify configuration command. 2 Answer "yes" to the "Modify interactive measurement specification?" question. 3 Answer "drive" to the "Should CMBT drive or receive Trig2?" question. 4 Answer "receive"...
Page 352: To Arm The Emulation Analyzer On External Analyzer Trigger
Chapter 10: Making Coordinated Measurements Using Trigger Signals To arm the emulation analyzer on external analyzer trigger 1 Enter the modify configuration command. 2 Answer "yes" to the "Modify interactive measurement specification?" question. 3 Answer "receive" to the "Should Analyzer drive or receive Trig2?" question. 4 Answer "drive"...
Page 353: To Arm The External Analyzer On Signal From Bnc
Chapter 10: Making Coordinated Measurements Using Trigger Signals To arm the external analyzer on signal from BNC 1 Enter the modify configuration command. 2 Answer "yes" to the "Modify interactive measurement specification?" question. 3 Answer "drive" to the "Should BNC drive or receive Trig2?" question. 4 Answer "receive"...
Page 355: Setting X Resources
Setting X Resources...
Page 356 Resources specifications in later files override those in earlier files. Files are read in the following order: The application defaults file. For example, /usr/lib/X11/app-defaults/HP64_Softkey in HP-UX or /usr/openwin/lib/X11/app-defaults/HP64_Softkey in SunOS. The $XAPPLRESDIR/HP64_Softkey file. (The XAPPLRESDIR environment variable defines a directory containing system-wide custom application defaults.)
Page 357 Chapter 11: Setting X Resources Resource specifications included in the command line with the -xrm option. System scheme files in directory $HP64000/lib/X11/HP64_schemes. System-wide custom scheme files located in directory $XAPPLRESDIR/HP64_schemes. User-defined scheme files located in directory $HOME/.HP64_schemes (note the dot in the directory name). Scheme files group resource specifications for different displays, computing environments, and languages.
Page 358: To Modify The Graphical User Interface Resources
Application Resources for Schemes Resource Values Description HP64_Softkey.platformScheme HP-UX Names the subdirectory for platform SunOS specific schemes. This resource should be (custom) set to the platform on which the X server is running (and displaying the Graphical User Interface) if it is different than the platform where the application is running.
Page 359 Chapter 11: Setting X Resources To modify the Graphical User Interface resources Commonly Modified Application Resources Resource Values Description HP64_Softkey.lines Specifies the number of lines in the main (min. 18) display area. HP64_Softkey.columns Specifies the number of columns, in (min. 80) characters, in the main display area.
Page 360 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 361 !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 362: 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 363 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 364: To Set Up Custom Action Keys
Chapter 11: Setting X Resources To set up custom action keys To set up custom action keys • Modify the "actionKeysSub.keyDefs" resource. The "actionKeysSub.keyDefs" resource defines a list of paired strings. The first string defines the text that should appear on the action key pushbutton. The second string defines the command that should be sent to the command line area and executed when the action key is pushed.
Page 365: To Set Initial Recall Buffer Values
Chapter 11: Setting X Resources To set initial recall buffer values To set initial recall buffer values • Modify the "entries" resource for the particular recall buffer. There are six popup recall buffers present in the Graphical User Interface. The resources for these popup recall buffers are listed in the following table.
Page 366 Chapter 11: 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 68302 emulators, modify the "*m68302*dirSelectSub.entries" resource: *m68302*dirSelectSub.entries: \ "$HOME" \ ".."...
Page 367: To Set Up Demos Or Tutorials
Chapter 11: 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 368 Chapter 11: 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 369 Chapter 11: Setting X Resources To set up demos or tutorials 2 Create the demo or tutorial index file. Each line in the index file contains first a quoted string that is the name of the topic which appears in the index popup and second the name of the file that is raised when the topic is selected.
Page 371: Part 3 Reference
Part 3 Reference...
Page 372 Part 3...
Page 373: Emulator/Analyzer Interface Commands
Emulator/Analyzer Interface Commands...
Page 374: 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 375 Chapter 12: Emulator/Analyzer Interface Commands Pulldown Command Line File→Context→Directory File→Context→Symbols File→Load→Emulator Config load configuration load <abs_file> File→Load→Executable File→Load→Program Only load <abs_file> nosymbols File→Load→Symbols Only load symbols store trace File→Store→Trace Data File→Store→Trace Spec store trace_spec File→Store→BBA Data bbaunload copy display to File→Copy→Display File→Copy→Memory copy memory to...
Page 376 Chapter 12: Emulator/Analyzer Interface Commands Pulldown Command Line Display→Context pwd, pws Display→Memory display memory Display→Memory→Mnemonic () display memory --EXPR-- mnemonic Display→Memory→Mnemonic at PC display memory mnemonic at_pc display memory mnemonic previous_display Display→Memory→Mnemonic Previous Display→Memory→Hex ()→bytes display memory --EXPR-- blocked bytes Display→Memory→Hex ()→words display memory --EXPR-- blocked words Display→Memory→Hex ()→long...
Page 377 Chapter 12: Emulator/Analyzer Interface Commands Pulldown Command Line Execution→Run→from PC Execution→Run→from () run from --EXPR-- Execution→Run→from Transfer Address run from transfer_address Execution→Run→from Reset run from reset Execution→Run→until () run until --EXPR-- Execution→Step Source→from PC step source Execution→Step Source→from () step source from --EXPR-- Execution→Step Source→from Transfer step source from transfer_address Address...
Page 378 Chapter 12: Emulator/Analyzer Interface Commands Pulldown Command Line Trace→Display display trace Trace→Display Options display trace Trace→Trace Spec N/A (browses recall buffer for trace commands) Trace→After () trace after STATE trace before STATE Trace→Before () Trace→About () trace about STATE Trace→Only () trace only STATE Trace→Only () Prestore trace only STATE prestore anything...
Page 379: How Popup Menus Map To The Command Line
Chapter 12: Emulator/Analyzer Interface Commands How Popup Menus Map to the Command Line The following tables show the items available in the popup menus and the command line commands to which they map. Mnemonic Memory Display Popup Command Line Set/Clear Breakpoint modify software_breakpoints set/clear --EXPR-- Edit Source ! vi +<line>...
Page 380 Chapter 12: Emulator/Analyzer Interface Commands Status Line Popup Command Line Remove Temporary Message Display Error Log display error_log Display Event Log display event_log Command Line On/Off (toggles command line) Command Line Popup Command Line Position Cursor, Replace Mode <INSERT CHAR> key (when in insert mode) Position Cursor, Insert Mode <INSERT CHAR>...
Page 381: Syntax Conventions
Chapter 12: Emulator/Analyzer Interface Commands Syntax Conventions Conventions used in the command syntax diagrams are defined below. Oval-shaped Symbols Oval-shaped symbols show options available on the softkeys and other commands that are available, but do not appear on softkeys (such as log_commands and wait). These appear in the syntax diagrams as: Rectangular-shaped Symbols Rectangular-shaped symbols contain prompts or references to other syntax...
Page 382: Commands
Chapter 12: Emulator/Analyzer Interface Commands Commands Emulator/analyzer interface commands are summarized in the table below and described in the following pages. !UNIX_COMMAND display event_log modify memory bbaunload display global_symbols modify register break display local_symbols_in modify software_breakpoints cd (change directory) display memory name_of_module cmb_execute display pod_command...
Page 383: Break
Chapter 12: 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 384: 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 385: Cmb_Execute
Chapter 12: 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 386: Copy
Chapter 12: 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 387 Chapter 12: 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 388 This copies the information into a file without headings. pod_command This allows you to copy the most recent commands sent to the HP 64700 Series emulator/analyzer. printer This option specifies your system printer as the destination device for the copy command.
Page 389: Copy Local_Symbols_In
Chapter 12: 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 390: Copy Memory
Chapter 12: 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 391 Chapter 12: 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 392: Copy Registers
Chapter 12: 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 393: Copy Trace
Chapter 12: 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 394: Display
Chapter 12: 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 395 Chapter 12: 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 396: Display Data
Chapter 12: 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 397 Chapter 12: 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 398 Chapter 12: 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 399: Display Global_Symbols
Chapter 12: 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 400: Display Local_Symbols_In
Chapter 12: 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 401: Display Memory
Chapter 12: Emulator/Analyzer Interface Commands display memory display memory This command displays the contents of the specified memory location or series of locations.
Page 402 Chapter 12: 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 403 Chapter 12: 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 404 Chapter 12: 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 405: Display Registers
Chapter 12: 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 406: Display Simulated_Io
Chapter 12: 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 407: Display Software_Breakpoints
Chapter 12: 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 408: Display Trace
Chapter 12: 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 409 Chapter 12: Emulator/Analyzer Interface Commands display trace Addresses captured by the analyzer are physical addresses. The offset_by option subtracts the specified offset from the addresses of the executed instructions before listing the trace. With an appropriate entry for offset, each instruction in the listed trace will appear as it does in the assembled or compiled program listing.
Page 410 Chapter 12: 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 411 Chapter 12: 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 412: 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 the "Starting and Exiting HP 64700 Interfaces" chapter.
Page 413: Expr
Chapter 12: 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 414 Chapter 12: Emulator/Analyzer Interface Commands --EXPR-- valid when "C" appears on the status line, which indicates a valid expression has been defined. <NUMBER> This can be an integer in any base (binary, octal, decimal, or hexadecimal), or can be a string of characters enclosed with quotation marks. <OP>...
Page 415 Chapter 12: Emulator/Analyzer Interface Commands --EXPR-- disp_buf thru +25 is the same as disp_buf thru disp_buf + 25 Examples 05fxh 0ffffh disp_buf + 5 symb_tbl + (offset / 2) start mod_name: line 15 end See Also The SYMB syntax description.
Page 416: Fcode
Chapter 12: 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 417 Chapter 12: 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 418: Forward
Chapter 12: 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 419: Help
Chapter 12: 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 420 Chapter 12: Emulator/Analyzer Interface Commands help store 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 421: Load
Chapter 12: 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 422 Chapter 12: 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 423: Log_Commands
Chapter 12: 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 424: Modify
Chapter 12: 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 425: Modify Configuration
Chapter 12: 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 426: Modify Keyboard_To_Simio
Chapter 12: 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 427: Modify Memory
Chapter 12: 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 428 Chapter 12: 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 429 Chapter 12: 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 430: Modify Register
Chapter 12: 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. Register modification cannot be performed during real-time operation of the emulation processor.
Page 431: Modify Software_Breakpoints
Chapter 12: 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 432 Chapter 12: 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 433: Performance_Measurement_End
Chapter 12: 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 434: Performance_Measurement_Initialize
Chapter 12: 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 435 Chapter 12: 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 436: Performance_Measurement_Run
Chapter 12: 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 437 Chapter 12: Emulator/Analyzer Interface Commands performance_measurement_run Refer to the "Making Software Performance Measurements" chapter for examples of performance measurement specification and use.
Page 438 Chapter 12: 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 439: Pod_Command
Chapter 12: 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 440: Qualifier
Chapter 12: 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 441 Chapter 12: Emulator/Analyzer Interface Commands QUALIFIER trace only address range mod_name:clear thru read_input <RETURN> See Also The trace command.
Page 442: Range
Chapter 12: 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 443 This indicates that the following address expression is the upper address in a range. The following sofkeys are available if you have an emulation analyzer that has 64 channels (for example, HP 64703/704/794): The value following this softkey is searched for on the lines that monitor processor signals CS0 through CS3.
Page 444 Chapter 12: Emulator/Analyzer Interface Commands RANGE pberr A value of 0 qualifies the state as /BERR active. pbio The value following this softkey is searched for on the lines that monitor processor signals PB11 through PB8. A value of 0 qualifies the state as a write to ROM. extra Combines the edma, pbclr, cs, pberr, grd, rom, pbio, and ipl softkeys.
Page 445: Reset
Chapter 12: Emulator/Analyzer Interface Commands reset reset This command suspends target system operation and reestablishes initial emulator operating parameters. 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 446: 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 447 Chapter 12: Emulator/Analyzer Interface Commands address Specifies an address for a temporary register breakpoint that will be programmed into one of the processor’s two breakpoint registers. Up to two addresses may be specified. --EXPR-- An expression is a combination of numeric values, symbols, operators, and parentheses, specifying a memory address.
Page 448: Sequencing
Chapter 12: 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 449 Chapter 12: 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 450: Set
Chapter 12: Emulator/Analyzer Interface Commands...
Page 451 Chapter 12: 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 452 Chapter 12: 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 453 Chapter 12: 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 454 Chapter 12: 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 455: Specify
Chapter 12: 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 456 Chapter 12: 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 457: State
Chapter 12: 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 458 Chapter 12: 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 459: Step
Chapter 12: 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 460 Chapter 12: 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 461: Stop_Trace
Chapter 12: 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 462: Store
Chapter 12: 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 463 Chapter 12: Emulator/Analyzer Interface Commands store must precede the file name with a backslash (\) so the system will recognize it as a file name. 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.
Page 464: Symb
Chapter 12: Emulator/Analyzer Interface Commands --SYMB-- --SYMB--...
Page 465 Chapter 12: 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 466 Chapter 12: 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 467 Chapter 12: 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 468 Chapter 12: 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 469 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 470 Chapter 12: Emulator/Analyzer Interface Commands --SYMB-- and made a reference to symbol i2, the retrieval utilities attempt to find a symbol called porthand.c:process_port.BLOCK_1.i2 which would not be found. The symbol utilities would then strip BLOCK_1 from the current working symbol, yielding porthand.c:process_port.i2 which is a valid symbol.
Page 471: Trace
Chapter 12: 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 472 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 473 Chapter 12: 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 474: Trigger
Chapter 12: 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 475 Chapter 12: Emulator/Analyzer Interface Commands TRIGGER Examples trace after MAIN <RETURN> trace after 1000H then data 5 <RETURN> Also see the trace command examples. See Also The trace command. Also, refer to the "Making Coordinated Measurements" chapter.
Page 476: Wait
Chapter 12: 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 477 Chapter 12: 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 478: Window
Chapter 12: 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 479 Chapter 12: Emulator/Analyzer Interface Commands WINDOW See Also The trace command and the SEQUENCING and QUALIFIER syntax descriptions.
Page 481: Error Messages
Error Messages...
Page 482 Error Messages This chapter contains a list of error messages that may occur while operating the emulator and analyzer. The error log records error messages received during the emulation session. You may want to display the error log to view the error messages. Sometimes several messages will be displayed for a single error to help you locate a problem quickly.
Page 483: Graphical/Softkey Interface Messages - Unnumbered
Graphical/Softkey Interface Messages - Unnumbered Address range too small for request - request truncated Cause: Too small of an address range is specified in a modify memory command. Action: Specify a larger memory range. Cannot create module file: Cause: Insufficient disk space for the module file. Action: Check disk space under $HP64000.
Page 484 Cause: The host system could not continue the previous emulation session because it could not load the continue file. Action: Try again. If the failure continues, call your HP Service Representative. Continuing previous session, continue file loaded Cause: This is a status message. An emulation session which was ended earlier with the end command has been restarted.
Page 485 (performance verification) command on the emulator to verify that it is functioning properly. Also, verify proper software installation. If loading default configuration still fails, then call your HP 64000 representative. <CONFIGURATION FILENAME> does not exist Cause: The configuration file you are trying to load does not exist.
Page 486 Emul700dmn queue failure Emul700dmn error in file operation Emul700dmn queue full Cause: The HP 64700 emulator daemon process command was too large for the host system to process. Action: You must press end_release_system to exit this emulation session completely; then start a new session. Make sure the host system is operating...
Page 487 Emul700dmn version incompatible with this product Cause: The emulation session could not begin because the version of the HP 64700 emulator daemon executable on host system is not compatible with the version of the Softkey Interface you are using.
Page 488 Error in configuration process Error starting configuration process Cause: Unexpected configuration error. Action: Verify proper software installation and call your HP 64000 representative. Fatal error from function <ADDRESS OF FUNCTION> Cause: This is an unexpected fatal system error. Action: Cycle power on the emulator and start again. If this is a persistent problem, call your HP 64000 representative.
Page 489 Cause: A user abort occurred while attempting to connect via LAN. Action: Possibly connecting to an emulator many miles away, be patient. HP 64700 I/O error; power down detected Cause: The emulator power was cycled. Action: Do not do this during a user interface session; this may force the user interface to end immediately.
Page 490 Chapter 13: Error Messages Graphical/Softkey Interface Messages - Unnumbered Illegal symbol name Cause: You tried to specify incorrect symbol names when entering commands. Action: Specify correct symbol names. To see global symbol names, use the display global_symbols command. To see local symbol names, use the display local_symbols_in <SYMB>...
Page 491 Chapter 13: Error Messages Graphical/Softkey Interface Messages - Unnumbered Invalid answer in <CONFIGURATION FILENAME> ignored Cause: You must provide acceptable responses to questions in the configuration file (file.EA). The emulator ignored the incorrect response. Incorrect responses may appear in configuration files when you have saved the configuration to a file, edited it later, and tried reloading it into the emulator.
Page 492 Chapter 13: Error Messages Graphical/Softkey Interface Messages - Unnumbered Load aborted Cause: While loading a file into the emulator, an event occurred that caused the host system to stop the load process. Action: Use the display error_log command to view any errors. If the problem persists, make sure the host system and emulator are operating properly, and that you are trying to load an acceptable file.
Page 493 Chapter 13: Error Messages Graphical/Softkey Interface Messages - Unnumbered Action: Limit the modify memory command to not overflow physical 0 or break the command into two separate modify commands. No address label defined Cause: The address trace label was somehow removed in the terminal interface using the tlb command.
Page 494 Chapter 13: Error Messages Graphical/Softkey Interface Messages - Unnumbered Not a valid trace file - load aborted Cause: You tried to load a file.TR that was not created by the emulation session. Action: Only load trace data files that were created by the emulator. Not compatible trace file - load aborted Cause: You tried to load a file.TR that was created by another type of emulator.
Page 495 Chapter 13: Error Messages Graphical/Softkey Interface Messages - Unnumbered Perfinit - error in input file line <NUMBER> Cause: You included an input file name with your "performance_measurement_initialize" command, and that file contains a syntax error. Action: Edit the file and correct the syntax error. Perfinit <—-EXPR—- ERROR>...
Page 496 Chapter 13: Error Messages Graphical/Softkey Interface Messages - Unnumbered Performance tool not initialized Cause: The Software Performance Measurement Tool (SPMT) has not been initialized. Action: To make accurate activity or duration measurements on current data, use the performance_measurement_initialize command to initialize the SPMT before running a performance measurement.
Page 497 Cause: The emulator was started using a new emulation session, and the user interface was set to default selections. Action: Call your HP Service Representative. Status unknown, run "emul700 -l <LOGICAL NAME>" Cause: The host system cannot determine the status of the emulator.
Page 498 Example: display trace symbols on. Timeout in emul700dmn communication Cause: The host system could not start the emulation session because the HP 64700 emulator process ran out of time before the emulator could start. Action: You must press end_release_system to exit this emulation session completely;...
Page 499 Unexpected message from emul700dmn Cause: The host system could not start the emulation session because of an unexpected message from the HP 64700 emulator process command. Action: You must press end_release_system to exit this emulation session completely; then start a new session. Make sure the host system is operating...
Page 500: Graphical/Softkey Interface Messages - Numbered
Chapter 13: Error Messages Graphical/Softkey Interface Messages - Numbered Graphical/Softkey Interface Messages - Numbered These numbered messages can occur because of various problems with the emulator/analyzer. 10315 Logical emulator name unknown; not found in 64700tab file Cause: This message may occur while trying to start up the emulator. It indicates that the emulator name specified could not be found in the 64700tab.net or /etc/hosts files.
Page 501 Cause: There may be characters dropped in the information returned from the emulator. Action: Ignore this message unless it becomes frequent. If it becomes frequent, you may have a fatal error; call your HP 64700 representative. 10351 Exceeded maximum 64700 command line length Cause: Your command is longer than 240 characters.
Page 502 Chapter 13: Error Messages Graphical/Softkey Interface Messages - Numbered Action: Upgrade the interface software of product firmware. 10360 Analyzer limitation; all range resources in use Analyzer limitation; all pattern resources in use Analyzer limitation; all expression resources in use Cause: Your trace specification would use more than the maximum number of resources available to the analyzer.
Page 503: Terminal Interface Messages
Chapter 13: Error Messages Terminal Interface Messages Terminal Interface Messages This section contains descriptions of error messages that can occur while using the Terminal Interface. The error messages are listed in numerical order, and each description includes the cause of the error and the action you should take to remedy the situation.
Page 504 Chapter 13: Error Messages Terminal Interface Messages Action: You must break the emulator’s execution into the monitor before you can enter the command. Emulator is in the reset state Cause: You have entered a command that requires the emulator to be running in the monitor (for example, displaying registers).
Page 505 Chapter 13: Error Messages Terminal Interface Messages Stack is in emulation ROM Cause: Your stack pointer pointed to a location in memory mapped as emulation ROM; you then attempted to run or step the emulation processor. The emulator was unable to access the stack to complete the transition from the monitor to the user program or vice versa.
Page 506: 68302 Emulator Messages
Chapter 13: Error Messages Terminal Interface Messages Monitor failure; halted Cause: The monitor is unable to run because the processor is halted (due to an external halt line or a halt instruction). Action: Release the external halt and retry the operation. If the processor halted due to a halt instruction, try the reset command, then retry the operation.
Page 507 Chapter 13: Error Messages Terminal Interface Messages Action: Reset the emulator. Check your foreground monitor source code to verify that it keeps the processor in the supervisor state and does not make transitions into the user program state. Supervisor stack in guarded memory at <address> Cause: The supervisor stack either was defined in or grew into a memory range mapped as guarded.
Page 508 HP 64170A has missing memory module: bank <bank number> Action: Make sure the HP 64170 memory board has at least one memory module installed in bank 0. It is not required for bank 1 to have a memory module. This must be corrected for the emulator to function correctly.
Page 509 HP 64170A has unrecognized memory module: bank <bank number> Cause: The HP 64170 memory board has detected an unusable memory module. Action: Verify that a memory module is installed in the bank in question. If the correct memory module is installed, or if there is no memory module installed, a hardware fault may be present.
Page 510: General Emulator And System Messages
Action: Write down the sequence of commands which caused the error. Cycle power on the emulator and reenter the commands. If the error repeats, call your local HP Sales and Service office for assistance. Incompatible compatibility table entry Cause: The emulation firmware (ROM) is not compatible with the analysis or system firmware in your HP 64700 system.
Page 511 Records expected: %s; records received: %s Cause: The HP 64700 received a different number of records than it expected to receive during a transfer operation. Action: Retry the transfer. If the failure is repeated, make sure that the data communications parameters are set correctly on the host and on the HP 64700.
Page 512 Chapter 13: Error Messages Terminal Interface Messages Transfer failed to start Cause: Communication link or transfer protocol incorrect. Action: Check link and transfer options. Timeout, receiver failed to respond Cause: Communication link or transfer protocol incorrect. Action: Check link and transfer options. Adjust PC failed during break Cause: System failure or target condition.
Page 513 Chapter 13: Error Messages Terminal Interface Messages Unable to run after CMB break Cause: System failure or target condition. Action: Run performance verification (Terminal Interface pv command), and check target system. Unable to break Cause: This message is displayed if the emulator is unable to break to the monitor because the emulation processor is reset, halted, or is otherwise disabled.
Page 514 Chapter 13: Error Messages Terminal Interface Messages Analyzer Break Cause: Status message. Guarded memory access break Cause: This message is displayed if the emulation processor attempts to read or write memory mapped as guarded. Action: Troubleshoot your program; or, you may have mapped memory incorrectly. Software breakpoint: %s Cause: This status message will be displayed if a software breakpoint is encountered during a program run.
Page 515 Chapter 13: Error Messages Terminal Interface Messages Unexpected software breakpoint Cause: If you have enabled software breakpoints, this message is displayed if a software breakpoint instruction is encountered in your program that was not inserted by a modify software_breakpoints set command and is therefore not in the breakpoint table.
Page 516 Chapter 13: Error Messages Terminal Interface Messages Guarded memory break: %s" Cause: A memory access to a location mapped as guarded memory has occurred during execution of the user program. Action: Investigate the cause of the guarded memory access by the user program. Write to ROM break: %s"...
Page 517 Action: Initialize the emulator or cycle power. Then reenter the command. If the same failure occurs, call your HP sales and service office. Unable to configure break on software breakpoints Cause: The emulator controller cannot enable breakpoints, possibly because the emulator is in an unknown state or because of a hardware failure.
Page 518 Chapter 13: Error Messages Terminal Interface Messages Software breakpoint break condition is disabled Cause: You have attempted to set or clear a software breakpoint when software breakpoints are disabled. Action: You must enable software breakpoints before you can set them. Specified breakpoint not in list: %s Cause: You tried to clear a software breakpoint that was not previously set.
Page 519 Chapter 13: Error Messages Terminal Interface Messages Breakpoint not added: %s Cause: You tried to insert a breakpoint in a memory location which was not mapped or was mapped as guarded memory. Action: Insert breakpoints only within memory ranges mapped to emulation or target RAM or ROM.
Page 520 Chapter 13: Error Messages Terminal Interface Messages Action: Check memory mapping and configuration questions. Break due to cause other than step Cause: An activity other than a step command caused the emulator to break. This could include any of the break conditions or a <CTRL>c break. Trace error during CMB execute Cause: System failure.
Page 521 Action: Retry the operation. If breaks are occurring continuously, you may wish to disable some of the break conditions. Invalid firmware for emulation subsystem Cause: This error occurs when the HP 64700 system controller determines that the emulation firmware (ROM) is invalid.
Page 522 Be sure that the correct ROM is installed in the emulation controller. Invalid analysis subsystem; product address: %s Cause: This error occurs when the HP 64700 system controller determines that the analysis firmware (ROM) is invalid. Action: This message is not likely to occur unless you have upgraded the ROMs in your emulator.
Page 523: Analyzer Messages
Chapter 13: Error Messages Terminal Interface Messages Analyzer Messages 1105 Unable to delete label; used by emulation analyzer: <label> Cause: This error occurs when you attempt to delete an emulation trace label which is currently being used as a qualifier in the emulation trace specification or is currently specified in the emulation trace format.
Page 524 Chapter 13: Error Messages Terminal Interface Messages 1110 Unable to redefine label; used by external timing analyzer: <label> Cause: This error occurs when you attempt to redefine an emulation or external trace label which is currently being used as a qualifier in the external timing trace specification.
Page 525 Chapter 13: Error Messages Terminal Interface Messages 2022 Sample period out of bounds: <bounds> Cause: The external timing sample period must be between 10 ns and 50 ms (in a 1/2/5 sequence). Action: Re-enter the command with the sample period between the bounds shown. 2030 Negated patterns not allowed in timing Cause: This error occurs when you attempt to specify a "not equals"...
Page 527: Specifications And Characteristics
Specifications and Characteristics...
Page 528: Emulator Specifications And Characteristics
The following specifications are for an emulator with a clock speed of 16.67 MHz. Maximum Clock Speed The maximum external clock speed is at least 20 MHz for the HP 64746 emulator. No wait states are required for emulation or target system memory. (The internal clock speed is 16 MHz.) Power The emulator draws an additional 40 milliamps from the target system when operating at 16.67 MHz.
Page 529 Chapter 14: Specifications and Characteristics Emulator Specifications and Characteristics Address and Function Codes One 74FCT245A load per bit plus 50 pf capacitance. Clocks One 74ACT load per bit plus 20 pf capacitance. Chip Selects One 74FCT244A load per bit plus 50 pf capacitance. Interrupts One F load per bit plus a 3.3K pullup and 50 pf capacitance.
Page 530 Chapter 14: Specifications and Characteristics Emulator Specifications and Characteristics Processor Emulator Worst Typical Description Unit Symbol Min Max Min Max Min Max Clock Period 16.7 8 16.7 - Clock Pulse Width Tcvc Clock Rise and Fall times Tcr,Tcf EXTAL to CLK0 Delay Clock High to FC, Addr valid Tchfcadv - Clock High to addr, data - Z...
Page 531 Chapter 14: Specifications and Characteristics Emulator Specifications and Characteristics Processor Emulator Worst Typical Description Unit Symbol Min Max Min Max Min Max AS,DS negated to data invalid Tshdoi Data Out to DS asserted write Tdosl Data Valid to Clock low (setup) Tdicl AS,DS negated to DTACK negated Tshdah...
Page 532 Chapter 14: Specifications and Characteristics Emulator Specifications and Characteristics Processor Emulator Worst Typical Description Unit Symbol Min Max Min Max Min Max Data Out hold from clock high Tchdoi RW asserted to Data bus change Trldbd HALT,RST pulse width clks Thrpw BGACK negated to AS,DS,RW drive clks Tgasd...
Page 533: Physical
Chapter 14: Specifications and Characteristics Emulator Specifications and Characteristics Electrical Characteristics of the HP 64700 The electrical characteristics of the HP 64700 communication ports are as follows. Communications Serial Port RS-232-C DCE or DTE to 38.4 Kbaud. RS-422 DCE to 460.8 Kbaud.
Page 534: Environmental
Chapter 14: Specifications and Characteristics Emulator Specifications and Characteristics Environmental Temperature Operating 0°C to +55°C (+32°F to 131°F) Non-operating -40°C to +70°C (-40°F to 158°F) Altitude Operating 4 600m (15 000 ft) Non-operating 15 300m (50 000 ft). Relative Humidity 15% to 95%.
Page 535: Part 4 Concept Guide
Part 4 Concept Guide...
Page 536 Part 4...
Page 537: Concepts
Concepts...
Page 538 Concepts This chapter provides conceptual information on the following topics: • X resources and the Graphical User Interface.
Page 539: Resources And The Graphical User Interface
Chapter 15: Concepts X Resources and the Graphical User Interface X Resources and the Graphical User Interface This section contains more detailed information about X resources and scheme files that control the appearance and operation of the Graphical User Interface. This section: •...
Page 540 Chapter 15: Concepts X Resources and the Graphical User Interface Class Names or Instance Names Can Be Used When specifying resource names, you can use either instance names or class names. For example, a "Done" pushbutton may have an instance name of "done" and a class name of "XmPushButton".
Page 541: How X Resource Specifications Are Loaded
Chapter 15: Concepts X Resources and the Graphical User Interface Specific Names Override General Names A more specific resource specification will override a more general one when both apply to a particular widget or application. The names for the application and the main window widget in HP64_Softkey applications have been chosen so that you may specify custom resource values that apply in particular situations: Apply to ALL HP64_Softkey applications:...
Page 542 Load Order Resource specifications are loaded from the following places in the following order: The application defaults file. For example, /usr/lib/X11/app-defaults/HP64_Softkey when the operating system is HP-UX or /usr/openwin/lib/X11/app-defaults/HP64_Softkey when the operating system is SunOS. The $XAPPLRESDIR/HP64_Softkey file. (The XAPPLRESDIR environment variable defines a directory containing system-wide custom application defaults.)
Page 543: Scheme Files
This resource should be set to the platform on which the X server is running (and displaying the Graphical User Interface) if it is different than the platform where the application is running. Values can be: HP-UX, SunOS, pc-xview, or a custom platform scheme directory name.
Page 544 Chapter 15: Concepts X Resources and the Graphical User Interface HP64_Softkey.sizeScheme: Names the size scheme file which defines the fonts and the spacing used. Values can be: Large, Small, or a custom scheme file name. HP64_Softkey.inputScheme: Names the input scheme file which specifies mouse and keyboard operation. Values can be: Input, or a custom scheme file name.
Page 545 You can modify scheme files by copying them to the directory for user-defined schemes and changing the resource specifications in the file. For example, if you wish to modify the color scheme, and your platform is HP-UX, you can copy the $HP64000/lib/X11/HP64_schemes/HP-UX/Softkey.Color file to $HOME/.HP64_schemes/HP-UX/Softkey.Color and modify its resource...
Page 547 Part 5 Installation Guide...
Page 548 Part 5...
Page 549 Installation...
Page 550 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 551 Chapter 16: Installation From here, you should proceed to the section titled "Installation for HP 9000 Hosted Systems" for instructions on how to install, verify, and start the Graphical User Interface on HP 9000 systems. Minimum Sun SPARCsystem Hardware and System Requirements The following is a set of minimum hardware and system recommendations for operation of the Graphical User Interface on Sun SPARCsystem workstations.
Page 552 – HP 64746A/G 68302 Emulator, 128 Kbytes emulation memory. – HP 64746B/H 68302 Emulator, 512 Kbytes emulation memory. – HP 64746J 68302 Emulator, uses the HP 64170 memory board which can contain up to 4 Mbytes of emulation memory. •...
Page 553 Do NOT stand the HP 64700 on the rear panel. You could damage the rear panel ports and connectors. If your emulator and analyzer boards are already installed in the HP 64700 Card Cage, go to "Step 2. Connect the HP 64700 to a Host Computer or Terminal".
Page 554 Step 1. Install Boards into the HP 64700 Card Cage 1 Use a ground strap when removing or installing boards into the HP 64700 Card Cage. A jack on the rear panel of the HP 64700 Card Cage is provided for this purpose.
Page 555 Chapter 16: Installation Step 1. Install Boards into the HP 64700 Card Cage 2 Turn the thumb screw and remove the top cover by sliding the cover toward the rear and up.
Page 556 Chapter 16: Installation Step 1. Install Boards into the HP 64700 Card Cage 3 Remove the side cover by unsnapping the two latches and lifting off. 4 Remove the card supports.
Page 557 Chapter 16: Installation Step 1. Install Boards into the HP 64700 Card Cage 5 First, completely loosen the four egress thumb screws. To remove emulator cards, insert a flat blade screwdriver in the access hole and eject the emulator cards...
Page 558 6 Insert a screw driver into the third slot of the right side of the front bezel, push to release catch, and pull the right side of the bezel about one half inch away from the front of the HP 64700. Then, do the same thing on the left side of the bezel.
Page 559 Chapter 16: Installation Step 1. Install Boards into the HP 64700 Card Cage 7 Lift the bezel panel to remove. Be careful not to put stress on the power switch extender. 8 If you’re removing an existing analyzer card that provides external analysis, remove the right angle...
Page 560 9 To remove the analyzer card, insert a flat blade screwdriver in the access hole and eject the analyzer card by rotating the screwdriver. Do not remove the system control board. This board is used in all HP 64700 emulation and analysis systems.
Page 561 10 Install HP 64703A (or HP 64704/6) and HP 64746 boards. The HP 64703A (or HP 64704/6) is installed in the slot next to the system controller board. The HP 64746 boards are installed in the bottom two slots of the HP 64700 with the memory board above the board that has the emulator probe. These boards are identified with labels that show the model number and the serial number.
Page 562 Chapter 16: Installation Step 1. Install Boards into the HP 64700 Card Cage 11 If you installed the HP 64703A analyzer card, install the right angle adapter board by turning the thumb screws clockwise. Connect the external analyzer probe cable to the right angle adapter board. Each connector of the external analyzer cable is keyed so that it can be connected to the right angle adapter board in only one way.
Page 563 Chapter 16: Installation Step 1. Install Boards into the HP 64700 Card Cage 12 To reinstall the front bezel, be sure that the bottom rear groove of the front bezel is aligned with the lip as shown below.
Page 564 Chapter 16: Installation Step 1. Install Boards into the HP 64700 Card Cage 13 Install the card supports. 14 To install the side cover, insert the side cover into the tab slots and fasten the two latches.
Page 565 Chapter 16: Installation Step 1. Install Boards into the HP 64700 Card Cage 15 Install the top cover in reverse order of its removal, but make sure that the side panels of the top cover are attached to the side clips on the frame.
Page 566 The HP 64700B automatically selects the 115 Vac or 220 Vac range. In the 115 Vac range, the HP 64700B will draw a maximum of 345 W and 520 VA. In the 220 Vac range, the HP 64700B will draw a maximum of 335 W and 600 VA.
Page 567 8120-2857 Brown * Part number shown for plug is industry identifier for plug only. Number shown for cable is HP part number for complete cable including plug. ** These cords are included in the CSA certification approval for the equipment.
Page 568 8120-4754 90/230 * Part number shown for plug is industry identifier for plug only. Number shown for cable is HP part number for complete cable including plug. ** These cords are included in the CSA certification approval for the equipment.
Page 569 The line switch is a push button located at the lower left hand corner of the front panel. To turn ON power to the HP 64700, push the line switch button in to the ON (1) position. The power light at the...
Page 570 Connecting the HP 64700 to a Computer or LAN Refer to the HP 64700 Series Installation/Service Guide for instructions on connecting the HP 64700 to a host computer (via RS-422 or RS-232) or LAN and setting the HP 64700’s configuration switches. (RS-422 and RS-232 are only...
Page 571 Step 1. Install the software from the media Installing HP 9000 Software This section shows you how to install the Graphical User Interface on HP 9000 workstations. These instruction also tell you how not to install the Graphical User Interface if you want to use just the conventional Softkey Interface.
Page 572 /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 573 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 574 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 575 -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 576 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 577 Chapter 16: Installation Step 1. Install the software from the media Installing Sun SPARCsystem Software This section shows you how to install the Graphical User Interface on Sun SPARCsystem workstations. These instructions also tell you how not to install the Graphical User Interface if you want to use just the conventional Softkey Interface.
Page 578 Chapter 16: Installation Step 2. Start the X server and OpenWindows Step 2. Start the X server and OpenWindows If you are not already running the X server, do so now. The X server is required to run the Graphical User Interface because it is an X application. •...
Page 579 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 580 Chapter 16: Installation Step 4. Verify the software installation 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 581 Chapter 16: Installation Step 5. Map your function keys 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 582 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 583 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 584 Chapter 16: Installation Step 2. Start the interface with the emul700 command Graphical User Interface. Otherwise, emul700 starts the conventional Softkey Interface. You should include an ampersand ("&") with the command to start the Graphical User Interface as a background process. Doing so frees the terminal window where you started the interface so that the window may still be used.
Page 585 Chapter 16: Installation Step 2. Start the interface with the emul700 command...
Page 586 Chapter 16: Installation Step 3. Exit the Graphical User Interface 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 587 Glossary access mode Specifies the types of cycles used to access target system memory locations. For example a "byte" access mode tells the monitor program to use load/store byte instructions to access target memory. analyzer An instrument that captures data on signals of interest at discreet periods.
Page 588 Individual levels of the sequencer. The HP 64705A analyzer provides 8 sequence terms.
Page 589 Glossary sequencer branch Occurs when the analyzer finds the primary or secondary branch state specified at a certain level and begins searching for the states specified at another level. target system The microprocessor system which the emulator plugs into. trace A collection of states captured on the emulation bus (in terms of the emulation bus analyzer) or on the analyzer trace signals (in terms of the external analyzer) and stored in trace memory.
Page 591 Index 68302 chip selects, 137 68302 internal DMA, 128 68302 internal memory space mapping, 121 about, trigger position specification, 256 absolute count, in the trace display, 280 absolute files, 421 loading, 181 loading without symbols, 182 storing memory contents into, 182 absolute status, in the trace display, 274 access mode, 587 access size (target memory), 134...
Page 592 125 analyzer, 587 arbitration analysis, 129 arming other HP 64700 Series analyzers, 5 breaking emulator execution into the monitor, 4 breaking execution of other HP 64700 Series emulators, 5 count qualifiers, 262 definition, 4 general description, 4 occurrence count, 259...
Page 593 OFF the HP 64700, 144 protect emulator against static discharge, 143 real-time dependent target system circuitry, 110 rear panel, do not stand HP 64700 on, 553 changing directory context in configuration window, 105 directory context in emulator/analyzer window, 192...
Page 594 See also slave clocks closing emulator/analyzer windows, 59 CMB (coordinated measurement bus), 336 EXECUTE line, 338, 385 HP 64700 connection, 339 READY line, 337 signals, 337 TRIGGER line, 337 cmb_execute command, 344, 385 color scheme, 358, 362, 544 column width, trace display option, 279...
Page 595 Index command select mouse button, 29 commands, 83 combining on a single command line, 83 completion, 83 editing in command line entry area, 80-81 entering in command line, 79 executing in command line, 79 keyboard entry, 83 line erase, 84 map, 126 recall, 84 recalling with dialog box, 82...
Page 596 Index storing, 104 context changing directory in configuration window, 105 changing directory in emulator/analyzer window, 192 changing symbol, 193 displaying directory from configuration window, 106 displaying directory from emulator/analyzer window, 192 displaying symbol, 192 coordinated measurements, 345 break_on_trigger syntax of the trace command, 345 definition, 336 copy command, 386-388 data, 387...
Page 597 Index pod commands screen to file, 236 registers to file, 235 trace listing to file, 235 count absolute/relative, trace display option, 280 count qualifiers, 262 count, occurrence, 259 cursor buttons, 28 data copy command, 387 display command, 396-398 data (analyzer state qualifier softkey), 254, 443, 458 data (external), trace display option, 283 data bus width, 134 data value...
Page 598 Index displaying from configuration window, 106 displaying from emulator/analyzer window, 192 Directory Selection dialog box operation, 73, 76 display area, 27 columns, 359 lines, 359-360 screen to file, 235 display command, 394-395 data, 396-398 error_log, 394 event_log, 395 global_symbols, 399 local_symbols_in, 400 memory, 401-404 memory mnemonic, 33, 219...
Page 599 Index DMA limitations, 128 DMA, internal 68302, 128 don’t care digits, 252 downloading absolute files, 5, 181 driving background cycles to target system, 135 DTACK, 137 interlock, needed for correct bus error response, 131 source, emulator configuration, 137 DTACK interlock, 130 DTACK when out-of-circuit, 130 dual-port emulation memory, 110 dummy part, 148...
Page 600 Index foreground or background, 112-119 function of, 112 emulation session exiting, 60 emulation, external analyzer mode, 328 emulator, 588 bus error response, 131 configuring the, 96 data bus width, 134 device table file, 32, 53-54 dimensions, 533 electrical characteristics, 528 environmental characteristics of, 534 error messages, 503 general description, 4...
Page 601 Index load command, 422 loading from file, 107 modify command, 425 modifying a configuration section, 102 monitor entry after, 109 restrict to real-time runs, 110 starting the configuration interface, 100 storing, 104 supervisor stack pointer reset value, 133 target memory access size, 134 target system interrupts enable/disable, 132 trace background/foreground operation, 140 TRAP instruction for breakpoint, 139...
Page 602 Index recalling entries, 71 symbol width and copy-and-paste to, 69 text entry, 68 with action keys, 71, 73 with pulldown menus, 71 Entry Buffer Recall dialog box operation, 74 environment variables DISPLAY, 575, 578 HP64000, 575, 579 KEYMAP, 581 LD_LIBRARY_PATH, 579-580 MANPATH, 576, 580 PATH, 576, 579 environment variables (UNIX)
Page 603 Index emulation session, 60 emulator/analyzer windows, 59 expressions, 251 --EXPR-- syntax, 413-415 external analyzer configuration, 325-333 general description, 4 labels, 326, 332 mode, 328 should emulation control?, 326 using, 320 external data, trace display option, 283 file breakpoints screen to, 235 data values screen to, 235 display area to, 235 editing, 232...
Page 604 121, 125, 264 halfbright, 79-80 halt, trace, 247 hand pointer, 27, 67 hardware HP 9000 memory needs, 550 HP 9000 minimum performance, 550 HP 9000 minimums overview, 550 SPARCsystem memory needs, 551 SPARCsystem minimum performance, 551 SPARCsystem minimums overview, 551...
Page 605 85 softkey driven information, 85 help command, 419-420 help index, displaying, 77 hexadecimal numbers, 252 HP 64700 Operating Environment, minimum version, 551 HP 9000 700 series Motif libraries, 550 HP-UX minimum version, 550 installing software, 571 minimum system requirements overview, 550...
Page 606 358, 362, 544 labels configuration file, 333 LANG environment variable, 544 LD_LIBRARY_PATH environment variable, 579-580 libraries, Motif for HP 9000/700, 550 limitations, DMA, 128 line numbers (source file), symbol display, 185 line numbers (trace) displaying about, 273 line numbers (trace), displaying about, 272...
Page 607 125 overlaid addresses, 125 resolution, 120 using emulation memory in place of target, 126 memory recommendations HP 9000, 550 SPARCsystem, 551 memory refresh, 98 menus editing command line with popup, 81 hand pointer means popup, 27, 67...
Page 608 112-119 foreground/background comparison, 114 function code selection, 116 function of, 112 selecting, 112-119 selecting entry after configuration, 109 Motif, HP 9000/700 requirements, 550 mouse choosing menu items, 65 mouse buttons, 29 mouse, choosing menu items, 64 multi-window...
Page 609 281 on-line help, 85 on_halt, trace command option, 264 only, trace command storage qualifier, 260 operating system HP 64700 Series minimum version, 551 HP-UX minimum version, 550 SunOS minimum version, 551 operators, 252 OR0-OR3 registers, 137...
Page 610 434-435 performance_measurement_run command, 436-437 physical characteristics of the emulator, 533 pin extender, 145 platform HP 9000 memory needs, 550 HP 9000 minimum performance, 550 SPARCsystem memory needs, 551 SPARCsystem minimum performance, 551 platform scheme, 358, 543 plug-in, 142...
Page 611 Index mnemonic memory display, 34 running from, 194 pulldown menus choosing with keyboard, 65 choosing with mouse, 64-65 pushbutton select mouse button, 29 QFP probe, 148 QUALIFIER, in trace command, 440-441 qualifiers, 254 count, 262 prestore, 261 simple trigger, 256 slave clock, 329 storage, 260 RAM, mapping emulation or target, 121...
Page 612 Index to file, 235 registers, displaying, 39 relative count, in the trace display, 280 relative humidity, operating and non-operating environments, 534 release_system, end command option, 47, 60, 104 repetitive display of memory, 223 reset (emulator), commands which cause exit from, 199 reset command, 445 reset SSP and foreground monitor, 133 reset value for supervisor stack pointer, 133...
Page 613 329 Slow clock, emulator status message, 108 softkey driven help information, 85 softkey pushbuttons, 27 softkeys, 83 software installation for HP 9000, 571 installation for SPARCsystems, 577 software breakpoints, 200-212 clearing, 210 clearing all, 212 copy command, 388...
Page 614 Index activity measurements, 291-305 adding traces, 296, 310 duration, 306-314 end, 433 ending, 316 how they are made, 290 initialize, 434-435 initializing, 294, 309 initializing, default, 294 initializing, duration measurements, 309 initializing, user defined ranges, 295, 309 initializing, with global symbols, 295 initializing, with local symbols, 295 memory activity, 291, 298 module duration, 306...
Page 615 Index Stack is in guarded memory, error message, 133 stack pointer (supervisor), reset value, 133 state, external analyzer mode, 328 STATE, in trace command, 457-458 static discharge, protecting the emulator probe against, 143 status copy command, 388 display command, 244, 395 status (analyzer state qualifier softkey), 254, 443, 458 predefined values for, 256 status line, 27...
Page 616 Index --SYMB-- syntax, 464-470 trace display, 278 synchronous measurements, 343 syntax conventions, 381 system requirements HP 64700 minimum version, 551 HP 9000 overview, 550 HP-UX minimum version, 550 OSF/Motif HP 9000/700 requirements, 550 SPARCsystem overview, 551 SunOS minimum version, 551...
Page 617 Index loading, 286-287 on_halt, 264 prestore qualifier, 261 recalling trace specifications, 250 starting the, 244 stopping the, 247 storage qualifier, 260 storage qualifier with prestore, 261 store command, 463 storing, 286-287 Trace Specification Selection dialog box, 250 trigger position, 256 trace command, 471-473 default, 244 loading and storing, 284-285...
Page 618 Index software breakpoints (68302), 200 trigger, 589 condition, 256 position, 256 position, accuracy of, 257 specifying a simple, 256 stop driving on break, 350 TRIGGER, CMB signal, 337 TRIGGER, in trace command, 474-475 trom, memory characterization, 121 TTL (softkey for specifying threshold voltages), 327 tutorials setting up, 367-369 undefined software breakpoint, 200...
Page 619 236 windows opening additional emulator/analyzer, 57 running the emulator/analyzer interface in multiple, 53 workstation HP 9000 memory needs, 550 HP 9000 minimum performance, 550 SPARCsystem memory needs, 551 SPARCsystem minimum performance, 551 write to ROM break, 138...
Page 620 Index X server, 356, 542 X Window System, 53 xbits, external analyzer label, 332 XEnv_68k_except symbol and effect on breakpoionts, 203...
Page 621 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 622 No other warranty is expressed or implied. HP specifically disclaims the implied warranties of merchantability and fitness for a particular purpose.
Page 623 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 624 Do Not Service Or Adjust Alone Do not attempt internal service or adjustment unless another person, capable of rendering first aid and resuscitation, is present. Do Not Substitute Parts Or Modify Instrument Because of the danger of introducing additional hazards, do not install substitute parts or perform any unauthorized modification of the instrument.
Page 625 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 626 Caution The Caution sign denotes a hazard. It calls your attention to an operating procedure, practice, condition, or similar situation, which, if not correctly performed or adhered to, could result in damage to or destruction of part or all of the product. Warning The Warning sign denotes a hazard.

This manual is also suitable for:

68302

HP 64746 User Manual

Quick Links

Related Manuals for HP 64746

Summary of Contents for HP 64746