ANSI INCITS 480-2011 Information Technology C BIOS Enhanced Disk Drive Specification - 4 (EDD-4).pdf

1、American National StandardDeveloped byfor Information Technology BIOS EnhancedDisk Drive Specification - 4(EDD-4)INCITS 480-2011INCITS 480-2011INCITS 480-2011American National Standardfor Information Technology BIOS Enhanced Disk Drive - 4(EDD-4)SecretariatInformation Technology Industry CouncilAppr

2、oved October 5, 2011American National Standards Institute, Inc.AbstractThis standard describes services currently in use on IA-32 and IA-64 compatible architecture personal computer systems. These services are provided by BIOS firmware to support hard disks up to 16 exabytes (16x1018bytes). This sta

3、ndard also provides BIOS level services for determining the relationship between BIOS device numbers and the physical mass storage devices attached to the personal computer. The services defined in this standard may be applied to mass storage devices with ATA, ATAPI, SCSI, USB, Fibre Channel, 1394,

4、I2O, and other interfaces. In addition, this standard defines the following:a) formatting required to make a CD or DVD bootable;b) INT 13h services used to access devices 8GB INT 13h Functions 156.1 Overview . 156.2 Data Structure . 156.3 Removable Media . 176.4 INT 13h Interface Subsets 176.4.1 Ove

5、rview . 176.4.2 Fixed Disk Access Subset 176.4.3 Device Locking and Ejecting Subset . 186.4.4 Enhanced Disk Drive (EDD) Support Subset 187 CD/DVD Boot 197.1 Overview . 19iiPage7.2 Boot Methods 217.2.1 Overview . 217.2.2 Emulation Process 217.2.3 No Emulation Boot 227.2.4 Floppy Boot . 227.2.5 Hard D

6、rive Boot 227.3 CD/DVD Format 237.3.1 Overview . 237.3.2 Boot Volume Descriptor (BVD) . 237.3.3 Validation Entry . 247.3.4 Initial/Default Entry 257.3.5 Section Header . 267.3.6 Section Entry 277.3.7 Section Entry Extension 288 INT 13h Function Definitions 298.1 Overview . 298.2 Reset Disk Subsystem

7、 (FN 00h) 308.3 Get Status of Last Operation (FN 01h) . 318.4 Read Sectors into Memory (FN 02h) 328.5 Write Sectors From Memory (FN 03h) 338.6 Verify Sectors (FN 04h) 348.7 Get Drive Parameters (FN 08h) 358.8 Read Buffer (FN 0Eh) . 368.9 Write Buffer (FN 0Fh) . 378.10 Get Disk Type (FN 15h) 388.11 S

8、et Media Type (FN 18h) . 398.12 Park Heads (FN 19h) 408.13 Identify Device Information (FN 25h) 418.14 Check Extensions Present (FN 41h) 428.15 Extended Read (FN 42h) 438.16 Extended Write (FN 43h) 448.17 Verify Sectors (FN 44h) 458.18 Lock/Unlock Media (FN 45h) 468.19 Eject Removable Media (FN 46h)

9、 . 478.20 Get Device Parameters (FN 48h) . 488.20.1 Overview . 488.20.2 Interface Path . 508.20.3 Device Path 518.20.4 Device Parameter Table Extension (DPTE) . 548.21 Get Extended Media Change Status (FN 49h) . 58iiiPage8.22 Initiate Disk Emulation (FN 4Ah) . 598.23 Terminate Disk Emulation (FN 4Bh

10、) . 628.24 Initiate Disk Emulation b) Logical Block Addressing (LBA);c) removes the requirement of using interrupt 41h/46h to point at the Fixed Disk Parameter Table information;d) makes location and configuration information available to operating systems that do not use the BIOS to access mass sto

11、rage devices;e) use data structures that apply to both IA-32 and IA-64 compatible architecture systems;f) use data structures that are able to address media capacities for the next 20 years; andg) boot from CD or DVD.This standard contains one informative annex, which is not considered part of the s

