MOOG D136-001-007伺服控制器，D136-001-007使用尺寸
顯示和修改內存的命令? 斷點(diǎn)和跟蹤功能? 一種功能強大的匯編/反匯編程序，用于修補程序? “通電自檢”功能，用于驗證系統此外，TRAP#15系統調用生成各種172Bug例程處理用戶(hù)可用的輸入/輸出、數據轉換和字符串函數程序。172Bug由三部分組成：? 描述了一種命令驅動(dòng)的用戶(hù)交互軟件調試器在本章中。這里稱(chēng)之為“調試器”或“172Bug”。
MOOG D136-001-007伺服控制器? MVME172LX的命令驅動(dòng)診斷包硬件，此處稱(chēng)為“診斷”。? 用戶(hù)界面或調試/診斷監視器，接受來(lái)自系統控制臺終端的命令。使用172Bug時(shí)，您可以在調試器目錄或診斷目錄。? 如果您在調試器目錄中，調試器將提示172 Bug>顯示，并且您可以在處置? 如果您在診斷目錄中，診斷提示172-顯示Diag>，所有診斷命令位于以及所有調試器命令。由于172Bug是命令驅動(dòng)的，因此它在對在鍵盤(pán)上輸入的用戶(hù)命令的響應。當您輸入命令，172Bug執行該命令并再次出現提示。但是，如果您輸入的命令導致執行用戶(hù)目標代碼（例如，GO），則控制可能返回也可能不返回，取決于用戶(hù)程序的結果。如果您使用過(guò)摩托羅拉的一個(gè)或多個(gè)其他調試軟件包，您可以將發(fā)現CISC 172Bug非常相似。也作出了一些努力使交互命令更加一致。例如命令和參數之間的分隔符可以是逗號或空格可互換。172Bug實(shí)現MVME172Bug主要用“C”編程語(yǔ)言編寫(xiě)，提供可移植性和可維護性的好處。必要時(shí)，匯編程序以單獨編譯的模塊的形式使用僅包含匯編代碼。不使用混合語(yǔ)言模塊。實(shí)際上，172Bug包含在安裝的單個(gè)27C040 DIP EPROM中在插座XU2中，提供512KB（128K長(cháng)字）的存儲空間?？蛇x地，172Bug可以在單個(gè)閃存中加載和執行內存芯片?？蓤绦写a在每次通電或重置固件條目和結果（包括預計算的內存設備中包含的校驗和）根據應為校驗和。
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.
