Motorola 700/800-Series User Manual

3-6

Debugger General Information

After power-up, you can reconfigure the baud rate of the 
debug port if necessary by using the 162Bug firmwareÕs Port 
Format (PF) command.

In order for high-baud rate serial communication 
between 162Bug 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.

8. 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 4 above. After power-up, you can 
reconfigure this (these) port(s) by programming the 
MVME162LX Z85230 Serial Communications Controllers 
(SCCs), or by using the 162Bug 

 command. 

9. EPROM/Flash configuration header J20 should be set to 

configuration 2, with jumpers between J20 pins 5 and 6, 8 and 
10, and 9 and 11. This sets it up for 512K x 8 EPROMs.

10. Power up the system. 162Bug executes some self-checks and 

displays the debugger prompt 

162-Bug>

 

(if 162Bug is in Board Mode). However, if the 

 command 

(Appendix A) has put 162Bug in System Mode, the system 
performs a selftest and tries to autoboot. Refer to the 

 and 

 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.