SATA: Difference between revisions

From OSDev.wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
Content added Content deleted
m (SPELLING! "suchas")
(Improved linkage)
Line 1: Line 1:
'''SATA''' Stands for "Serial AT Attachment", and is the current leading standard for harddrives and optical media, having succeeded the [[ATA|(Parallel) ATA]] interface. Practically all SATA drives can be used using either [[AHCI]] or [[ATA PIO Mode|ATA]]
Apparently, there are three supposedly definitive, conflicting standards for SATA. It may be best to wait for the industry to shake out a little more completely, before trying to write SATA drivers.

If you want to try anyway, then get the ATA7, and ATA8 technical docs from www.t13.org. Then maybe try paying $25 to get the technical specs from www.sata-io.org. Hopefully, the discrepancies between the standards aren't too bad.


==Introduction==
==Introduction==


SATA, short for Serial ATA, is a bus interface for communicating with mass storage devices (such as disk drives, optical drives, etc). SATA provides higher transfer rates than PATA and is backward compatible. If an OS does not recognize SATA, it can use drives like ordinary PATA drives with no issues. The SATA specification is split into three distinct protocol 'layers'.
SATA is a bus interface for communicating with mass storage devices (such as disk drives, optical drives, etc). The composition is mostly identical to PATA, where one controller connects to several devices using SATA cables. SATA wiring is also one-on-one instead of allowing more than one device to be connected to a single cable. When SATA was introduced, almost all host controllers were configured to masquerade as an PATA controller, needing no change from the existing disk drivers. The majority of SATA controllers also support [[AHCI]], which offers connecting more devices than PATA allows, and significant other advantages over the legacy protocol.

Computers that are currently shipped often are [[AHCI]] only, and backwards compatibility mode, if present, has to be manually enabled from the BIOS - a change that often comes with the cost of making the installed OSes unbootable.

The actual SATA specification is split into three distinct protocol 'layers'.


* Physical Layer - Information relating to the physical connectors, etc. Not especially relevant here.
* Physical Layer - Information relating to the physical connectors, etc. Not especially relevant here.
* Link Layer
* Link Layer
* Transport Layer
* Transport Layer

At the time of writing, there were three supposedly definitive, conflicting standards for SATA. It may be best to wait for the industry to shake out a little more completely, before trying to write SATA drivers.

If you want to try anyway, then get the ATA7, and ATA8 technical docs from www.t13.org. Then maybe try paying $25 to get the technical specs from www.sata-io.org. Hopefully, the discrepancies between the standards aren't too bad.


==Detection and Initialization==
==Detection and Initialization==


Send a standard IDENTIFY command to the drive (0xEC). The drive should respond with an error in the ERR bit of the Status Register, and a pair of "signature bytes". On the Primary ATA bus, you get the signature bytes by reading IO ports 0x1F4 and 0x1F5, and you should see values of 0x3C and 0xC3.
Send a standard IDENTIFY command to the drive (0xEC). The drive should respond with an error in the ERR bit of the Status Register, and a pair of "signature bytes". On the Primary ATA bus, you get the signature bytes by reading IO ports 0x1F4 and 0x1F5, and you should see values of 0x3C and 0xC3.

==x86 Examples==

==Comments==


==See Also==
==See Also==
Line 26: Line 28:
* http://www.ata-atapi.com -- Public Domain C driver sourcecode, including SATA, Busmatering DMA, ATAPI -- not perfect, but good.
* http://www.ata-atapi.com -- Public Domain C driver sourcecode, including SATA, Busmatering DMA, ATAPI -- not perfect, but good.



{{stub}}


[[Category:ATA]]
[[Category:ATA]]

Revision as of 10:30, 1 November 2014

SATA Stands for "Serial AT Attachment", and is the current leading standard for harddrives and optical media, having succeeded the (Parallel) ATA interface. Practically all SATA drives can be used using either AHCI or ATA

Introduction

SATA is a bus interface for communicating with mass storage devices (such as disk drives, optical drives, etc). The composition is mostly identical to PATA, where one controller connects to several devices using SATA cables. SATA wiring is also one-on-one instead of allowing more than one device to be connected to a single cable. When SATA was introduced, almost all host controllers were configured to masquerade as an PATA controller, needing no change from the existing disk drivers. The majority of SATA controllers also support AHCI, which offers connecting more devices than PATA allows, and significant other advantages over the legacy protocol.

Computers that are currently shipped often are AHCI only, and backwards compatibility mode, if present, has to be manually enabled from the BIOS - a change that often comes with the cost of making the installed OSes unbootable.

The actual SATA specification is split into three distinct protocol 'layers'.

  • Physical Layer - Information relating to the physical connectors, etc. Not especially relevant here.
  • Link Layer
  • Transport Layer

At the time of writing, there were three supposedly definitive, conflicting standards for SATA. It may be best to wait for the industry to shake out a little more completely, before trying to write SATA drivers.

If you want to try anyway, then get the ATA7, and ATA8 technical docs from www.t13.org. Then maybe try paying $25 to get the technical specs from www.sata-io.org. Hopefully, the discrepancies between the standards aren't too bad.

Detection and Initialization

Send a standard IDENTIFY command to the drive (0xEC). The drive should respond with an error in the ERR bit of the Status Register, and a pair of "signature bytes". On the Primary ATA bus, you get the signature bytes by reading IO ports 0x1F4 and 0x1F5, and you should see values of 0x3C and 0xC3.

See Also

AHCI

External Links