Ratoc SCSI & RAID Devices Driver



SCSI long ruled the performance peripheral category for storage and other devices. With many advantages over competing busses, including flexibility, speed, and reliability, SCSI devices are found everywhere. However, as computing platforms move towards cheaper internal busses and serial busses in general, finding SCSI host adapters capable of interfacing with older SCSI devices has become difficult. SCSI itself is transitioning to SAS (Serial Attached SCSI). On the newer desktop realm, the few PCIe SCSI host adapters are expensive. For newer laptops, there aren't any ExpressCard to SCSI host adapters we are aware of. This brings us to SCSI host adapters utilizing external busses like high performance FireWire and prosaic USB. While Ratoc's FireWire and USB to SCSI adapters have been on the market for quite some time, they are beginning to grow in popularity since they are an inexpensive and accessible way to work with older SCSI devices. This document is intended to clear up some of the confusion over deploying Ratoc adapters with SCSI devices.

  1. Ratoc Scsi & Raid Devices Driver Updater
  2. Ratoc SCSI & RAID Devices Driver
  3. Ratoc Scsi To Firewire Adapter
  4. Ratoc Scsi & Raid Devices Driver Win 7
  5. Ratoc Scsi & Raid Devices Driver Download
FireWire To Ultra SCSI
FW-USCSI-01
Ratoc FireWire to Ultra SCSI Converter
FireWire to Ultra SCSI adapters have the advantage of a much faster host connection than USB, and FireWire is superior to USB in every regard.
USB To Ultra SCSI
USB-USCSI-01
Ratoc USB 2.0 to Ultra SCSI Converter
USB 2.0 to Ultra SCSI adapters can be used with a number of SCSI devices.
  • Re: Looking for drivers for AMD-RAID Configuration SCSI Processor Device First of all, that's a typo on my part, it's actually the Alienware 15 R3. That said, things did finally get worked out, but not without a bit of pain and suffering.
  • This driver package supports the operating system/boot device included in the RAID array and standalone NVMe boot device with a separate SATA RAID storage array. Package Contents. This Software package contains various independent drivers (Column 1) designed to support the following Microsoft® Windows® platforms (Column 2).
Ratoc SCSI & RAID Devices driver
USB To Ultra Wide SCSI
USB-UWSCSI-01
Ratoc USB 2.0 to Ultra Wide SCSI Converter U2SCX-LVD
USB 2.0 to Ultra SCSI adapters can be used with Ultra Wide SCSI Devices.

Dell-sas-hba-12gbps Dell EMC Host Bus Adapter User's Guide HBA330 and External 12 Gbps SAS HBA overview. This driver package supports the operating system/boot device included in the RAID array and standalone NVMe boot device with a separate SATA RAID storage array. Supported RAID Levels RAID 0,1,10 for both NVMe and SATA RAID on the above listed AMD products.


Ratoc offers three SCSI host adapter models: The FR1SX (FW-USCSI-01) FireWire to Ultra SCSI, the U2SCX (USB-USCSI-01) USB to Ultra SCSI, and the U2SCX-LVD (USB-UWSCSI-01) USB to Ultra Wide SCSI. The FR1SX and U2SCX feature a HD-50 connector and are native Ultra SCSI devices. They are backwards and forward compatible with many other SCSI standards when used with connector adapters. While both rated to handle Ultra SCSI throughput of 20MB/s, the FR1SX tends to realize much better sustained throughput since FireWire isn't hampered by USB 2.0's CPU utilization overhead. The U2SCX-LVD features a HD-68 connector and is a native Ultra Wide SCSI device. It is also backward and forward compatible with many other SCSI standards when used with connector adapters. U2SCX-LVD is rated as handling Ultra Wide SCSI throughput of 40MB/s, however this maximum is doubtful since nearly any real world benchmark of USB 2.0 sustained throughput maxes out at around 33MB/s. That said, it is faster than the U2SCX, albeit considerably more expensive. When the better performance of the U2SCX-LVD isn't paramount, many customers prefer the U2SCX with a High Density 50F to High Density 68M Adapter combination over the U2SCX-LVD since is over $150 cheaper.