12、tandard.Requests for interpretation, suggestions for improvement and addenda, or defect reports are welcome. They should be sent to the INCITS Secretariat, Information Technology Industry Council, 1101 K Street NW, Suite 610, Washington, DC 20005.This standard was processed and approved for submitta

13、l to ANSI by InterNationalCommittee for Information Technology Standardization (INCITS). Committee approv-al of this standard does not necessarily imply that all committee members voted forapproval. At the time it approved this standard, INCITS had the following members:Don Wright, ChairJennifer Gar

14、ner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems, Inc Scott Foshee Steve Zilles (Alt.)AIM Global, Inc. . Steve HallidayApple Computer, Inc. . Kwok Lau Helene Workman (Alt.)David Singer (Alt.)Distributed Management Task Force John Crandall Jeff Hilland (Alt.)Electronic Indus

15、tries Alliance . Edward Mikoski, Jr. Henry Cuschieri (Alt.)EMC Corporation . Gary RobinsonFarance, Inc. Frank FaranceTimothy Schoechle (Alt.)GS1 US . Ray Delnicki Frank Sharkey (Alt.)James Chronowski (Alt.)Mary Wilson (Alt.)viOrganization Represented Name of RepresentativeHewlett-Packard Company Kar

16、en Higginbottom Paul Jeran (Alt.)IBM Corporation Gerald Lane Robert Weir (Alt.)Arnaud Le Hors (Alt.)Debra Boland (Alt.)Steve Holbrook (Alt.)Alexander Tarpinian (Alt.)IEEE . Terry deCourcelleJodie Haasz (Alt.)Bob Labelle (Alt.)Joan Woolery (Alt.)Intel Philip Wennblom Grace Wei (Alt.)Stephen Balogh (A

17、lt.)Lexmark International. Don Wright Dwight Lewis (Alt.)Paul Menard (Alt.)Jerry Thrasher (Alt.)Microsoft Corporation . Jim Hughes Dick Brackney (Alt.)John Calhoun (Alt.)National Institute of Standards b) The INT 13h interface allows more than two devices to be attached to a system but has no consis

18、tent method for storing the additional configuration parameters;c) The INT 13h interface does not define CHS-independent methods for addressing devices. The methods defined by the INT 13h interface are not device-geometry independent. A different method of address representation and operation is nee

19、ded;d) Methods of data transfer continue to be added to ATA devices. Capabilities such as, DMA modes, multi-sector data transfers and PIO modes are not reported to the operating system via the INT 13h interface;e) Systems require more than two storage devices, and with this requirement comes the req

20、uirement to assign the order in which the devices are to be accessed. The INT 13h interface does not provide this capability;f) The INT 13h interface does not make location and configuration information available to operating systems that do not use the BIOS to access mass storage devices;g) The INT

21、 13h interface does not provide a linkage between the BIOS device assignments on the operating system device letter assignments; andh) The INT 13h interface does not use data structures that apply to both IA-32 and IA-64 compatible architecture systems.INCITS 480-20112The set of AT Attachment standa

22、rds consists of this standard and the ATA implementation standards described in AT Attachment - 8 ATA/ATAPI Architecture Model (ATA8-AAM). Enhance Disk Drive - 4 (EDD-4) specifies a common set of procedures used to access or boot storage devices. Figure 1 shows the relationship of this standard to t

23、he other standards and related projects in the ATA and SCSI families of standards and specifications.Figure 1 ATA document relationships ATAttachment 8Architecture Model(ATA8-AAM)Packet deliveredcommand setsAT Attachment 8Parallel Transport(ATA8-APT)AT Attachment 8Serial Transport(ATA8-AST)ATA/ATAPI

24、 Command Set - 2 (ACS-2)EDD-4 and Related host standards and specificationsOtherrelateddevice specificationsINCITS 480-201132 Normative References2.1 GeneralThe standards list in 2.2, 2.3, and 2.4 contain provisions that, through reference in the text, constitute provisions of this standard. At the

