About this Manual We’ve added this manual to the Agilent website in an effort to help you support your product. This manual is the best copy we could find; it may be incomplete or contain dated information. If we find a more recent copy in the future, we will add it to the Agilent website. Support for Your Product Agilent no longer sells or supports this product. Our service centers may be able to perform calibration if no repair parts are needed, but no other support from Agilent is available.
User’s Guide Publication number E3458-97001 October 1998 © Copyright Hewlett-Packard Company 1994-1998 All Rights Reserved For Safety information, Warranties, and Regulatory information, see the pages behind the index.
Motorola CPU32 Emulation—At a Glance This manual describes how to set up several HP emulation products: an emulation probe, an emulation module, and an emulation migration. These emulators provide a low-cost way to debug embedded software for Motorola CPU32 microprocessors. The emulator lets you use the target processor’s built-in background debugging features, including run control and access to registers and memory.
Chapter : Motorola CPU32 Emulation—At a Glance Emulation Module The emulation module plugs into your HP16600A/700A-series logic analysis system frame. You can connect the emulation module to an analysis probe or you can connect it to a debug port on the target system through the provided target interface module (TIM). Emulation Migration The emulation migration includes a target interface module and firmware.
Chapter : In This Book In This Book This book documents the following products: Emulation Probe Processor supported Product ordered Includes CPU32 HP E5900A Option #030 HP E3458A emulation probe, HP E3458A target interface module (TIM) Processor supported Product ordered Includes CPU32 HP E5901A Option #030 HP 16610A emulation module, HP E3458A target interface module (TIM) Processor supported Product ordered Includes CPU32 HP E5902A Option #030 HP E3458A target interface module (TIM) Em
Contents Motorola CPU32 Emulation—At a Glance 1 Overview Overview 2 15 16 Setup Flowchart 17 Emulation Probe 18 Equipment supplied 18 Minimum equipment required 20 To connect the emulation probe to a power source To power on the system 22 To power off the system 22 Connection Sequence 22 Emulation Module 23 Equipment supplied 23 Minimum equipment required Emulation Migration Equipment supplied 24 25 25 Minimum equipment required Additional Information Sources 2 20 26 27 Connecting the
Contents Setting Up a LAN Connection to a PC or Workstation 31 To obtain an IP address 32 To configure LAN parameters using the built-in terminal interface To configure LAN parameters using BOOTP 37 To set the 10BASE-T configuration switches 40 To verify LAN communications 41 Setting Up a Serial Connection 42 To set the serial configuration switches To connect a serial cable 44 To verify serial communications 46 3 42 Installing the Emulation Module Installing the Emulation Module 34 47 48 To inst
Contents 5 Connecting and Configuring the Emulator Connecting and Configuring the Emulator Using the Emulation Control Interface 59 60 61 To start the Emulation Control Interface from the main System window 62 To start the Emulation Control Interface from the Workspace window 63 To start the Emulation Control Interface from the Workspace window for an emulation probe 64 Designing a Target System for the Emulator 65 Debug port connections 65 8-pin BDM port 67 10-pin BDM port 67 Target VDD 67 CONFIG2
Contents To configure the Trigger Out BNC (Emulation Probe Only) 85 To configure the Trigger In BNC (Emulation Probe Only) 86 Testing the emulator and target system To test memory accesses 87 To test with a running program 6 87 87 Using Internal Registers (SIM and EMSIM Registers) 89 Internal Registers (SIM and EMSIM Registers) 90 The purpose of SIM Registers 90 The purpose of EMSIM registers 90 Configuring the SIM Registers 91 Summary 91 How SIM Register Values are Set 91 The effect of processor
Contents To compare SIM and EMSIM registers 99 Summary of EMSIM-related built-in commands 7 100 Internal Representation of SIM and EMSIM Registers 101 Using the Emulator with a Debugger 103 Using the Emulator with a Debugger Setting up Debugger Software 104 107 To connect the logic analysis system to the LAN 108 To change the port number of an emulation module 110 To verify communication with the emulator 111 To export the logic analysis system’s display to a workstation To export the logic analy
Contents Getting started 124 To send commands to the emulator Download performance 131 Error conditions 132 8 130 Using the Analysis Probe and Emulation Module Together 133 Using the Analysis Probe and Emulation Module Together What are some of the tools I can use? 134 Which assembly-level listing should I use? 134 Which source-level listing should I use? 135 Where can I find practical examples of measurements? Triggering the Emulation Module from the Analyzer 134 135 136 To stop the processor when
Contents 9 Updating Firmware Updating Firmware 147 148 Emulation Probe Firmware 149 To display current firmware version information 149 To update firmware for an emulation probe 149 Emulation Module Firmware 150 To display current firmware version information 150 To update firmware for an emulation module using the Emulation Control Interface 150 To update firmware for an emulation module using the Setup Assistant 151 10 Specifications and Characteristics Processor compatibility 154 Emulation pr
Contents Emulation Module Status Lights 162 Emulation Probe Status Lights 163 Emulation Probe Status Lights 164 Emulator Built-in Commands 165 To telnet to the emulation module 165 To telnet to the emulation probe 166 To use the built-in commands 167 Problems with the BDM Connection If a user interface behaves erratically Problems with Configuration 169 169 170 If you have problems displaying some registers If you have problems initializing some registers Problems with the Target System If boot ar
Contents Problems with the Serial Interface (Emulation Probe Only) 180 If you cannot verify RS-232 communication 180 If you have RS-232 connection problems with the MS Windows Terminal program 181 Problems with the Emulation Probe 182 To run the power up self test 182 To run the emulation probe performance verification tests 184 To run the performance verification tests using the logic analysis system 184 To run complete performance verification tests for an emulation probe 185 If a performance verifi
Contents 14
1 Overview 15
Overview This chapter describes: • Setup flowchart • Equipment used with the emulation probe • Connection sequences for the emulation probe • Equipment used with the emulation module • Additional information sources 16 CPU32 Emulation
Chapter 1: Overview Setup Flowchart Setup Flowchart Emulation module Emulation migration HP E5901A Emulation probe HP E5902A Install emulation module (if necessary) HP E5900A Migrating a module or a probe? Module Probe Connect power supply Connect to LAN Install software on logic analysis system Update emulator firmware Target Interface Module Connection type? Connect emulator Analysis Probe Connect emulation module to analysis probe.
Chapter 1: Overview Emulation Probe Emulation Probe Equipment supplied • An emulation probe. • A 12V power supply for the emulation probe. • A power cord. • A target interface module (TIM) circuit board. • An emulation probe loopback test board (HP part number E3496-66502). • A 50-pin ribbon cable (connects the emulation probe to the target interface module). • A 10-pin ribbon cable (connects the target interface module to your target system). • Firmware for the emulation probe on 3.
Chapter 1: Overview Emulation Probe Equipment Supplied with the Emulation Probe CPU32 Emulation 19
Chapter 1: Overview Emulation Probe Minimum equipment required The following equipment is required to use the emulation probe: • A method for connecting the emulator to the target system. You can use an HP analysis probe or you can design a debug port connector on the target system. The target system must meet the criteria on page 65. • A host computer, such as a PC or workstation. You can also connect the emulation probe to an HP 16600A or HP 16700A logic analysis system.
Chapter 1: Overview Emulation Probe 1 Connect the power cord to the power supply and to a socket outlet. 2 Connect the 12V power cord to the back of the emulation probe. The power light on the target side of the emulation probe will be light. The emulation probe does not have an On/Off switch.
Chapter 1: Overview Emulation Probe To power on the system With all components connected, power on your system as follows: 1 Logic analyzer, if you are using one. 2 Emulation probe. 3 Your target system. To power off the system Power off your system as follows: 1 Your target system. 2 Emulation probe. 3 Logic analyzer, if you are using one. Connection Sequence Disconnect power from the target system, emulation probe, and logic analyzer before you make or break connections.
Chapter 1: Overview Emulation Module Emulation Module This section lists equipment supplied with the emulation module and lists the minimum equipment required to use the emulation module. Equipment supplied The equipment supplied with your emulation module includes: • An HP 16610A emulation module. If you ordered an emulation module as part of your HP 16600A or HP 16700A logic analysis system, it is already installed in the frame. • A target interface module (TIM) circuit board.
Chapter 1: Overview Emulation Module Equipment Supplied with the Emulation Module Minimum equipment required The following equipment is required to use the emulation module: A method for connecting to the target system. The HP E2480A analysis probe provides a debug port connector. You can also design a debug port connector on the target system (see “Designing a Target System for the Emulator” on page 65). • An HP 16600A or HP 16700A logic analysis system.
Chapter 1: Overview Emulation Migration Emulation Migration This section lists equipment supplied with the emulation migration and lists the minimum equipment required to use the emulation migration. Equipment supplied The equipment supplied with your emulation migration includes: • A target interface module (TIM) circuit board. • Firmware for the emulation module and/or updated software for the Emulation Control Interface on a CD-ROM.
Chapter 1: Overview Minimum equipment required Minimum equipment required The following equipment is required to use the emulation migration: • An emulation module or emulation probe. • A 50-pin data cable (supplied with the emulation module or probe). • A method for connecting to the target system. An HP analysis probe provides a debug port connector. You can also design a debug port connector on the target system.
Chapter 1: Overview Additional Information Sources Additional Information Sources Additional or updated information can be found in the following places: Newer editions of this manual may be available. Contact your local HP representative. If you have an analysis probe, the instructions for connecting the probe to your target microprocessor are in the analysis probe documentation.
28 CPU32 Emulation
2 Connecting the Emulation Probe to a LAN 29
Connecting the Emulation Probe to a LAN You can connect your PC, workstation, or logic analysis system to the emulation probe via a serial or LAN connection. Serial connection A serial connection allows you to complete all of the performance verification tests and set LAN parameters. Other use of the serial port is not supported. LAN connection A LAN connection will allow you to make your measurements quickly and easily. A few of the performance verification tests cannot be run over a LAN.
Chapter 2: Connecting the Emulation Probe to a LAN Connecting the Emulation Probe to a LAN Setting Up a LAN Connection to a PC or Workstation The emulation probe has two LAN connectors: • A BNC connector that can be directly connected to an IEEE 802.3 Type 10BASE2 cable (ThinLAN). When using this connector, the emulation probe provides the functional equivalent of a Medium Attachment Unit (MAU) for ThinLAN. • An IEEE 802.3 Type 10BASE-T (StarLAN) connector.
Chapter 2: Connecting the Emulation Probe to a LAN Connecting the Emulation Probe to a LAN To obtain an IP address 1 Obtain the following information from your local network administrator or system administrator: • An IP address for the emulation probe. You can also use a "LAN name" for the emulation probe, but you must configure it using the integer dot notation (such as 127.0.0.1). • The gateway address. The gateway address is an IP address and is entered in integer dot notation.
Chapter 2: Connecting the Emulation Probe to a LAN Connecting the Emulation Probe to a LAN 3 Write down the link-level address of the emulation probe. You will need this address if you use BOOTP to set the IP address. The link-level address (LLA) is printed on a label above the LAN connectors on the emulation probe. This address is configured in each emulation probe shipped from the factory and cannot be changed.
Chapter 2: Connecting the Emulation Probe to a LAN Connecting the Emulation Probe to a LAN To configure LAN parameters using the built-in terminal interface 1 Set configuration switches S1 through S4 to ON, and set the other switches as appropriate for your serial interface. Switch settings are printed on the bottom of the emulation probe.
Chapter 2: Connecting the Emulation Probe to a LAN Connecting the Emulation Probe to a LAN 4 Display the current LAN configuration values by entering the lan command: R> lan lan is disabled lan -i 0.0.0.0 lan -g 0.0.0.0 lan -p 6470 Ethernet Address : 08000903212f The "lan -i" line shows the current IP address (IP address) of the emulation probe. The Ethernet address, also known as the link level address, is preassigned at the factory, and is printed on a label above the LAN connectors.
Chapter 2: Connecting the Emulation Probe to a LAN Connecting the Emulation Probe to a LAN This connection can be made by using either the 10BASE-T connector or the 10BASE2 (BNC) connector on the emulation probe. Do not use both connectors at the same time. 7 Set the configuration switches to indicate the type of connection that is to be made. Switch S1 must be set to OFF, indicating that a LAN connection is being made.
Chapter 2: Connecting the Emulation Probe to a LAN Connecting the Emulation Probe to a LAN Example To assign an IP address of 192.6.94.2 to the emulation probe, enter the following command: R>lan -i 192.6.94.2 Now, cycle power on the emulation probe so that the new address will take effect. See Also Page 172, if you have problems verifying LAN communication. To configure LAN parameters using BOOTP Use this method only on a workstation which is running bootpd, the BOOTP daemon.
Chapter 2: Connecting the Emulation Probe to a LAN Connecting the Emulation Probe to a LAN 2 Add an entry to the host BOOTP database file, /etc/bootptab. Example # Global template for options common to all HP64700 # emulators and Emulation Probes. # Use a different gateway addresses if necessary. hp64700.global:\ :gw=0.0.0.0:\ :vm=auto:\ :hn:\ :bs=auto:\ :ht=ether # Specific emulator entry specifying hardware address # (link-level address) and ip address. hpprobe.div.hp.com:\ :tc=hp64700.
Chapter 2: Connecting the Emulation Probe to a LAN Connecting the Emulation Probe to a LAN Switch S5 should be set to OFF if you are connecting to the BNC connector Switch S5 should be set to ON if you are connecting to the 10BASE-T connector. Set all other switches to ON. 5 Connect the power cord to the emulation probe. 6 Verify that the power light stays on after 10 seconds. The IP address will be stored in EEPROM. 7 Set switch S6 back to ON.
Chapter 2: Connecting the Emulation Probe to a LAN Connecting the Emulation Probe to a LAN To set the 10BASE-T configuration switches Set switches S7 and S8 to ON unless one of the following conditions is true: • If the LAN cable exceeds the standard length, set switch S7 to OFF. The emulation probe has a switch-selectable, twisted-pair receiver threshold. With switch S7 set to OFF, the twisted-pair receiver threshold is lowered by 4.5 dB.
Chapter 2: Connecting the Emulation Probe to a LAN Connecting the Emulation Probe to a LAN To verify LAN communications 1 Verify your emulation probe is now active and on the network by issuing a telnet to the IP address. This connection will give you access to the emulation probe’s built-in terminal interface. 2 To view the LAN parameters, enter the lan command at the terminal interface prompt. 3 To exit from this telnet session, type D at the prompt.
Chapter 2: Connecting the Emulation Probe to a LAN Setting Up a Serial Connection Setting Up a Serial Connection To set up a serial connection to an emulation probe, you will need to: • Set the serial configuration switches • Connect a serial cable between the host computer and the emulation probe • Verify communications Serial connections on a workstation If you are using a UNIX workstation as the host computer, you need to use a serial device file.
Chapter 2: Connecting the Emulation Probe to a LAN Setting Up a Serial Connection interface uses the DSR:CTS/RTS lines for flow control. Set S5 to OFF (HW HANDSHAKE OFF) if your serial interface uses software flow control (XON/XOFF). If your serial interface supports hardware handshaking, you should use it (set switch S5 to ON). Hardware handshaking will make the serial connection much more reliable. 4 Set switches S6-S8 for the baud rate you will use.
Chapter 2: Connecting the Emulation Probe to a LAN Setting Up a Serial Connection To connect a serial cable CAUTION: Use a grounded, shielded cable. If the cable is not shielded, or if the cable is not grounded at the serial controller, the emulation probe may be damaged by electrostatic discharge. Connect an RS-232C modem cable from the host computer to the emulation probe. The recommended cable is HP part number C2932A. This is a 9-pin cable with one-to-one pin connections.
Chapter 2: Connecting the Emulation Probe to a LAN Setting Up a Serial Connection Serial Cable Pinout Pin Number Signal Signal Description 1 DCD Data Carrier Detect (not used) 2 TD Transmit Data (data coming from HP emulation probe) 3 RD Receive Data (data going to HP emulation probe) 4 DTR Data Terminal Ready (not used) 5 GND Signal Ground 6 DSR Data Set Ready (Output from HP emulation probe) 7 RTS Request to Send (Input to HP emulation probe) 8 CTS Clear to Send (connected to pi
Chapter 2: Connecting the Emulation Probe to a LAN Setting Up a Serial Connection To verify serial communications 1 Start a terminal emulator program on the host computer. If you are using a PC, the Terminal application in Microsoft Windows will work fine. If you are using a UNIX workstation, you can use a terminal emulator such as cu or kermit. 2 Plug the power cord into the emulation probe.
3 Installing the Emulation Module 47
Installing the Emulation Module This chapter shows you how to install an emulation module in your HP 16600A/700A-series logic analysis system. If your emulation module is already installed in your logic analysis system frame, you may skip this chapter. CAUTION: These instructions are for trained service personnel. To avoid dangerous electric shock, do not perform any service unless qualified to do so.
Chapter 3: Installing the Emulation Module Installing the Emulation Module To install the emulation module in an HP 16700A-series logic analysis system or an HP 16701A expansion frame You will need T-10 and T-15 Torx screw drivers. 1 Turn off the logic analysis system and REMOVE THE POWER CORD. Remove any other cables (including mouse or video monitor cables). 2 Turn the logic analysis system frame upside-down. 3 Remove the bottom cover. 4 Remove the slot cover. You may use either slot.
Chapter 3: Installing the Emulation Module Installing the Emulation Module 5 Install the emulation module. 6 Connect the cable and re-install the screws. You may connect the cable to either of the two connectors. If you have two emulation modules, note that many debuggers will work only with the "first" module: the one toward the top of the frame ("Slot 1"), plugged into the connector nearest the back of the frame. 7 Reinstall the bottom cover, then turn the frame right-side-up.
Chapter 3: Installing the Emulation Module Installing the Emulation Module To install the emulation module in an HP 16600A-series logic analysis system You will need T-8, T-10, and T-15 Torx screw drivers (supplied with the modules). 1 Turn off the logic analysis system and REMOVE THE POWER CORD. Remove any other cables (such as probes, mouse, or video monitor). 2 Slide the cover back. 3 Remove the slot cover.
Chapter 3: Installing the Emulation Module Installing the Emulation Module 4 Install the emulation module. 5 Connect the cable and re-install the screws. 6 Reinstall the cover. Tighten the screws snugly ( 2 N-m or 18 inch-pounds). 7 Plug in the power cord, reconnect the other cables, and turn on the logic analysis system. The new emulation module will be shown in the system window.
4 Installing Software on an HP 16600A/ 700A 53
Installing Software on an HP 16600A/700A This chapter explains how to install the software you will need for your analysis probe or emulation solution. Installing and loading Installing the software will copy the files to the hard disk of your logic anlysis system. Later, you will need to load some of the files into the appropriate hardware module.
Chapter 4: Installing Software on an HP 16600A/700A Installing Software on an HP 16600A/700A What needs to be installed HP 16600A/700A-series logic analysis systems If you ordered an emulation solution with your logic analysis system, the software was installed at the factory.
Chapter 4: Installing Software on an HP 16600A/700A Installing Software on an HP 16600A/700A To install the software from CD-ROM (HP 16600A/700A) Installing a processor support package from a CD-ROM will take just a few minutes. If the processor support package requires an update to the HP 16600A/700A operating system, installation may take approximately 15 minutes. If the CD-ROM drive is not connected, see the instructions printed on the CD-ROM package.
Chapter 4: Installing Software on an HP 16600A/700A Installing Software on an HP 16600A/700A See Also The instructions printed on the CD-ROM package for a summary of the installation instructions. The online help for more information on installing, licensing, and removing software. To list software packages which are installed (HP 16600A/700A) In the System Administration Tools window, click List... .
58 CPU32 Emulation
5 Connecting and Configuring the Emulator 59
Chapter 5: Connecting and Configuring the Emulator Connecting and Configuring the Emulator Connecting and Configuring the Emulator This chapter shows you how to connect the emulator to the target system and how to configure the emulator and target. Here is a summary of the steps for connecting and configuring the emulator: 1 Make sure the target system is designed to work properly with the emulator. (page 65) 2 Install the emulation module in your logic analysis system, if necessary.
Chapter 5: Connecting and Configuring the Emulator Using the Emulation Control Interface Using the Emulation Control Interface The Emulation Control Interface in your HP16600A/700A-series logic analysis system allows you to control an emulator (an emulation module or an emulation probe). As you set up the emulator, you will use the Emulation Control Interface to: • Update firmware (which reloads or changes the processor-specific personality of the emulator).
Chapter 5: Connecting and Configuring the Emulator Using the Emulation Control Interface analyzer to cause a break. Using a debugger with the Emulation Control Interface is not recommended because: See Also • The interfaces can get out of synchronization when commands are issued from both interfaces. This causes windows to be out-of-date and can cause confusion. • Most debuggers cannot tolerate another interface issuing commands and may not start properly if another interface is running.
Chapter 5: Connecting and Configuring the Emulator Using the Emulation Control Interface To start the Emulation Control Interface from the Workspace window 1 Open the Workspace window. 2 Drag the Emulator icon onto the workspace. 3 Right-click on the Emulator icon, then select Start Session....
Chapter 5: Connecting and Configuring the Emulator Using the Emulation Control Interface To start the Emulation Control Interface from the Workspace window for an emulation probe If you have a stand-alone emulation probe connected to the logic analysis system via LAN, use the Emulation Probe icon instead of the Emulator icon. 1 Open the Workspace window. 2 Drag the Emulation Probe icon onto the workspace. 3 Right-click on the Emulation Probe icon, then select Start Session....
Chapter 5: Connecting and Configuring the Emulator Designing a Target System for the Emulator Designing a Target System for the Emulator Debug port connections If you plan to connect the emulator directly to the target system, the target system should have a debug port (BDM) connector. The connector should be a dual row header strip (“Berg connector”), 10 pins per inch, with 25 mil pins. Some of the signals at the BDM port share the same lines, as shown in the diagrams on the following pages.
Chapter 5: Connecting and Configuring the Emulator Designing a Target System for the Emulator The following signals should be available at the BDM port: BDM signal definitions Mnemonic Name Direction Signal Description GND Ground BKPT Breakpoint Input (to target) Signals a hardware breakpoint. Also used to place the CPU32 in background debug mode.
Chapter 5: Connecting and Configuring the Emulator Designing a Target System for the Emulator 8-pin BDM port An 8-pin BDM port should be a dual row header strip ("Berg connector"), 4 pins per row, 10 pins per inch, with 25 mil pins. If you plan to use the 10-pin cable, use a header with 2 rows of 5 pins.
Chapter 5: Connecting and Configuring the Emulator Designing a Target System for the Emulator CONFIG2 pin The CONFIG2 pin on CPU32+ processors shares a pin with the processor FREEZE output. The emulator can pull this line down and cause the CPU32+ to power up in Slave Mode with the internal CPU disabled. To ensure that CONFIG2 is high at reset, the target should supply sufficient pullup current to drive the FREEZE input on the emulator.
Chapter 5: Connecting and Configuring the Emulator Connecting the Emulator to the Target System Connecting the Emulator to the Target System Choose one of the following methods for connecting the emulator to a target system. • Directly through a debug port connector on the target board. • Through an HP E2480A analysis probe, which provides a direct connection to the debug port pins.
Chapter 5: Connecting and Configuring the Emulator Connecting the Emulator to the Target System After you have connected the emulator to your target system, you may need to update the firmware in the emulator. See Also For information on designing a debug port on your target board, see page 65. For a list of the parts supplied with the emulator, see page 23.
Chapter 5: Connecting and Configuring the Emulator Connecting the Emulator to the Target System CAUTION: Be careful to orient the connector as shown below. If the connector is rotated, your target system or the emulator may be damaged. 6 Turn on the power to the logic analysis system, then turn on the power to the target system. See Also “Designing a Target System for the Emulator” on page 65. To connect to a target system via an 8-pin debug port 1 Remove power from the target system and the emulator.
Chapter 5: Connecting and Configuring the Emulator Connecting the Emulator to the Target System 4 Plug one end of the 10-pin cable into the target interface module. 5 Plug the other end of the 10-pin cable into the target system. Orient the red wire toward pin 1 of the connector. Pins 1 and 2 of the cable should be the ones which are not connected. Connect pin 3 of the cable to pin 1 of the target connector. CAUTION: Be careful to orient the connector as shown below.
Chapter 5: Connecting and Configuring the Emulator Connecting the Emulator to the Target System To connect to a target system using an analysis probe 1 Remove power from the target system. 2 Plug one end of the 50-pin cable into the emulator. The connectors are keyed. 3 Plug the other end of the 50-pin cable into the connector on the analysis probe.
Chapter 5: Connecting and Configuring the Emulator Connecting the Emulator to the Target System To verify communication between the emulator and target system 1 Turn on the target system. 2 Start the Emulation Control Interface.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator Configuring the Emulator The emulator has several user-configurable options. These options may be customized for specific target systems and saved in configuration files for future use. The easiest way to configure the emulator is through the Emulation Control Interface in an HP16600A or HP16700A logic analysis system.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator To configure using the Emulation Control Interface The easiest way to configure the emulator is to use the Emulation Control Interface. 1 Start an Emulation Control Interface session. In the system window, click the Emulation Control Interface icon, and then select Start Session.... 2 Open a Configuration window. Select Configuration...
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator See Also Help➞Help on this window in the Configuration window for information on each of the configuration options. Help in the Emulation Control Interface menu for help on starting an Emulation Control session.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator Example To see a complete list of configuration items, type help cf.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator To configure the processor type Processor type configuration Value Built-in command Notes CPU32 Processor Types 68330 68331 68332 68333 68334 68335 68336 68338 68340 68341 68349 68360 68376 683xx cf cf cf cf cf cf cf cf cf cf cf cf cf cf proc=68330 proc=68331 proc=68332 proc=68333 proc=68334 proc=68335 proc=68336 proc=68338 proc=68340 proc=68341 proc=68349 proc=68360 proc=68376 proc=683xx Use for other CPU32 processors CPU16
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator will allow display and modification from the user interface. For example, when 68332 is selected as the processor type, the interface will support direct access to the SIM, the QSM, the TPU, and the TPURAM registers. The emulator does not have explicit support for all CPU32 processors.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator Processor clock speed configuration Value Processor clock is at least 33 33 MHz cf procck=33 25 25 MHz cf procck=25 20 20 MHz cf procck=20 16 16 MHz cf procck=16 8 8 MHz (default) cf procck=8 4 4 MHz cf procck=4 2 2 MHz cf procck=2 1 1 MHz cf procck=1 512 512 kHz cf procck=512 32 32 kHz cf procck=32 Built-in command Use the cf dprocck command to display the default clock speed.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator the 131 kHz processor clock rate. When the configuration process is complete, the emulator will change the communication rate to a rate based on the clock speed (procck). The emulator will not communicate correctly with target systems that have a processor clock rate slower than 131 kHz. Note The emulator does not automatically match the communication speed to the actual target speed (SYNCR register).
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator Emulation probe • If your target system runs at a default clock rate less than 8 MHz but greater than 131 kHz, set switch S2 to OFF. Detailed information about processor clock rates Most target systems will communicate with the emulator properly and with excellent performance following the basic guidelines given in the preceding sections.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator rate specified in the configuration can support. Resetting the target processor also resets the SYNCR to its default value. If the target processor is reset while running user code (as opposed to putting the processor in a reset state from the interface), no communications rate change takes place within the emulator. The initialization code that runs on the target system from reset is required to set the SYNCR to the correct value.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator processor through the emulator can be recovered by applying the configuration to the emulator with the target processor clock rate set to a known good value. To configure restriction to real-time runs Real-time runs configuration Built-in command Value Emulator configuration no Allows commands which break to the monitor. Examples include commands which display memory or registers.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator Trigger out configuration Value The Trigger Out BNC will Built-in command fixhigh Always be high cf trigout=fixhigh fixlow Always be low cf trigout=fixlow monhigh Go high when the processor is running in background (Default) cf trigout=monhigh monlow Go low when the processor is running in background cf trigout=monlow To configure the Trigger In BNC (Emulation Probe Only) With an emulation module, this configuration i
Chapter 5: Connecting and Configuring the Emulator Testing the emulator and target system Testing the emulator and target system After you have connected and configured the emulator, you should perform some simple tests to verify that everything is working. See Also Chapter 11, “Troubleshooting the Emulator,” beginning on page 159, for information on testing the emulator hardware. To test memory accesses 1 Start the Emulation Control Interface and configure the emulator, if necessary.
RAM or flash memory. 3 Use the Breakpoints window to set breakpoints. Use the Registers window to initialize register values. The new register or breakpoint values are sent to the processor when you press the Enter key or when you move the cursor out of the selected register field. 4 In the Run Control window, click Run. 5 Use the Memory Mnemonic window to view the program and use the Memory window to view any output which has been written to memory.
6 Using Internal Registers (SIM and EMSIM Registers) 89
Chapter 6: Using Internal Registers (SIM and EMSIM Registers) Internal Registers (SIM and EMSIM Registers) Internal Registers (SIM and EMSIM Registers) The purpose of SIM Registers The CPU32 family of processors provides a variety of internal peripheral and memory modules that are directly connected to the CPU32 core through an internal bus. These modules are configured through memory mapped register banks.
Chapter 6: Using Internal Registers (SIM and EMSIM Registers) Configuring the SIM Registers Configuring the SIM Registers Summary If you have a boot ROM that initializes the SIM registers, you don’t have to configure the EMSIM registers in order to load code and run your target. It is a good idea to configure the EMSIM registers anyway, since the EMSIM registers are used configure an analysis probe. Page 93 discusses how to copy the SIM registers into the EMSIM registers.
Chapter 6: Using Internal Registers (SIM and EMSIM Registers) Configuring the SIM Registers Based on the previous discussion, it should be clear that the EMSIM values specified during configuration need to match the intended programming and of use of your CPU32 target system. You need to carefully decide how the processor will be configured and the corresponding SIM values.
Chapter 6: Using Internal Registers (SIM and EMSIM Registers) Configuring EMSIM Register Values Configuring EMSIM Register Values There are two methods you can use to configure EMSIM register values: • Copy values from the SIMs into the EMSIM registers, or • Manually define each of the EMSIM values. This will not change the value of the SIM registers.
Chapter 6: Using Internal Registers (SIM and EMSIM Registers) Configuring EMSIM Register Values 3 Open the Workspace window and select File➞Save Configuration.... The EMSIM values will be saved as part of the configuration. This allows you to restore the EMSIM values by loading the configuration.
Chapter 6: Using Internal Registers (SIM and EMSIM Registers) Configuring SIM Register Values Configuring SIM Register Values There are three ways to configure the values of the SIM registers: • Using code in your target’s boot ROM, or • Copying values from the EMSIM registers into the SIM registers, or • Manually entering the value of each SIM register using the Emulation Control Interface Some registers can only be written once after processor reset.
Chapter 6: Using Internal Registers (SIM and EMSIM Registers) Configuring SIM Register Values 2 Break the target processor. Some registers can only be written once after processor reset. If you set the EMSIM values, then reset and break, the EMSIM values will be written to the SIM registers. If your initialization code then attempts to write to one of the "write once after reset" registers, the writes will fail. In this case, you must run from reset to correctly execute the initialization code.
Chapter 6: Using Internal Registers (SIM and EMSIM Registers) Saving and Loading EMSIM Values Saving and Loading EMSIM Values You can use the Emulation Control Interface to save the EMSIM values to a configuration file then to restore the EMSIM values. The configuration file contains more than just the EMSIM values. When you load the configuration, the whole emulator configuration will be restored, including all configuration settings, and the locations of windows.
Chapter 6: Using Internal Registers (SIM and EMSIM Registers) Saving and Loading EMSIM Values 3 Select a file name and click Load. This will not change the SIM registers. To apply the new values to the corresponding SIM registers, see “To copy EMSIM registers to target SIM registers” on page 95.
Chapter 6: Using Internal Registers (SIM and EMSIM Registers) Configuring SIM and EMSIM Values Using Built-In Commands Configuring SIM and EMSIM Values Using BuiltIn Commands To compare SIM and EMSIM registers Target SIM registers may compared to the EMSIM to determine if they have changed. The only way to do this is with a built-in command: • Enter the sync diff command. This will display the differences between the SIM and EMSIM register sets.
Chapter 6: Using Internal Registers (SIM and EMSIM Registers) Configuring SIM and EMSIM Values Using Built-In Commands Summary of EMSIM-related built-in commands See Also Command Meaning sync sim Copy values from SIM registers to EMSIM registers sync emsim Copy values from EMSIM registers to SIM registers sync diff Display differences between SIM and EMSIM registers reset break Reset, break, and copy values from EMSIM registers to SIM registers Use the help sync command to display help for thes
Chapter 6: Using Internal Registers (SIM and EMSIM Registers) Internal Representation of SIM and EMSIM Registers Internal Representation of SIM and EMSIM Registers Internal to the emulator the EMSIM and SIM memory spaces are accessed using memory suffixes of the form offset@emsim and offset@reg. All memory mapped registers in the 683xx family are contained within a contiguous 4k block of memory (8k for the 68360).
102 CPU32 Emulation
7 Using the Emulator with a Debugger 103
Using the Emulator with a Debugger Several prominent companies design and sell state-of-the-art source debuggers which work with the HP emulation module and emulation probe. Benefits of using a debugger The debugger will enable you to control the execution of your processor from the familiar environment of your debugger. Using a debugger lets you step through your code at the source-code level.
Chapter 7: Using the Emulator with a Debugger Using the Emulator with a Debugger Here is an example of what the display on your PC or workstation might look like: CPU32 Emulation 105
Chapter 7: Using the Emulator with a Debugger Using the Emulator with a Debugger Minimum requirements To use a debugger with the emulator, you will need: • A debugger which is compatible with the emulator • A LAN connection to the PC or workstation that is running the debugger • X windows or an X terminal emulator, such as Reflection X on a PC. This is required only if you wish to have the logic analysis system user interface displayed on your PC or workstation screen, along with the debugger.
Chapter 7: Using the Emulator with a Debugger Setting up Debugger Software Setting up Debugger Software The instructions in this manual assume that your PC or workstation is already connected to the LAN, and that you have already installed the debugger software according to the debugger vendor's documentation. To use your debugger with the emulator, follow these general steps: • Connect the emulator to your target system (see page 69).
Chapter 7: Using the Emulator with a Debugger Setting up Debugger Software To connect the logic analysis system to the LAN Information on setting up a LAN connection is provided in the online help or installation manual for your logic analysis system. Your debugger will require some information about the LAN connection before it can connect to the emulator. This information may include: • IP address (Internet address) or LAN name of the logic analysis system.
Chapter 7: Using the Emulator with a Debugger Setting up Debugger Software Write the information here for future reference: IP Address of Logic Analysis System ___________________________ LAN Name of Logic Analysis System ___________________________ Gateway Address ___________________________ Port Number of Emulator ___________________________ CPU32 Emulation 109
Chapter 7: Using the Emulator with a Debugger Setting up Debugger Software To change the port number of an emulation module Some debuggers do not provide a means to specify a port number. In that case, the debugger will always connect to port 6470 (the first emulator). If you need to connect to another module, or if the port number of the first module has been changed, you must change the port number to be 6470.
Chapter 7: Using the Emulator with a Debugger Setting up Debugger Software To verify communication with the emulator 1 Telnet to the IP address. For example, on a UNIX system, enter “telnet 6472”. This connection will give you access to the emulator’s built-in terminal interface. You should see a prompt, such as “M>”. 2 At the prompt, type: ver You should then see information about the emulator and firmware version. 3 To exit from this telnet session, type D at the prompt.
Chapter 7: Using the Emulator with a Debugger Setting up Debugger Software To export the logic analysis system’s display to a workstation By exporting the logic analyzer’s display, you can see and use the logic analysis system’s windows on the screen of your workstation. To do this, you must have telnet software and X window installed on your computer.
Chapter 7: Using the Emulator with a Debugger Setting up Debugger Software To export the logic analysis system’s display to a PC By exporting the logic analyzer’s display, you can see and use the logic analysis system’s windows on the screen of your PC. To do this, you must have telnet software and an X terminal emulator installed on your computer. The following instructions use the Reflection X emulator from WRQ, running on Windows 95, as an example. 1 On the PC, start the X terminal emulator software.
Chapter 7: Using the Emulator with a Debugger Using the Green Hills debugger Using the Green Hills debugger Compatibility Version 1.8.8.A of the MULTI Development Environment from Green Hills Software, Inc. is one of several debuggers which connect to the emulator. This section provides information that is specific to using MULTI with the emulator. It is intended to be used in conjunction with the MULTI documentation provided by Green Hills Software.
Chapter 7: Using the Emulator with a Debugger Using the Green Hills debugger follow these steps: a Prepare the executable. Go to the 68000PC subdirectory where you installed MULTI. Copy the default.lnk file to user.lnk. b Start MULTI. On Unix, enter "multi". On Windows, double-click the Green Hills icon. c Set up the MULTI software environment: • • • Replace the project default.bld (in the Builder dialog box next to the project button) with hpdemo/ecs.bld and press ENTER.
Chapter 7: Using the Emulator with a Debugger Using the Green Hills debugger • In the Builder window, click Debug to open the Debugger window, then in the Debugger window’s command pane, enter: remote hpserv IP_address Starting hpserv opens two windows: the Target window and the I/O window. Commands entered in the Target window are sent directly to the emulator. The I/O window sends input (stdin) to and receives output (stdout) from the target program while it is running.
Chapter 7: Using the Emulator with a Debugger Using the Green Hills debugger 6 Specify an initialization address for the stack pointer. This is required if the stack pointer is neither initialized when the processor is reset nor set in the start-up code generated by the compiler.
Chapter 7: Using the Emulator with a Debugger Using the Green Hills debugger To configure the emulator, analysis probe, and target using an initialization script You can use an initialization script to configure the emulator and set up your target system. If you will always be using the same configuration, this way will save time and reduce errors. 1 Save the configuration commands in a text file, one command per line. Green Hills provides an example initialization sequence in the file hpserv.
Chapter 7: Using the Emulator with a Debugger Using the Green Hills debugger Example: script to configure EMSIM and SIM registers The following script was written for a target which does not have boot ROM and which is connected to an analysis probe. The script sets the EMSIM registers, then copies the EMSIM values to the target processor (sync emsim) and to the analysis probe (pp load) to enable address reconstruction.
Chapter 7: Using the Emulator with a Debugger Using the Green Hills debugger To perform common debugger tasks • To display registers, click the regs button in the Display window. • To set a breakpoint, click on the source code line where the breakpoint is to be located. • To clear a breakpoint, click again on the source line. • To step through code, click next. • To run from the current PC, click go.
Chapter 7: Using the Emulator with a Debugger Using the Green Hills debugger NOTE: logging commands in this way may result in a VERY large file. Beware of the disk space it may require. To reinitialize the system If you suspect that the emulator is out of sync with the MULTI debugger, you may want to reinitialize it. Perform the steps below to accomplish reinitialization: 3 In the Target window, type: init -c 4 Repeat step 5 in the "Getting started" section to configure the emulator.
Chapter 7: Using the Emulator with a Debugger Using the Green Hills debugger Using MULTI with the Hewlett-Packard Processor Probe from Green Hills Software, Inc. The Green Hills web site: http://www.ghs.com “Configuring the Emulator” on page 75 for more information on configuration options and the "cf" command.
Chapter 7: Using the Emulator with a Debugger Using the Software Development Systems debugger Using the Software Development Systems debugger Compatibility Version 7.2 of the SingleStep debugger from Software Development Systems, Inc. is one of several debuggers which connect to the HP emulator. This section provides information that is specific to using SingleStep with the emulator. It is intended to be used in conjunction with the SingleStep documentation provided by SDS.
Chapter 7: Using the Emulator with a Debugger Using the Software Development Systems debugger Getting started 1 Check that your emulator is programmed with firmware for a CPU32 processor: For an emulation module, go to the system window of the logic analyzer interface and verify that the Emulation Module icon is described as a "Motorola CPU16/32 BDM Emulator". If it is not, follow the instructions on page 147 to update the firmware.
Chapter 7: Using the Emulator with a Debugger Using the Software Development Systems debugger performs this initialization. However, when SingleStep resets the target, it immediately places the processor in debug mode. Any initialization code which may exist on the target board has not been run. SingleStep provides a way for target initialization to occur without running application code through the use of the "_config" alias.
Chapter 7: Using the Emulator with a Debugger Using the Software Development Systems debugger Example If you load the est360.wsp and set up the Debug Dialog options for the target you are connecting to, when you click OK, the file 68360.cfg will be created and place in the cmd directory. Comments have been added to this file, in order to explain the items (comments begin with a #). Contents of 68360.
Chapter 7: Using the Emulator with a Debugger Using the Software Development Systems debugger the SIM registers before issuing these two commands. “control –c” is used by SingleStep to forward a command to the emulator. For help on either the “sync sim” or “pp load” command, issue the commands, control –c “help sync” or control –c “help pp load” into the Command window. Also, note that the help pp load command will refer to the analysis probe as a preprocessor. They are one in the same.
Chapter 7: Using the Emulator with a Debugger Using the Software Development Systems debugger # # # # # # write write write write write write -b -w -w -w -w -b SD:0x0100100C SD:0x01001010 SD:0x01001014 SD:0x01001016 SD:0x01001026 SD:0x01001008 = = = = = = 0x8C 0x8000 0x0000 0x00A0 0x070F 0x84 # # # # # # CLKOCR PLLCR CDVCR PEPAR PICR AVR # Reset, run, break in order to set up chip selects # We can issue these commands since the target has boot # code in ROM that sets up the chip select registers co
Chapter 7: Using the Emulator with a Debugger Using the Software Development Systems debugger In summary, there are two ways for you to configure the emulator and your target. The first method consisted of loading an existing workspace, using the Debug Dialog to modify any items needed followed by clicking the OK button and having it create a corresponding .cfg file.
Chapter 7: Using the Emulator with a Debugger Using the Software Development Systems debugger specific to initializing the processor. It is executed each time the processor is reset. The value of the _reset alias can be viewed by issuing a "alias _reset" from the command window. • Execute the commands specified by the _config alias. The _config alias should be used to specify commands that are specific to initializing (configuring) the target system.
Chapter 7: Using the Emulator with a Debugger Using the Software Development Systems debugger Examples To see the speed that the emulator is using to communicate with the target system you would issue the following command in the SingleStep command window: control -c "cf procck" To change the speed to match a 25MHz processor clock you would issue the following command in the command window: control -c "cf procck=25" For more information about "terminal interface" commands see page 77.
Chapter 7: Using the Emulator with a Debugger Using the Software Development Systems debugger Error conditions "!ERROR 800! Invalid command: bcast" usually means that there is not a target interface module (TIM) connected to the emulator or the emulator does not have firmware for the CPU32 family. Verify that the emulator is connected to the target.
8 Using the Analysis Probe and Emulation Module Together 133
Chapter 8: Using the Analysis Probe and Emulation Module Together Using the Analysis Probe and Emulation Module Together Using the Analysis Probe and Emulation Module Together This chapter describes how to use an analysis probe, an emulation module, and other features of your HP 16600A or HP 16700A logic analysis system to gain insight into your target system.
Chapter 8: Using the Analysis Probe and Emulation Module Together Using the Analysis Probe and Emulation Module Together section of memory in the Memory Disassembly window. • Your debugger shows your program as it was actually assembled, and (if it supports the emulation module) shows which line of assembly code corresponds to the value of the program counter on your target system.
Chapter 8: Using the Analysis Probe and Emulation Module Together Triggering the Emulation Module from the Analyzer Triggering the Emulation Module from the Analyzer You can trigger the emulation module from the logic analyzer using either the Source Viewer window or the Intermodule window. If you are using the HP B4620B Source Correlation Tool Set, using the Source Viewer window is the easiest method.
Chapter 8: Using the Analysis Probe and Emulation Module Together Triggering the Emulation Module from the Analyzer trigger from the logic analyzer. To disable the processor stop on trigger, select Trace➞Disable Break Emulator On Trigger. 3 Click Group Run in the Source window (or other logic analyzer window). 4 If your target system is not already running, click Run in the emulation Run Control window to start your target.
Chapter 8: Using the Analysis Probe and Emulation Module Together Triggering the Emulation Module from the Analyzer 3 Click Group Run in the Source window (or other logic analyzer window). 4 If your target system is not already running, click Run in the emulation Run Control window to start your target. See Also See the online help for your logic analysis system for more information on setting triggers.
Chapter 8: Using the Analysis Probe and Emulation Module Together Triggering the Emulation Module from the Analyzer clock to stop. Therefore most intermodule measurements will have to be stopped to see the measurement. Example An intermodule measurement has been set up where the analyzer is triggering the emulation module. The following sequence could occur: 1. The analyzer triggers. 2. The trigger (“Break In”) is sent to the emulation module. 3.
Chapter 8: Using the Analysis Probe and Emulation Module Together Tracing Until the Processor Halts Tracing Until the Processor Halts If you are using a state analyzer, you can begin a trace, run the processor, then manually end the trace when the processor has halted. To halt the processor, you can set a breakpoint using the Emulation Control Interface or a debugger. Some possible uses for this measurement are: • • • To store and display processor bus activity leading up to a system crash.
Chapter 8: Using the Analysis Probe and Emulation Module Together Triggering the Logic Analyzer from the Emulation Module Triggering the Logic Analyzer from the Emulation Module You can create an intermodule measurement which will allow the emulation module to trigger another module such as a timing analyzer or oscilloscope. If you are only using a state analyzer to capture the processor bus then it will be much simpler to use “Tracing until processor halts” as described on page 140.
Chapter 8: Using the Analysis Probe and Emulation Module Together Triggering the Logic Analyzer from the Emulation Module Group Run The intermodule bus signals can still be active even without a Group Run.
Chapter 8: Using the Analysis Probe and Emulation Module Together Triggering the Logic Analyzer from the Emulation Module For example, suppose you have the following IMB measurement set up: Clicking the Group Run button (at the very top of the Intermodule window or a logic analyzer window) will start the analyzer running. The analyzer will then wait for an arm signal. Now when the emulation module transitions into “Monitor” from “Running” (or from “Reset”), it will send the arm signal to the analyzer.
Chapter 8: Using the Analysis Probe and Emulation Module Together Triggering the Logic Analyzer from the Emulation Module If you define a trigger on some state and the debugger happens to read the same state, then you may falsely trigger your analyzer measurement. In summary, when you are making an analysis measurement be aware that the debugger could be impacting your measurement.
Chapter 8: Using the Analysis Probe and Emulation Module Together Triggering the Logic Analyzer from the Emulation Module using a state analyzer on the processor bus the status may never change upon receiving the emulation module trigger (analysis arm). This occurs because the qualified processor clock needed to switch the state analyzer to the next state is stopped.
Chapter 8: Using the Analysis Probe and Emulation Module Together Triggering the Logic Analyzer from the Emulation Module If you are going to run the emulation module from Reset you must do a Reset followed by Break to properly set the breakpoints. The Reset will clear all on-chip hardware breakpoint registers. The Break command will then reinitialize the breakpoint registers.
9 Updating Firmware 147
Updating Firmware Firmware gives your emulator a “personality” for a particular processor or processor family. After you have connected the emulator to your target system, you may need to update the firmware to give it the right personality for your processor. You must update the firmware if: • You have an emulation module which was not shipped already installed in the logic analysis system. • You need to change the personality of the emulator for a new processor.
Chapter 9: Updating Firmware Emulation Probe Firmware Emulation Probe Firmware To display current firmware version information • Use telnet or a terminal emulator to access the built-in "terminal interface" and use the ver command to view the version information for firmware currently in the emulation probe. To update firmware for an emulation probe To update the firmware, you must have access to the World Wide Web and a PC or a workstation connected to your emulation probe.
Chapter 9: Updating Firmware Emulation Module Firmware Emulation Module Firmware Always update firmware by installing a processor support package. This will ensure that the version of the Emulation Control Interface software is compatible the version of the emulator firmware. To display current firmware version information 1 In the Update Firmware window, click Display Current Version. There are usually two firmware version numbers: one for “Generics” and one for the personality of your processor.
Chapter 9: Updating Firmware Emulation Module Firmware 4 Update Firmware. 5 In the Update Firmware window, select the firmware to load into the emulation module. 6 Click Update Firmware. In about 20 seconds, the firmware will be installed and the screen will update to show the current firmware version. See also “Installing Software” beginning on page 53 for instructions on how to install the processor support package from the CD-ROM.
Chapter 9: Updating Firmware Emulation Module Firmware window. 3 Follow the instructions displayed by the Setup Assistant. See also Page page 53 for instructions on how to install a the processor support package from the CD-ROM.
10 Specifications and Characteristics 153
Processor compatibility The emulator supports Motorola 68330, 68331, 68332, 68F333, 68334, 68335, 68336, 68338, 68340, 68341, 68349, 68360, or 68376 microprocessors operating at clock speeds up to 25 MHz. The emulator supports both 5V and 3.3V operation.
Chapter 10: Specifications and Characteristics Emulation probe electrical characteristics BNC, labeled TRIGGER OUT Output Drive. Logic high level with 50-ohm load >= 2.0 V. Logic low level with 50-ohm load <= 0.4 V. Output function is selectable, see the configuration section (page 75). BNC, labeled BREAK IN Input. Edge-triggered TTL level input (active high), 20 pf, with 2K ohms to ground in parallel. Maximum input: 5V above VCC; 5 V below ground. The BNC introduces approximately 2.
Chapter 10: Specifications and Characteristics Emulation Probe and Emulation Module Electrical Characteristics Emulation Probe and Emulation Module Electrical Characteristics Characteristic Symbol Value Unit Supply Voltage from Target VDD -0.3 to +5.5 V Characteristic Symbol VDD = 5 Volts Min Max Input Current (VDD) Iil Input Voltage Vin VSS-0.5 VDD+0.5 Input High Voltage Vih 2 Input Low Voltage Vil VSS-0.5 Input High Current Iih Input Low Current VDD = 3.
Chapter 10: Specifications and Characteristics Emulation Probe and Emulation Module Electrical Characteristics Emulation probe environmental characteristics Temperature Operating, +0 C to +40 C (+32 to +104 F); nonoperating, -40 to +60 C (-40 to +140 F). Altitude Operating/nonoperating 4600 m (15 000 ft). Relative Humidity 15% to 95%. For indoor use only.
158 CPU32 Emulation
11 Troubleshooting the Emulator 159
Chapter 11: Troubleshooting the Emulator Troubleshooting the Emulator Troubleshooting the Emulator If you have problems with the emulator, your first task is to determine the source of the problem.
Chapter 11: Troubleshooting the Emulator Troubleshooting the Emulator Troubleshooting Guide Common problems and what to do about them Symptom What to do See also Commands from the Emulation Control Interface or debugger have no effect 1 Verify LAN communication. 2 Check that you are using the correct firmware. 3 Use the Emulation Control Interface or a telnet connection to try a few built-in commands. If this works, your debugger may not be configured properly.
Chapter 11: Troubleshooting the Emulator Status Lights Status Lights Emulation Module Status Lights The emulation module uses status lights to communicate various modes and error conditions. The following table gives more information about the meaning of the power and target status lights.
Chapter 11: Troubleshooting the Emulator Status Lights Emulation Probe Status Lights The following illustration shows the status lights on both sides of the emulation probe and what they mean: Lit when the power suply is properly connected to the emulation probe Lit when the target processor is running in debug mode Lit when the target system is in a reset state Lit when the target processor is running in normal (user program) mode Lit when LAN data is being transmitted Lit when 10BASE-T connection has a
Chapter 11: Troubleshooting the Emulator Status Lights Emulation Probe Status Lights The emulation probe uses status lights to communicate various modes and error conditions. The following table gives more information about the meaning of the power and target status lights.
Chapter 11: Troubleshooting the Emulator Emulator Built-in Commands Emulator Built-in Commands The emulator has some built-in commands (sometimes called the “terminal interface”) which you can use for troubleshooting.
Chapter 11: Troubleshooting the Emulator Emulator Built-in Commands If the LAN name of the logic analysis system is “test2” and you have only one emulation module installed, the command might look like this: telnet test2 6472 4 If you do not see a prompt, press the key a few times. To exit from this telnet session, type D at the prompt.
Chapter 11: Troubleshooting the Emulator Emulator Built-in Commands To use the built-in commands Here are a few commonly used built-in commands: Useful built-in commands b cf help init lan m pp load reg r rep rst s sync diff sync emsim sync sim ver Break—go into the background monitor state Configuration—read or write configuration options Help—display online help for built-in commands Initialize—init -c re-initializes everything in the emulator except for the LAN software; init -p is the equivalent of c
Chapter 11: Troubleshooting the Emulator Emulator Built-in Commands The prompt indicates the status of the emulator: Emulator prompts U M p R r d ? Running user program Running in background monitor No target power Emulation reset Target reset Cable disconnected Unknown state Examples To set register R0, then view R0 to verify that it was set, enter: R>rst M>reg M>reg reg -m r0=ffff r0 R0=0000ffff To break execution then step a single instruction, enter: M>b M>s PC=xxxxxxxx M> To determine what firmw
Chapter 11: Troubleshooting the Emulator Problems with the BDM Connection Problems with the BDM Connection If a user interface behaves erratically ❏ Check the orientation of the cable connecting the target interface module to your target system. If the cable is offset or rotated, the emulator will try to interpret the “random” signals with unpredictable results. If the cable is rotated, the emulator or target system may also be damaged. ❏ Check that the processor clock speed has been properly configured.
Chapter 11: Troubleshooting the Emulator Problems with Configuration Problems with Configuration If you have problems displaying some registers ❏ If your user interface can read or write “generic” registers, but cannot access registers that are unique to your target microcontroller, check that the target microcontroller matches the processor type you have configured in the emulator. You can use the Configuration window in the Emulation Control Interface to configure the target processor type.
Chapter 11: Troubleshooting the Emulator Problems with the Target System Problems with the Target System If boot area accesses fail When you start a debugger interface or attempt to run from reset, the emulator makes four accesses to the target system boot area to find reset values for the SP and PC. It then attempts to read the values on the stack and the code at the PC. This problem can result in unknown values for the SP and PC (displayed as ???) and can make the debugger interface respond very slowly.
Chapter 11: Troubleshooting the Emulator Problems with the LAN Interface (Emulation Module Only) Problems with the LAN Interface (Emulation Module Only) If LAN communication does not work If you cannot verify the connection, or if the commands are not accepted by the emulation module: ❏ Make sure that you wait for the power-on self test to complete before connecting. ❏ Make sure that the LAN cable is connected.
Chapter 11: Troubleshooting the Emulator Problems with the LAN Interface (Emulation Module Only) If there are many subnet masks in use on the local subnet, the logic analysis system may take a very long time to connect to the network after it is turned on.
Chapter 11: Troubleshooting the Emulator Problems with the Emulation Module Problems with the Emulation Module Occasionally you may suspect a hardware problem with the emulation module or target interface module. The procedures in this section describe how to test the hardware, and if a problem is found, how to repair or replace the broken component.
Chapter 11: Troubleshooting the Emulator Problems with the Emulation Module To run complete performance verification tests using a telnet connection (Emulation Module Only) 1 Disconnect the 50-pin cable from the emulation module, and plug the loopback test board (HP part number E3496-66502) directly into the emulation module. Do not plug anything into the other end of the loopback test board. On a good system, the RESET LED will light and the BKG and USER LEDs will be out.
Chapter 11: Troubleshooting the Emulator Problems with the Emulation Module To execute tests 3, 4, and 5 only for 2 cycles: pv -t3-5 2 The results on a good system with the loopback test board connected, are as follows: M>pv 1 Testing: HPE3499C Series Emulation System Test 1: Powerup PV Results Test 2: Target Probe Feedback Test Test 3: Boundary Scan Master Test Test 4: I2C Test Test 5: Data Lines Test Number of tests: 1 Number of failures: 0 Passed! Passed! Passed! Passed! Passed! Copyright (c) Hewlett
Chapter 11: Troubleshooting the Emulator Problems with the LAN Interface (Emulation Probe Only) Problems with the LAN Interface (Emulation Probe Only) If you cannot verify LAN communication If you cannot verify connection using the procedure in "To verify LAN communication", or if the commands are not accepted by the emulation probe: ❏ Make sure that you have connected the emulation probe to the proper power source and that the power light is lit.
Chapter 11: Troubleshooting the Emulator Problems with the LAN Interface (Emulation Probe Only) ❏ Use a serial connection to run the LAN performance verification tests (see page 174). If you have LAN connection problems ❏ If the emulation probe does not accept commands from the HP 16600A/700A: 1. Check that switch S1 is "0" (attached to LAN, not RS-232). 2. Check that switch S5 is in the correct position for your LAN interface (either 10BASE2 or 10BASE-T).
Chapter 11: Troubleshooting the Emulator Problems with the LAN Interface (Emulation Probe Only) If the "POL" LED is lit The "POL" LED indicates that the polarity is reversed on the receive pair if you are using a 10BASE-T connection. The emulator should still work properly in this situation, but other LAN devices may not work. If it takes a long time to connect to the network ❏ Check the subnet masks on the other LAN devices connected to your network.
Chapter 11: Troubleshooting the Emulator Problems with the Serial Interface (Emulation Probe Only) Problems with the Serial Interface (Emulation Probe Only) If you cannot verify RS-232 communication If the emulation probe prompt does not appear in the terminal emulator window: ❏ Make sure that you have connected the emulation probe to the proper power source and that the power light is lit.
Chapter 11: Troubleshooting the Emulator Problems with the Serial Interface (Emulation Probe Only) If you have RS-232 connection problems with the MS Windows Terminal program ❏ Remember that Windows 3.1 only allows two active RS-232 connections at a time. To be warned when you violate this restriction, choose Always Warn in the Device Contention group box under 386 Enhanced in the Control Panel.
Chapter 11: Troubleshooting the Emulator Problems with the Emulation Probe Problems with the Emulation Probe To run the power up self test 1 Unplug the emulation probe, then plug it in. 2 Watch the status lights.
Chapter 11: Troubleshooting the Emulator Problems with the Emulation Probe Pwr/Target LEDs Meaning 8 ●● ❍❍ RAM tested successfully 9 ❍● ●❍ LAN internal feedback tested successfully 10 ❍● ❍❍ Boundary scan master (BSM) test begun 11 ●● ●❍ BSM test completed, start system, load drivers, initialize LAN If the power up self test fails, the RESET LED will flash the number of the test, then stay lit. If any of the LEDs fail to change, or all of them remain on, there is a system failure.
Chapter 11: Troubleshooting the Emulator Problems with the Emulation Probe To run the emulation probe performance verification tests In addition to the powerup tests, there are several additional performance verification (PV) tests available. Some of these tests can be performed through the HP 16700A/16700Aseries logic analysis system. The LAN tests for an emulation probe can only be executed through the RS-232 port.
Chapter 11: Troubleshooting the Emulator Problems with the Emulation Probe To run complete performance verification tests for an emulation probe The LAN tests can only be executed through the RS-232 port. The remainder of this section assumes that the tests are being run from a terminal emulator connected to the RS-232 port. 1 Disconnect the 50-pin cable from the emulation probe, and plug the emulator loopback test board (HP part number E349666502) directly into the emulator.
Chapter 11: Troubleshooting the Emulator Problems with the Emulation Probe 5 Enter the pv 1 command. See Also Options available for the pv command are explained in the help screen displayed by typing help pv or ? pv at the prompt. Examples Here are some examples of ways to use the pv command.
Chapter 11: Troubleshooting the Emulator Problems with the Emulation Probe If a performance verification test fails There are some things you can do if a failure is found on one of these tests. Details of the failure can be obtained through using a -v value (“verbose level”) of 2 or more.
Chapter 11: Troubleshooting the Emulator Problems with the Emulation Probe then try to set them to correct values. If you are unable to set them to correct values, their is a failure in the FLASH ROM which requires service from HP.
Chapter 11: Troubleshooting the Emulator Problems with the Emulation Probe TEST 5: Target Probe Feedback Test TEST 6: Boundary Scan Master Test TEST 7: I2C Test TEST 8: Data Line Test If these tests are not executed, check that you have connected the emulator loopback test board. If these tests fail, return the emulator to HP for replacement.
Chapter 11: Troubleshooting the Emulator Returning Parts to Hewlett-Packard for Service Returning Parts to Hewlett-Packard for Service The repair strategy for this emulation solution is board replacement. Exchange assemblies are available when a repairable assembly is returned to Hewlett-Packard. These assemblies have been set up on the “Exchange Assembly” program. This lets you exchange a faulty assembly with one that has been repaired, calibrated, and performance verified by the factory.
Chapter 11: Troubleshooting the Emulator Returning Parts to Hewlett-Packard for Service To obtain replacement parts The following table lists some parts that may be replaced if they are damaged or lost. The part numbers are subject to change. Contact your nearest Hewlett-Packard Sales Office for further information.
Chapter 11: Troubleshooting the Emulator Returning Parts to Hewlett-Packard for Service To clean the instrument If the instrument requires cleaning: 1 Remove power from the instrument. 2 Clean with a mild detergent and water. 3 Make sure that the instrument is completely dry before reconnecting it to a power source.
Glossary Analysis Probe A probing solution connected to the target microcontroller. It provides an interface between the signals of the target microcontroller and the inputs of the logic analyzer. Formerly called a “preprocessor.” Elastomeric Probe Adapter A connector that is fastened on top of a target microcontroller using a retainer and knurled nut.
Glossary corresponding odd and even logic analyzer pod cables. High-Density Termination Adapter Cable Same as a HighDensity Adapter Cable, except it has a termination in the Mictor connector. Jumper Moveable direct electrical connection between two points. Mainframe Logic Analyzer A logic analyzer that resides on one or more board assemblies installed in an HP16500, HP1660-series, or HP16600A/700A-series mainframe.
Glossary mainframe logic analyzer in that it does not offer card slots for installation of additional capabilities, and its specifications are not modified based upon selection from a set of optional hardware boards that might be installed within its frame. that obtains one-quarter of the signals from an elastomeric probe adapter (one side of a target microcontroller) and makes them available for probing.
196 CPU32 Emulation
Index A address, IP IP address, 32 altitude specifications, 157 analysis probe connecting to, 73 definition, 193 processors supported, 4 product numbers, 4 assistant See setup assistant B BDM port See debug port BKG light, 162, 164, 185 BNC break in, 86 trigger out, 85 BNC, LAN, 31, 155 bootp, 37, 38 break in configuration, 86 breakpoints tracing until, 145 built-in commands configuration, 77 LAN configuration, 34 list of commands, 165 bus cycle termination, 65 C cables BDM, 71 emulator, 70 LAN, 40 serial,
Index flexible adapter definition, 193 G gateway address, 35, 178 general-purpose flexible adapter definition, 193 Green Hills debugger, 114 H high-density adapter cable definition, 193 high-density termination adapter definition, 194 host computer connecting to, 29 HRESET signal, 65 I IEEE 802.
Index verifying, 46 service ports, 35 service, how to obtain, 190 setup See configuration setup assistant, 151 definition, 194 signals debug port, 65 SIM registers configuring, 95 displaying, 90 introduction, 90 SingleStep debugger, 123 skid, reducing, 138 slow clock message, 144, 146, 161 software installing, 53 list of installed, 57 software probe See emulation probe solution at a glance, 2 definition, 194 description of, 2 solving problems emulation probe, 182 source code displays, 134 specifications al
200 CPU32 Emulation
DECLARATION OF CONFORMITY according to ISO/IEC Guide 22 and EN 45014 Manufacturer’s Name: Hewlett-Packard Company Manufacturer’s Address: Colorado Springs Division 1900 Garden of the Gods Road Colorado Springs, CO 80907 USA declares, that the product Product Name: Processor Probe Model Number(s): E3458A Product Option(s): All conforms to the following Product Specifications: Safety: IEC 1010-1:1990+A1 / EN 61010-1:1993 UL3111 CSA-C22.2 No. 1010.
Product Regulations Safety EMC IEC 1010-1:1990+A1 / EN 61010-1:1993 UL3111 CSA-C22.2 No. 1010.1:1993 This Product meets the requirement of the European Communities (EC) EMC Directive 89/336/EEC. Emissions EN55011/CISPR 11 (ISM, Group 1, Class A equipment), Immunity EN50082-1 Code1 IEC 555-2 IEC 555-3 IEC 801-2 (ESD) 4kV CD, 8kV AD IEC 801-3 (Rad.) 3 V/m IEC 801-4 (EFT) 0.5 kV, 1kV 1 1 1 1 1 Notes2 1,2 2 1 Performance Codes: 1 PASS - Normal operation, no effect.
© Copyright Hewlett-Packard Company 1994-1998 All Rights Reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. Restricted Rights Legend Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in subparagraph (C) (1) (ii) of the Rights in Technical Data and Computer Software Clause in DFARS 252.227-7013. HewlettPackard Company, 3000 Hanover Street, Palo Alto, CA 94304 U.S.A.
Product Warranty This Hewlett-Packard product has a warranty against defects in material and workmanship for a period of one year from date of shipment. During the warranty period, Hewlett- Packard Company will, at its option, either repair or replace products that prove to be defective. For warranty service or repair, this product must be returned to a service facility designated by Hewlett- Packard.
