HP 16600A Series User Manual page 191

Chapter 8: Using the Emulator with a Debugger
Using the Green Hills debugger
To perform common debugger tasks
• To display registers, click the
• To set a breakpoint, click on the source code line where the breakpoint is
to be located.
• To clear a breakpoint, click again on the source line.
• To step through code, click
• To run from the current PC, click
• To toggle the display between source code and source code interlaced with
assembly code, click
• To load program symbols, reset the PC, reset the stack pointer, and run
from the start, click
To send commands to the emulation module
MULTI communicates to the emulation module using the emulation
module's "terminal interface" commands. MULTI automatically
generates and sends the commands required for normal operation. If
you want to communicate directly with the emulation module during a
debug session, you may do so using "terminal interface" commands
through the Target window (which comes up when hpserv is brought
up). You can also enter these commands from the Debugger window's
command pane by preceding the command with the "target" command.
To view commands sent by MULTI to the
emulation module
The communication between MULTI and the emulation module can be
viewed by running hpserv in a logging mode:
remote hpserv -dc -a
The options -dc and -da log both asynchronous and console messages
and the -o <filename> directs these messages to a log file called
<filename>. When using this option, disconnect from hpserv (to flush
out the file) and then you may view <filename> to see what
commands MULTI sent to the emulation module.
190
regs
button in the Display window.
next
.
go
.
assem
.
restart
.
-o <filename> <emulation module>
Solutions for CPU32