Laptop User Manual

Debugger General Information
3-2 MVME166 Single Board Computer Installation Guide
3
When using 166Bug, you operate out of either the debugger directory or the
diagnostic directory. If you are in the debugger directory, the debugger
prompt "
166-Bug>" is displayed and you have all of the debugger commands
at your disposal. If you are in the diagnostic directory, the diagnostic prompt
"
166-Diag>" is displayed and you have all of the diagnostic commands at your
disposal as well as all of the debugger commands. You may switch between
directories by using the Switch Directories (SD) command, or may examine
the commands in the particular directory that you are currently in by using the
Help (HE) command.
Because 166Bug is command-driven, it performs its various operations in
response to user commands entered at the keyboard. When you enter a
command, 166Bug executes the command and the prompt reappears.
However, if you enter a command that causes execution of user target code
(e.g., "GO"), then control may or may not return to 166Bug, depending on the
outcome of the user program.
If you have used one or more of Motorola’s other debugging packages, you
will find the CISC 166Bug very similar. Some effort has also been made to
make the interactive commands more consistent. For example, delimiters
between commands and arguments may now be commas or spaces
interchangeably.