Motorola PrPMC800/800ET Processor PMC Module User Manual
PrPMC800/800ET Processor PMC Module Installation and Use (PrPMC800A/IH5)
5 PPCBug
42
25. Verifies the configuration data that is resident in NVRAM, and displays a warning
message if the verification failed.
26. 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.
27. Displays the BUS clock speed, verifies that the BUS clock speed matches the
configuration data, and displays a warning message if the verification fails.
28. Probes PCI bus for supported network devices.
29. Probes PCI bus for supported mass storage devices.
30. Initializes the memory/IO addresses for the supported PCI bus devices.
31. Executes Self-Test, if so configured. (Default is no Self-Test.)
32. Extinguishes the board fail LED, if Self-Test passed, and outputs any warning
messages.
33. Executes boot program, if so configured. (Default is no boot.)
34. Executes the debugger monitor (issues the
PPC7-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 PPC7-Bug prompt appears on the screen, the debugger
is ready to accept debugger commands. When the PPC7-Diag prompt appears on the screen,
the debugger is ready to accept diagnostics commands. To switch from one mode to the other,
enter SD.
you enter at the keyboard. When the PPC7-Bug prompt appears on the screen, the debugger
is ready to accept debugger commands. When the PPC7-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 enter 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.
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.
After the debugger executes the command, the prompt reappears. However, if the command
causes execution of user target code (for example GO) then control may or may not return to
the debugger, depending on what the user program does. For example, if a breakpoint has been
specified, control returns to the debugger when the breakpoint is encountered during execution
of the user program. Alternately, the user program could return to the debugger by means of
the System Call Handler routine RETURN. For more about this, refer to the GD, GO, and GT
command descriptions in the PPCBug Firmware Package User’s Manual.
causes execution of user target code (for example GO) then control may or may not return to
the debugger, depending on what the user program does. For example, if a breakpoint has been
specified, control returns to the debugger when the breakpoint is encountered during execution
of the user program. Alternately, the user program could return to the debugger by means of
the System Call Handler routine RETURN. For more about this, refer to the GD, GO, and GT
command descriptions in the PPCBug Firmware Package User’s Manual.
A debugger command is made up of the following parts:
❏
The command name, either uppercase or lowercase (for example, MD or md).
❏
Any required arguments, as specified by command.
❏
At least one space before the first argument. Precede all other arguments with either
a space or comma.
❏
One or more options. Precede an option or a string of options with a semicolon (;). If
no option is entered, the command’s default option conditions are used.