Motorola MVME162P-242, Installation And Use Manual

Page: 65 / 134

Using 162Bug
http://www.motorola.com/computer/literature 3-5
3
Using 162Bug
162Bug is command-driven; it performs its various operations in response
to commands that you enter at the keyboard. When the
162-Bug>
prompt
appears on the terminal screen, the debugger is ready to accept debugger
commands. When the
162-Diag>
prompt appears on the screen, the
debugger is ready to accept diagnostics commands.
To switch from one mode to the other, enter SD (Switch Directories). To
examine the commands in the directory that you are currently in, use the
Help command (HE).
What you key in is stored in an internal buffer. Execution begins only after
the carriage return is entered. This allows you to correct entry errors, if
necessary, with the control characters described in the Debugging Package
for Motorola 68K CISC CPUs User’s Manual, Chapter 1.
After the debugger executes the command you have entered, 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, then control returns to the
debugger when the breakpoint is encountered during execution of the user
program. Alternatively, the user program could return to the debugger by
means of the System Call Handler routine RETURN (described in the
Debugging Package for Motorola 68K CISC CPUs User’s Manual,
Chapter 5, listed in Appendix E, Related Documentation).
A debugger command is made up of the following parts:
❏
The command name, either uppercase or lowercase (e.g., MD or
md).
❏
A port number (if the command is set up to work with more than one
port).
❏
Any required arguments, as specified by the command.
❏
At least one space before the first argument. Precede all other
arguments with either a space or a comma.