MOOG D136-001-007伺服控制器，D136-001-007使用尺寸
显示和修改内存的命令❏ 断点和跟踪功能❏ 一种功能强大的汇编/反汇编程序，用于修补程序❏ “通电自检”功能，用于验证系统此外，TRAP#15系统调用生成各种172Bug例程处理用户可用的输入/输出、数据转换和字符串函数程序。172Bug由三部分组成：❏ 描述了一种命令驱动的用户交互软件调试器在本章中。这里称之为“调试器”或“172Bug”。
MOOG D136-001-007伺服控制器❏ MVME172LX的命令驱动诊断包硬件，此处称为“诊断”。❏ 用户界面或调试/诊断监视器，接受来自系统控制台终端的命令。使用172Bug时，您可以在调试器目录或诊断目录。❏ 如果您在调试器目录中，调试器将提示172 Bug>显示，并且您可以在处置❏ 如果您在诊断目录中，诊断提示172-显示Diag>，所有诊断命令位于以及所有调试器命令。由于172Bug是命令驱动的，因此它在对在键盘上输入的用户命令的响应。当您输入命令，172Bug执行该命令并再次出现提示。但是，如果您输入的命令导致执行用户目标代码（例如，GO），则控制可能返回也可能不返回，取决于用户程序的结果。如果您使用过摩托罗拉的一个或多个其他调试软件包，您可以将发现CISC 172Bug非常相似。也作出了一些努力使交互命令更加一致。例如命令和参数之间的分隔符可以是逗号或空格可互换。172Bug实现MVME172Bug主要用“C”编程语言编写，提供可移植性和可维护性的好处。必要时，汇编程序以单独编译的模块的形式使用仅包含汇编代码。不使用混合语言模块。实际上，172Bug包含在安装的单个27C040 DIP EPROM中在插座XU2中，提供512KB（128K长字）的存储空间。可选地，172Bug可以在单个闪存中加载和执行内存芯片。可执行代码在每次通电或重置固件条目和结果（包括预计算的内存设备中包含的校验和）根据应为校验和。
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
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:
❏ 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 MVME172LX
hardware, referred to here as “the diagnostics”.
❏ A user interface or debug/diagnostics monitor that accepts
commands from the system console terminal.
When using 172Bug, you operate out of either the debugger directory or
the diagnostic directory.
❏ If you are in the debugger directory, the debugger prompt 172-Bug>
is displayed and you have all of the debugger commands at your
disposal.
❏ If you are in the diagnostic directory, the diagnostic prompt 172-
Diag> is displayed and you have all of the diagnostic commands at
your disposal as well as all of the debugger commands.
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. If you have used one or more of Motorola’s other debugging packages, you
will find the CISC 172Bug very similar. Some effort has also been made
to make the interactive commands more consistent. For example,
delimiters between commands and arguments may be commas or spaces
interchangeably.
172Bug Implementation
MVME172Bug is written largely in the "C" programming language,
providing benefits of portability and maintainability. Where necessary,
assembler has been used in the form of separately compiled modules
containing only assembler code. No mixed language modules are used.
Physically, 172Bug is contained in a single 27C040 DIP EPROM installed
in socket XU2, providing 512KB (128K longwords) of storage.
Optionally, the 172Bug can be loaded and executed in a single Flash
memory chip. The executable code is checksummed at every power-on or
reset firmware entry, and the result (which includes a pre-calculated
checksum contained in the memory devices) is verified against the
expected checksum.
