Motorola 700 Series, Installation And Use Manual

Page: 72 / 156

3-2
Debugger General Information
3
❏
A command-driven diagnostic package for the MVME162LX
hardware, described in the MVME162Bug Diagnostics Manual
and hereinafter referred to as ‘‘the diagnostics’’.
❏
A user interface that accepts commands from the system
console terminal.
When using 162Bug, you operate out of either the debugger
directory or the diagnostic directory. If you are in the debugger
directory, the debugger prompt
162-Bug>
is displayed and you have all of the debugger commands at your
disposal. If you are in the diagnostic directory, the diagnostic
prompt
162-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 you may examine the commands in your current directory by
using the Help (
HE
) command.
Because 162Bug is command-driven, it performs its various
operations in response to user commands entered at the keyboard.
When you enter a command, 162Bug 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 162Bug, 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 162Bug 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.