HP 7700 Series User Manual
HP 7700 Series User Manual

HP 7700 Series User Manual

Emulator softkey interface
Table of Contents

Advertisement

Quick Links

HP 64146
7700 Series Emulator
Softkey Interface
User's Guide
HP Part No. 64146-97005
Printed in U.S.A.
February 1994
Edition 2

Advertisement

Table of Contents
loading

Summary of Contents for HP 7700 Series

  • Page 1 HP 64146 7700 Series Emulator Softkey Interface User’s Guide HP Part No. 64146-97005 Printed in U.S.A. February 1994 Edition 2...
  • Page 3 Hewlett-Packard Company. The information contained in this document is subject to change without notice. AdvanceLink, Vectra and HP are trademarks of Hewlett-Packard Company. IBM and PC AT are registered trademarks of International Business Machines Corporation.
  • Page 4 Printing History New editions are complete revisions of the manual. The date on the title page changes only when a new edition is published. A software code may be printed before the date; this indicates the version level of the software product at the time the manual was issued. Many product updates and fixes do not require manual changes, and manual corrections may be done without accompanying product changes.
  • Page 5 Using This Manual This manual introduces you to the HP 64146A/B 7700 Series Emulator as used with the Softkey Interface. This manual: Shows you how to use emulation commands by executing them on a sample program and describing their results.
  • Page 6 Organization Chapter 1 Introduction to the 7700 Series Emulator. This chapter briefly introduces you to the concept of emulation and lists the basic features of the 7700 Series emulator. Chapter 2 Getting Started. This chapter shows you how to use emulation commands by executing them on a sample program.
  • Page 7 Commands, options, and parts of command syntax which may be entered by pressing softkeys. normal User specified parts of a command. Represents the HP-UX prompt. Commands which follow the "$" are entered at the HP-UX prompt. <RETURN> The carriage return key.
  • Page 8 Notes...
  • Page 9: Table Of Contents

    Introduction ......1-1 Purpose of the 7700 Series Emulator ....1-1 Supported Microprocessors .
  • Page 10 From the "pmon" User Interface ....2-8 From the HP-UX Shell ..... . 2-9 On-Line Help .
  • Page 11 Prerequisites ......3-1 Installing the Target System Probe ....3-2 In-Circuit Configuration Options .
  • Page 12 Running the Example ..... . . 5-2 Features Available via Pod Commands ....5-4 Debugging C Programs .
  • Page 13 Illustrations Figure 1-1. HP 64146 Emulator for MELPS 7700 Series ..1-2 Figure 2-1. Connecting the Emulation Pod ... . . 2-3 Figure 2-2. Sample Program Listing ....2-4 Figure 2-3.
  • Page 14 Notes 6-Contents...
  • Page 15: Introduction To The 7700 Series Emulator

    Emulator (usually referred to as the target system). The emulator performs just like the MELPS 7700 Series microprocessor, but is a device that allows you to control the MELPS 7700 Series directly. These features allow you to easily debug software before any hardware is available, and ease the task of integrating hardware and software.
  • Page 16: Figure 1-1. Hp 64146 Emulator For Melps 7700 Series

    Figure 1-1. HP 64146 Emulator for MELPS 7700 Series 1-2 Introduction...
  • Page 17: Table 1-1. Supported Microprocessors

    Supported A list of the supported 7700 Series microprocessors is shown in Table 1-1. You need to purchase appropriate emulation pod and emulation Microprocessors processor. Processor Clock Emulation Emulation Processor ================================================================= M37700/1 M2-xxxFP/SP | M37700SAFP M37700T-HPD M2AxxxFP/SP | SFP/SP SAFP/SP...
  • Page 18 As you can see from Table 1-1, the HP 64146A/B emulator can emulate M37702/3M2 and M37702/3S1 processor by default. These emulation pods can be used with clock up to 25 MHz. Also, HP 64146B emulator can emulate M37702 M6L processor using default emulation pod, HP 64146-61002.
  • Page 19: Features Of The 7700 Series Emulator

    Refer to Chapter 4 of this manual for more detail. Emulation memory The HP 64146A/B 7700 Series emulator is used with one of the following Emulation Memory Cards. HP 64726A 128K byte Emulation Memory Card...
  • Page 20: Analysis

    ROM (which will stop a runaway program). Analysis The HP 64146A/B 7700 Series emulator is used with one of the following analyzers which allows you to trace code execution and processor activity.
  • Page 21: Register Display And Modification

    The foreground monitor occupies processor memory space and executes as if it were part of your program. Register Display and You can display or modify the 7700 Series internal register contents. This includes the ability to modify the program counter (PC) and the Modification program bank register (PG) values so you can control where the emulator starts a program run.
  • Page 22: Coverage Measurements

    Coverage Coverage memory is provided for the processor’s external program memory space. This memory allows you to perform coverage Measurements measurements on programs in emulation memory. Reset Support The emulator can be reset from the emulation system under your control; or your target system can reset the emulation processor. Watch Dog Timer You can configure the emulator to disable the watch dog timer.
  • Page 23: Limitations, Restrictions

    Limitations, Restrictions Access to Internal Modifying internal RAM or SFR suspends user program execution. Trace Internal RAM Read data from the internal RAM or SFR is not traced correctly by the emulation analyzer. Note Write data is also not traced correctly, when the following conditions are met: The emulator is used with the M37795 emulation pod.
  • Page 24: Emulation Commands In Stop/Wait Mode

    Stack Address In some versions of 7700 microprocessor, the stack can be located in Bank FF. However, the HP 64146A/B 7700 Series emulator doesn’t support the feature. The stack must be located in Bank 0. 1-10 Introduction...
  • Page 25: Getting Started

    Getting Started Introduction This chapter will lead you through a basic, step by step tutorial designed to familiarize you with the use of the HP 64146A/B 7700 Series emulator with the Softkey Interface. This chapter will: Tell you what must be done before you can use the emulator as shown in the tutorial examples.
  • Page 26: Before You Begin

    Before beginning the tutorial presented in this chapter, you must have completed the following tasks: 1. Connected the emulator to your computer. The HP 64700 Series Installation/Service manual shows you how to do this. 2. Installed the Softkey Interface software on your computer.
  • Page 27: A Look At The Sample Program

    Figure 2-1. Connecting the Emulation Pod A Look at the Sample The sample program used in this chapter is listed in Figure 2-2. The program emulates a primitive command interpreter. The sample Program program is shipped with the Softkey Interface and may be copied from the following location.
  • Page 28 .PUB Init .PUB Msgs .PUB Cmd_Input .PUB Msg_Dest .SECTION BUFFER ;********************************************************** ; Command input byte. ;********************************************************** Cmd_Input: .BLKB ;********************************************************** ; Destination of the command messages. ;********************************************************** Msg_Dest: .BLKB .BLKB 100H Stack: .SECTION TABLE Msgs: Msg_A: .BYTE ’THIS IS MESSAGE A’ Msg_B: .BYTE ’THIS IS MESSAGE B’...
  • Page 29 .INDEX ;********************************************************** ; Check if the command entered is command A, command B, ; or invalid command. ;********************************************************** Process_Cmd: A,#41H Cmd_A A,#42H Cmd_B Cmd_I ;********************************************************** ; Command A is entered. A = the number of bytes in ; message A. X = location of the message.
  • Page 30 Processing Commands When a command is entered, the Clear_Output routine clears the destination area. Then, the instructions from Process_Cmd to Cmd_A determine whether the command was "A", "B", or an invalid command. If the command input byte is "A" (ASCII 41 hex), execution is transferred to the instructions at Cmd_A.
  • Page 31 ,-s -ms Figure 2-3. Linkage Editor Command File Generate HP To generate HP Absolute file for the Sofktey Interface, you need to use "m77cnvhp" absolute file format converter program. The m77cnvhp Absolute file converter is provided with the Softkey Interface. To generate HP Absolute file, enter following command: $ m77cnvhp cmd_rds <RETURN>...
  • Page 32: Entering The Softkey Interface

    After the measurement system has been initialized, enter the configuration interface with the following command. msconfig <RETURN> To define a measurement system for the 7700 Series emulator, enter: make_sys emm77 <RETURN> Now, to add the emulator to the measurement system, enter: add <module_number>...
  • Page 33: From The Hp-Ux Shell

    2-4. The status message shows that the default configuration file has been loaded. If the command is not successful, you will be given an error message and returned to the HP-UX prompt. Error messages are described in the Softkey Interface Reference manual.
  • Page 34: On-Line Help

    <RETURN> key to see the next line, just as you do with the HP-UX more command. After all the information on the particular topic has been displayed (or after you press "q" to quit scrolling through information), you are prompted to press <RETURN>...
  • Page 35: Pod Command Help

    Pod Command Help To access the emulator’s firmware resident Terminal Interface help information, you can use the following commands. display pod_command <RETURN> pod_command ’help m’ <RETURN> Pod Commands Time Command 10:00:00 help m m - display or modify processor memory space m <addr>...
  • Page 36: Configuring The Emulator

    Configuring the You need to configure the emulator for this tutorial. To configure the emulator, type the following command to get into the configuration Emulator session. modify configuration <RETURN> Trace the following answer to configure the emulator. Details of each question will be described later.
  • Page 37: Table 2-1. Chip Group And Chip Type For Configuration

    <chip_name> Processor <chip_name> Processor ======================================||====================================== 7700M2 | M37700M2-xxxFP 7704M2 | M37704M2-xxxFP M2AxxxFP M2AxxxFP | M37701M2-xxxSP | M37705M2-xxxSP M2AxxxSP M2AxxxSP ------------------+-------------------||-------------------+------------------ 7700M4 | M37700M4-xxxFP 7704M3 | M37704M3BxxxFP M4AxxxFP ||-------------------+-------------------- | M37701M4-xxxSP 7704M4 | M37704M4BxxxFP M4AxxxSP ||-------------------+-------------------- ------------------+-------------------|| 7704S1 | M37704S1FP 7700S | M37700SFP S1AFP SAFP...
  • Page 38: Loading Absolute Files

    Loading Absolute The "load" command allows you to load absolute files into emulation or target system memory. If you wish to load only that portion of the Files absolute file that resides in memory mapped as emulation RAM or ROM, use the "load emul_mem" syntax. If you wish to load only the portion of the absolute file that resides in memory mapped as target RAM, use the "load user_mem"...
  • Page 39: Local

    Local When displaying local symbols, you must include the name of the source file in which the symbols are defined. For example, display local_symbols_in cmd_rds.a77: <RETURN> Symbols in cmd_rds.a77: Static symbols Symbol name ____________________ Address range __ Segment _____________ Offset Cear_Input 00C005 0005...
  • Page 40: Displaying Memory In Mnemonic Format

    Displaying You can display, in mnemonic format, the absolute code in memory. To display memory in mnemonic format from the address of label Init, Memory in enter the following command: Mnemonic Format display memory Init mnemonic options m0x0 <RETURN> You need to specify the values of M flag and X flag at the staring address of mnemonic memory display.
  • Page 41: Displaying Memory With Symbols

    Displaying You can include symbol information in memory display. Memory with Symbols set symbols on <RETURN> The "set" command is effective only to the window in which the Note command is invoked. You need to use this command at each window. Memory :mnemonic :file = cmd_rds.a77: address...
  • Page 42: Running The Program

    Running the The "run" command lets you execute a program in memory. Entering the "run" command by itself causes the emulator to begin executing at Program the current program counter address. The "run from" command allows you to specify an address at which execution is to start. For example to run the sample program from the address of Init label, run from Init <RETURN>...
  • Page 43: Modifying Memory

    Modifying Memory The sample program simulates a primitive command interpreter. Commands are sent to the sample program through a byte sized memory location labeled Cmd_Input. You can use the modify memory feature to send a command to the sample program. For example, to enter the command "A"...
  • Page 44: Breaking Into The Monitor

    <RETURN> Using Software Software breakpoints are provided with an 7700 Series BRK instruction. When you define or enable a software breakpoint, the Breakpoints emulator will replace the opcode at the software breakpoint address with a BRK instruction.
  • Page 45 Note Because software breakpoints are implemented by replacing opcodes with BRK instructions, you cannot define software breakpoints in target ROM. Software breakpoints should not be set, cleared, enabled, or disabled Note while the emulator is running user code. If any of these commands are entered while the emulator is running user code, and the emulator is executing code in the area where the breakpoint is being modified, program execution may be unreliable.
  • Page 46: Enabling/Disabling Software Breakpoints

    Enabling/Disabling When you initially enter the Softkey Interface, software breakpoints are disabled. To enable the software breakpoints feature, enter the Software Breakpoints following command. modify software_breakpoints enable <RETURN> When software breakpoints are enabled and you set a software breakpoint, the 7700 BRK instruction will be placed at the address specified.
  • Page 47: Clearing A Software Breakpoint

    As you can see, the software breakpoint is shown in the memory display with an asterisk, and the instruction at the address is replaced with a BRK instruction. Note When a software breakpoint is inserted, the mnemonic in memory display may not be accurate. Enter the following command to run the sample program again.
  • Page 48: Stepping Through The Program

    Stepping Through The step command allows you to step through program execution an instruction or a number of instructions at a time. Also, you can step the Program from the current program counter or from a specific address. To step through the example program from the address of the software breakpoint set earlier, enter the following command.
  • Page 49 Registers Next_PC 00C01D PC C01D PG 00 DT 00 SP 0221 PS 0031 <..mx...c> 0075 0000 0200 0120 DPR 0000 STATUS: M37700--Stepping complete_____________________________________..display registers trace step display modify break ---ETC-- Following list shows the register names and class that may be used with the "display registers"...
  • Page 50: Using The Analyzer

    <RETURN> Using the Analyzer HP 64700 emulators contain an emulation analyzer. The emulation analyzer monitors the internal emulation lines (address, data, and status). Optionally, you may have an additional 16 trace signals which monitor external input lines.
  • Page 51: Displaying The Trace

    The message "Emulation trace started" will appear on the status line. Now, modify the command input byte to "A" with the following command. modify memory Cmd_Input bytes to 41h <RETURN> The status line now shows "Emulation trace complete". Displaying the Trace The trace listings which follow are of program execution on the 7700 Series emulator.
  • Page 52: Displaying Trace With Time Count Absolute

    Trace List Offset=0 Label: Address Data Opcode or Status time count Base: symbols mnemonic w/symbols relative +015 :cmd_rds:+000002 5448 xx48H data write 4.00 +016 :cmd_rds:+000002 5349 5349H data read 8.00 +017 :cmd_rds:+000003 4949 49xxH data write 8.00 +018 :cmd_rds:+000004 4953 xx53H data write 4.00...
  • Page 53: Changing The Trace Depth

    Trace List Offset=0 Label: Address Data Opcode or Status time count Base: symbols mnemonic w/symbols absolute +015 :cmd_rds:+000002 5448 xx48H data write 84.0 +016 :cmd_rds:+000002 5349 5349H data read 92.0 +017 :cmd_rds:+000003 4949 49xxH data write + 100. +018 :cmd_rds:+000004 4953 xx53H data write...
  • Page 54: 7700 Series Analysis Status Qualifiers

    7700 Series Analysis The status qualifier "write" was used in the example trace command used above. The following analysis status qualifiers may also be used Status Qualifiers with the 7700 Series emulator. Qualifier Status bits (40..47) Description backgrnd...
  • Page 55: Restriction Of The Analyzer

    As you can see in line 11 of the trace listing, data read from internal RAM (which should be 00 hex) appears FF hex. For a Complete For a complete description of using the HP 64700 Series analyzer with the Softkey Interface, refer to the Analyzer Softkey Interface User’s Description Guide.
  • Page 56: Exiting The Softkey Interface

    Exiting the There are several options available when exiting the Softkey Interface: exiting and releasing the emulation system, exiting with the intent of Softkey Interface reentering (continuing), exiting locked from multiple emulation windows, and exiting (locked) and selecting the measurement system display or another module.
  • Page 57: In-Circuit" Emulation

    Show you how to use features related to in-circuit emulation. Prerequisites Before performing the tasks described in this chapter, you should be familiar with how the emulator operates in general. Refer to the HP 64700 Emulators: System Overview manual and the "Getting Started" chapter of this manual.
  • Page 58: Installing The Target System Probe

    Installing the Target System Probe POSSIBLE DAMAGE TO THE EMULATOR PROBE. The Caution emulation probe contains devices that are susceptible to damage by static discharge. Therefore, precautionary measures should be taken before handling the microprocessor connector attached to the end of the probe cable to avoid damaging the internal components of the probe by static electricity.
  • Page 59: In-Circuit Configuration Options

    In-Circuit The 7700 Series emulator provides configuration options for the following in-circuit emulation issues. Configuration Refer to the "Configuring the Emulator" for more information on these Options configuration options. Using the Target System Clock Source You can configure the emulator to use the external target system clock source.
  • Page 60 Notes 3-4 In-Circuit Emulation...
  • Page 61: Configuring The Emulator

    Configuring the Emulator Introduction Your 7700 Series emulator can be used in all stages of target system development. For instance, you can run the emulator out-of-circuit when developing your target system software, or you can use the emulator in-circuit when integrating software with target system hardware.
  • Page 62 Emulator Reconfiguration: – Selecting microprocessor to be emulated. – Selecting CPU operation mode. – Defining the reset value of the stack pointer. Memory Configuration: – Enabling the high speed access mode – Selecting the background or foreground emulation monitor. – Mapping memory. Emulator Pod Configuration: –...
  • Page 63: General Emulator Configuration

    Selects the internal clock oscillator as the emulator clock source. The internal clock is provided from the emulation pod. In the case of HP 64146-61001 or HP 64146-61602 emulation pod, the clock speed is 1 MHz. When you use an emulation pod with...
  • Page 64: Enter Monitor After Configuration

    Note Your target system must have a clock generation circuit. The emulation pod cannot generate clock signal using a ceramic (or quartz crystal) resonator. Note Changing the clock source drives the emulator into the reset state. The emulator may later break into the monitor depending on how the following "Enter monitor after configuration?"...
  • Page 65: Restrict To Real-Time Runs

    Restrict to real-time The "restrict to real-time" question lets you configure the emulator so that commands which cause the emulator to break to monitor and runs? return to the user program are refused. All commands, regardless of whether or not they require a break to the emulation monitor, are accepted by the emulator.
  • Page 66: Micro-Processor Group

    Micro-processor This configuration item allows you to select the processor you are going to emulate. group? 7700 When you are going to emulate M37700xx or M37701xx, select this item. 7702 When you are going to emulate M37702xx or M37703xx, select this item. 7704 When you are going to emulate M37704xx or M37705xx, select this item.
  • Page 67: Figure 4-1. Chip Group And Type For Configuration

    <chip_name> Processor <chip_name> Processor ======================================||====================================== 7700M2 | M37700M2-xxxFP 7704M2 | M37704M2-xxxFP M2AxxxFP M2AxxxFP | M37701M2-xxxSP | M37705M2-xxxSP M2AxxxSP M2AxxxSP ------------------+-------------------||-------------------+------------------ 7700M4 | M37700M4-xxxFP 7704M3 | M37704M3BxxxFP M4AxxxFP ||-------------------+-------------------- | M37701M4-xxxSP 7704M4 | M37704M4BxxxFP M4AxxxSP ||-------------------+-------------------- ------------------+-------------------|| 7704S1 | M37704S1FP 7700S | M37700SFP S1AFP SAFP...
  • Page 68 SFR area start address? SFR area end address? Second SFR area start address? Second SFR area end address? Specify the start address and end address of internal SFR of your processor. These addresses can be defined on 16 byte boundaries. If your processor has only one SFR area, specify the same value as the first one for the "Second SFR ..."...
  • Page 69: Processor Mode

    Processor mode? This configuration defines operation mode of the processor. single The emulator will operate in single-chip mode. expand8 The emulator will operate in memory expansion mode with 8 bit data width. expand16 The emulator will operate in memory expansion mode with 16 bit data width.
  • Page 70: Memory Configuration

    Caution Without a stack pointer, the emulator is unable to make the transition to the run state, step or perform many other emulation functions. Memory The memory configuration questions allows you to select the monitor type and to map memory. To access the memory configuration Configuration questions, you must answer "yes"...
  • Page 71: Monitor Type

    Enables the high speed access mode of the emulator. In the high speed access mode: The emulator can run with no wait state up to 25 MHz. you can map the emulation memory only to the following address ranges. Memory Monitor Available location 128K...
  • Page 72 The monitor program then reads the command from the communications area and executes the 7700 Series instructions which read the contents of the target system memory locations. After the monitor has completed its task, execution returns to the user program.
  • Page 73: Mapping Memory

    Monitor address? The default configuration specifies a monitor address of 0b800 hex. The monitor base address must be located on a 2K byte boundary other than internal RAM and Special Function Register area; otherwise, configuration will fail. Monitor filename? This question allows you to specify the name of the foreground monitor program absolute file.
  • Page 74 The default emulator configuration maps location C000 hex through FFFF hex as emulation ROM. This must be needed when you use the 7700 Series internal ROM. You don’t have to map internal RAM area since the emulator uses internal RAM of the emulation processor.
  • Page 75 Note You should map all memory ranges used by your programs before loading programs into memory. This helps safeguard against loads which accidentally overwrite earlier loads if you follow a map/load procedure for each memory range. Internal RAM and SFR The emulator uses internal RAM of emulation processor to emulate user program.
  • Page 76: Emulator Pod Configuration

    Note When you specify "fcode", the "fcode" becomes the new default to display memory. That is, once you specify "fcode i", you need to specify "fcode none" to display emulation memory. When you don’t map the internal RAM and SFR area to emulation RAM (when you don’t copy the contents to emulation memory), you can access the internal RAM and SFR without specifying "fcode"...
  • Page 77: Respond To Target System Interrupts

    system memory locations, the monitor will either use byte or word instructions to accomplish the read/write. byte Specifies that the emulator will access target system memory by byte accesses. word Specifies that the emulator will access target system memory by word accesses. Respond to target This configuration allows you to specify whether or not the emulator responds to interrupt signals from the target system during foreground...
  • Page 78: Debug/Trace Configuration

    Debug/Trace The debug/trace configuration questions allows you to specify breaks on writes to ROM, and specify that the analyzer trace Configuration foreground/background execution, and bus release cycles. To access the trace/debug configuration questions, you must answer "yes" to the following question. Modify debug/trace options? Break processor on This question allows you to specify that the emulator break to the...
  • Page 79: Trace Refresh Cycles By Emulation Analyzer

    this option so that all emulation processor cycles may be viewed in the trace display. Trace refresh cycles This question is asked only when the 7720 processor is selected in "Micro-processor group?" configuration question. by emulation analyzer? You can direct the emulator to send refresh cycle data to emulation analyzer or not to send it.
  • Page 80: Simulated I/O Configuration

    Replace 16-bit You can direct the emulator whether or not to display symbols in 16bit addresses in mnemonic field of memory and trace display. addresses with symbolic references? Symbols are displayed only in 24bit addresses of mnemonic field. Symbols are displayed both in 16 and 24bit addresses of mnemonic field.
  • Page 81: External Analyzer Configuration

    External Analyzer The external analyzer configuration options are described in the Analyzer Softkey Interface User’s Guide. Configuration Saving a The last configuration question allows you to save the previous configuration specifications in a file which can be loaded back into the Configuration emulator at a later time.
  • Page 82 This feature is especially useful after you have exited the Softkey Interface with the "end release_system" command; it saves you from having to modify the default configuration and answer all the questions again. To reload the current configuration, you can enter the following command.
  • Page 83: Using The Emulator

    In this chapter, we will discuss in more detail other features of the emulator. This chapter discusses: Internal RAM and SFR of 7700 Series. Features available via "pod_command". Debugging C Programs Limitations and restrictions of the emulator.
  • Page 84: Sample Program

    Sample Program In the "Getting Started" chapter, we looked at a sample program which functioned as a primitive command interpreter. In this section, we will use the same program. Internal RAM and As described in chapter 2 and chapter 4, the emulator breaks into the monitor when displaying internal RAM or SFR.
  • Page 85 Now, let’s display the message written to the destination area. display memory fcode i Msg_Dest blocked byte <RETURN> The above command displays the contents of internal RAM. Sample program is suspended, and the monitor reads the internal RAM. To display the data copied to emulation memory, enter the following command.
  • Page 86: Features Available Via Pod Commands

    Be careful when using the "pod_command". The Softkey Interface, and the configuration files in particular, assume that the configuration of the HP 64700 pod is NOT changed except by the Softkey Interface. Be aware that what you see in "modify configuration" will NOT reflect the HP 64700 pod’s configuration if you change the pod’s configuration with this...
  • Page 87: Debugging C Programs

    Debugging C Softkey Interface has following functions to debug C programs. Programs Including C source lines in memory mnemonic display Including C source lines in trace listing Stepping C sources Display memory in various data type The following section describes such features. Displaying Memory You can display memory in mnemonic format with C source lines.
  • Page 88: Stepping C Sources

    Stepping C Sources You can direct the emulator to execute a line or a number of lines at a time. For example, to step one line from the beginning of function main, enter the following command. step source from _main <RETURN> To step 1 line from the current line, enter the following command.
  • Page 89: Storing Memory Contents To An Absolute File

    To display memory C000 hex through C020 hex in mnemonic format: display memory 0c000h thru 0c020h mnemonic Now, to disable logging, type "log" and press TAB key, select "off", and press Enter. The command file you created looks like this: load configuration cmd_rds load cmd_rds display memory 0c000h thru 0c020h mnemonic...
  • Page 90: Limitations, Restrictions

    Limitations, Restrictions Access to Internal Modifying internal RAM or SFR suspends user program execution. Trace Internal RAM Read data from the internal RAM or SFR is not traced correctly by the emulation analyzer. Note Write data is also not traced correctly in the following case: The emulator is used with the M37795 emulation pod.
  • Page 91: Emulation Commands In Stop/Wait Mode

    Stack Address In some versions of 7700 microprocessor, the stack can be located in Bank FF. However, the HP 64146A/B emulator doesn’t support the feature. The stack must be located in Bank 0. Using the Emulator 5-9...
  • Page 92 Notes 5-10 Using the Emulator...
  • Page 93: Using The Foreground Monitor

    Using the Foreground Monitor Introduction By using and modifying the optional foreground monitor, you can provide an emulation environment which is customized to the needs of a particular target system. The foreground monitors are supplied with the emulation software and can be found in the following path: /usr/hp64000/monitor/* The monitor programs are named fm7700b.a77.
  • Page 94: Background Monitors

    Background Monitors A background monitor is an emulation monitor which overlays the processor’s memory space with a separate memory region. Entry into the monitor is normally accomplished by jamming the monitor addresses onto the processor’s address bus. Usually, a background monitor will be easier to work with in starting a new design.
  • Page 95: An Example Using The Foreground Monitor

    An Example Using In the following example, we will illustrate how to use a foreground monitor with the sample program from the "Getting Started" chapter. the Foreground By using the emulation analyzer, we will also show how the emulator Monitor switches from state to state using a foreground monitor.
  • Page 96: Modifying The Emulator Configuration

    LOCATE_ADRS .EQU 0B800H ;start monitor on 2k boundary in bank 0 ;rather than sfr/iram area PROCMODEREG .EQU 0005EH ;processor mode register;s address For example, if you want to locate the monitor at a000 hex, you may change the address "0B800H" to "0A000H". Processor Mode Register Address You may need to modify the .EQU statement at the PROCMODEREG label.
  • Page 97 Reset map (change of monitor type requires map reset)? yes You must answer this question as shown to change the monitor type to foreground. Monitor address? 0b800h Specifies that the monitor will reside in the 2K byte block from b800 hex through bfff hex.
  • Page 98: Load The Program Code

    Configuration file name? fmconfig If you wish to save the configuration specified above, answer this question as shown. Load the Program Now it’s time to load the sample program. You can load the sample program with the following command: Code load cmd_rds <RETURN>...
  • Page 99: Limitations Of Foreground Monitors

    Limitations of Listed below are limitations or restrictions present when using a foreground monitor. Foreground Monitors Step Command Step command is not available when you are using the emulator with a foreground monitor. Synchronized You cannot perform synchronized measurements over the CMB when using a foreground monitor.
  • Page 100 Notes A-8 Using A Foreground Monitor...
  • Page 101: Using The Format Converter

    Using the Format Converter How to Use the The format converter is a program that generates HP format files from MELPS 7700 Hex format file and its symbol file. This means you can Converter use available language tools to create MELPS 7700 Hex format file, then load the file into the emulator using the format converter.
  • Page 102: Specifications

    Specifications The following are specifications of the format converter. Label names and Symbol names must be 15 and less characters in length. File name must be 14 and less characters in length. Up to 10000 sections can be handled. Up to 1000 functions can be handled. If a label name or symbol name contains "?", it will be replaced with "_".
  • Page 103 Index absolute file, loading 2-14 absolute files storing 5-7 analyzer 7700 Series status qualifiers 2-30 configuring the external 4-21 restriction 2-31 storage qualifier 2-29 using the 2-26 assemble assembling the sample program 2-7 assembling the getting started sample program 2-7...
  • Page 104 4-17 in-circuit 3-3 processor mode 4-9 configuring the emulator for sample program 2-12 convert absolute file to HP Absolute 2-7 converter, m77cnvhp 2-7 coordinated measurements 4-20, 5-7 copy memory 5-4 coverage analysis 5-4 Debugging C programs 5-5...
  • Page 105 RAM and ROM characterization 4-13 size of 4-13 emulation monitor 4-11 background 4-12 Emulation pod 1-4 ordering information 1-4 Emulation processor 1-4 ordering information 1-4 Emulator before using 2-2 configuration 4-1 device table file 2-9 limitations 5-8 prerequisites 2-2 probe installation into target system 3-2 purpose 1-1 emulator configuration break processor on write to ROM 4-18...
  • Page 106 analyzer 1-6 breakpoints 1-7 clock speed 1-5 coverage measurements 1-8 emulation memory 1-5 foreground and background monitor 1-6 high speed access mode 1-5 processor reset control 1-8 register display/modify 1-7 restrict to real-time runs 1-7 single-step processor 1-7 Emulator limitations 1-9 Access to Internal RAM 1-9, 5-8 DMA support 1-9, 5-8 emulation command fails in stop/wait mode 1-10, 5-9...
  • Page 107 foreground operation tracing 4-18 format converter B-1 getting started 2-1 prerequisites 2-2 global symbols displaying 2-14 guarded memory accesses 4-14 hardware installation 2-2 help on-line 2-10 pod command information 2-11 softkey driven information 2-10 high speed access mode 1-5, 4-10 in-circuit configuration options 3-3 in-circuit emulation 3-1 installation...
  • Page 108 creating 2-8 initialization 2-8 memory blocked display 2-18 characterization 4-13 copying 5-4 mapping 4-13 mnemonic display 2-16 mnemonic display and M flag, X flag 2-16 mnemonic display with C sources 5-5 mnemonic display with symbols 2-17 modifying 2-19 searching for strings or expressions 5-4 memory display with 16bit symbols 4-20 memory mapping...
  • Page 109 3-2 user program suspended when modifying internal RAM 5-3 on-line help 2-10 PATH, HP-UX environment variable 2-8 - 2-9 pmon, User Interface Software 2-8, 2-32 pod_command 2-11 features available with 5-4...
  • Page 110 mapping emulation or target 4-13 real-time execution restricting the emulator to 4-5 register display/modify 2-24 registers classes 2-24 names 2-25 release_system end command option 2-32, 4-21 - 4-22 respond to target system interrupts emulator configuration 4-17 restrict to real-time runs emulator configuration 4-5 permissible commands 4-5 target system dependency 4-5...
  • Page 111 2-22 software installation 2-2 stack pointer 1-10, 5-9 stack pointer,defining 4-9 static discharge, protect the emulator probe from 3-2 status qualifiers (7700 Series) 2-30 step command 2-24 with C program 5-5 stop mode 1-10 storage qualifier 2-29 string delimiters 2-11...
  • Page 112 emulator configuration 4-19 trace, displaying the 2-27 trace, displaying with time count absolute 2-28 trace, reducing the trace depth 2-29 tracing background operation 4-18 trigger state 2-27 trigger, specifying 2-26 undefined software breakpoint 2-21 user (target) memory, loading absolute files 2-14 wait mode 1-10 watchdog timer enable/disable by emulator configuration 4-17...

This manual is also suitable for:

64146a64146b

Table of Contents