SA9923a-E自动化卡件,ABB中文PDF说明书在线阅读
处理输入/输出、数据转换和字符串的各种PPCBug例程用户程序可以通过系统调用处理程序使用函数。PPCBug由三部分组成：❏ 命令驱动的用户交互软件调试器。它是以下简称“调试器”或“PPCBug”❏ 一组命令驱动的诊断，以下简称作为“诊断”❏ 接受系统控制台命令的用户界面航空站使用PPCBug时，您将在调试器目录之外进行操作或诊断目录。
SA9923a-E自动化卡件调试器提示（PPC1 Bug或PPC1 Diag）告诉您当前的目录由于PPCBug是命令驱动的，它在对在键盘上输入的用户命令的响应。控制流程PPCBug在PPCBug固件包用户手册中进行了描述，附录D中列出了相关文件。当您输入命令，PPCBug执行该命令，并再次出现提示。
但是，如果您输入的命令导致执行用户目标代码（例如，GO），则控制可能返回或可能不返回到PPCBug，取决于用户程序的结果。PPCBug类似于之前的摩托罗拉固件调试包（例如，MVME147Bug、MVME167Bug、，MVME187Bug），由于微处理器架构的不同而有所不同。这些主要反映在指令助记符、寄存器中显示、汇编器/反汇编器的寻址模式和传递系统调用的参数。内存要求PPCBug最多需要768KB（可能更少）的读/写容量内存（即DRAM）。调试器从顶部分配此空间内存。例如，一个系统包含64MB（04000000美元）的读/写内存将PPCBug内存页放置在位置$03F80000至$03FFFFFF。PPCBug实现PPCBug主要用C编程语言编写，提供了可移植性和可维护性的好处。必要时，组装语言以单独编译程序的形式使用仅包含汇编代码的模块。没有混合语言模块习惯于物理上，PPCBug包含在两个32针插口PLCC闪存中一起提供1MB存储的设备。可执行代码为每次通电或重置固件条目时的校验和，以及结果（包括闪存设备中包含的预计算校验和），根据预期校验和进行验证。
Various PPCBug routines that handle I/O, data conversion, and string
functions are available to user programs through the System Call handler.
PPCBug consists of three parts:
❏ A command-driven user-interactive software debugger. It is
hereafter referred to as “the debugger” or “PPCBug.”
❏ A set of command-driven diagnostics, which is hereafter referred to
as “the diagnostics.”
❏ A user interface which accepts commands from the system console
terminal.
When using PPCBug, you will operate out of either the debugger directory
or the diagnostic directory. The debugger prompt
(PPC1-Bug or PPC1-Diag) tells you the current directoryBecause PPCBug is command-driven, it performs its various operations in
response to user commands entered at the keyboard. The flow of control in
PPCBug is described in the PPCBug Firmware Package User’s Manual,
listed in Appendix D, Related Documentation. When you enter a
command, PPCBug 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 PPCBug,
depending on the outcome of the user program.
The PPCBug is similar to previous Motorola firmware debugging
packages (for example, MVME147Bug, MVME167Bug,
MVME187Bug), with differences due to microprocessor architectures.
These are primarily reflected in the instruction mnemonics, register
displays, addressing modes of the assembler/disassembler, and the passing
of arguments to the system calls.
Memory Requirements
PPCBug requires a maximum of 768KB (maybe less) of read/write
memory (that is, DRAM). The debugger allocates this space from the top
of memory. For example, a system containing 64MB ($04000000) of
read/write memory will place the PPCBug memory page at locations
$03F80000 to $03FFFFFF.PPCBug Implementation
PPCBug is written largely in the C programming language, providing
benefits of portability and maintainability. Where necessary, assembly
language has been used in the form of separately compiled program
modules containing only assembler code. No mixed-language modules are
used.
Physically, PPCBug is contained in two socketed 32-pin PLCC Flash
devices that together provide 1MB of storage. The executable code is
checksummed at every power-on or reset firmware entry, and the result
(which includes a precalculated checksum contained in the Flash devices),
is verified against the expected checksum.
