User`s guide

CPU32 Emulation 161
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. page 41
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....
page 165
Emulator built-in commands do
not work
1 Check that the emulator has been properly configured
for your target system.
page 75
2 Run the emulator performance verification tests. page 174
3 If the performance verification tests pass, then there is
an electrical problem with the connection to the target
processor OR the target system may not have been
designed according to "Designing a Target System."
page 65
page 171
"Slow or missing clock" message
after a logic analyzer run
Check that the target system is running user code or is in
reset. (This message can appear if the processor is in
background mode.)
"Slow clock" message in the
Emulation Control Interface or
"c>" prompt in the built-in
“terminal interface”
Check that the clock rate is properly configured. page 80
Some commands fail Check the "restrict to real-time runs" configuration page 85
Host computer reports LAN
connection problems
Follow the checklists in this chapter. page 177
page 172