System Considerations - Motorola MVME167 Series User Manual

6. Connect the P2 Adapter Board and specified cable(s) to the MVME167 at P2 on
the backplane at the MVME167 slot, to mate with (optional) terminals or other
peripherals at the EIA-232-D serial ports, parallel port, SCSI ports, and LAN
Ethernet port. Refer to the manuals listed in Related Documentation in Chapter 1
for information on installing the P2 Adapter Board and the MVME712X transition
module(s). (Some connection diagrams are in the
MVME166/MVME167/MVME187 Single Board Computers Programmer's
Reference Guide.) Some cable(s) are not provided with the MVME712X
module(s), and therefore are made or provided by the user. (Motorola
recommends using shielded cables for all connections to peripherals to minimize
radiation.) Connect the peripherals to the cable(s). Detailed information on the
EIA-232-D signals supported is found in Appendix A.
7. Install any other required VMEmodules in the system.
8. Replace the chassis cover.
9. Connect power cable to ac power source and turn equipment power ON.

System Considerations

The MVME167 needs to draw power from both P1 and P2 of the VMEbus backplane.
P2 is also used for the upper 16 bits of data for 32-bit transfers, and for the upper 8
address lines for extended addressing mode. The MVME167 may not operate properly
without its main board connected to P1 and P2 of the VMEbus backplane.
Whether the MVME167 operates as a VMEbus master or as a VMEbus slave, it is
configured for 32 bits of address and for 32 bits of data (A32/D32). However, it
handles A16 or A24 devices in the address ranges indicated in Chapter 3. D8 and/or
D16 devices in the system must be handled by the MC68040 software. Refer to the
memory maps in Chapter 3.
The MVME167 contains shared onboard DRAM whose base address is
software-selectable. Both the onboard processor and offboard VMEbus devices see
this local DRAM at base physical address $00000000, as programmed by the
MVME167Bug firmware. This may be changed, by software, to any other base
address. Refer to the MVME166/MVME167/MVME187 Single Board Computers
Programmer's Reference Guide for details.
If the MVME167 tries to access offboard resources in a nonexistent location, and is not
system controller, and if the system does not have a global bus timeout, the MVME167
waits forever for the VMEbus cycle to complete. This would cause the system to hang
up. There is only one situation in which the system might lack this global bus timeout:
the MVME167 is not the system controller, and there is no global bus timeout
elsewhere in the system.
MVME167/D3
Installation Instructions
2-7
2