Technical data

Bringing up the Board
http://www.mcg.mot.com/literature 2-7
2
Note In order for high-baud-rate serial communication between
172Bug and the terminal to work, the terminal must do some
form of handshaking. If the terminal being used does not do
hardware handshaking via the CTS line, then it must do
XON/XOFF handshaking. If you get garbled messages and
missing characters, then you should check the terminal to
make sure XON/XOFF handshaking is enabled.
4. If you want to connect devices (such as a host computer system
and/or a serial printer) to the other EIA-232-D port connectors,
connect the appropriate cables and configure the port(s) as detailed
in step 3 above. After power-up, you can reconfigure these port(s)
by programming the MVME172LX Z85230 Serial
Communications Controllers (SCCs), or by using the 172Bug PF
command.
5. The EPROM/Flash header J20 must be set to configuration 3, with
jumpers between J20 pins 5-6, 8-10, and 9-11. This sets it up for
512K x 8 EPROMs.
6. Power up the system. 172Bug executes some self-checks and
displays the debugger prompt
172-Bug> if the firmware is in Board
mode.
However, if the ENV command has put 172Bug in System mode,
the system performs a self-test and tries to autoboot. Refer to the
ENV and MENU commands (Table 4-3).
If the confidence test fails, the test is aborted when the first fault is
encountered. If possible, an appropriate message is displayed, and
control then returns to the menu.
7. Before using the MVME172LX after the initial installation, set the
date and time using the following command line structure:
172-Bug> SET [mmddyyhhmm]|[<+/-CAL>;C]
For example, the following command line starts the real-time clock
and sets the date and time to 10:37 a.m., September 7, 1999:
172-Bug> SET 0907991037