
UDI Developer’s Toolkit
A-2
Universal Debugger Interface Specification
6
UDIErrorCantOpenConfigFile
The IPC Layer associates a configuration
name (the first parameter to
UDIConnect
)
with a TIP and its parameters by means of a
configuration file. The IPC Layer was unable
to open the file. This error can occur only
during a
UDIConnect
call.
7
UDIErrorCantStartTIP
The host operating system has failed to start
the TIP at the IPC Layer’s request. The reason
the OS failed is not indicated. Generally, the
OS fails because of resource limitations or a
failure to find the TIP’s executable file
executable. This error can occur only during a
UDIConnect
call.
8
UDIErrorConnectionUnavailable
This error is returned from a TIP that should
connect, but cannot because the requested
target is already in use. It is returned only by
UDIConnect
.
9
UDIErrorTryAnotherTIP
Returned by a TIP in response to a
UDIConnect
request if the TIP cannot service
the UDIConnect, but does not know whether
another running TIP is able to service it. This
error should never be seen by the DFE.
10
UDIErrorExecutableNotTIP
The executable file identified in the
configuration file entry for the requested
configuration is not a TIP. This error can
occur only during a
UDIConnect
call.
11
UDIErrorInvalidTIPOption
The configuration passed to a
UDIConnect
call has options identified in the configuration
file that the associated TIP finds invalid. This
can be simply an unrecognized option or a
combination of options that is inconsistent,
for example requesting a simulation of the
Am29000 and the Am29050 simultaneously.
12
UDIErrorCantDisconnect
Indicates that the TIP is incapable of
disconnecting at this time; for example, the
TIP is temporarily unable to notify other
processes of the disconnection. The error can
occur only during UDIDisconnect calls.
13
UDIErrorUnknownError
Is returned from
UDIGetErrorMsg
if the