
October 13 1995, Draft 1
399
Chapter 7 Software Debugging
shown below. The loadfile and loadpath variables are used to specify the default
image file to load into emulation memory. In the example below, the default image
file is /tftpboot/netrom/target/sa29040.hex. The key parameters in the configuration
file should be arranged to describe the type of memory being emulated. The example
below shows four 27c020 memory devices combined to produce a 32–bit memory
system. This will require four NetROM cables. It is possible (and common) to
emulate only an 8–bit wide memory system.
;part of the startup2.bat NetROM configuration file
host
163.181.22.9
;server IP address
loadfile sa29040.hex
;29K program (image file)
loadpath /netrom/target ;path to 29k program
romtype
27c020
;ROM type
romcount 4
;number of ROMs
podorder 0:1:2:3
;pod order
wordsize 32
;memory width
setenv
setenv
setenv
setenv
setenv
setenv
setenv
A NetROM can support TELNET and direct TCP connections simultaneously.
The MonTIP program forms a direct connection to the NetROM via the parameter
information located in the udi_soc file (see section 7.5.6). An example udi_soc entry
is shown below.
# udi_soc file entry to support NetROM
netrom2 AF_UNIX soc montip –t netrom –netaddr 163.181.22.60 –netport 1234
It is possible to have a TELNET session active with a NetROM while also
running MonTIP. Of course, the user controls the NetROM via a front–end debug
tool such as UDB which directs the operation of MonTIP via the UDI interface. From
a window running the TELNET command “telnet netrom2” (for example), the
“newimage” NetROM command can be used to download a file (usually the default)
into emulation memory. The sa29040.hex image file contains OS–boot, the
DebugCore, and support driver code for an SA29040 evaluation board. Once
installed it enables DebugCore messages to be exchanged between the 29K target
and the host computer running MonTIP.
A
software reset
can be performed by issuing a reset command from UDB.
Normally the DebugCore is successfully running and will perform the reset. Under
extreme conditions the DebugCore may no longer be in control of the 29K processor.
In this case a
hardware reset
can be performed. This requires that the 29K reset pin be
asserted. From the TELNET session this is accomplished via the “tgtreset”
command. The technique requires that a reset wire be used to connect the reset output
pin on the back of the NetROM (marked R) to a connection post on the target system.
The connection post must be wired to the processor reset pin. For this reason, it is best
to incorporate a reset connection post on each 29K target system for use by the
NetROM.
Once a NetROM has been added to a network, a TELNET connection can be
used to confirm its correct installation. After issuing a “newimage” command, and