Table of Contents
Advertisement
Chapter 12: Troubleshooting the Emulation Probe
Troubleshooting Guide
Try one of the following until you get a different prompt:
• Cycle power on the emulation probe. (Turn off your target power first.)
• Check that the proper firmware is installed for the target board adapter
or the type of emulation probe shown on the front panel of the
emulation probe.
The proper firmware is installed at the factory but it could accidentally be
changed. A "ver" command will display the firmware which is currently loaded.
Refer to "Updating Firmware" on page 135 if the firmware is incorrect.
• Run the performance verification tests. Refer to "To run the emulation
probe performance verification (PV) tests" on page 177.
Connection to the wrong target or connection to the target with the pins
connected backward could potentially damage the emulation probe. Use the
performance verification tests to validate that the emulation probe itself is
working correctly.
If a telnet connection to the emulation probe
displays the prompt "?>"
The "?>" prompt indicates that the emulation probe is having trouble talking
to the target and it doesn't know what state the target is in.
• Validate that the emulation probe is connect to a powered up target.
Refer to Chapter 6, "Connecting the Emulation Probe to Your Target System,"
beginning on page 65.
• Try initializing the emulation probe with the "init -p" command.
Some emulation probes need to read the Processor Version Register of the
target processor as the emulation probe is initialized.
• Check the emulation probe configuration settings.
Enter the cf command to display the configuration settings. Note that some
emulation probes must set the processor type with the "procs" command.
• Try defaulting the configuration with the "cf default" command.
• Decrease the JTAG communication speed. Some targets need slower
speeds to properly communicate.
150
Agilent Technologies Emulation for the PowerPC 400/600/700
Advertisement
Chapters
Table of Contents
Troubleshooting
