Operating Procedures; Evb Mode; Jump-Eeprom Mode - Motorola M68EVB912B32 User Manual

Table of Contents

Advertisement

OPERATION
6. Apply power to the EVB and to the terminal. If the terminal is a host computer,
a. Verify that it has booted correctly.
b. Start the communications program for terminal emulation — section 2.5.3 and
Appendix B  Communications Program Examples.
7. Reset the EVB by pressing and releasing the on-board reset switch (S1).

3.2.2 Operating Procedures

After starting the EVB in accordance with section 3.2.1, follow the operating procedure for the
EVB mode that was selected: EVB mode, JUMP-EEPROM mode, POD mode, or BOOTLOAD
mode. These procedures are described in the following sections.

3.2.2.1 EVB Mode

In EVB mode, the MC68HC912B32 begins executing code at the address contained in the
alternate reset vector at $F7FE (for information on the alternate reset and interrupt vector table,
see Vector Jump Table: Interrupt and Reset Addresses on page E-4). The code pointed to by
the alternate reset vector may either be D-Bug12 (factory default) or a user's program that has
replaced D-Bug12 in Flash EEPROM.
D-Bug12  upon reset, the D-Bug12 sign-on banner and prompt should appear on the terminal's
display as follows:
D-Bug12 v 2.0.0
Copyright 1996 - 1997 Motorola Semiconductor
For Commands type "Help"
>
If the prompt does not appear, check all connections and verify that startup steps 1
through 7 in section 3.2.1 have been performed correctly.
When the prompt appears, D-Bug12 is ready to accept commands from the terminal as
described in section 3.5.
User boot program  upon reset, the user program executes immediately. D-Bug12 commands
are not available. Terminal communications take place either via the SCI under control
of the user program or via the BDM interface and a serial debug interface tool such as
Motorola's SDI.

3.2.2.2 JUMP-EEPROM Mode

In JUMP-EEPROM mode, the user code in byte-erasable EEPROM starting at address $0D00 is
executed immediately. Terminal communications are controlled by the user code via the SCI or
by an appropriate serial debug tool via the BDM interface. For more information, refer to
3-4
68EVB912B32UM/D

Advertisement

Table of Contents
loading

Table of Contents