Termination Power or Term Power

All Ratoc SCSI host adapters require power to operate. That power is supplied either by an optional (purchased separately) AC adapter, or through drawing power off the SCSI buses' Term Power. In order to use Term Power, the SCSI device the Ratoc adapter is connected to must provide it. This invariably brings up two questions: what is Term Power, and does my device provide it? Answering the first question, according to the SCSI Trade Association:

'Terminators are powered from the 'term power' line on the SCSI bus. Term power can come from any device on the bus, and is provided by either the host, a drive on the bus, the backplane, or any combination thereof. Term power is provided through a diode and fuse - historically - the drop across the diode and cable allows for a term power range of 4.0 to 5.25 volts.'

As for the second question one must consult with the SCSI device's manufacturer or documentation. If the SCSI device doesn't provide Termination Power, then purchase the optional PS-5V2A 5VDC 2A External Power Supply/Adapter ST (USB/SCSI) power supply, or find an AC adapter with the same specifications at a local supplier.

Bear in mind termination (ie. terminating resistors) and termination power are not the same thing. The presence of an external terminating resistor, or a switch for an internal terminating resistor, have no bearing or whether a SCSI device provides termination power.

SCSI Connectors

Ratoc Scsi & Raid Devices Driver Updater

There has been a whole range of SCSI connectors over the years. Part of the confusion people run into is that there is overlap between SCSI standards and connectors. In other words, several connectors are applicable to single SCSI standards. As this document focuses on device compatibility with Ratoc SCSI adapters, it will not address internal SCSI connectors. While roughly ten different external SCSI connectors exist, there are four in particular that are the most commonly found. The following drawings depict the four more common SCSI connectors with the types featured on Ratoc's host adapters indicated in parenthesis.

If your SCSI device's connection doesn't match the connector present on a Ratoc host adapter, then a low cost adapter plug employed between the connectors will allow its use. Synchrotech carries three types of adapters that take the FR1SX and U2SCX HD-50 connector and provide an alternate connector on the other side. Synchrotech doesn't stock any converters for the U2SCX-LVD since it is typically used with 68-pin LVD type devices to begin with.

Using the Ratoc FR1SX or U2SCX with a SCSI device featuring a HD50F

Ratoc SCSI & RAID Devices Driver

Ratoc's FR1SX or U2SCX plug directly into SCSI devices featuring female HD50 (50 pin) connectors.

Using the Ratoc FR1SX or U2SCX with a SCSI device featuring a C50F

To use Ratoc's FR1SX or U2SCX with a SCSI device featuring a female C50 (50 pin Centronics style) connector, use the SCSI-RCL3005 High Density 50F to Centronics 50M adapter (Ultra to Fast SCSI I/II).
The bottom four images are the SCSI-RCL3005 pin-outs as a line drawing on the left and a photograph on the right. One side of the connector receives the FR1SX or U2SCX (images in top row) and the other side plugs into the SCSI peripheral (images in bottom row).

Ratoc SCSI & RAID Devices Driver

Using the Ratoc FR1SX or U2SCX with a SCSI device featuring a HD68F

To use Ratoc's FR1SX or U2SCX with a SCSI device featuring a female HD68 (68 pin) connector, use the SCSI-RCL3068 High Density 50F to High Density 68M Adapter (Ultra to Ultra Wide/LVD SCSI).
The bottom four images are the SCSI-RCL3068 pin-outs as a line drawing on the left and a photograph on the right. One side of the connector receives the FR1SX or U2SCX (images in top row) and the other side plugs into the SCSI peripheral (images in bottom row).

Using the Ratoc FR1SX or U2SCX with a SCSI device featuring a DB25F

To use Ratoc's FR1SX or U2SCX with a SCSI device featuring a female DB25 (25 pin 'Mac' style) connector, use the SCSI-RCL3025 High Density 50F to D-Sub 25M Adapter (Ultra to Fast SCSI I/II Mac).
The bottom four images are the SCSI-RCL3025 pin-outs as a line drawing on the left and a photograph on the right. One side of the connector receives the FR1SX or U2SCX (images in top row) and the other side plugs into the SCSI peripheral (images in bottom row).

