M5249C3 Freescale Semiconductor, M5249C3 Datasheet - Page 20

• Manufacturer Part Number: M5249C3
• Description: KIT EVAL FOR M5249 W/ETHERNET
• Manufacturer: Freescale Semiconductor
• Series: ColdFire®r
• Type: Microprocessorr

Specifications of M5249C3

• Contents: Module and Misc Hardware
• Processor To Be Evaluated: MCF5249
• Interface Type: RS-232, Ethernet
• For Use With/related Products: MCF5249
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant

Using the Monitor/Debug Firmware
Copyright 1995-2002 Motorola, Inc.
ColdFire MCF5249 EVS Firmware v2e.1a.1a (Build XXX on XXX)
Enter 'help' for help.
dBUG>
If you did not get this response check the setup, refer to
Operation.”
Other means can be used to re-initialize the M5249C3 Computer Board firmware. These means are
discussed in the following paragraphs.
2.2.2.1
Hard RESET (S1) is the red button. Depressing this button causes all processes to terminate, resets the
MCF5249 processor and board logic and restarts the dBUG firmware. Pressing the RESET button would
be the appropriate action if all else fails.
2.2.2.2
ABORT (S2) is the button located next to the RESET button. The abort function causes an interrupt of the
present processing (a level 7 interrupt on MCF5249) and gives control to the dBUG firmware. This action
differs from RESET in that no processor register or memory contents are changed, the processor and
peripherals are not reset, and dBUG is not restarted. Also, in response to depressing the ABORT button,
the contents of the MCF5249 core internal registers are displayed.
The abort function is most appropriate when software is being debugged. The user can interrupt the
processor without destroying the present state of the system. This is accomplished by forcing a
non-maskable interrupt that will call a dBUG routine that will save the current state of the registers to
shadow registers in the monitor for display to the user. The user will be returned to the ROM monitor
prompt after exception handling.
2.2.2.3
dBUG does have a command that causes the dBUG to restart as if a hardware reset was invoked. The
command is "RESET".
2.3
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 (8N1). The baud rate default
is 19200 bps — a speed commonly available from workstations, personal computers and dedicated
terminals.
The command line prompt is: dBUG>
2-4
Command Line Usage
Hard RESET Button
ABORT Button
Software Reset Command
M5249C3 User’s Manual, Rev. 1
All Rights Reserved.
Section 1.9, “System Power-up and Initial
Freescale Semiconductor