Welcome, Guest. Please login or register.

Author Topic: SCSI madness  (Read 13150 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline freqmax

  • Hero Member
  • *****
  • Join Date: Mar 2006
  • Posts: 2179
    • Show all replies
Re: SCSI madness
« on: April 24, 2011, 12:03:02 PM »
Some basic rules:

* Always have terminators at both ends of your physical bus-cable. No stubs!

Terminator--Device--Device--Device--Device--Terminator

* Check termination on the devices and their ID. Get hold of documentation. Ie NO device in the middle of the bus-cable may have their termination enabled.

* Beware of older devices that doesn't implement termination power with correct polarity. These devices has to have their bus-power disabled!

* Check that "parity enable" is set to the same on all devices. It's usually disabled.

* Controller is usually located at ID=7 but can vary.

* Highest ID have the highest priority. Except for wide-scsi where the priority is 7..0 and then 15..8.

* ID numbers only matters for software. So the numbering doesn't have to follow how the drives are physically attached.

Things that are nice about SCSI is that you can have many drives and the host interface can query them about just about anything. Sector ordering is consistent such that you can swap drives with friends. The electrical interface is consistent and electrically sound. SCSI drives usually have much higher build quality. Track-reordering makes it faster. It's even possible to let one controller boot from another controller if one wishes to do so ;), or have more than one controller use the same disc. On the host side, transfers are usually implemented with DMA and other efficient means etc..
« Last Edit: April 24, 2011, 12:13:20 PM by freqmax »
 

Offline freqmax

  • Hero Member
  • *****
  • Join Date: Mar 2006
  • Posts: 2179
    • Show all replies
Re: SCSI madness
« Reply #1 on: April 28, 2011, 12:11:48 AM »
Besides even if there's no more SCSI/IDE drives to get hold of. One can replace them the same way as has done with the floppy. Besides there's always the possibility to use a unix machine (PC) as a fileserver.

It's also possible to create a SCSI <-> S-ATA bridge with an FPGA like Spartan-6, even in their low-end versions.

In the end it's all about how the communication link is done. What kind of hardware assitance it uses (DMA) and time slots. Like idle priority, fast mem only, chip mem etc.. If one reads the technical specification it becomes obvious that U160 still beats S-ATA in reliability.