Mxi-express x1 multisystem extension interface for pci, pci express, compactpci/compactpci express, expresscard, and pxi/pxi express bus computers, ni pci-8361, ni pxi-8361, ni pxi-8368, ni pci-8366, ni pxi-8364, ni pxie-8360, ni pcie-8361, ni pxi-8366, n (120 pages)
Page 2
National Instruments Corporate Headquarters 6504 Bridge Point Parkway Austin, TX 78730-5039 (512) 794-0100 (800) 433-3488 (toll-free U.S. and Canada) Technical support fax: (512) 794-5678 Branch Offices: Australia 03 879 9422, Austria 0662 435986, Belgium 02 757 00 20, Canada (Ontario) 519 622 9310, Canada (Québec) 514 694 8521, Denmark 45 76 26 00, Finland 90 527 2321, France 1 48 65 33 70,...
Page 3
Any action against National Instruments must be brought within one year after the cause of action accrues. National Instruments shall not be liable for any delay in performance due to causes beyond its reasonable control. The warranty provided herein does not cover damages, defects, malfunctions, or service failures caused by owner's failure to follow the National Instruments installation, operation, or maintenance instructions;...
Page 4
Be sure that the equipment is plugged into a grounded outlet and that the grounding has not been defeated with a cheater plug. Notice to user: Changes or modifications not expressly approved by National Instruments could void the user's authority to operate the equipment under the FCC Rules.
Page 7
Appendix C VXI-MXI Component Placement .................. C-1 Removing the Metal Enclosure from the VXI-MXI ............C-1 Removing the INTX Daughter Card from the VXI-MXI ..........C-3 Installing the INTX Daughter Card onto the VXI-MXI ..........C-4 Appendix D Connector Descriptions .....................
Chapter 5, Programming Considerations, explains important considerations for programming the VXI-MXI and configuring a system using VXI-MXIs. • Chapter 6, Theory of Operation, contains a functional overview of the VXI-MXI board and explains the operation of each functional block making up the VXI-MXI. •...
About This Manual How to Use This Manual If you will be installing your VXI-MXI into a system with a VXIbus Resource Manager, you only need to read Chapters 1 through 3 of this manual. If you have more than two VXI-MXIs extending your system, you will find useful system configuration information in Chapter 5.
VXI-MXI interface module uses address mapping to transparently translate bus cycles on the VXIbus system bus (VMEbus) to the MXIbus and vice versa. The VXI-MXI is housed in a metal enclosure to improve EMI performance and to provide easy handling. Because the enclosure includes cut-outs to facilitate changes to switch and jumper settings, it should not be necessary to remove it under most circumstances.
The VXI-MXI is an extended class Register-Based VXIbus device with optional Slot 0 capability so that it can reside in any slot in a C-size or D-size VXIbus chassis. The VXI-MXI converts A32, A24, A16, D32, D16, and D08(EO) VXIbus bus cycles into MXIbus bus cycles and vice versa.
– 10 MHz clock – MODID register – TTL and ECL Trigger line support All integrated circuit drivers and receivers used on the VXI-MXI meet the requirements of both the VMEbus specification and the MXIbus specification. Front Panel Features The VXI-MXI has the following front panel features: •...
General Information Chapter 1 What Your Kit Should Contain Your VXI-MXI kit should contain the following components: Component Part Number Standard VXI-MXI Interface Module 181045-01 Enhanced VXI-MXI Interface Module with INTX option 181045-02 VXI-MXI User Manual 320222-01 Optional Equipment Equipment...
VXIbus mainframe chassis before removing the module from the bag. 4. As you remove the VXI-MXI module from its bag, be sure to handle it only by its edges. Avoid touching any of the IC components or connectors. Inspect the module for loose components or any other sign of damage.
Electrical Characteristics All integrated circuit drivers and receivers used on the VXI-MXI meet the requirements of the VMEbus specification. Table 2-1 contains a list of the VMEbus signals used by the VXI-MXI and the electrical loading presented by the circuitry on the interface board (in terms of device types and their part numbers).
• VMEbus Master • VMEbus Slave • Interrupter • IACK Daisy-Chain Driver When the VXI-MXI is configured as a VXIbus Slot 0 device, it also has the following VMEbus modules: • VMEbus Timer • Arbiter • System Clock Driver VXI-MXI User Manual...
Chapter 2 General Description The VXI-MXI does not support the following VMEbus modules: • Serial Clock Driver • Power Monitor Table 2-3 indicates the VXI-MXI VMEbus compliance levels. Table 2-3. VXI-MXI VMEbus Compliance Levels Compliance Notation Description Bus Slave Compliance Levels...
Page 22
General Description Chapter 2 Table 2-3. VXI-MXI VMEbus Compliance Levels (Continued) Compliance Notation Description Bus Master Compliance Levels D08(EO) 8-bit data path from MXIbus D16 & D08(EO) 8-bit or 16-bit data path from MXIbus 32-bit data path from MXIbus Generates 16-bit short I/O addresses when specified...
General Description VXI-MXI Functional Description In simplest terms, the VXI-MXI can be thought of as a bus translator that converts VXIbus signals into appropriate MXIbus signals. From the perspective of the MXIbus, the VXI-MXI implements a MXIbus interface to communicate with other MXIbus devices. From the perspective of the VMEbus, the VXI-MXI is an interface to the outside world.
Page 25
VXIbus, the MXIbus address/data lines are demultiplexed into separate VXIbus address and data lines. • MXIbus System Controller Functions If the VXI-MXI is the MXIbus System Controller, this circuitry provides the MXIbus arbiter, interrupt daisy-chain generation, and the MXIbus System Controller timeout logic. •...
General Description Chapter 2 The following information applies only to VXI-MXI kits that include the INTX daughter card option. Figure 2-2 is a block diagram of the circuitry of the INTX daughter card. INTX Registers Interrupt Control Trigger Control System Resets...
Page 27
VXIbus mainframe across the INTX connection, an interrupt handler in another VXIbus mainframe can generate an interrupt acknowledge cycle to handle that interrupt. The VXI-MXI in the requesting mainframe recognizes that the MXIbus interrupt acknowledge cycle is for the request it is...
VXIbus Slot 0 The VXI-MXI is shipped from the factory configured to be installed in Slot 0 of the VXIbus mainframe. If another device is already in Slot 0, you must decide which device will be the Slot 0 device and reconfigure the other device for Non-Slot 0 use.
VXIbus Model Code in the Device Type Register. If the VXIbus Model Code for the VXI-MXI is hex 00FE, the module is configured as a Slot 0 device; if the code is hex 08FE, the module is configured as a Non-Slot 0 device.
The VXIbus RM has Logical Address 0 by definition. The VXI-MXI does not have VXIbus RM capability, so do not set the logical address for the VXI-MXI to 0. If you are configuring a multiple-mainframe VXIbus/MXIbus system, refer to Chapter 5, Programming Considerations, for instructions on planning a VXIbus/MXIbus system logical address map.
VXIbus specification. Request level 3 is the highest priority request level and request level 0 is the lowest. You can change the VXI-MXI to use any of the other three request levels by changing the jumper configuration on the jumper blocks labeled VMEbus Request Level on the front panel.
In the case of multiple VXI-MXIs, it is recommended that the BTO be enabled on the VXI-MXI that is installed in Slot 0. The BTO monitors the current bus cycle and asserts the bus error (BERR) signal if a data transfer acknowledge (DTACK) or BERR is not received from the selected slave within the given amount of time after data strobe (DS1 or DS0) becomes active.
VME BTO Chain Position jumper block selects how the VXIbus local bus is used to disable the VMEbus timeout when outward MXIbus transfers occur. If another device has a BTO module, remember to enable the BTO on the VXI-MXI and to disable the VMEbus BTO on the other device.
When you have multiple VXI-MXI modules installed in adjacent slots, the VXIbus local bus is used to send a signal to the VXI-MXI with the VMEbus BTO to indicate that an outward MXIbus transfer is in progress. The following figures show how to configure the VME BTO Chain Position jumper block to select how the VXIbus local bus is used to disable the VMEbus timeout during outward MXIbus transfers.
Configuration and Installation If the system contains more than one VXI-MXI, select which card will supply the VMEbus timeout, and set the jumper block according to the VXI-MXI's position in relation to the adjacent VXI-MXIs. Figure 3-9 shows four possible settings.
Configuration and Installation Chapter 3 For the VXI-MXIs that do not supply the VMEbus timeout, set the VME BTO Chain Position jumper block to reflect each VXI-MXI's position in relation to the adjacent VXI-MXIs. See Figure 3-10. VME BTO VME BTO...
Manager. In all the other mainframes, the VXI-MXIs must be the highest priority requesters. This means that a VXI-MXI should be installed in Slot 0 of its respective mainframe. In the case of multiple VXI-MXIs in a single mainframe, the additional VXI-MXIs should be installed in the slots adjacent to the Slot 0 VXI-MXI.
The VXI-MXI is shipped from the factory configured for non-MXIbus System Controller operation. If the VXI-MXI is the first device in the MXIbus link, configure the VXI-MXI as the MXIbus System Controller by changing the default setting of the slide switch from Disabled to Enabled, as shown in Figure 3-12.
Figure 3-13 shows how to position the jumper array to set the MXIbus System Controller timeout value. When the VXI-MXI is not configured to be the MXIbus System Controller, the setting of this jumper array has no effect. Notice that when the LNGMXSCTO bit in the MXIbus Control Register is zero, the selected timeout value is in microseconds.
MXIbus chain. The MXIbus fairness feature is controlled by the Fairness slide switch. If you want your VXI-MXI to be a fair requester, change the slide switch from the Disabled setting to Enabled, as shown in Figure 3-14.
CLK10 Source Select jumper array to select one of these options, as shown in Figure 3-15. The VXI-MXI is configured at the factory to be a Slot 0 device driving the CLK10 signal from the onboard oscillator. If you are installing the VXI-MXI in a slot other than Slot 0, change the jumper array so that the VXI-MXI is configured to receive the CLK10 signal.
CLK10 signals of the two mainframes together using the EXT CLK SMB connectors on the front panel of the VXI-MXI. One mainframe should source the CLK10 signal to the SMB connection. The other device receives the CLK10 signal from the SMB connection and drives it on the VXIbus CLK10 lines.
Configuration and Installation Chapter 3 The VXI-MXI must be installed in Slot 0 if you want to route the INTX CLK10 signal to the VXIbus CLK10 signal. The CLK10 Source Select jumpers on the VXI-MXI must be set to configure the VXI-MXI to receive the CLK10 because the INTX daughter card will now be sourcing the clock signal.
Configuration and Installation Reset Signal Select The VXI-MXI generates a 200 ms active low pulse both on power-up and when you press the pushbutton system reset switch on the front panel. Using the Reset Signal Select slide switch, you can route the pulse to either VMEbus signal ACFAIL* or SYSRESET*. See Figure 3-19.
Verify the following configuration considerations before installing the VXI-MXI: • If installing the VXI-MXI in a slot other than Slot 0, verify that you have changed the settings of the two VXIbus Slot 0 slide switches, the VME BTO Chain Position jumper, and the CLK10 Source Select jumpers.
C-size cards in D-size mainframes. 4. Insert the VXI-MXI into the slot of the mainframe by aligning the top and bottom of the card with the card guides inside the mainframe. Slowly push the VXI-MXI straight into the slot until it seats in the backplane receptacles.
When shutting down a system, you must ensure that all devices that could be adversely affected by unintended bus cycles or interrupts have their windows and interrupt mapping disabled. The VXI-MXI itself will not be affected during power-down; however, there may be devices in the same frame as the VXI-MXI that could be affected.
VMEbus SYSRESET signal is active. A hard reset clears all the registers on the VXI-MXI. A soft reset occurs when the RESET bit in the VXIbus Control Register is set. A soft reset clears signals that are asserted by bits in the configuration registers but does not clear configuration information stored in the configuration registers.
* The three INTX registers at offsets 12, 14, and 18 are only available on VXI-MXIs with the INTX daughter card option. On VXI-MXIs without the INTX option, the entire range between offsets 12 and 1C (inclusive) is VXI-MXI Reserved Space. VXI-MXI User Manual...
These bits indicate the device class of the VXIbus device as follows: 00 = Memory 01 = Extended 10 = Message-Based 11 = Register-Based The VXI-MXI is an extended device defined by National Instruments; therefore, these bits are configured in hardware as binary 01. 13-12r ADDR Address Space Bits...
Slot 0 devices. When the VXI-MXI is in Slot 0, bit 11 is 0 and its model code is hex 00FE. When the VXI-MXI is not in Slot 0, bit 11 is 1 and its model code is hex 08FE.
This register provides status information about this VXIbus device and provides a bit to force the VXI-MXI into a Soft Reset state. The RESET bit is cleared on a hard reset. Hard and soft resets have no effect on the other bits on this register.
Page 66
RESET Reset Bit When this bit is set, the VXI-MXI is forced into the Soft Reset state. When this bit is cleared, the VXI-MXI is in the normal operation state. This bit is readable and is cleared on a hard reset.
MODID6 MODID5 MODID4 MODID3 MODID2 MODID0 This register provides control and status of the MODID lines when the VXI-MXI is installed in Slot 0. Mnemonic Description 15-14r/w 0 Reserved Bits These bits are reserved and read back as zeros. Write a zero when writing to these bits.
Attributes: Read/Write This register defines the range of logical addresses that are mapped into and out of the VXI-MXI through the MXIbus. This register defines a configuration window in the upper 16 KB of A16 space. These bits are cleared on a hard reset.
Page 69
Logical Address Window Base Address Bits These bits, in conjunction with the LASIZE bits, define the base address of the Logical Address window for the VXI-MXI. The LASIZE bits indicate the number of LABASE bits that are most significant. LABASE7 is the most significant, and LABASE0 is the least.
Page 70
LAHIGH > range LALOW The VXIbus logical addresses mapped out of the VXI-MXI are the inverse of this range, that is, MXIbus logical addresses greater than or equal to the LAHIGH value or less than the LALOW value.
This register defines the range of addresses in the lower 48 KB of A16 space that is mapped into and out of the VXI-MXI through the MXIbus. Earlier versions of the VXI-MXI required the A16 window to be statically configured with a DIP switch. Now the A16 window can only be dynamically configured with this register.
Page 73
A16 Window Base Address Bits These bits, in conjunction with the A16SIZE bits, define the base address of the A16 window for the VXI-MXI. The A16SIZE bits indicate the number of A16BASE bits that are most significant. A16BASE7 is the most significant and A16BASE0 is the least.
Page 74
A16HIGH > range A16LOW The VXIbus A16 addresses mapped out of the VXI-MXI are the inverse of this range, that is, MXIbus A16 addresses greater than or equal to the A16HIGH value or less than the A16LOW value.
This register defines the range of addresses in A24 space that are mapped into and out of the VXI-MXI through the MXIbus. These bits are cleared on a hard reset. The CMODE bit in the MXIbus Control Register selects the format of this register. If the CMODE bit is 0 (default), a Base/Size window comparison is used to determine the range of addresses in the window.
Page 77
A24 Window Base Address Bits These bits, in conjunction with the A24SIZE bits, define the base address of the A24 window for the VXI-MXI. The A24SIZE bits indicate the number of A24BASE bits that are most significant. A24BASE7 is the most significant and A24BASE0 is the least.
Page 78
A24HIGH > range A24LOW The VXIbus A24 addresses mapped out of the VXI-MXI are the inverse of this range, that is, MXIbus A24 addresses greater than or equal to the A24HIGH value or less than the A24LOW value.
This register defines the range of addresses in A32 space that are mapped into and out of the VXI-MXI through the MXIbus. These bits are cleared on a hard reset. The CMODE bit in the MXIbus Control Register selects the format of this register. If the CMODE bit is 0 (default), a Base/Size window comparison is used to determine the range of addresses in the window.
Page 81
A32 Window Base Address Bits These bits, in conjunction with the A32SIZE bits, define the base address of the A32 window for the VXI-MXI. The A32SIZE bits indicate the number of A32BASE bits that are most significant. A32BASE7 is the most significant and A32BASE0 is the least.
Page 82
A32HIGH > range A32LOW The VXIbus A32 addresses mapped out of the VXI-MXI are the inverse of this range, that is, MXIbus A32 addresses greater than or equal to the A32HIGH value or less than the A32LOW value.
Attributes: Read only SUBCLASS These bits define the subclass of a VXIbus extended device. The VXI-MXI is a VXIbus Mainframe Extender. Such devices are assigned the subclass code hex FFFC. Hard and soft resets have no effect on this register.
Read/Modify Write Select Mode Bit This bit, along with the MXIbus Address Modifiers, selects how the VXI-MXI will treat a MXIbus cycle when the MXIbus Address Strobe is held low for multiple data transfers. This bit is cleared on hard and soft resets.
Page 91
MXSCTO MXIbus System Controller Timeout Status Bit If this VXI-MXI is the MXIbus System Controller, this bit is set if the VXI-MXI sent a MXIbus BERR on the last MXIbus transfer in response to a MXIbus System Controller Timeout. This bit is cleared when this register is read and on hard and soft resets.
Page 92
FAIR VXI-MXI Fairness Status Bit When this bit is set, the VXI-MXI is configured as a fair MXIbus requester. If this bit is cleared, the VXI-MXI is configured as an unfair MXIbus requester. FAIR is selected with slide switch S2.
Page 93
3r/w LNGMXSCTO Long MXIbus System Controller Timeout Bit When the VXI-MXI powers on, this bit is cleared and, if the VXI-MXI is the MXIbus System Controller, the MXIbus System Controller timeout is between 100 µs and 400 µs (selected by jumper W8).
Lock MXIbus or VXIbus Bit When this bit is set by a VXIbus device, the MXIbus is locked by that device as soon as the MXIbus is won by the VXI-MXI. When the MXIbus is locked, indivisible operations to remote resources can be performed across the MXIbus.
DRVECL1 DRVECL0 PULSE This register provides the logical address of the VXI-MXI and the status of the eight TTL Trigger lines on the VXIbus. This register is also used to drive the TTL and ECL Trigger lines individually. The bits in this register are cleared on hard and soft resets.
Description 15-13r/w LINT[3-1] Local Interrupt Line Bits These bits select the VMEbus interrupt request line onto which the local VXI-MXI interrupts are routed. The local interrupts are BKOFF, TRIGINT, ACFAIL, and SYSFAIL. LINT3 LINT2 LINT1 VMEbus Interrupt Request Line Local Interrupt Disabled...
TRIG7DIR TRIG6DIR TRIG5DIR TRIG4DIR TRIG3DIR TRIG2DIR TRIG1DIR TRIG0DIR This register maps the VXIbus TTL Trigger lines to and from the Trigger In and Trigger Out SMB connectors on the front panel of the VXI-MXI. These bits are cleared on a hard reset. Mnemonic...
MXIbus link. The address mapping windows on the VXI-MXI can be configured to have a Base/Size format or a High/Low format. The CMODE bit in the MXIbus Control Register selects which format the mapping windows use.
VXIbus mainframe on Level 1, you must change the logical addresses of both VXI-MXI interfaces so that they are not at the default of 1. Select a logical address that is greater than or equal to the number of logical addresses required by the mainframe.
Figure 5-5. Notice that the system does not take up as much of the logical address space as the Base/Size method of configuration because address requirements do not have to occupy blocks in powers of two. With High/Low configuration, each VXI-MXI window can be configured for exactly the amount of address space the mainframe needs.
Table 5-3. Next, assign the A16 space, starting with the root device and working down the VXIbus/MXIbus system tree. To assist you in configuring the A16 window switches on the VXI-MXI interfaces in your system, the following pages include worksheets, an address map diagram, and an example.
Page 131
9. The next step is to determine the range of addresses, or base address, size, and direction of the A16 window for each VXI-MXI in the system. We first assign A16 space to the VXIbus RM Mainframe. From Figure 5-15, we see it needs 16 KB of A16 space, so we assign it the bottom 16 KB of A16 space, addresses 0 through 3FFF hex.
Programming Considerations Chapter 5 5000 through 5FFF to MXIbus #3. For the VXI-MXI connected to MXIbus #3, we set Base = 5000, Size = 4 because 4 KB = 256 * 2 , and the direction toward MXIbus #3, or Out.
Amount of A16 space required for this mainframe: Round up to next address break: MXIbus #1 First Level MXIbus Link: 8 KB + 512 Amount of A16 space required for devices connected to this VXI-MXI: Round up to next address break: 4000 A16 Window: Base: Size:...
Total amount of A16 space required for this window: Round up total amount to the next address size break: First Level VXI-MXI: A16 Window: Base: Size: Direction: Second Level VXI-MXI #1: A16 Window: Base: Size: Direction: Second Level VXI-MXI #2: A16 Window: Base:...
Total amount of A16 space required for this window: Round up total amount to the next address size break: First Level VXI-MXI: 5000 A16 Window: Base: Size: Direction: Second Level VXI-MXI #1: A16 Window: Base: Size: Direction: Second Level VXI-MXI #2: A16 Window: Base: Size:...
Page 138
Resource Manager Mainframe: Amount of A16 space required for this mainframe: Round up to next address break: First Level MXIbus Link: Amount of A16 space required for devices connected to this VXI-MXI: Round up to next address break: A16 Window: Base: Size:...
Page 139
Total amount of A16 space required for this window: Round up total amount to the next address size break: First Level VXI-MXI: A16 Window: Base: Size: Direction: Second Level VXI-MXI #1: A16 Window: Base: Size: Direction: Second Level VXI-MXI #2: A16 Window: Base:...
Page 140
Total amount of A16 space required for this window: Round up total amount to the next address size break: First Level VXI-MXI: A16 Window: Base: Size: Direction: Second Level VXI-MXI #1: A16 Window: Base: Size: Direction: Second Level VXI-MXI #2: A16 Window: Base:...
Page 141
Total amount of A16 space required for this window: Round up total amount to the next address size break: First Level VXI-MXI: A16 Window: Base: Size: Direction: Second Level VXI-MXI #1: A16 Window: Base: Size: Direction: Second Level VXI-MXI #2: A16 Window: Base:...
Page 142
Total amount of A16 space required for this window: Round up total amount to the next address size break: First Level VXI-MXI: A16 Window: Base: Size: Direction: Second Level VXI-MXI #1: A16 Window: Base: Size: Direction: Second Level VXI-MXI #2: A16 Window: Base:...
VXIbus ID Register. If two devices share a logical address, they will both respond to an address access without any indication of an error. B. For each VXI-MXI found in the mainframe, starting with the lowest addressed VXI-MXI, the RM: Sets the VXI-MXI logical address window to map all of the logical address space outward and enables the window.
Repeats Step 2 recursively. c. Sets the VXI-MXI inward logical address mapping window to cover the range up to (but not including) the VXI-MXI with the next highest logical address that was found in the logical address space. Sets the VXI-MXI outward logical address mapping window to cover the range of the devices connected to that extender.
Page 145
VXI-MXIs at logical addresses 2 and 4 and moves DC devices to the lowest unused logical addresses (for example, 1, 3, 5, 6). 2. Enables the logical address window of the VXI-MXI found at logical address 2 for the entire outward mapping range of 0 to FF. Scans all logical addresses, skipping all previously encountered devices, and finds the VXI-MXI in VXIbus Mainframe #3, the VXI-MXI in VXIbus Mainframe #2, MXIbus Device A, and MXIbus Device B.
Device A (E0 to E3), and MXIbus Device B (E4). Enables the logical address window of the VXI-MXI at logical address 2 with an outward range of 80 to FF by writing the value 4180 hex to the Logical Address Window Register (Base/Size format).
MODID lines. In accordance with the VXIbus specification for a Slot 0 device, the VXI-MXI pulls up each MODID line with a 16.9 k resistor. When the VXI-MXI is not a Slot 0 device, the MODID0 line is pulled to ground with a 825 resistor.
VMEbus. When the LOCK bit in the Local Bus Lock Register is set by a MXIbus device, the VXI-MXI interface will not release the VMEbus once it is granted the bus (on the next transaction) until the LOCK bit is cleared by a MXIbus device.
When asserted, the trigger line indicates a Start signal. When unasserted, the trigger line indicates a Stop signal. The VXI-MXI can be configured either to drive its 10 MHz VXIbus CLK10 signal to other mainframes or to receive a 10 MHz CLK10 signal from another mainframe via the EXT CLK SMB connector on the front panel.
Page 151
VMEbus interrupt requests can be handled by an interrupt handler on another VMEbus device in the VXIbus mainframe or by an external device on the MXIbus. The VXI-MXI has IACK daisy- chain driver circuitry that passes interrupt acknowledge cycles not meant for the VXI-MXI to other interrupters in the VXIbus mainframe.
VXIbus mainframe by reading from a designated address in the MXIbus configuration space on the remote VXI-MXI. The external device must know which VMEbus interrupt level it is servicing and read from the appropriate address. Table 6-1 shows the designated addresses for VMEbus IRQ[7–1].
VXI-MXI Configuration Registers The VXI-MXI configuration registers are accessible from both the VXIbus and the MXIbus and are used to configure the VXI-MXI. These registers are described in detail in Chapter 4, Register Descriptions. When the VXI-MXI interface decodes a VMEbus address specifying the configuration space on the card, the least significant VMEbus address lines are used to specify the registers in configuration space and the VMEbus operation does not need to request control of the MXIbus.
The VMEbus address lines map directly to the MXIbus address lines. The VMEbus requires six address modifier lines, while MXIbus only defines five. The VMEbus address modifier lines map to the MXIbus address modifier lines as shown in Table 6-2. The VXI-MXI responds to the VMEbus address modifier codes shown in Table 6-3.
The MXIbus PAR* signal is generated and sent during the address portion of all MXIbus cycles initiated by the VXI-MXI. It is also generated and sent during the data portion of MXIbus master write cycles. When the VXI-MXI detects a parity error in the data transfer portion of a MXIbus read cycle, it asserts the VMEbus BERR* signal to indicate to the VMEbus host that the data read contains an error.
Mainframe VMEbus VMEbus Figure 6-2. Deadlock Situation If the VXI-MXI responds with a VMEbus BERR* to a transfer initiated by a VXIbus device, the transfer was not completed successfully. The following situations are possible reasons for an unsuccessful transfer: •...
MXIbus cycles. The VMEbus is not requested if the MXIbus address received has a parity error. Parity is also checked when MXIbus data is written to the VXI-MXI slave circuitry. If a parity error occurs, the bad data is not written to the VMEbus and a BERR is sent back to the MXIbus master.
An onboard slide switch sets whether or not the VXI-MXI interface board is the MXIbus System Controller. If it is the system controller, the VXI-MXI must be the first device in the MXIbus daisy-chain. Onboard arbitration circuitry transparently performs the MXIbus arbitration for the MXIbus chain.
Page 160
MXIbus. When the LOCK bit in the Local Bus Lock Register is set by a VXIbus device, the VXI-MXI interface will not release the MXIbus the next time it is granted the bus (on the next transaction) until the LOCK bit is cleared by a VXIbus device.
Page 161
Theory of Operation Chapter 6 For example, if the VXI-MXI owns the VMEbus and it receives a VMEbus bus request from another VXIbus device, the VXI-MXI continues holding the VMEbus and arbitrates for the MXIbus. When it wins the MXIbus, the VXI-MXI can then release the VMEbus so that another VMEbus requester can gain ownership of the VMEbus.
VXI-MXI and the INTX daughter card. Removing the Metal Enclosure from the VXI-MXI The VXI-MXI is housed in a metal enclosure to improve EMC performance and to provide easy handling. Because the enclosure includes cut-outs to facilitate changes to switch and jumper settings, it should not be necessary to remove it under normal circumstances.
VXI system. Figure E-2 shows the configuration of the VXI-MXI in Frame A. Figure E-3 shows the configuration of the VXI-MXI in Frame B. You can find more detailed drawings of each configurable jumper and switch in Chapter 3.
BTO Unit Notice that although the VXI-MXI in Frame A is not the VXI System Controller (not a Slot 0 device) it still has the VXI BTO unit. This VXI-MXI is, however, the MXIbus System Controller and therefore has the MXI BTO unit as well.
Filling out a copy of the Technical Support Form before contacting National Instruments helps us help you better and faster. National Instruments provides comprehensive technical assistance around the world. In the U.S. and Canada, applications engineers are available Monday through Friday from 8:00 a.m.
Page 186
National Instruments for technical support helps our applications engineers answer your questions more efficiently. If you are using any National Instruments hardware or software products related to this problem, include the configuration forms from their user manuals. Use additional pages if necessary.
Page 187
Completing this form accurately before contacting National Instruments for technical support helps our applications engineers answer your questions more efficiently.
Page 188
Other Products • Other MXIbus Devices in System Manufacturer Model Function Slot Logical Address • Other VXIbus Devices Manufacturer Model Function Slot Logical Address • Address Space(s) and Size(s) of Other Devices: _________________________________________________ _________________________________________________ _________________________________________________ _________________________________________________ • VXI Interrupt Level(s) of Other Devices: _________________________________________________ _________________________________________________ _________________________________________________...
Page 189
Documentation Comment Form National Instruments encourages you to comment on the documentation supplied with our products. This information helps us provide quality products to meet your needs. Title: VXI-MXI User Manual Edition Date: October 1993 Part Number: 320222-01 Please comment on the completeness, clarity, and organization of the manual.
Page 193
Daughter Card A board that plugs directly into the expansion connectors of another board. The VXI-MXI is available with or without a daughter card option called the INTX card. Deadlock Unresolved situation in which two devices are vying for the use of a resource.
Page 194
These devices have a subclass register within their configuration space that defines the type of extended device. The VXI-MXI is an extended class mainframe extender device. Fair Requester A MXIbus master that will not arbitrate for the MXIbus after releasing it until it detects the bus request signal inactive.
Page 195
INTX Interrupt and Timing Extension; a daughter card option that plugs into the two daughter card connectors on the VXI-MXI. It extendes the seven VMEbus interrupt lines, the eight VXIbus TTL trigger lines, the VXIbus CLK10 signal, and the VMEbus reset signals SYSRESET*, SYSFAIL*, and ACFAIL*.
Page 196
Mainframe Extender A device such as the VXI-MXI that interfaces a VXIbus mainframe to an interconnect bus. It routes bus transactions from the VXIbus to the interconnect bus or vice versa. A mainframe extender has a set of registers that defines the routing mechanisms for data transfers, interrupts, triggers, and utility bus signals, and has optional VXIbus Slot 0 capability.
Page 197
A device configured for installation in any slot in a VXIbus mainframe other than Slot 0. Installing such a device into Slot 0 can damage the device, the VXIbus backplane, or both. The VXI-MXI can be configured as either a Slot 0 device or a Non-Slot 0 device.
Page 198
MODID functions. Additional Slot 0 services include trigger control. Installing such a device into any other slot can damage the device, the VXIbus backplane, or both. The VXI-MXI can be configured as either a Slot 0 device or a Non-Slot 0 device.
Page 199
Soft Reset Occurs when the RESET bit in the VXIbus Control Register of the VXI-MXI is set. A soft reset clears signals that are asserted by bits in the configuration registers but does not clear configuration information stored in the configuration registers.
Page 203
EXT CLK SMB input/output, 3-20 DTB requester compliance level (ROR), 2-3 INTX CLK10 mapping, 3-20 to 3-22 DTRIG[7-0] bit, 4-39 factory default settings for VXI-MXI with INTX, 3-3 without INTX, 3-2 interlocked arbitration mode, 3-13 to 3-14 logical address, 3-6 to 3-7...
Page 204
4-47 interrupter compliance levels, 2-4 INTLCK bit, 4-33 INTX daughter card FAIR bit, 4-34 block diagram, 2-8 front panel of VXI-MXI interface module, cable connections, 3-27 CLK10 control, 2-9 functional description. See theory of CLK10 mapping, 3-20 to 3-22 operation.
Page 205
LABASE[7-0] bits, 4-11 master mode state machine. See MXIbus LADD[7-0] bit, 4-39 master mode state machine. LADIR bit, 4-10, 4-11 metal enclosure for VXI-MXI, removing, LAEN bit, 4-10, 4-11 3-4, C-1 LAHIGH[7-0] bits, 4-12 MIRQ[7-1]DIR bit, 4-37 to 4-38 LALOW[7-0] bits, 4-12...
Page 206
MXIbus IRQ Configuration Register, 4-37 to 4-38 MXIbus Lock Register, 4-36 OMS[2-0] bits, 4-41 to 4-42 MXIbus master mode state machine operation of VXI-MXI. See theory of deadlock situation, 6-10 operation. definition, 2-7 OTS[3-0] bits, 4-43 master to slave transfers, 6-7...
Page 207
VMEbus signals 4-41 to 4-44, 6-2 list of signals, 2-1 to 2-2 Trigger Synchronous Acknowledge VXI-MXI support for, 1-4 to 1-5 Register, 4-50 Size configuration format, 5-3 to 5-4 register maps, 4-2 to 4-3 slave mode state machine. See MXIbus resets, 4-1 slave mode state machine.
Page 208
Index SUBCLASS bit, 4-30 requester and arbiter circuitry, 6-2 Subclass Register, 4-30 VXI-MXI configuration registers, 6-6 switches. See jumpers and switches. VXIbus System Controller functions, 6-1 Synchronous protocol, 6-3 timing specifications, A-3 SYSFAIL bit, 4-46 transceivers. See MXIbus transceivers; SYSFAIL signal, 2-5, 6-3 VMEbus transceivers.
Page 209
VME BTO circuitry. VMEbus transceivers address and address modifier transceivers, 2-5, 6-1 control signal transceivers, 2-5, 6-2 data transceivers, 2-5, 6-1 VXI-MXI interface module. See also INTX daughter card. block diagram, 2-6 definition, 1-1, 1-4 electrical characteristics, 2-1 to 2-2 features, 1-4...