Title: The IDE/ATA Interface
1The IDE/ATA Interface
- How can our mini-Operating System, executing in
protected mode, access the hard disk?
2The EDD services
- So far we have relied upon the Extended Disk
Drive service-functions (available in real-mode
via int 0x13) to perform any transfers of data
between main memory and our computer systems
hard disk - But these service-functions in ROM-BIOS are
designed to be executed in real-mode - Can we achieve their effects when PE1?
3Persistent data storage
- Any operating system we might design, no matter
how minimal, would need to offer a way to write
and to read persistent data, organized into
some kind of file system that is maintained on
a secondary storage device, such as a hard disk
or a diskette
4Hardware interfacing
- Modern computer platforms are expected to provide
a specially designed peripheral processor, the
hard disk controller, which can be programmed by
system software to carry out data-transfers
between a disk and the computers primary memory - The programming interface for hard disk
controllers continues to evolve, but a stable set
of standard capabilities exists
5A few cautions
- Our classroom and laboratory computers are shared
by many users who are taking various computer
sciences courses - Writing to the hard disk in a careless way can do
damage to the operating systems (making a machine
completely unusable) - In your early experiments you will need to use
great caution to avoid corrupting vital areas of
these shared hard disks!
6Typical Chipset Layout
CPU Central Processing Unit
MCH Memory Controller Hub (Northbridge)
DRAM Dynamic Random Access Memory
Graphics Controller
NIC Network Interface Controller
ICH I/O Controller Hub (Southbridge)
AC Audio Controller
Multimedia Controller
HDC Hard Disk Controller
Firmware Hub
Timer
Keyboard
Mouse
Clock
7Which I/O ports?
- The disk-controller on our USF systems is a
component within the I/O-Controller Hub - The port-addresses used for accessing it are
assigned by the ROM-BIOS during the system-
startup process and are stored in certain
Base-Address registers within the PCI
Configuration Space for Intels SATA Controller
component of the ICH device
8Tools we used
- We used our pciprobe.cpp application to perform
a PCI bus scan and report all the PCI devices
which our system contains - We used the PCI CLASS-CODE for SATA Mass Storage
devices (code 0x010601) to identify the
hard-disks controller device - We wrote an LKM (Linux Kernel Module) that shows
the PCI Configuration Space
9BAR field-formats
31
15
0
i/o-port address
1
0
reserved
I/O Space Indicator
31
7 6 5
4 3 2 1 0
memory address
0
Type
P R E F
0
0
0
Memory Space Indicator
10SATA Controller BARs
IDE Command-Block for Primary Drive
BAR0 BAR1 BAR2 BAR3 BAR4 BAR5
IDE Control-Block for Primary Drive
IDE Command-Block for Secondary Drive
IDE Control-Block for Secondary Drive
DMA Control-Block
11Fixed-Size blocks
- All data-transfers to and from the hard disk are
comprised of fixed-size blocks called sectors
(whose size equals 512 bytes) - On modern hard disks, these sectors are
identified by sector-numbers starting at 0 - This scheme for addressing disk sectors is known
as Logical Block Addressing (LBA) - So the hard disk is just an array of sectors
12Platform-specific parameters
- Although older PCs used some standard I/O
port-addresses for communicating with their Disk
Controllers, newer PCs like ours allow these
port-addresses to be assigned dynamically during
the systems startup - To keep our demonstration-code as short and
uncluttered as possible, we will hard-code the
port-numbers our machines use
13The ATA/IDE Interface
- All communication between our driver and the Hard
Disk Controller is performed with in and out
instructions that refer to ports - Older PCs had standard i/o port-numbers for
communicating with the Disk Controller - But newer PCs assign these dynamically
14IDE Command Block registers
- When reading
- Data
- Error
- Sector Count
- LBA Low
- LBA Mid
- LBA High
- Device
- Status
- When writing
- Data
- Features
- Sector Count
- LBA Low
- LBA Mid
- LBA High
- Device
- Command
15IDE Control Block Registers
- When reading
- Alternate Status
- When writing
- Device Control
INCRITS InterNational Committee on Information
Technology Standards Committee T-13
16Bus Master DMA
- When reading
- Primary DMA Control
- Primary DMA Status
- Primary PRD Pointer
- When writing
- Primary DMA Control
- Primary DMA Status
- Primary PRD Pointer
PRD Physical Region Descriptor
INTEL ICH7 I/O Controller Hub Datasheet SATA
Controller Registers
17Two I/O design-paradigms
- PIO Programmed I/O for reading
- The cpu outputs parameters to the controller
- The cpu waits till the data becomes available
- The cpu transfers the data into main memory
- DMA Direct Memory Access for reading
- The cpu outputs parameters to the controller
- The cpu activates the DMA engine to begin
- The cpu deactivates the DMA engine to end
18PIO algorithm overview
- First select the device to read from
- Wait until the controller is not busy and does
not have any data that it wants to transfer - Write to Command Blocks Device register to
select the disk to send the command to - Wait until the controller indicates that it is
ready to receive your new command
19PIO overview (continued)
- Place the commands parameters into the
appropriate Command Block registers - Put command-code in Command register
- Then wait until the controller indicates that it
has read the requested sectors data and is ready
for you to transfer it into memory - Use a loop to input 256 words (one sector) from
the Command Blocks Data register
20PIO overview (conclusion)
- After you have transferred a sector, check the
Controller Status to see if there were any errors
(if so read the Error register) - To implement this algorithm, we need to look at
the meaning of some individual bits in the Status
register (and Error register)
21Status register (cmd7)
7 6 5 4 3
2 1 0
BSY
DRDY
DF
DRQ
ERR
Legend BSY (Device still Busy with prior
command) 1yes, 0no DRDY (Device is Ready for
a new command) 1yes, 0no DF (Device Fault
command cannot finish) 1yes, 0no DRQ
(Data-transfer is currently Requested) 1yes,
0no ERR (Error information is in Error
Register) 1 yes, 0no
22Device register (cmd6)
7 6 5 4 3
2 1 0
1
LBA (1)
1
DEV (0/1)
Sector-ID 27..24
Legend LBA (Logical Block Addressing) 1yes,
0no DEV (Device selection) 1slave, 0master
Sector-ID Most significant 4-bits of 28-bit
Sector-Address
23Error register (cmd1)
7 6 5 4 3
2 1 0
UNC
MC
IDNF
MCR
ABRT
NM
Legend UNC (Data error was UnCorrectable)
1yes, 0no MC (Media was Changed) 1yes,
0no IDNF (ID Not Found) 1yes, 0no MCR
(Media Change was Requested) 1yes, 0no ABRT
(Command was Aborted) 1 yes, 0no NM (No
Media was present) 1yes, 0no
24Device Control register (ctl2)
7 6 5 4 3
2 1 0
HOB
0
0
0
0
SRST
nIEN
0
Legend HOB (High-Order Byte) 1yes, 0no
SRST (Software Reset requested) 1yes, 0no
nIEN (negate Interrupt Enabled) 1yes,
0no NOTE The HOB-bit is unimplemented on our
machines it is for large-capacity disks that
require 44-bit sector-addresses
25Advantage of DMA
- For a multiprogramming operating system that
employs timesharing to concurrently execute
multiple tasks, there is an obvious advantage in
offloading the data-transfer step to a
peripheral processor - It frees the CPU to do work on other tasks during
the time-interval when the data is actually being
transferred
26DMA Command register
7 6 5 4 3
2 1 0
0
0
0
0
Read/ Write
0
0
Start /Stop
Legend Start/Stop 1 Start DMA transfer 0
Stop DMA transfer Read/Write 1 Read to
memory 0 Write from memory
27DMA Status register
7 6 5 4 3
2 1 0
PRDIS
-
-
0
0
INT
ERR
ACT
Legend ACT (DMA engine is currectly Active)
1 yes 0 no ERR (The controller encountered
an Error) 1yes 0no INT (The controller
generated an Interrupt 1yes 0no PRDIS (PRD
Interrupt Status) 1active, 0inactive
Software clears these labeled bits by writing 1s
to them
28PRD Pointer register
31
0
Physical memory-address of the PRD Table (must be
quadword aligned)
Each PRD (Physical Region Descriptor) consists of
these three fields
Base-address of the physical region
bytes 3..0
Size of the region
Reserved (0)
E O T
bytes 7..4
NOTE The total size of the PRD Table cannot
exceed 64KB
29DMA algorithm overview
- First select the device to read from
- Wait until the controller is not busy and does
not have any data that it wants to transfer - Write to Command Blocks Device register to
select the disk to send the command to - Wait until the controller indicates that it is
ready to receive your new command - NOTE This step is the same as for PIO
30DMA overview (continued)
- Engage the DMA engine for writing to memory by
outputting 0x08 to the DMA Command Port - Clear the labeled bits in the DMA Status register
- Place the commands parameters into the
appropriate IDE Command Block registers - Put command-code in IDE Command register
- Activate the DMA data-transfer by outputting 0x09
to the DMA Command register - Then wait until the DMA Status register indicates
that the DMA data-transfer has been completed
31DMA algorithm (concluded)
- Turn off the DMA engine by writing 0x08 to the
DMA Command register (to clear ACT) - Clear the labeled bits in the DMA Status register
(by writing 1s to those bits) - Read the IDE Status register (to clear any
interrupt from the IDE Controller), and if bit 0
is set (indicating some error-information is
available), then read IDE Error register
32DMA demo satademo.s
- We created this example showing how to program
the Disk-Drive controller while in protected mode
to read in the hard disks Master Boot Record and
then display its four Partition-Table entries - It shows how to read a disk-sector using the
hardwares DMA capability
33In-class exercise
- Use our satainfo.c Linux module to learn which
i/o-port addresses are assigned to Intels SATA
Controller on the machines in our classroom - Then modify the code in our satademo.s
source-file so that it can be used to display the
Partition-Tables entries for a machine in our
classroom