Freescale Semiconductor ColdFire MCF5274, User Manual

Page: 43 / 104

Chapter 3. Using the Monitor/Debug Firmware 3-5
Command Line Usage
3.3 Command Line Usage
The user interface to dBUG is the command line. A number of features have been
implemented to achieve an easy and intuitive command line interface.
dBUG assumes that an 80x24 ASCII character dumb terminal is used to connect to the
debugger. For serial communications, dBUG requires eight data bits, no parity, and one stop
bit (8-N-1) with no flow control. The baud rate default is 19200 bps—a speed commonly
available from workstations, personal computers and dedicated terminals.
The command line prompt is: dBUG>
Any dBUG command may be entered from this prompt. dBUG does not allow command
lines to exceed 80 characters. Wherever possible, dBUG displays data in 80 columns or
less. dBUG echoes each character as it is typed, eliminating the need for any local echo on
the terminal side.
The <Backspace> and <Delete> keys are recognized as rub-out keys for correcting
typographical mistakes.
Command lines may be recalled using the <Control> U, <Control> D and <Control> R key
sequences. <Control> U and <Control> D cycle up and down through previous command
lines. <Control> R recalls and executes the last command line.
In general, dBUG is not case-sensitive. Commands may be entered either in uppercase or
lowercase, depending upon the user’s equipment and preference. Only symbol names
require that the exact case be used.
Most commands can be recognized by using an abbreviated name. For instance, entering h
is the same as entering help. Thus it is not necessary to type the entire command name.
The commands DI, GO, MD, STEP and TRACE are used repeatedly when debugging.
dBUG recognizes this and allows for repeated execution of these commands with minimal
typing. After a command is entered, press the <Return> or <Enter> key to invoke the
command again. The command is executed as if no command line parameters were
provided.
3.4 Commands
This section lists the commands that are available with all versions of dBUG. Some board
or CPU combinations may use additional commands not listed below.