Freescale Semiconductor ColdFire MCF5274, User Manual

Page: 39 / 104

Chapter 3. Using the Monitor/Debug Firmware 3-1
Chapter 3
Using the Monitor/Debug Firmware
The M5275EVB single board computer has a resident firmware package that provides a
self-contained programming and operating environment. The firmware, named dBUG,
provides the user with monitor/debug interface, inline assembler and disassembly, program
download, register and memory manipulation, and I/O control functions. This chapter is a
how-to-use description of the dBUG package, including the user interface and command
structure.
3.1 What Is dBUG?
dBUG is a traditional ROM monitor/debugger that offers a comfortable and intuitive
command line interface that can be used to download and execute code. It contains all the
primary features needed in a debugger to create a useful debugging environment.
The firmware provides a self-contained programming and operating environment. dBUG
interacts with the user through pre-defined commands that are entered via the terminal.
These commands are defined in Section 3.4, “Commands.”
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 character dumb-terminal is utilized 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 default baud rate is 19200 but can be changed after
power-up.
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.
In general, dBUG is not case sensitive. Commands may be entered either in upper or lower
case, depending upon the user’s equipment and preference. Only symbol names require that
the exact case be used.