Table of Contents
Advertisement
172Bug Firmware
172Bug includes:
3
In addition, the TRAP #15 system calls make various 172Bug routines that
handle I/O, data conversion, and string functions available to user
programs.
172Bug consists of three parts:
When using 172Bug, you operate out of either the debugger directory or
the diagnostic directory.
Because 172Bug is command-driven, it performs its various operations in
response to user commands entered at the keyboard. When you enter a
command, 172Bug executes the command and the prompt reappears.
However, if you enter a command that causes execution of user target code
(for example, GO), then control may or may not return to 172Bug,
depending on the outcome of the user program.
3-2
Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com
Commands for display and modification of memory
Breakpoint and tracing capabilities
A powerful assembler/disassembler useful for patching programs
A "self-test at power-up" feature which verifies the integrity of the
system
A command-driven user-interactive software debugger, described
in this chapter. It is referred to here as "the debugger" or "172Bug".
A command-driven diagnostic package for the MVME172P4
hardware, referred to here as "the diagnostics".
A user interface or debug/diagnostics monitor that accepts
commands from the system console terminal.
If you are in the debugger directory, the debugger prompt
is displayed and you have all of the debugger commands at your
disposal.
If you are in the diagnostic directory, the diagnostic prompt
is displayed and you have all of the diagnostic commands at
Diag>
your disposal as well as all of the debugger commands.
Computer Group Literature Center Web Site
172-Bug>
172-
Advertisement
Table of Contents
