1. Manuals
  2. Brands
  3. Solflower Manuals
  4. Adapter
  5. SFPCI -VME SERIES
  6. User manual and installation manual

Solflower SFPCI -VME SERIES User Manual And Installation Manual

Pci-to-vmebus interface
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
SFPCI - VME SERIES
User's Manual
and Installation Guide
olflower
Computer, Inc.
SFPCI-VME SERIES User's Manual and Installation Guide
Solflower Computer, Inc
3511 Thomas Road, Ste-2
Santa Clara, CA 95054
(408) 982-8680, Fax (408) 982-8685
http://www.solflower.com
rev 2.0

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SFPCI -VME SERIES and is the answer not in the manual?

Questions and answers

Summary of Contents for Solflower SFPCI -VME SERIES

  • Page 1 SFPCI - VME SERIES User’s Manual and Installation Guide Solflower Computer, Inc olflower 3511 Thomas Road, Ste-2 Santa Clara, CA 95054 Computer, Inc. (408) 982-8680, Fax (408) 982-8685 http://www.solflower.com SFPCI-VME SERIES User’s Manual and Installation Guide rev 2.0...
  • Page 2 Solflower Computer, Inc. reserves the right to make changes to this document and any product described herein to improve reliability, function or design. Solflower Computer, Inc. does not assume any liability arising out of the application or use of any product or circuit described herein.

  • Page 3: Applicable Documents

    Overview Overview CHAPTE R 1 1.1 INTRODUCTION The SFPCI-VME series of products provide a PCI-to-VMEbus interface, and the capability of handling PCI master and slave functions. In addition, the series provide VMEbus arbiter function, built-in DMA engine on board, as well as other system controller functions of the VMEbus as described in the following sections.

  • Page 4: Unpacking Instructions

    Caution: Since electrostatic discharge may damage the printed circuit boards, do not remove the printed circuit boards from the static bags unless you are wearing grounding straps. --------------------------------------------------------------------------------------------------------------------- FIGURE 1 SFPCI-VME Components Cable PCI short card SF_PCI VME 6U card SF_VME 6U-VME Enclosure rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...

  • Page 5: Jumper Installation

    SFPCI-VME Series Installation SFPCI-VME Series CHAPTE R 2 Installation 2.1 Jumper Installation Due to pin count limitations between the PCI interface board and the VMEbus, only four (4) continuous interrupt levels may be selected out of the seven (7) possible VME bus interrupts.
  • Page 6 SFPCI-VME set for BG3 and BR3 Interrupt Level 1234 SF_VME Card AM CODE D&C D&F IRQn BGOUT Ready D&C D&F Interrupt SEL 4 3 2 1 7 6 5 4 3 2 1 0 RBRQ SF_PCI Card rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 7 SFPCI-VME Series Installation 2.1.2 VME Backplane Jumper Select The jumpers on VMEbus backplanes for connecting Bus Grand and interrupt acknowledge signals. Make sure these jumpers are removed from the slot in which the VME cards will be installed FIGURE 3 SFPCI-VME Enclosure with 6-Slot and 4-Slot Back-plane SLO T N U M B ER S lo t 4...
  • Page 8 A and the other two, hardwired with internal devices are PCI bus B. You can install PCI short card to any available PCI slot, but for best performance, the PCI short card should be installed in 64bit PCI slot (PCI bus A). rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 9 SFPCI-VME Series Installation FIGURE 4 SF_PCI card installation to Ultra AX SPARCengine PCI Bus B PCI Bus A PCI - VME 2.2.2 Install SF_PCI Card to SME Ultra AXi SPARCengine The Ultra AXi SPARCengine provides 6 PCI slots. They are all 32 bits, 33MHz, 5V only.
  • Page 10 SFPCI-VME Series Installation FIGURE 5 Ultra AXi Layout PCI bus A PCI bus B rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 11 SFPCI-VME Series Installation 2.2.3 Install SF_PCI Card to Sun Ultra 5, Ultra 10 The Sun Ultra 5 and Ultra 10 have 3 and 4 32 bit PCI slots respectively for expansion. PCI-VME can be installed in any available PCI slot without any restriction. PCI-VME card will detect Ultra5/10 PCI bus and adjust automatically to support 32 bit.
  • Page 12 SFPCI-VME Series Installation FIGURE 7 Install SF_PCI Card to Ultra10 rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 13 SFPCI-VME Series Installation 2.2.4 Install SF_PCI Card to Ultra 30 / Ultra 60 system The Ultra 30 / Ultra 60 system provide 4 PCI slots. You can install PCI Short Card to one of the slot 2, 3 or 4. Slot 1 is dedicated for 3.3V PCI card. Note that slot 2,3 and 4 share the same bus with internal storage and network devices.
  • Page 14 SFPCI-VME Series Installation FIGURE 9 Ultra 30 back side 2.2.5 Select SF_PCI slot on Ultra 450 system FIGURE 10 install SF_PCI card to Ultra 450 system rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 15 SFPCI-VME Series Installation There is total 10 PCI slots available on the Ultra 450 system. You can install PCI Card to any PCI slot except the 3.3V slot (slot 4,5 and 6). It is also not recommended to install PCI short card in slot 10. This slot is shared with to the internal devices such as SCSI and network.
  • Page 16 64 / 32 or 64 33 and 66 3.3 V JIO0 64 / 32 or 64 33 and 66 3.3 V JIO1 64 / 32 or 64 JIO1 64 / 32 or 64 rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 17 SFPCI-VME Series Installation FIGURE 12 V250 PCI slots location rev 2.0 SFPCI-VME SERIES User’s Guide and Installation Manual...
  • Page 18 Sun Blade 1500 PCI slots Slot Width (bits)/ Clock Rates DC Voltage/ Slot Card Type (bits) (MHz) Card Type 64 / 32 33 and 66 3.3 V 64 / 32 64 / 32 rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 19 The SF_VME card should be installed in slot 1as a system controller. There are a total of up to six VMEbus slots available in the Solflower VMEbus card cage SFVMEB1. Aside from the slot occupied by the SF_VME VMEbus interface board, all of the other slots are available for “customer owned”...

  • Page 20: Cable Installation

    Check the pins of the connector on both sides for broken or bent pins. If all pins are not bent or damaged, position the Solflower SF_VME card cage adjacent to the SPARC system, and install the cable between the PCIbus interface board and the VMEbus interface board.

  • Page 21: Architecture Description

    Architecture Description Architecture Description CHAPTE R 3 This section describes the general architecture of the PCI-VME chip Universe from Tundra Microcomputer Corporation. The Universe chip consists of three major modules: master module, slave module and interrupt module 3.1 VMEbus Interface VME Bus PCI Bus VMEbus Slave Channel...

  • Page 22: Pci Bus Interface

    (TXFIFO) and the PCI bus master receives data acknowledgment from the Universe with zero wait states. Meanwhile, the Universe obtains the VMEbus and writes the data to the VMEbus resource independent of the initiating PCI master. rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...

  • Page 23: Interrupter And Interrupt Handler

    Architecture Description To allow PCI masters to perform RMW and ADOH cycles, the Universe provides a Special Cycle Generator. The Special Cycle Generator can be used in combination with a VMEbus ownership function to guarantee PCI masters exclusive access to VMEbus resources over several VMEbus transactions.

  • Page 24: Dma Controller

    Linked-list operation is initiated through a pointer in an internal Universe register, but the inked-list itself resides in PCI bus memory. rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 25 Performance Consideration Performance Consideration CHAPTE R 4 As a VME bus bridge, the Universe’s most important function is passing data. This function resides in three of its channels: the PCI Slave Channel, VME Slave Channel, and the DMA Channel. Since each channel operates independently of the others and because each has its own unique characteristics, the following analysis reviews the data transfer performance for each channel.
  • Page 26 Coupled Write - non-block 420 ns - block 390ns Pre-fetched Read - VME slave response (1st data beat) (see coupled table) - VME slave response (other data beats) 65 ns rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 27 Performance Consideration TABLE 7 VME Slave Channel Performance Cycle Type Performance Decoupled Write - non-block slave response 130 ns - block slave response 65 ns Register Access - reads 360 ns - writes 240 ns TABLE 8 DMA Channel Performance Cycle Type Performance PCI Reads...
  • Page 28 PCI-VME performance is degraded by cable length between two adapter cards. The cable delay is shown in the preceding table. This delay time must be added to the timing calculation of the total system transfer per VME cycle. rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...

  • Page 29: Software Installation

    The PVME release 1.2 from Solflower is comprised of the following components: 5.3 Components The PVME release from Solflower, in addition to the binary device driver itself, is comprised of components for driver configuration and for illustrating testing and usage.

  • Page 30: Installation

    The devlink.tab file for PVME is appended to the file of that name in the /etc directory. We also make a backup file of the system /etc/devlink.tab file for safety’s sake. rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...

  • Page 31: Driver Installation

    Software Installation # cp /etc/devlink.tab /etc/devlink.tab.BAK # cat /etc/devlink.tab.BAK devlink.tab > /etc/devlink.tab 5.4.3 Driver Installation The driver is installed via the Solaris add_drv(1m) command. The syntax of the command used is: # add_drv -c vme -i ‘pvme “pci10e3,0”’ pvme This causes lines to be appended to the system file /etc/driver_aliases. Henceforth, if the UltraSPARC platform is shut down and rebooted, the PVME device driver will be automatically loaded until the user requests that the driver be removed from the system.
  • Page 32 5.6 pvme.conf - PVME Configuration File Options The PVME configuration file, pvme.conf, contains a number of optional settings that control the behavior and performance of the PVME VME-to-PCI bridge. 5.6.1 interrupt-priorities Syntax: interrupt-priorities=N; rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 33 SPARC interrupt at this time. Values that interrupt-priorities may assume are: 3, 4, 6, 8, and 9. As an example, the version of pvme.conf shipped by Solflower contains the line: interrupt-priorities=4; This sets the SPARC interrupt to IPL 4. This is the default.
  • Page 34 Note that not all VME devices support block-mode transfers. This feature should be enabled ONLY when you know that the target VME device supports block-mode. Example 2. pvme.conf: VME Data Transfer Control Directives Syntax: dma-blt= “on” | “off”; mem-blt= “on” | “off”; rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 35 Software Installation 5.6.3.4 VME Request and Arbitration Controls Example 3. pvme.conf: VME Request and Arbitration Controls Syntax: ctl-mode= “syscon”; arb-mode= “priority” | “round-robin”; request-level=0..3 request-mode= “demand” | “fair” release-mode: “release-on-request” | “release-when-done” bus-timeout=1..7; arb-timeout=1..2; dtack-enable= “rescind”; 5.6.3.5 VME Power Controls power-fail= “on”...
  • Page 36 The reason is that file descriptors that may be open to the user’s VME device driver are unknown to the PVME nexus driver. These file descriptors provide a “backdoor” to the rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 37 Software Installation PVME driver’s VME space if bus mappings to VME space have been established before the VMEbus went off-line. 5.6.6.2 VME leaf driver file descriptors Similarly, the PVME nexus driver has no way to detect the open(2) and close(2) operations on the user’s leaf driver.
  • Page 38 VME A32 space. Example 4, “User mapping of a VME address space,” on page 35 illustrate show this might be done. rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 39 Software Installation Example 4. User mapping of a VME address space char * vme_map(char * vme_device, int vme_off, int bytes) int fd; fd = open(vme_device, O_RDWR); printf("[Mapping 0x%x bytes at VME offset 0x%x]\n", bytes, vme_off); return (mmap((caddr_t)0, bytes, PROT_RW, MAP_SHARED, fd, vme_off)); #define VME_OFFSET 0x00100000 #define VME_BYTES 0x00010000 int main()

  • Page 40: Known Limitations

    Before you attempt to access the VMEbus with the CPU, you should make sure that no VMEbus device is performing a tranfer of data to PCI memory. Typically, a way to trigger this problem is to use mmap(2) to map a chunk of rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 41 Software Installation VME memory into a program’s address space and then to access the mmaped VME memory it while a VME device is performing a DMA transfer. Such simultaneous attempts to access the VMEbus should be avoided by the user as much as possible. rev 2.0 SFPCI-VME SERIES User’s Guide and Installation Manual...
  • Page 42 CHAPTE R 6 6.1 General The SF_VME board rev. F is a new member of the Solflower SFPCI-VME Adaptor series. It implements hardware byte swapping function to solve the problems inherent in joining Big and Little Endian buses. The SF_VME rev F is physically and electrically backward compatible with the older (rev D &...
  • Page 43 Byte Swapping Capability The content for ID register should reflects the revision of SF_VME Adaptor board. If this is a rev. F board, a read back from ID register will return 01000110, which is an “F” in ASCII. Application software can enable/disable byte swap logic “on-the-fly”. Once the byte swap function is set up by executing a command, byte swapping function is ready.
  • Page 44 4.7k Ohm Jumper U44 10 Ohm Jumper U45 10 Ohm Address=EF00 FIGURE 16 Jumper setting for address 0xDF00 4.7k Ohm 4.7k Ohm Jumper U44 10 Ohm Jumper U45 10 Ohm Address=DF00 rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...

  • Page 45: Theory Of Operation

    Byte Swapping Capability FIGURE 17 Jumper setting for address 0xCF00 4.7k Ohm 4.7k Ohm Jumper U44 10 Ohm Jumper U45 10 Ohm Address=CF00 6.2 Theory Of Operation The core of byte swapping function lies in the Xilinx XC95xx CPLD. This chipset responds to simple read/write in certain VME A16 address to set up byte swapping functions.
  • Page 46 "Host Data" is the result of the data being read from the VME into a register in the CPU. "Read Address (Host)" is the address read from the boards mapped into the host system's memory. "Width" is the number of bits read into the register. rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 47 Byte Swapping Capability 6.3.1 Byte Swapping for bytes: FIGURE 18 Byte Swapping For Bytes Devices D[31:24] D[15:8] / D[31:24] VD[7:0] D[23:16] D[7:0] / D[23:16] VD[15:8] D[15:8] VD[23:16] VD[31:24] D[7:0] Universe II PCI Bus DS1* DS0* A1 LW* DS1* DS0* A1 LW* Xilinx XC95xx Byte Swap...
  • Page 48 VME side. The swapping is done by swap the two bytes of the word as shown in Figure 19. Along with data, control signals such as DS1*, DS0*, A1, LW* are regenerated by Xilinx XC95xx to appropriate values before VME devices/memory. rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 49 Byte Swapping Capability 6.3.3 Byte swapping for long words FIGURE 20 Byte Swapping for long words Devices D[31:24] D[31:24] VD[7:0] D[23:16] D[23:16] VD[15:8] D[15:8] D[15:8] VD[23:16] D[7:0] VD[31:24] D[7:0] Universe II PCI Bus DS1* DS0* A1 LW* DS1* DS0* A1 LW* Xilinx XC95xx Byte Swap...
  • Page 50 Byte Swapping Capability 6.5 Byte Swapping Set Up Utility with Linux 2.4 Kernel Solflower provides an utility program called “swp_ctl” to enable/disable byte swapping function. With SF_VME rev F installed and flat cable connected, power on the VME crate and your host that runs Linux 2.4 Kernel. The "swp_ctl" program is used to enable/disable hardware byte-swapping.
  • Page 51 Byte Swapping Capability sta register: 0x05FF bid register: 0x46FF --0x46 is “F” in ASCII, stands for revision F. These are the default values of these registers. Here is the possible settings of the cmd register: Values Meaning ------------- 0x01FF Enable byte-swap 0x02FF Enable word-swap 0x04FF Enable lword-swap 0x08FF Disable all swapping...

  • Page 52: System Specifications

    The A32 permits address range from 0x00000000 to max available on the PCI address space. VME transfers dma to PCI memory is set for 1MB window and supports both A24 and A32 spaces rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...
  • Page 53 System Specifications: 7.1.6 AM codes PCI-VME supports the following AM codes Short supervisory access Standard supervisory data access Standard supervisory 64 bit block transfer Extended supervisory data access. Extended supervisory 64 bit block transfer Short supervisory access Standard supervisory data access Standard supervisory block transfer Extended supervisory data access.

  • Page 54: Cable Specifications

    7.3.2 4-slot VME enclosure dimension 4” x 16” x 16” (HxWxD) 250W selectable 110/220V AC 50/60Hz power supply 7.4 Cable specifications Cable are in 18”(1.5ft), 36” (3ft), 10ft, 15ft, 20ft, 24ft length, 100 pin flat ribbon shielded cable. rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...

  • Page 55: Warranty And Repair

    Solflower products are warranted against defective materials and workmanship within the warranty period of one year from date of invoice. Within the warranty period, Solflower will, free of charge, repair or replace any defective unit covered by this warranty, shipping prepaid. A Return of Materials Authorization number (RMA #) should be obtained from Solflower prior to the return of any defective product.
  • Page 56 Warranty and Repair rev 2.0 SFPCI -VME SERIES User’s Guide and Installation Manual...

This manual is also suitable for:

Sfpci-vme series

Table of Contents