Using the Ratoc host adapters with other types of SCSI connectors

There are other types of SCSI connectors, converter plugs, and gender changers on the market. Some companies to investigate for alternate connectors and converters are Granite Digital, The Mate Company, and Paralan Corporation. There are several to choose from and the preceding list is provided as a service, not an endorsement or recommendation.

Important FR1SX FireWire to Ultra SCSI Information

Before purchasing the FR1SXFireWire to Ultra SCSI host adapter, check Ratoc's system requirements and compatibility lists carefully.

Important U2SCX USB 2.0 to Ultra SCSI Information

Before purchasing the U2SCXUSB 2.0 to Ultra SCSI host adapter, check Ratoc's system requirements and compatibility lists carefully.

Important U2SCX-LVD USB 2.0 to Ultra Wide SCSI Information

Before purchasing the U2SCX-LVDUSB 2.0 to Ultra Wide SCSI host adapter, check Ratoc's system requirements and compatibility lists carefully.

More Useful SCSI Information

Overview of SCSI Standards and Cables
http://www.scsita.org/terms/SCSI_Overview.html
Visual Guide to SCSI Connectors
http://www.scsita.org/aboutscsi/Pictures.html
The 7 Generations of SCSI
http://www.scsita.org/aboutscsi/7gen.html
Overview of SCSI Standards and Cables
http://www.scsita.org/aboutscsi/SCSI_Overview.html
SCSI Termination Tutorial
http://www.scsita.org/aboutscsi/SCSI_Termination_Tutorial.html
STA-Endorsed Terms and Terminology for SCSI
http://www.scsita.org/aboutscsi/SCSI_Termination_Tutorial.html#Table1

Ratoc FireWire and USB solutions for Internal SCSI Devices

The connectors on internal SCSI devices differ from those found on external devices. Further, pre SCA style devices also require power connectors (typically Molex style). None of the Ratoc FireWire or USB (FR1SX, U2SCX, or U2SCX-LVD) work with IDC Header or SCA internal SCSI devices.

A solution to this is to purchase and external enclosure for the internal SCSI device and then connect it to the host system using one of the Ratoc solution. External SCSI enclosures can be special ordered from specialty stores.

Controller Register Map¶

For RR44xx Intel IOP based adapters, the controller IOP is accessed via PCI BAR0 and BAR2

BAR0 offsetRegister
0x11C5CLink Interface IRQ Set
0x11C60Link Interface IRQ Clear
BAR2 offsetRegister
0x10Inbound Message Register 0
0x14Inbound Message Register 1
0x18Outbound Message Register 0
0x1COutbound Message Register 1
0x20Inbound Doorbell Register
0x24Inbound Interrupt Status Register
0x28Inbound Interrupt Mask Register
0x30Outbound Interrupt Status Register
0x34Outbound Interrupt Mask Register
0x40Inbound Queue Port
0x44Outbound Queue Port

For Intel IOP based adapters, the controller IOP is accessed via PCI BAR0:

BAR0 offsetRegister
0x10Inbound Message Register 0
0x14Inbound Message Register 1
0x18Outbound Message Register 0
0x1COutbound Message Register 1
0x20Inbound Doorbell Register
0x24Inbound Interrupt Status Register
0x28Inbound Interrupt Mask Register
0x30Outbound Interrupt Status Register
0x34Outbound Interrupt Mask Register
0x40Inbound Queue Port
0x44Outbound Queue Port

For Marvell not Frey IOP based adapters, the IOP is accessed via PCI BAR0 and BAR1:

BAR0 offsetRegister
0x20400Inbound Doorbell Register
0x20404Inbound Interrupt Mask Register
0x20408Outbound Doorbell Register
0x2040COutbound Interrupt Mask Register
BAR1 offsetRegister
0x0Inbound Queue Head Pointer
0x4Inbound Queue Tail Pointer
0x8Outbound Queue Head Pointer
0xCOutbound Queue Tail Pointer
0x10Inbound Message Register
0x14Outbound Message Register
0x40-0x1040Inbound Queue
0x1040-0x2040Outbound Queue

