
UDI Services
3-48
Universal Debugger Interface Specification
taken.
UDIWaiting
CPU is in wait mode.
UDIWarned
CPU was warned.
The two
StopReasons
,
UDIRunning
and
UDIHalted
, are special. They can
return a fine state of 0, or if the TIP wants to return additional information,
they can use a fine state from the following list of predefined fine states or a
TIP–defined negative fine state. Note that in all cases, gross state
UDIHalted
means that the target will remain halted until some action by the DFE (for
example,
UDIExecute
) is taken to restart it.
Fine State
2
Meaning
UDIResetAsserted
Reset is currently asserted.
UDITransientReset
Target went through a reset but is not currently
reset.
UDINoClock
Indicates the target has no clock.
Any negative value
Fine state is TIP defined. DFE can call
UDIGetErrorMessage, passing the fine state as an
argument to get a textual description for the fine
state.
The following are some combinations of gross state with these fine states and
how they would be interpreted:
UDIRunning
+
UDITransientReset
Target is executing but went through a transient
Reset since the last
UDIWait
call.
UDIRunning
+
UDIResetAsserted
Target is currently Reset but may resume execution
at any time.
UDIHalted
+
UDIResetAsserted
Target is currenly Reset and will not resume
execution until some action is taken by the DFE to
restart it. (If reset deasserts, will enter UDIHalted +
UDITransientReset state).
UDIHalted
+
UDITransientReset
Target is not currently reset but is halted (until
further DFE action is taken) because reset had been
asserted earlier and the target is configured such that
resets cause it to enter a halted state.
2
Used with
UDIHalted
or
UDIRunning