25、time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the standards listed in 2.2, 2.3, and 2.4.Copies of these standards ma

26、y be obtained from ANSI: Approved ANSI standards, approved and draft international and regional standards (ISO, IEC, CEN/CENELEC, ITUT), and approved and draft foreign standards (including BSI, JIS, and DIN). For further information, contact ANSI Customer Service Department at 212-642-4900 (phone),

27、212-302-1286 (fax), or via the World Wide Web at http:/www.ansi.org.Additional availability contact information is provided as needed.2.2 Approved ReferencesCopies of the following documents may be obtained from ANSI, an ISO member organization:a) Approved ANSI standards;b) approved international an

28、d regional standards (ISO and IEC); andc) approved foreign standards (including JIS and DIN).For further information, contact the ANSI Customer Service Department:Phone +1 212-642-4980Fax: +1 212-302-1286Web: http:/www.ansi.orgE-mail: ansionlineansi.orgor the InterNational Committee for Information

29、Technology Standards (INCITS):Phone +1 202-737-8888Web: http:/www.incits.orgE-mail: incitsitic.orgTable 1 lists approved ANSI standards, approved international and regional standards (ISO, IEC, CEN/CENELEC, ITUT). Additional information may be available at http:/www.t10.org and http:/www.T13.org.Tab

30、le 1 Approved ANSI ReferencesName ReferenceVolume and File Structure of CD-ROM For Information Interchange ISO 9660-1988Fibre Channel Framing and Signaling Interface - 2 (FC-FS-2) INCITS 424-2007(FC-LS) INCITS 433-2006AT Attachment 8 - ATA/ATAPI Command Set - 8 (ATA8-ACS) INCITS 452-2009Serial Attac

31、hed SCSI - 1.1 (SAS-1.1) INCITS 417-2006Serial Bus Protocol - 2 (SBP-2) INCITS 325-1998Reduced Block Commands (RBC) INCITS 330-2003Multi-Media Commands - 5 (MMC-5) INCITS 430-2007BIOS Enhanced Disk Drive Services - 3 (EDD-3) INCITS 407-2005Extended Unique Identifier, 64-bit (EUI-64) ANSI/IEEE 394:19

32、95IEEE Standard for a High Performance Serial Bus IEEE 1394-2008INCITS 480-201142.3 References under DevelopmentAt the time of publication, the referenced standards were still under development. For information on the current status of the document, or regarding availability, contact the relevant st

33、andards body or other organization as indicated in table 2.2.4 Other ReferencesThese standards and specifications are also referenced.BIOS Boot Specification (Compaq, Phoenix and Intel),For the BIOS Boot Specification published by Phoenix Technologies, contact them at El Torito CD-ROM Boot Specifica

34、tionFor the El Torito CD-ROM Boot Specification published by Phoenix Technologies, contact them at ATAPI Removable Media BIOS SpecificationFor the ATAPI Removable Media BIOS Specification published by Phoenix Technologies, contact them at Universal Serial Bus 3.0 SpecificationFor the Universal Seria

35、l Bus 3.0 Specification, contact the USB Implementors Forum at www.usb.orgMass Storage OverviewFor the Mass Storage Overview specification, contact the USB Implementors Forum at www.usb.org, www.usb.org/developersUnified Extensible Firmware Interface Specification, Version 2.3 (UEFI-2.3) plus errata

36、For the UEFI-2.3 specification, contact the Unified EFI Forum at www.uefi.orgTable 2 References Under DevelopmentName Project NumberATA/ATAPI Command Set - 2 (ACS-2) INCITS 2015DSerial Bus Protocol - 3 (SBP-3) INCITS 1467DMulti-Media Commands - 6 (MMC-6) INCITS 1836DSCSI Primary Commands - 4 (SPC-4)

