SA9923a-E自動(dòng)化卡件,ABB中文PDF說(shuō)明書在線閱讀
處理輸入/輸出、數(shù)據(jù)轉(zhuǎn)換和字符串的各種PPCBug例程用戶程序可以通過(guò)系統(tǒng)調(diào)用處理程序使用函數(shù)。PPCBug由三部分組成：? 命令驅(qū)動(dòng)的用戶交互軟件調(diào)試器。它是以下簡(jiǎn)稱“調(diào)試器”或“PPCBug”? 一組命令驅(qū)動(dòng)的診斷，以下簡(jiǎn)稱作為“診斷”? 接受系統(tǒng)控制臺(tái)命令的用戶界面航空站使用PPCBug時(shí)，您將在調(diào)試器目錄之外進(jìn)行操作或診斷目錄。
SA9923a-E自動(dòng)化卡件調(diào)試器提示（PPC1 Bug或PPC1 Diag）告訴您當(dāng)前的目錄由于PPCBug是命令驅(qū)動(dòng)的，它在對(duì)在鍵盤上輸入的用戶命令的響應(yīng)?？刂屏鞒蘌PCBug在PPCBug固件包用戶手冊(cè)中進(jìn)行了描述，附錄D中列出了相關(guān)文件。當(dāng)您輸入命令，PPCBug執(zhí)行該命令，并再次出現(xiàn)提示。
但是，如果您輸入的命令導(dǎo)致執(zhí)行用戶目標(biāo)代碼（例如，GO），則控制可能返回或可能不返回到PPCBug，取決于用戶程序的結(jié)果。PPCBug類似于之前的摩托羅拉固件調(diào)試包（例如，MVME147Bug、MVME167Bug、，MVME187Bug），由于微處理器架構(gòu)的不同而有所不同。這些主要反映在指令助記符、寄存器中顯示、匯編器/反匯編器的尋址模式和傳遞系統(tǒng)調(diào)用的參數(shù)。內(nèi)存要求PPCBug最多需要768KB（可能更少）的讀/寫容量?jī)?nèi)存（即DRAM）。調(diào)試器從頂部分配此空間內(nèi)存。例如，一個(gè)系統(tǒng)包含64MB（04000000美元）的讀/寫內(nèi)存將PPCBug內(nèi)存頁(yè)放置在位置$03F80000至$03FFFFFF。PPCBug實(shí)現(xiàn)PPCBug主要用C編程語(yǔ)言編寫，提供了可移植性和可維護(hù)性的好處。必要時(shí)，組裝語(yǔ)言以單獨(dú)編譯程序的形式使用僅包含匯編代碼的模塊。沒(méi)有混合語(yǔ)言模塊習(xí)慣于物理上，PPCBug包含在兩個(gè)32針插口PLCC閃存中一起提供1MB存儲(chǔ)的設(shè)備?？蓤?zhí)行代碼為每次通電或重置固件條目時(shí)的校驗(yàn)和，以及結(jié)果（包括閃存設(shè)備中包含的預(yù)計(jì)算校驗(yàn)和），根據(jù)預(yù)期校驗(yàn)和進(jìn)行驗(yàn)證。
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.
