
October 13 1995, Draft 1
366
Addendum to –– Evaluating and Programming the 29K RISC Family
nected to a UNIX machine. The MiniMON29K messages, transferred to the DOS
host via plug–in card shared memory, are sent to the TIP host via the rs232 connec-
tion. The
montip
program supports several command–line options, as shown below.
Not all are applicable to both DOS and UNIX host machines.
montip –t target [–r OS–boot] [–m msg_log] [–com serial_port]
[–re msg_retries] [–mbuf msg_bufsize] [–bl msg_loopcount]
[–to timeout] [–seg PC_seg_addr] [–port PC_port_base]
[–baud baudrate] [–le] [–R|P]
A explanation of the command line options can be obtained by just entering
montip
on your TIP host machine. When the
montip
process is started it
advertises
its readiness to service UDI requests. A DFE process will typically connect to the
TIP process and a debug session will commence. Alternatively, there is no need to
first start the TIP process. When a DFE process is started, such as
mondfe
, it will look
for the advertised TIP; if the TIP process is not found the DFE will automatically start
the TIP. This is how
montip
is normally started. The start–up
montip
parameters are
taken from the “UDI Configuration File”. The format of this file is explained in the
following section discussing
mondfe
.
7.5.6 The MiniMON29K User–Interface, MonDFE
The MiniMON29K DFE process,
mondfe
, is a primitive 29K debugger. It pro-
vides a basic user–interface for the MiniMON29K product. It is fully UDI compliant
(at least UDI version 1.2 ); and it can be used with any of the available TIP processes
such as
isstip
,
mtip
,
montip
, etc. It is very easy to operate but has less debugging
capability compared to other DFEs, such as
gdb
,
xray29u
or
UDB
(see section 7.7)
etc.; for example it does not support symbolic debugging.
It is very useful for simply loading application programs and starting their
execution where no debugging support is required. Its simple command set also
makes it easy to learn; when running, simply type the
h
command to obtain a com-
plete list of available commands. The
h
command can also be used to explain each
command’s operation; for example, “
h s
” will explain the operation of the
set
com-
mand. Several command–line options are supported.
mondfe
[–D] –TIP tip_id [–q] [–e echo_file] [–c command_file]
[–ms mem_stack_size] [–rs reg_stack_size] [–le]
[–log logfile] [pgm_name [arg_list]]
A list of command line options can be had by entering
mondfe
on your DFE host
processor. The process is typically started by entering a command such as “modfe
–D –TIP serial”. The “–D” option causes an interactive debug session to commence.
The UDI conforming TIP process communicating with
mondfe
is identified by the
“–TIP serial” command line option.
DFEs and TIPs establish communication via a UDI Configuration File. On
UNIX machines this file is called
udi_soc
; on DOS machines it is called
udiconfs.txt
.