37、 INCITS 1731DINCITS 480-201153 Definitions, Abbreviations, and Conventions3.1 Definitions and Abbreviations3.1.1 ATA (AT Attachment) device: An AT Attachment (also known as IDE) is a storage device that conforms to an ATA standard.3.1.2 BDA: The BIOS Data Area is an area of reserved memory used by t

38、he BIOS and OS to store data about the system hardware. It is located at memory segment 40h starting with 40h:00h.3.1.3 BIOS: The Basic Input/Output System (BIOS) is the firmware stored in non-volatile (NV) memory located on the computers main board. The BIOS executes POST to test and initialize the

39、 system components and then loads the OS. The BIOS also handles the low-level Input/Output to the various peripheral devices connected to the computer.3.1.4 byte: A sequence of eight contiguous bits considered as a unit. See 3.3.10.3.1.5 Carry Clear: A condition where the Carry Flag in the EFLAGS re

40、gister is cleared to zero.3.1.6 Carry Set: A condition where the Carry Flag in the EFLAGS register is set to one.3.1.7 CF: The Carry Flag is a bit in the EFLAGS register in the microprocessor.3.1.8 CHS: CHS addressing is a method of addressing the contents of a storage device using logical cylinders

41、 (C), logical heads (H), and logical sectors (S). See LBA addressing for another addressing method.3.1.9 Conventional: When a word, term, or phrase is modified by the word “conventional“ it refers to the legacy style, or method of operation that is limited to addressing ATA devices that have a 528 M

42、B capacity or less. See 3.2.10xxx for the definition of “Enhanced“.3.1.10 DOS: DOS is a disk operating system that uses the system BIOS as a firmware abstraction layer to access system hardware. Examples of DOS based operating systems include MS-DOS, DR-DOS, PC-DOS, Free DOS, Windows3.11, and Window

43、s95.3.1.11 DWord: A sequence of four contiguous bytes considered as a unit. See 3.3.10.3.1.12 EFLAGS register: An Intel Architecture 32-bit status register or 64-bit status register.3.1.13 enhanced: When a word, term, or phrase is modified by the word “enhanced“ it means there is a “conventional“ an

44、d an “enhanced“ method of operation. The “enhanced“ method is defined by this standard.3.1.14 Host: The Host is the computer system that is controlled by the BIOS.3.1.15 Hybrid MBR boot code: IA-32 compatible code located in the MBR that processes the GPT disk layout.3.1.16 Hybrid VBR boot code: IA-

45、32 compatible code located in the VBR that processes the GPT disk layout.3.1.17 IA-32 compatible: IA-32 compatible refers to computer processor architectures that are compatible with the Intel Architecture 32-bit wide processor and data bus.3.1.18 IA-64 compatible: IA-64 compatible refers to compute

46、r processor architectures that are compatible with the Intel Architecture 64-bit wide processor and data bus.3.1.19 INT 13h: A BIOS interrupt service that provides a protocol independent method for addressing floppy, hard drive, and other storage devices.3.1.20 INT 40h: INT 40h is a BIOS interrupt s

47、ervice that provides a protocol independent method for addressing INT 13h devices that have a device number less than or equal to 7Fh.3.1.21 GPT disk layout: The disk layout defined by the Unified EFI specification (see UEFI-2.3).3.1.22 LBA: LBA is a method of addressing a device that involves using

48、 a Logical Block Address (e.g., using 28-bit addressing, this method of addressing allows a maximum sector address of 228-1, or 137.4 GB of data on an ATA device). See CHS for another address method.INCITS 480-201163.2 Symbols and abbreviations3.3 Conventions3.3.1 OverviewLowercase is used for words

49、 having the normal English language meaning. Certain words and terms used in this standard have a specific meaning beyond the normal English language meaning. These words and terms are defined either in clause 3 or in the text where they first appear.The names of abbreviations, commands, fields, and acronyms used as signal names are in all uppercase (e.g., IDENTIFY DEVICE). Fields containing only one bit are usually referred to as the “name” bit instead of the “name” field. (See 3.3.6 for the naming convention used for namin