Using PPCBug
http://www.motorola.com/computer/literature 5-5
5
26. Verifies the configuration data that is resident in NVRAM, and
displays a warning message if the verification failed.
27. Calculates and displays the MPU clock speed, verifies that the MPU
clock speed matches the configuration data, and displays a warning
message if the verification fails.
28. Displays the BUS clock speed, verifies that the BUS clock speed
matches the configuration data, and displays a warning message if
the verification fails.
29. Probes PCI bus for supported network devices.
30. Probes PCI bus for supported mass storage devices.
31. Initializes the memory/IO addresses for the supported PCI bus
devices.
32. Executes Self-Test, if so configured. (Default is no Self-Test.)
33. Extinguishes the board fail LED, if Self-Test passed, and outputs
any warning messages.
34. Executes boot program, if so configured. (Default is no boot.)
35. Executes the debugger monitor (that is, issues the
PPC4-Bug>
prompt).
Using PPCBug
PPCBug is command-driven; it performs its various operations in response
to commands that you enter at the keyboard. When the PPC4-Bug prompt
appears on the screen, the debugger is ready to accept debugger
commands. When the PPC4-Diag prompt appears on the screen, the
debugger is ready to accept diagnostics commands. To switch from one
mode to the other, enter SD.
What you key in is stored in an internal buffer. Execution begins only after
you press the Return or Enter key. This allows you to correct entry errors,
if necessary, with the control characters described in the PPCBug
Firmware Package User’s Manual.
To Next Page
Loading...
