MOTOROLA MVME162-512 Embedded Controller

MVME162 Module Installation

With EPROM and IndustryPacks installed and headers properly configured,

proceed as follows to install the MVME162 in the VME chassis:

1. Turn all equipment power OFF and disconnect the power cable from the

AC power source

Inserting or removing modules while power is applie

2. Remove the chassis cover as instructed in the user’s manual for the

equipment.

3. Remove the filler panel from the card slot where you are going to install

the MVME162.– If you intend to use the MVME162 as system controller, it must occupy

the leftmost card slot (slot 1). The system controller must be in slot 1

to correctly initiate the bus-grant daisy-chain and to ensure proper

operation of the IACK daisy-chain driver.– If you do not intend to use the MVME162 as system controller, it can

occupy any unused double-height card slot.

4. Slide the MVME162 into the selected card slot. Be sure the module is

seated properly in the P1 and P2 connectors on the backplane.  Do not

damage or bend connector pins.

5. Secure the MVME162 in the chassis with the screws provided, making

good contact with the transverse mounting rails to minimize RF

emissions.

6. Install the MVME712 series transition module in the front or the rear of the

VME chassis.  (To install an MVME712M, which has a double-wide front

panel, you may need to shift other modules in the chassis.)

7. On the chassis backplane, remove the INTERRUPT ACKNOWLEDGE

(IACK) and BUS GRANT (BG) jumpers from the header for the card slot

occupied by the MVME162

Connect the P2 Adapter Board or LCP2 Adapter Board and cable(s) to

MVME162 backplane connector P2. This provides a connection point for

terminals or other peripherals at the EIA-232-D serial ports, SCSI ports,

and LAN Ethernet port.

For information on installing the P2 or LCP2 Adapter Board and the

MVME712 series transition module(s), refer to the manuals listed in

Related Documentation in Chapter 1 (the MVME162 Embedded Controller

Programmer’s Reference Guide provides some connection diagrams).

Connect the appropriate cable(s) to the panel connectors for the EIA-232

D serial ports, SCSI port, and LAN Ethernet port.– Note that some cables are not provided with the MVME712 series

module and must be made or purchased by the user. (Motorola

recommends shielded cable for all peripheral connections to minimize

radiation.)

10. Connect the peripheral(s) to the cable(s).   Appendix A supplies detailed

information on the EIA-232-D signals supported. Appendix B describes

the Ethernet LAN (Local Area Network) port connections. Appendix C

describes the SCSI (Small Computer System Interface) I/O bus connections.

11. Install any other required VMEmodules in the system.

12. Replace the chassis cover.

13. Connect the power cable to the AC power source and turn the equipment

power ON

System Considerations

The MVME162 draws power from VMEbus backplane connectors P1 and P2.

P2 is also used for the upper 16 bits of data in 32-bit transfers, and for the upper

8 address lines in extended addressing mode.  The MVME162 may not function

properly without its main board connected to VMEbus backplane connectors

P1 and P2.

Whether the MVME162 operates as a VMEbus master or as a VMEbus slave, it

is configured for 32 bits of address and 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/

MC68LC040 software.  Refer to the memory maps in Chapter 3.

The MVME162 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 MVME162Bug firmware.  This may be changed via

software to any other base address.  Refer to the MVME162 Embedded Controller

Programmer’s Reference Guide for more information.

If the MVME162 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 MVME162 waits forever for the VMEbus cycle to complete.  This will cause

the system to lock up.  There is only one situation in which the system might

lack this global bus timeout:  when the MVME162 is not the system controller

and there is no global bus timeout elsewhere in the system.

Multiple MVME162s may be installed in a single VME chassis.  In general,

hardware multiprocessor features are supported