
October 13 1995, Draft 1
400
Addendum to –– Evaluating and Programming the 29K RISC Family
possibly a “tgtrest” command, the 29K target system is ready for operation. The
chosen debug tool (UDB, GDB, etc.) can then be invoked and used to examine,
modify and control the target 29K processor in the normal way. Once correct
installation has been confirmed, there is no need to first establish a TELENT
connection before initiating normal program debug. All that is necessary is to start
execution of the chosen debugger.
The NetROM driver (for the 29K side of the virtual UART) that is built into the
image file, typically operates in poll–mode. This refers to the 29K processor on
occasion polling the UART to determine if it is receiving a message from MonTIP.
The image file can be built with an interrupt–mode driver. This enables MonTIP to
interrupt the 29K at any time (if interrupts are enabled) when it wishes to send a
message (such as halt) to the DebugCore. To enable operation of this technique, an
interrupt wire must be used to connect the interrupt output pin on the back of the
NetROM to an interrupt input post on the 29K system. Once again, the post should be
incorporated into any design which wishes to make sue of a NetROM.
7.9.2 HP16500B Logic Analyzer
Network Installation
The use of logic analyzers for tracing program execution was previously
presented in section 7.8. This section briefly deals with the details of configuring the
logic analyzer’s operation for use in the Fusion3D environment. A high speed
connection to the analyzer is achieved via the optional Ethernet link. This requires
that the analyzer be allocated a unique IP address. Using the analyzer’s
communications set–up window, the IP address is recorded for future use. With Unix
networks, the IP address and chosen name are entered into the network database file
/etc/hosts. The following example allocates an IP address for an analyzer called
“hpla”.
#entries in /etc/hosts file allocating IP addresses
163.181.22.117 hpla
163.181.22.121 ginger
# logic analyzer
# X–terminal
The analyzer connection can be confirmed by establishing a telnet connection.
This is accomplished with a “telnet hpla 5025” command. Port number 5025 enables
access to the analyzer command parser. Commands can then be directly issued to the
analyzer. One very useful command: “xwin on, ’163.181.22.121:0.0’”, establishes a
remote window interface to the analyzer. The example command shown causes an
analyzer front panel interface to be presented on the display determined by the IP
address 163.181.22.121. Checking the example /etc/hosts file, it appears to be an
X–terminal known to the network by the name ginger. It is important that the X server
allow the analyzer to make connection to the server. The “xhost + hpla” command
can be used to add hpla to the list of machines that are allowed to make connection to