For Marvell Frey IOP based adapters, the IOP is accessed via PCI BAR0 and BAR1:

BAR0 offsetRegister
0x0IOP configuration information.
BAR1 offsetRegister
0x4000Inbound List Base Address Low
0x4004Inbound List Base Address High
0x4018Inbound List Write Pointer
0x402CInbound List Configuration and Control
0x4050Outbound List Base Address Low
0x4054Outbound List Base Address High
0x4058Outbound List Copy Pointer Shadow Base Address Low
0x405COutbound List Copy Pointer Shadow Base Address High
0x4088Outbound List Interrupt Cause
0x408COutbound List Interrupt Enable
0x1020CPCIe Function 0 Interrupt Enable
0x10400PCIe Function 0 to CPU Message A
0x10420CPU to PCIe Function 0 Message A
0x10480CPU to PCIe Function 0 Doorbell
0x10484CPU to PCIe Function 0 Doorbell Enable

I/O Request Workflow of Not Marvell Frey¶

All queued requests are handled via inbound/outbound queue port.A request packet can be allocated in either IOP or host memory.

To send a request to the controller:

  • Get a free request packet by reading the inbound queue port orallocate a free request in host DMA coherent memory.

    The value returned from the inbound queue port is an offsetrelative to the IOP BAR0.

    Requests allocated in host memory must be aligned on 32-bytes boundary.

  • Fill the packet.

  • Post the packet to IOP by writing it to inbound queue. For requestsallocated in IOP memory, write the offset to inbound queue port. Forrequests allocated in host memory, write (0x80000000|(bus_addr>>5))to the inbound queue port.

  • The IOP process the request. When the request is completed, itwill be put into outbound queue. An outbound interrupt will begenerated.

    For requests allocated in IOP memory, the request offset is posted tooutbound queue.

    For requests allocated in host memory, (0x80000000|(bus_addr>>5))is posted to the outbound queue. If IOP_REQUEST_FLAG_OUTPUT_CONTEXTflag is set in the request, the low 32-bit context value will beposted instead.

  • The host read the outbound queue and complete the request.

    For requests allocated in IOP memory, the host driver free the requestby writing it to the outbound queue.

Non-queued requests (reset/flush etc) can be sent via inbound messageregister 0. An outbound message with the same value indicates the completionof an inbound message.

I/O Request Workflow of Marvell Frey¶

All queued requests are handled via inbound/outbound list.

To send a request to the controller:

  • Allocate a free request in host DMA coherent memory.

    Requests allocated in host memory must be aligned on 32-bytes boundary.

  • Fill the request with index of the request in the flag.

    Fill a free inbound list unit with the physical address and the size ofthe request.

    Set up the inbound list write pointer with the index of previous unit,round to 0 if the index reaches the supported count of requests.

  • Post the inbound list writer pointer to IOP.

  • The IOP process the request. When the request is completed, the flag ofthe request with or-ed IOPMU_QUEUE_MASK_HOST_BITS will be put into afree outbound list unit and the index of the outbound list unit will beput into the copy pointer shadow register. An outbound interrupt will begenerated.

  • The host read the outbound list copy pointer shadow register and comparewith previous saved read pointer N. If they are different, the host willread the (N+1)th outbound list unit.

    The host get the index of the request from the (N+1)th outbound listunit and complete the request.

Non-queued requests (reset communication/reset/flush etc) can be sent via PCIeFunction 0 to CPU Message A register. The CPU to PCIe Function 0 Message registerwith the same value indicates the completion of message.

User-level Interface¶

Ratoc Scsi To Firewire Adapter

The driver exposes following sysfs attributes:

Ratoc Scsi & Raid Devices Driver Win 7

NAMER/WDescription
driver-versionRdriver version string
firmware-versionRfirmware version string
Ratoc SCSI & RAID Devices Driver

Copyright © 2006-2012 HighPoint Technologies, Inc. All Rights Reserved.

Ratoc Scsi & Raid Devices Driver Download

This file is distributed in the hope that it will be useful,but WITHOUT ANY WARRANTY; without even the implied warranty ofMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See theGNU General Public License for more details.