VMEbus Interface
The VMEbus interface provides VME64 data transfers as well as a fully functional high performance 32-
bit VMEbus interface as defined by the IEEE 1014 Rev C VMEbus Specification. It is based upon the
SCV64 from Newbridge Microsystems.
See the SCV64 User Manual, the Newbridge Microsystems data book for more information.
SCV64
The SCV64 is a 64-bit interface to the VMEbus address and data buses with the local PT-VME161 bus.
It may act as a VMEbus Master or Slave. The local DRAM and EPAK address spaces of the PT-VME161
are accessible to a VMEbus Master through the SCV64. The SCV64 is also capable of DMA transfers
between local memory (DRAM or EPAK) and the VMEbus.
VME 64 Transfers
VME64 is a newly defined capability of the VMEbus. VMEbus Block Transfer mode (BLT) only uses
the address bus during the first transfer cycle to pass the start address of the transfer. The slave is respon-
sible for latching this address and incrementing it internally as subsequent data arrives. As a result the
address lines on the VMEbus are unused during all but the first transfer. Data is passed every transfer
cycle on the data bus.
The 64 bit Multiplexed Block Transfer (D64MBLT) mode makes a minor change to the first cycle and
takes advantage of the address bus being otherwise unused during a block transfer data phase. A MBLT
cycle is divided into two phases, address and data. During the first transfer cycle address only is passed
and on all subsequent cycles data is passed. The combination of the 32 data lines, 31 address lines, and
the [LWORD*] signal provide a 64 bit path on the VMEbus. A double longword can then be transferred
on each Data Strobe/Data Acknowledge handshake. The address phase can be either A32 or A64. A32
transfers pass the address normally (on the address bus) and the 32 data lines are unused, A64 transfers
pass the high order 32 bits of the 64 bit address on the data lines. During the data phase the 31 address
lines, and the [LWORD*] signal are used to pass the high order 32 bits of the 64 bit data. Specific
Address Modifiers are used to identify A64:D64MBLT and A32:D64MBLT cycles.
Transfer Modes
The SCV64 is capable of two operational modes: "decoupled" and the traditional "atomic". The
decoupled mode takes full advantage of the VMEbus bandwidth by using the receive and transmit
FIFOs, built into the chip, that decouple the local bus from the VMEbus. The FIFOs immediately
accept writes from one bus, release that bus for use, then finish the write to the destination bus. In
atomic mode the SCV64 bypasses the FIFOs, simply buffering the data and address to the destina-
tion bus, forcing any associated wait states back to the source bus.
All read, read-modify-write, and interrupt acknowledge cycles are atomic. To preserve data integ-
rity, atomic cycles are not performed until all write cycles queued ahead of the atomic cycle are
completed.
Decoupled
This feature allows transfers on the VMEbus to be completely "decoupled" from any latencies
incurred on the local bus. VMEbus transfers can proceed at a rate that is determined strictly by
Extensible Single Board Computer/Controller User's Manual 33
Performance Computer
Need help?
Do you have a question about the PT-VME161 and is the answer not in the manual?