
UDI session_id
When using the UDB source level debugger to control a logic analyzer, a
mktarget
command must be placed in the udb.rc start–up command file. As
explained in section 7.7, a GIO process, controlled by UDB, uses the assigned
mktarget
parameters to connect to a 29K target (in this case via MonTIP). An
example udb.rc entry is shown below.
executable
UDI session_id
October 13 1995, Draft 1
401
Chapter 7 Software Debugging
the X server. To obtain the name of your terminal’s display, print the environment
variable DISPLAY as shown below.
echo $DISPLAY
ginger:0.0
#Unix shell command
#response
It is important for the successful operation of MonTIP that the environment
variable DISPLAY be correctly initialized. Note that some HP workstations set the
variable to the value “l(fā)ocal:0.0”, this does not create any difficulty for MonTIP.
UDI Installation
The udi_soc file (for Unix based systems) must contain an entry for
establishing, via UDI, the MonTIP to analyzer connection. The MonTIP option “–la
name” is provided for this purpose. The example below shows a udi_soc entry for a
session identified by the name “trace”. Note that the udi_soc file format was
described in detail in section 7.5.6. If a logic analyzer were being used alone, the
example udi_soc entry would be adequate. However, a NetROM is typically
combined with an analyzer. In this case the two entries shown below would be
combined to produce a single entry with a unique session identifier.
# udi_soc file entry to support logic analyzer1
trace
AF_UNIX soc
montip –la hpla
rom
AF_UNIX soc
montip –t netrom –netaddr 163.181.22.60 –netport 1234
# udb.rc, UDB startup command file
#driver args (GIO ID, GIO executable, exec. flags, udi_soc session ID)
#mktarget
name id
type driver
(args....)
mktarget
LA
1
29040 dr_gio
0 ios_udi –be trace
Note that normally the GIO and UDB processes determine the endian of the 29K
target via examining the processor’s CFG special register. When an analyzer is used
alone, there is no connection to the 29K processor and the CFG register can not be
accessed. This necessitates that the
mktarget
command specify the target endian.
The “–be” switch is used in the example to select big–endian operation. The “–le”
switch is available for selecting little–endian. The following section 7.9.3 describes
how user defined buttons can be used to issue
mktarget
commands.
Accessing the Analyzer File System
It is very convenient to be able to
drive
the logic analyzer remotely from, say, the
X–terminal on your desk. Note that a colour monitor is required to achieve full