Table of Contents
Advertisement
Chapter 4: Connecting the Emulator to a Target System
If the target system appears to work correctly, go to the paragraph titled, "Installing
the Monitor", later in this chapter. Otherwise, verify operation of the target system
as described next.
To verify operation of the target system
Get the prompt by pressing <RETURN>, or use the command es to get more
information about the emulator status. If the system is working the prompt will
normally be "U>", but there are a few situations where the system will be working
properly and the prompt will be something different. If the bus is taken away from
the MC6833x often or for long periods of time, the emulator can display the "g>"
prompt or alternate between "g>" and "U>". If the MC6833x is running code in its
internal memory for long periods of time, the emulator may display the "b>"
prompt. The emulator may alternate between any of these prompts during normal
operation.
All other prompts usually indicate a problem. Even the "g>" or "b>" prompts can
indicate a problem. To understand problems indicated by the prompts, you need to
know whether bus cycles were executed, how many bus cycles were executed,
what type of bus cycles were executed, and whether the target system is still
executing bus cycles. You can tell the difference between these conditions by
checking the trace status to see if any bus cycles were captured. The analyzer may
have states in its internal pipeline that will not be reported until the trace is halted.
b>th;ts
Emulation trace halted
--- Emulation Trace Status ---
User trace halted
Arm ignored
Trigger not in memory
Arm to trigger ?
States 0 (0) ?..?
Sequence term 2
Occurrence left 1
b>
If the trace status indicates that the trace was halted, look at the number of states
collected to decide how many bus cycles were executed. If the status indicates that
the user trace was completed, a large number of states were executed. If this is the
case, it may help to take another trace to see if bus cycles are still being executed.
Again, view the trace status to determine if bus cycles are executing.
Plugging The Emulator Into A Target System
<- trace status
<- number of states captured
65
Advertisement
Table of Contents
