
UDI Services Overview
Universal Debugger Interface Specification
2-9
mode. If the DFE does not wish to leave transparent
mode, it must acquire input from the user and call
UDIPutTrans
, as described above.
A special usage of
UDIPutTrans
(called with a
Count=0) tells the TIP that the DFE wants to get the
prompt from the TIP on the next
UDIGetTrans
call. If
the TIP has a prompt, it returns
UDIErrorTransPrompt
to
UDIPutTrans
and then
returns the actual prompt on the next
UDIGetTrans
call
(again with the return
UDIErrorTransPrompt
). If the
TIP has no prompt, it returns
UDIErrorTransDone
to
the
UDIPutTrans
(Count=0) call. If the TIP is not in a
state where a prompt is possible, i.e., if the TIP is not
between commands, etc., then it returns
UDIErrorCantAccept
to the
UDIPutTrans
(Count=0)
call.
UDITransMode
If
UDIGetTrans
requests a call to
UDITransMode
, the
DFE must call
UDITransMode
, the TIP will return the
new mode that it wishes the DFE to use and then the
DFE must resume calling
UDIGetTrans
.
Using UDIDFE calls in Transparent Mode
A TIP is allowed to use
UDIDFEGetInput
and
UDIDFEPutOutput
with
IOType
UDIIOTypeTip
xxx
when servicing transparent mode calls with the
exception that the prompt, if any, can only be returned by
UDIGetTrans
.
Other
UDIDFE
xxx
calls may be used by the TIP without restriction during
transparent mode.
Because the TIP may mix
UDIDFEGetInput
and
UDIDFEPutOutput
with
IOType
UDIIOTypeTip
xxx
with transparent mode handling, the DFE is
required to treat transparent mode I/O and
UDIIOTypeTip
xxx
I/O in a similar
manner.
Symbolic Mapping
The functions in this group, new with version 1.3 of UDI, are implemented by
the DFE and called by the TIP. Generally, these functions would be used by a
TIP that is operating in transparent mode.