Specifications

4
Debugger Interface
Industry-leading debuggers can
control the emulation probe and
module. You can set breakpoints,
single-step through code, examine
variables, and modify source code
variables from the high-level source
code debugger interface.
Debugger interfaces must be
ordered directly from the debugger
vendor.
Debugger Connections
Green Hills Software, Inc.
30 West Sola Street
Santa Barbara, CA 93101 USA
Phone: [phone]
http://www.ghs.com
Microtec, A Mentor Graphics
Company
880 Ridder Park Drive
San Jose, CA 95131 USA
Phone: [phone]
Phone: [phone]
http://www.mentor.com/microtec
Diab-SDS
323 Vintage Park Drive
Foster City, CA 94404 USA
Phone: [phone]
http://www.diabsds.com
WindRiver Systems
500 Wind River Way
Alameda, CA 94501 USA
Phone: [phone]-WIND
http://www.wrs.com
Please check with your local
Agilent Test and Measurement
sales office or visit our web site at
http://www.agilent.com/find/las-data
for the current list of debugger
connections.
Emulation Control
Interface
The emulation module integrated
into the logic analysis system can
be controlled directly by the emula-
tion control interface. You can
easily display and modify contents
of microprocessor registers, system
memory, and I/O. You can also
view memory code segments
disassembled into familiar
Motorola/IBM PowerPC 603
assembly instructions.
From the run control window you
can instruct the microprocessor to
run, break, reset, or single-step. You
also can choose whether the mem-
ory, I/O, and register displays are
updated for breaks and single steps.
Writing command files that set up
registers, memory, and I/O in your
system is easy with the command
language. Once the command file is
written, save it on the logic analyzer
hard disk. When you want to
initialize your hardware system to a
particular state, simply recall and
execute the command file. Unlike
a debugger interface, the emulation
control interface does not refer-
ence back to the high-level source
code.
Figure 3: Emulation Control Interface