User’s Guide Publication number E3453-97001 May 2000 © Copyright Agilent Technologies 1994-2000 All Rights Reserved For Safety information, Warranties, and Regulatory information, see the pages behind the index.
Motorola MPC8240 and MPC8260 Emulation—At a Glance This manual describes how to set up several Agilent Technologies 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 MPC8240 and MPC8260 microprocessors. The emulator lets you use the target processor’s built-in background debugging features, including run control and access to registers and memory.
Emulation Module The emulation module plugs into your Agilent Technologies 16600A/ 700A-series logic analysis system frame. You can connect the emulation module a debug port on the target system or analysis probe through the provided target interface module (TIM). OR Emulation Migration The emulation migration includes a target interface module and firmware. Use the emulation migration if you already have an emulation probe or an emulation module for another processor.
In This Book This book documents the following products: Emulation Probe Processor supported Product ordered Includes MPC8240 Agilent Technologies E5900A Option #100 Agilent Technologies 16610A emulation probe, target interface module (TIM) MPC8260 Agilent Technologies E5900A Option #100 Agilent Technologies 16610A emulation probe, target interface module (TIM) Emulation Module Processor supported Product ordered Includes MPC8240 Agilent Technologies E5901A Option #100 Agilent Technologies 1
Contents Motorola MPC8240 and MPC8260 Emulation—At a Glance Emulation Probe 2 Emulation Module 3 Emulation Migration 3 In This Book 1 Overview Setup Flowchart 15 Emulation Probe 16 Equipment supplied 16 Minimum equipment required 18 To connect the emulation probe to a power source To power on the system 20 To power off the system 20 Connection Sequence 20 Emulation Module 21 Equipment supplied 21 Minimum equipment required Emulation Migration Equipment supplied 18 22 23 23 Minimum equipment re
Contents 2 Connecting the Emulation Probe to a LAN Setting Up a LAN Connection to a PC or Workstation 29 To obtain an IP address 30 To configure LAN parameters using the built-in terminal interface To configure LAN parameters using BOOTP 35 To set the 10BASE-T configuration switches 38 To verify LAN communications 39 Setting Up a Serial Connection 32 40 To set the serial configuration switches To connect a serial cable 42 To verify serial communications 44 41 3 Installing the Emulation Module To inst
Contents emulation probe 62 Designing a MPC8240 or MPC8260 Target System Debug Port Connection 63 Reset Signals for the MPC8240 Reset Signals for the MPC8260 To test the emulator 65 63 64 64 Connecting the Emulator to the Target System 66 To connect to a target system using a 16-pin debug port 67 To connect to a target system using an analysis probe 68 To verify communication between the emulator and target system Configuring the Emulator 69 70 To configure using the Emulation Control Interface
Contents 6 Using the Emulator with a Debugger Setting Up Debugger Software 87 To connect the logic analysis system to the LAN 88 To change the port number of an emulation module 89 To verify communication with the emulator 90 To export the logic analysis system’s display to a workstation To export the logic analysis system’s display to a PC 92 91 7 Using the Analysis Probe and Emulation Module Together What are some of the tools I can use? 94 Which assembly-level listing should I use? 94 Which source-l
Contents 8 Updating Firmware Emulation Probe Firmware 109 To display current firmware version information 109 To update firmware for an emulation probe 109 Emulation Module Firmware 110 To display current firmware version information 110 To update firmware for an emulation module using the Emulation Control Interface 110 To update firmware for an emulation module using the Setup Assistant 112 9 Specifications and Characteristics Emulation module and emulation probe—operating characteristics 114 Emula
Contents Emulator Built-in Commands 125 To telnet to the emulation module 125 To telnet to the emulation probe 126 To use the built-in commands 127 Problems with the Target System 129 What to check first 129 To check the debug port connector signals 130 To interpret the initial prompt 132 If you see memory-related problems 136 If running from reset causes problems 137 If you see the "!ASYNC_STAT 173!" error message 137 If you see the “!ERROR 145!” error message 138 Other error messages 138 Problems w
Contents Problems with the Emulation Probe 149 To run the power up self test 149 To run the emulation probe performance verification tests 151 To run the performance verification tests using the logic analysis system 151 To run complete performance verification tests for an emulation probe 152 If a performance verification test fails 154 Returning Parts to Agilent Technologies for Service To return a part to Agilent Technologies To obtain replacement parts 158 To clean the instrument 159 157 157 Glos
Contents 12
1 Overview 13
Chapter 1: 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 14 MPC8240 and MPC8260 Emulation
Chapter 1: Overview Setup Flowchart Setup Flowchart Emulation module Emulation migration E5901A Emulation probe E5902A Install emulation module (if necessary) 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 (Agilent part number E349666502). • A 50-pin ribbon cable (connects the emulation probe to the target interface module). • A 16-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 MPC8240 and MPC8260 Emulation 17
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 Agilent Technologies analysis probe or you can design a debug port connector on the target system. The target system must meet the criteria on page 63. • A host computer, such as a PC or workstation.
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 Agilent Technologies 16610A emulation module. If you ordered an emulation module as part of your Agilent Technologies 16600A or 16700A logic analysis system, it is already installed in the frame.
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 Agilent Technologies analysis probe provides a debug port connector. You can also design a debug port connector on the target system (see “Designing a MPC8240 or MPC8260 Target System” on page 63). • An Agilent Technologies 16600A or 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 Agilent Technologies 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 Agilent Technologies representative. If you have an analysis probe, the instructions for connecting the probe to your target microprocessor are in the analysis probe documentation.
MPC8240 and MPC8260 Emulation
2 Connecting the Emulation Probe to a LAN 27
Chapter 2: 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 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. Use either the 10BASE2 or the 10BASE-T connector. Do not use both.
Chapter 2: 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. The default gateway address is 0.0.0.
Chapter 2: 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 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. If you will use a baud rate of 9600 baud, set the switches like this: 2 Connect an ASCII terminal (or terminal emulator) to the emulation probe’s RS-232 port with a 9-pin RS-232 cable.
Chapter 2: 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 and connect the emulation probe to your network. 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 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 139, 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. 1 Make sure that BOOTP is enabled on your host computer.
Chapter 2: 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 Agilent 64700 # emulators and Emulation Probes. # Use a different gateway addresses if necessary. 64700.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. probe.example.com:\ :tc=64700.global:\ :ha=080009090B0E:\ :ip=192.6.29.
Chapter 2: 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. Do this so that the emulation probe does not request its IP address each time power is cycled.
Chapter 2: 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. This should allow you to use cable lengths of up to about 200 meters.
Chapter 2: Connecting the Emulation Probe to a LAN NOTE: Setting switch S8 to OFF when Link Beat integrity checking is required by your network will cause the remote MAU to disable communications. 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.
Chapter 2: Connecting the Emulation Probe to a LAN Example $ telnet 192.35.12.6 R>lan lan is enabled lan -i 192.35.12.6 lan -g 0.0.0.
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 To set the serial configuration switches 1 Set switch S1 to ON (RS-232). 2 Set switches S2-S4 to ON. 3 Set switch S5 to ON (HW HANDSHAKE ON) if your serial 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).
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. Use 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 Agilent Technologies emulation probe) 3 RD Receive Data (data going to Agilent Technologies emulation probe) 4 DTR Data Terminal Ready (not used) 5 GND Signal Ground 6 DSR Data Set Ready (Output from Agilent Technologies emulation probe) 7 RTS Request to Send (Input to Agile
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.
Chapter 2: Connecting the Emulation Probe to a LAN Setting Up a Serial Connection 46 MPC8240 and MPC8260 Emulation
3 Installing the Emulation Module 45
Chapter 3: Installing the Emulation Module This chapter shows you how to install an emulation module in your Agilent Technologies 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 To install the emulation module in a 16700Aseries logic analysis system or a 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 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 To install the emulation module in a 16600Aseries 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 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 a 16600A/700A 51
Chapter 4: Installing Software on a 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 analysis system. Later, you will need to load some of the files into the appropriate hardware module.
Chapter 4: Installing Software on a 16600A/700A To install the software from CD-ROM (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 Agilent Technologies 16600A/700A logic analysis system 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 a 16600A/700A 9 Click Close. The configuration files are stored in /logic/configs/hp/ processor. The inverse assemblers are stored in /logic/ia. 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 (16600A/700A) In the System Administration Tools window, click List... .
Chapter 4: Installing Software on a 16600A/700A MPC8240 and MPC8260 Emulation 55
56 MPC8240 and MPC8260 Emulation
5 Connecting and Configuring the Emulator 57
Chapter 5: 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 63) 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 Agilent Technologies 16600A/ 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 (emulation module) 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 MPC8240 or MPC8260 Target System Designing a MPC8240 or MPC8260 Target System Debug Port Connection A 2x8 0.1 inch center BERG-style connector is required to connect the emulation probe to the MPC8260 PowerQUICC II JTAG interface or the MPC8240 JTAG interface. The header should be placed as close to the microprocessor as possible to ensure signal integrity.
Chapter 5: Connecting and Configuring the Emulator Designing a MPC8240 or MPC8260 Target System Reset Signals for the MPC8240 The SRESET, HRESET signals from the JTAG connector may be logically ORed with their respective signals on the target system. The MPC8240 has two hard resets, HRST_CPU and HRST_CTRL. HRESET from the debug connector must be routed to the HRST_CPU reset logic and optionally routed to the HRST_CTRL reset logic depending on system requirements.
Chapter 5: Connecting and Configuring the Emulator Designing a MPC8240 or MPC8260 Target System JTAG Connector Pinout and Electrical Information !"#! $ % & ' ( ( ) ( ( (* ) + , To test the emulator If this is the first time that you have used the emulator, you should run the built-
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 Agilent Technologies 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 63. For a list of the parts supplied with the emulator, see page 21.
Chapter 5: Connecting and Configuring the Emulator Connecting the Emulator to the Target System 5 Plug the other end of the 16-pin cable into the target system. Orient the red wire away from pin 1 of the connector and towards the key pin. See the drawing on page 65. CAUTION: Be careful to orient the connector as described above. 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.
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 Agilent Technologies 16600A or 16700A 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 information on each of the configuration options. Help in the Emulation Control Interface menu for help on starting an Emulation Control session. To configure using the built-in commands If you are unable to configure the emulator with the Emulation Control Interface or a debugger interface, you can configure the emulator using the built-in “terminal interface” commands. 1 Connect a telnet session to the emulator over the LAN.
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 Emulation module configured for Built-in command MPC8260 Motorola MPC8260 (ver. 1.0) cf proc=MPC8260 MPC8240 Motorola MPC8240 (ver. 1.0) cf proc=MPC8240 The cfsave -s command will store the processor type configuration in the emulation module’s flash memory. The cfsave -r command will restore this configuration.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator To configure reset vector address The reset vector address configuration item specifies which reset vector the target hardware is using. This value does not set the reset vector. This is done by the hardware.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator To configure the BNC Break In control BNC Break In control configuration Value Emulation module configured for Built-in command rising Causes the 'break in' input to halt the processor on a rising edge (Default). cf breakin=rising falling Breaks the processor on a falling edge.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator To configure the JTAG clock speed (communication speed) The Agilent Technologies emulation module needs to be configured to communicate at a rate which is compatible with your target processor. The JTAG clock speed is independent of processor clock speed. The base JTAG clock frequency is 10MHz. This configuration item selects the division factor for the clock.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator Configuration registers (MPC8260 Only) Configuration registers are emulation probe copies of particular registers and are used as described below. These registers may be read/written by using the 'reg' command. cf_immr The cf_immr register is used by the probe to determine the location of the internal memory map and to read/write the IMMR memory mapped register. Do not modify the IMMR by using a direct memory access.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator Before resetting the target or issuing the probe reset command (rst), the cf_immr register must be set to the reset value as defined by the reset configuration word. If after reset user code changes the IMMR value, then the cf_immr copy must also be updated. The default value for cf_immr is 0x0f000000 when the emulation probe is powered on or when the 'init -c' command is issued.
Chapter 5: Connecting and Configuring the Emulator Configuring the Emulator Software Breakpoints The number of software breakpoints is unlimited but they cannot be used with ROM or FLASH memory. Software breakpoints cannot be used to debug exceptions. Do not modify the IABR register while software breakpoints are enabled. It is recommended that only -t (temporary) or -p (permanent) breakpoints be used by a debugger.
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 10, “Troubleshooting the Emulator,” beginning on page 120, for information on testing the emulator hardware. To test memory accesses 1 Start the Emulation Control Interface and configure the emulator and target memory system.
Chapter 5: Connecting and Configuring the Emulator Testing the emulator and target system To test with a running program To more fully test your target, you can load simple programs and execute them. 1 Compile or assemble a small program and store it in a Motorola SRecord or Intel Hex file. 2 Use the Load Executable window to download the program into RAM or flash memory. 3 Use the Breakpoints window to set breakpoints. Use the Registers window to initialize register values.
6 Using the Emulator with a Debugger 83
Chapter 6: Using the Emulator with a Debugger Several prominent companies design and sell state-of-the-art source debuggers which work with the Agilent Technologies 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 6: Using the Emulator with a Debugger Here is an example of what the display on your PC or workstation might look like: MPC8240 and MPC8260 Emulation 85
Chapter 6: 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 6: 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 66).
Chapter 6: 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 6: 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 6: 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 6: 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 6: 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.
7 Using the Analysis Probe and Emulation Module Together 93
Chapter 7: 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 Agilent Technologies 16600A or 16700A logic analysis system to gain insight into your target system.
Chapter 7: Using the Analysis Probe and Emulation Module Together Which source-level listing should I use? Different tools display source code for different uses: • The Source Viewer window allows you to follow how the processor executed code as the analyzer captured a trace. Use the Source Viewer to set analyzer triggers. The Source Viewer window is available only if you have licensed the Agilent Technologies B4620B Source Correlation Tool Set.
Chapter 7: 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 Agilent Technologies B4620B Source Correlation Tool Set, using the Source Viewer window is the easiest method.
Chapter 7: Using the Analysis Probe and Emulation Module Together Triggering the Emulation Module from the Analyzer The emulation module is now set to halt the processor after receiving a 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 7: Using the Analysis Probe and Emulation Module Together Triggering the Emulation Module from the Analyzer The emulation module is now set to stop the processor when the logic analyzer triggers. 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 7: Using the Analysis Probe and Emulation Module Together Triggering the Emulation Module from the Analyzer To stop the analyzer and view a measurement • To view an analysis measurement you may have to click Stop after the trigger occurs. When the target processor stops it may cause the analyzer qualified clock to stop. Therefore most intermodule measurements will have to be stopped to see the measurement.
Chapter 7: 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 7: 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 100.
Chapter 7: 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 7: 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 7: 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 7: 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 7: 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.
8 Updating Firmware 107
Chapter 8: 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 8: 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 8: 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 8: Updating Firmware Emulation Module Firmware 4 In the system window, click the emulation module and select 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 52 for instructions on how to install the processor support package from the CDROM.
Chapter 8: Updating Firmware Emulation Module Firmware To update firmware for an emulation module using the Setup Assistant The Setup Assistant is an online tool for connecting and configuring your logic analysis system for microprocessor and bus analysis. The Setup Assistant is available on the Agilent Technologies 16600A and 16700A-series logic analysis systems.
9 Specifications and Characteristics 113
Chapter 9: Specifications and Characteristics Emulation module and emulation probe—operating characteristics Emulation module and emulation probe— operating characteristics The following operating characteristics are not specifications, but are typical operating characteristics for the Agilent Technologies 16610A emulation module, emulation probe, and MPC8240 or MPC8260 target interface module.
Chapter 9: Specifications and Characteristics Emulation module and emulation probe—operating 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 70). BNC, labeled BREAK IN Input. Edge-triggered TTL level input (active high), 20 pf, with 2K ohms to ground in parallel.
Chapter 9: Specifications and Characteristics Emulation Probe and Emulation Module Electrical Characteristics Emulation Probe and Emulation Module Electrical Characteristics - )( + # # - - ' - % # .
Chapter 9: 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.
118 MPC8240 and MPC8260 Emulation
10 Troubleshooting the Emulator 119
Chapter 10: Troubleshooting the Emulator If you have problems with the emulator, your first task is to determine the source of the problem.
Chapter 10: 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. If this does not work, continue with the steps for the next symptom...
Chapter 10: 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 10: 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 10: 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 10: 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 10: 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 10: 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 reg mtest r rep rst s 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 cycling power (it will break LAN
Chapter 10: Troubleshooting the Emulator Emulator Built-in Commands The prompt indicates the status of the emulator: Emulator prompts U M p R r c ? Running user program Running in background monitor No target power Emulation reset Target reset Checkstop Unknown state Examples To set register r0, then view r0 to verify that is was set, enter: U>rst M>b M>reg r0=1234abcd M>reg r0 reg r0=1234abcdf To break execution then step a single instruction, enter: U>b M>s PC=fff00108 M> To determine what firmware
Chapter 10: Troubleshooting the Emulator Problems with the Target System Problems with the Target System What to check first Verify that the cf options are correct for your target. 1 Try some basic built-in commands using the Command Line window or a telnet connection: U>rst U> This should reset the target and display a "U>" prompt if 'cf reset=run'. U>rst M> This should reset the target and display an "M>" prompt if 'cf reset=stop'.
Chapter 10: Troubleshooting the Emulator Problems with the Target System If any of these commands don’t work, there may be a problem with the design of your target system, a problem with the revision of the processor you are using, or a problem with the configuration of the emulation module. 2 Check that the emulation module firmware matches your processor. To do this, enter: M>ver To check the debug port connector signals • Check for the following logic levels on the target debug port.
Chapter 10: Troubleshooting the Emulator Problems with the Target System Levels with the emulation module connected: !"# 55 ! #7 ?! ? 4 6 55 ! #7 ?! ? 4 6 = ! #7 ?" 7? 4 + >( $ ')@ 4 4A B !;6 7C & ' = - ! #7 ?! ? 4 ( ( )#5 - ! #7 ?" 7? 4 6 ) ( ( )#5 - ! #7 ?" 7? 4 6 )( + )#5 , = MPC8240 and MPC8260 Emulation 6 6 131
Chapter 10: Troubleshooting the Emulator Problems with the Target System To interpret the initial prompt The initial prompt can be used to diagnose several common problems. To get the most information from the prompt, follow this procedure: 1 Connect the emulation module to your target system. 2 Set the default configuration settings. Enter: M>init -c If you are using the MPC8240, also enter: M>cf proc=MPC8240 You can enter this command at any prompt.
Chapter 10: Troubleshooting the Emulator Problems with the Target System Now you can do some more tests: 3 Enter the reset command: U>rst U> If the prompt after rst is "?>" A bad status code (0xXX) was received from the processor. Valid status is 0x01, any other status indicates bad scan of the instriction register or failure of the reset signals. Verify TCK, TDO, TDI, TMS, and TRST are all changing state on an HRESET.
Chapter 10: Troubleshooting the Emulator Problems with the Target System Continue with more tests: 4 Enter the break command: U>b M> If the prompt after b is "M>" with error messages If you see: "!ERROR 145! Unable to soft stop - freezing the processor clocks" the processor is hard stopped. Check the mask revision, processor type, and firmware version. If all of these look good, the target may not be terminating cycles (pending external bus cycles).
Chapter 10: Troubleshooting the Emulator Problems with the Target System the chip is probably correct. Now enter: M>m -d4 -a4 0=11111111,22222222,33333333,44444444 M>m -d4 -a4 0..
Chapter 10: Troubleshooting the Emulator Problems with the Target System 6 At the "M>" prompt , check the processor’s revision level: For example: M> reg pvr reg pvr=xxxxxxxx M> At the time of this release both 8240 and 8260 the pvr part number 00910101 or 00810101. If you see memory-related problems 1 Enter: M>m -d4 -a4 0=11111111,22222222,33333333,44444444 M>m -d4 -a4 0..
Chapter 10: Troubleshooting the Emulator Problems with the Target System 2 Hand load a little program: start: addi r1,1 nop nop bra start - 0x38210001 0x60000000 0x60000000 0x4bfffff4 The opcode 0x4bfffff4 is a branch to a relative offset, so this program can be placed at any start address. M>reg r1=0 M>m -a2 -d2 10000=3821,1,6000,0,6000,0,4bff,fff4 M>r 10000 U>reg r1 reg r1=00034567 # or some number U>reg r1 reg r1=00102333 # or some number U> This program will loop forever, incrementing r1.
Chapter 10: Troubleshooting the Emulator Problems with the Target System was not set in the boot code. This can be fixed by ’ORing’ in 0x00000002 into the SRR1 register and resuming the run. If you see the “!ERROR 145!” error message If the following error arises: !ERROR clocks 145! Unable to soft stop - freezing the processor The processor is in an unstable state and should be reset via a hard reset or a power-on reset. The 'rst' command may not be able to bring the processor into a known state.
Chapter 10: 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 10: Troubleshooting the Emulator Problems with the LAN Interface (Emulation Module Only) If it takes a long time to connect to the network ❏ Check the subnet masks on the other LAN devices connected to your network. All of the devices should be configured to use the same subnet mask. Subnet mask error messages do not indicate a major problem. You can continue using the emulation module. The subnet mask is set in the logic analysis system’s System Admin window.
Chapter 10: 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 10: 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 (Agilent 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 10: 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: E3499B 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) Agilent T
Chapter 10: 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 10: Troubleshooting the Emulator Problems with the LAN Interface (Emulation Probe Only) ❏ Use a serial connection to run the LAN performance verification tests (see page 141). If you have LAN connection problems ❏ If the emulation probe does not accept commands from the Agilent Technologies 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 10: 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 10: 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 10: 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 10: 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 10: 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 10: 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 Agilent Technologies 16700A/16700A-series logic analysis system. The LAN tests for an emulation probe can only be executed through the RS-232 port.
Chapter 10: 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 (Agilent part number E349666502) directly into the emulator.
Chapter 10: 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 10: 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 10: 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 Agilent Technologies.
Chapter 10: 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 Agilent Technologies for replacement.
Chapter 10: Troubleshooting the Emulator Returning Parts to Agilent Technologies for Service Returning Parts to Agilent Technologies for Service The repair strategy for this emulation solution is board replacement. Exchange assemblies are available when a repairable assembly is returned to Agilent Technologies. 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 10: Troubleshooting the Emulator Returning Parts to Agilent Technologies for Service measurement system to the service center, including the logic analysis system, target interface module, and cables. In some parts of the world, on-site repair service is available. Ask an Agilent Technologies sales or service representative for details. 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.
Chapter 10: Troubleshooting the Emulator Returning Parts to Agilent Technologies 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.
Chapter 10: Troubleshooting the Emulator Returning Parts to Agilent Technologies for Service 160 MPC8240 and MPC8260 Emulation
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 Agilent Technologies 16500, 1660series, or 16600A/700A-series mainframe.
Glossary components which provide a specific set of capabilities. It is designed to perform logic analysis. A standalone logic analyzer differs from a 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. different order for delivery at the other side of the board.
164 MPC8240 and MPC8260 Emulation
Index A active signals 63 address, IP IP address 30 altitude specifications 117 analysis probe connecting to 68 definition 161 processors supported 4 product numbers 4 assistant See setup assistant !ASYNC_STAT 173! MSR.
Index ordering information 4 overview 4 !ERROR 145! Unable to soft stop freezing the processor clocks 134 ERROR 145 138 ERROR 905 132 error messages 138 ethernet address 33 examples, measurement 95 extender 161 F files loading vs.
Index POWER line 65, 130, 131 Power Sense 116 power supply 18 power-on self test 149 preprocessor See analysis probe problems, LAN 145 problems, RS-232 148 processor clock speed 77 processor mask revision 133 processor revision 130 processor support package 53 processor type 74, 133, 134 processors supported 4 program counter 129 prompt, initial 132 prompts 128 list of 128 prototype analyzer definition 162 PV See performance verification R real-time runs 75 references 25 repair emulation module 157 require
Index definition 163 trigger emulation module 96 in/out specifications 115 on break 101 trigger out configuration 76 troubleshooting 121 TRST signal 63, 65, 116, 130, 131, 133 TRST_L signal 132 U until processor halts 100 Updating Firmware 108 USER LED 152 USER light 122, 124 V versions emulation module firmware 110 emulation probe firmware 109 voltage emulation module 116 W watchdog freeze 137 web sites logic analyzers 25 See Also under debugger names wizard See setup assistant workstation connecting to 2
DECLARATION OF CONFORMITY according to ISO/IEC Guide 22 and EN 45014 Manufacturer’s Name: Agilent Technologies Manufacturer’s Address: Digital Design Product Generation Unit 1900 Garden of the Gods Road Colorado Springs, CO 80907 USA declares, that the product Product Name: Emulation Probe Model Number(s): E3453A 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 Agilent Technologies 1994-2000 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. Agilent Technologies,3000 Hanover Street, Palo Alto, CA 94304 U.S.A.
Product Warranty This Agilent Technologies product has a warranty against defects in material and workmanship for a period of one year from date of shipment. During the warranty period, Agilent Technologies 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 Agilent Technologies.
