1 implementation and memory requirements, Ppcbug firmware – Artesyn MVME51005E SBC Installation and Use (July 2014) User Manual
Page 40

PPCBug Firmware
MVME51005E Single Board Computer Installation and Use (6806800A38D)
42
PPCBug consists of three parts:
A command-driven, user-interactive software debugger, described in the PPCBug
Firmware Package User’s Manual, listed in
Appendix D, Related Documentation
(hereafter
referred to as “debugger” or “PPCBug”).
A command-driven diagnostics package for the MVME5100 hardware (hereafter referred
to as “diagnostics”). The diagnostics package is described in the PPCBug Diagnostics
Manual, listed in
Appendix D, Related Documentation
A user interface or debug/diagnostics monitor that accepts commands from the system
console terminal.
When using PPCBug, you operate out of either the debugger directory or the diagnostic
directory.
If you are in the debugger directory, the debugger prompt PPC6-Bug> is displayed and you
have all of the debugger commands at your disposal.
If you are in the diagnostic directory, the diagnostic prompt PPC6-Diag> is displayed and
you have all of the diagnostic commands at your disposal as well as all of the debugger
commands.
Because PPCBug is command-driven, it performs its various operations in response to user
commands entered at the keyboard. 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.
3.2.1
Implementation and Memory Requirements
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.
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. The result (which includes a precalculated checksum contained in the flash
devices), is verified against the expected checksum.