
UDI Developer’s Toolkit
6-2
Universal Debugger Interface Specification
The executables for
isstip
. This is an instruction set simulator–based TIP
normally distributed with AMD’s High C
r
29K
t
product. Since it is self–
contained and does not require actual target hardware, it may be a
convenient test TIP to connect to for DFE developers. Note that the source
for
isstip
is not provided.
The UDI Procedural Interface and the Sample IPC Code
The most important part of the toolkit to UDI developers is the sample IPC
source code. This sample IPC source code maps the UDI procedural interface
(as defined in Chapters 2 and 3) to one of the two defined IPC methods: the
DOS IPC method and the UNIX socket IPC method.
This chapter assumes that the DFE or TIP developer will write code using the
UDI procedural interface and will then link with the sample IPC source code
supplied in the toolkit. The advantages of this approach are:
The procedural interface provides a host–independent interface to UDI.
For testing and debugging purposes, developers can link a DFE and TIP
together into one executable if both use the UDI procedural interface.
Developers can save time by using the existing IPC implementation code
provided in this toolkit since they will not have to be concerned with IPC
details.
We refer to the IPC code in this toolkit as “sample” IPC code because the use
of this code is in no way required to meet UDI interoperability. Developers
could always write their own IPC code and even define a different procedural
interface and it would be interoperable as long as it meets the IPC
specifications described in Chapters 4 and 5 and the semantics described in
Chapters 2 and 3. However, the sample IPC source code should meet the needs
of most developers. The limitations of the sample IPC source code are
described in the next section.
Limitations of the Sample IPC Code
The sample IPC source code has been built and tested in the following host
development environments:
UNIX socket IPC code
SunOS 4.1.x bundled C compiler