
October 13 1995, Draft 1
402
Addendum to –– Evaluating and Programming the 29K RISC Family
control of the analyzer. As described above, remote control of the analyzer is enabled
via the “xwin on” command. When remote control of the analyzer is no longer
required, the command “xwin off”, entered via the telnet connection to the analyzer,
discontinues the remote display. Connection to the analyzer command parser is
broken when the TELNET session is terminated.
Only one user can be in
control
of the analyzer at any time. This means the
analyzer can not be driven from the front panel when a remote window is active.
When MonTIP controls the analyzer, it requests a remote window be presented on the
MonTIP host computer (actually, the DISPLAY variable identifies the screen).
Consequently, it is not possible for another user to establish a second remote window
connection. However, it is possible to simultaneously have an FTP connection active
when remotely controlling the analyzer. The example command sequence below
demonstrates how this is achieved.
1%
ftp hpla
Connected to hpla.
220 HP16500B V01.00 FUSION FTP server (Version 3.3) ready.
Name (hpla:danm):
data
230 User DATA logged in.
ftp>
cd system/disk/hard/amd/danm
200 Remote Directory changed to ”/system/disk/hard/amd/danm”.
ftp>
#Unix shell command
When entering a login name, the identifier “data” was used in the above
example. This enables read access to files located on the analyzer disk system.
Entering the identifier “control” enables read–write access to the file system.
However, logging in as “control” is not permitted if another user is identified as
already controlling the analyzer. Files can be transferred from/to the analyzer using
the FTP commands get/put; remember you may have to first use the binary command
to enable transfer of binary data files.
Triggering the Analyzer for Trace Capture
The HP16500B logic analyzer is equipped with a very sophisticated triggering
capability. Hence, debuggers controlling the logic analyzer tend to rely on the
analyzer’s triggering logic. When using the PI–Am29040 preprocessor, the
POD_040 configuration file prepares the analyzer for triggering on access to the
memory location described by analyzer trigger term A. This may, or may not, be
adequate for your triggering requirements. All changes to trigger logic must be
entered using the logic analyzer front panel display (remotely if desired). If using the
POD_040 file, all that is necessary is to supply the trigger address in the ADDR field
of term A. Of course the address must be entered in hexadecimal format unless a
symbol file has been loaded into the analyzer.
When on–chip caches are used, instruction and data accesses may not always
appear on the processor bus. This complicates the task of triggering the analyzer. It is
also not possibly to simply use the ADDR field of term A when a microcontroller is