A floppy-disk controller (FDC) is a hardware component that directs and controls reading from and writing to a computer's floppy disk drive (FDD). It has evolved from a discrete set of components on one or more circuit boards to a special-purpose integrated circuit (IC or "chip") or a component thereof. An FDC is responsible for reading data presented from the host computer and converting it to the drive's on-disk format using one of a number of encoding schemes, like FM encoding (single density) or MFM encoding (double density), and reading those formats and returning it to its original binary values.
Depending on the platform, data transfers between the controller and host computer would be controlled by the computer's own microprocessor, or an inexpensive dedicated microprocessor like the MOS 6507 or Zilog Z80. Early controllers required additional circuitry to perform specific tasks like providing clock signals and setting various options. Later designs included more of this functionality on the controller and reduced the complexity of the external circuitry; single-chip solutions were common by the later 1980s.
By the 1990s, the floppy disk was increasingly giving way to hard drives, which required similar controllers. In these systems, the controller also often combined a microcontroller to handle data transfer over standardized connectors like SCSI and IDE that could be used with any computer. In more modern systems, the FDC, if present at all, is typically part of the many functions provided by a single super I/O chip.
__TOC__
The first floppy disk drive controller (FDC) like the first floppy disk drive (the IBM 23FD) shipped in 1971 as a component in the IBM 2385 Storage Control Unit for the IBM 2305 fixed head disk drive,[1] and of the System 370 Models 155 and 165. The IBM 3830 Storage Control Unit, a contemporaneous and quite similar controller, uses its internal processor to control a 23FD.[2] The resultant FDC is a simple implementation in IBMs' MST hybrid circuits on a few printed circuit cards.[2] The drive, FDC and media were proprietary to IBM and although other manufacturers provided early FDDs prior to 1973 there were no standards for FDCs, drives or media.
IBM's 1973 introduction of the 3740 Data Entry System created the basic media standard for the 8-inch single sided floppy disk, IBM's "Type 1" diskette, which coupled with rapidly increasing requirements for inexpensive, removable direct access storage for many small applications caused a dramatic growth in drive and controller shipments.[3]
Prior to the introduction of special purpose integrated circuit versions, most FDCs consisted of at least one printed circuit implemented with 40 or more ICs.[4] Examples of such FDCs include:
The first FDC implemented as a special purpose integrated circuit is the Western Digital FD1771[14] announced on 19 July 1976.[15] The initial design supported a single format and required additional circuitry but over time, as a family, the design became multi-sourced and evolved to support many formats and minimize external circuitry.
The NEC μPD765 was announced in 1978[16] and in 1979 NEC introduced the μPD72068, which was software compatible with the μPD765, incroporating a Digital PLL.[17] The μPD765 became a quasi-industry standard when it was adopted in the original IBM PC (1981); the FDC was physically located on its own adapter card along with support circuitry. Other vendors such as Intel produced compatible parts. This design evolved over time into a family offering an almost complete FDC on a chip.[18]
As of March 1986, Sharp had commercialized the FDC LH0110.[19]
In early 1987, Intel introduced the 82072 CHMOS High Integrated Floppy Disk Controller for use in industry standard PC computers.[20] [21]
Ultimately in most computer systems the FDC became a part of a Super I/O chip or a Southbridge chip.[22] [23] However, in later motherboards, as floppy disks were phased out by personal computer users, this interface was eliminated. Some manufacturers developed USB-based floppy disk controllers.[24]
A floppy disk stores binary data not as a series of values, but a series of changes in value. Each of these changes, recorded in the polarity of the magnetic recording media, causes a voltage to be induced in the drive head as the disk surface rotates past it. It is the timing of these polarization changes and the resulting spikes of voltage that encode the ones and zeros of the original data. One of the functions of the controller is to turn the original data into the proper pattern of polarizations during writing, and then recreate it during reads.
As the storage is based on timing, and that timing is easily affected by mechanical and electrical disturbances, accurately reading the data requires some sort of reference signal, the clock. As the on-disk timing is constantly changing, the clock signal has to be provided by the disk itself. To do this, the original data is modified with extra transitions to allow the clock signal to be encoded in the data and then use clock recovery during reads to recreate the original signal. Some controllers require this encoding to be performed externally, but most designs provide standard encodings like FM and MFM.
The controller also provides a number of other services to control the drive mechanism itself. These typically include the movement of the drive head to center over the separate tracks on the disk, tracking the location of the head and returning it to zero, and sometimes functionally to format a disk based on simple inputs like the number of tracks, sectors per track and number of bytes per sector.
To produce a complete system, the controller has to be combined with additional circuitry or software that acts as a bridge between the controller and the host system. In some systems, like the Apple II and IBM PC, this is controlled by software running on the computer's host microprocessor and the drive interface is connected directly to the processor using an expansion card. On other systems, like the Commodore 64 and Atari 8-bit computers, there is no direct path from the controller to the host CPU and a second processor like the MOS 6507 or Zilog Z80 is used inside the drive for this purpose.
The original Apple II controller was in the form of a plug-in card on the host computer. It could support two drives, and the drives eliminated most of the normal onboard circuitry. This allowed Apple to arrange a deal with Shugart Associates for a simplified drive that lacked most of its normal circuitry. This meant that the combined cost of a single drive and controller card was roughly the same as on other systems, but a second drive could be connected for a smaller additional cost.
The IBM PC took a more conventional approach, their adaptor card could support up to four drives; on the PC direct memory access (DMA) to the drives was performed using DMA channel 2 and IRQ 6. The diagram below shows a conventional floppy disk controller which communicates with the CPU via an Industry Standard Architecture (ISA) bus or similar bus and communicates with the floppy disk drive with a 34 pin ribbon cable. An alternative arrangement that is more usual in recent designs has the FDC included in a super I/O chip which communicates via a Low Pin Count (LPC) bus.
Most of the floppy disk controller (FDC) functions are performed by the integrated circuit but some are performed by external hardware circuits. The list of functions performed by each is given below.
The FDC has three I/O ports. These are:
The first two reside inside the FDC IC while the Control port is in the external hardware. The addresses of these three ports are as follows.
Port Address [hex] | Port Name | Location | Port type | |
---|---|---|---|---|
3F5 | Data port | Bidirectional I/O | ||
3F4 | Main status register | FDC IC | Input | |
3F2 | Digital control port | External hardware | Output |
This port is used by the software for three different purposes:
This port is used by the software to read the overall status information regarding the FDC IC and the FDD's. Before initiating a floppy disk operation the software reads this port to confirm the readiness condition of the FDC and the disk drives to verify the status of the previously initiated command. The different bits of this register represent :
Bit | Representation | |
---|---|---|
0 | FDD 0: Busy in seek mode | |
1 | FDD 1: Busy in seek mode | |
2 | FDD 2: Busy in seek mode | |
3 | FDD 3: Busy in seek mode | |
4 | FDC Busy; Read/Write command in progress | |
5 | Non-DMA mode | |
6 | DIO; Indicates the direction of data transfer between the FDC IC and the CPU | |
7 | MQR; Indicates data register is ready for data transfer |
This port is used by the software to control certain FDD and FDC IC functions. The bit assignments of this port are:
Bit | Representation | |
---|---|---|
0 and 1 | Device number to be selected | |
2 | RESET FDC IC (Low) | |
3 | Enable FDC interrupt and DMA request signals | |
4 to 7 | Turn ON the motor in disk drive 0, 1, 2 or 3 respectively |
A controller connects to one or more drives using a flat ribbon cable, 50 wires for 8" drives and 34 wires for 3.5" & 5.25" drives. A "universal cable" has four drive connectors, two each for 3.5" & 5.25" drives.[25] In the IBM PC family and compatibles, a twist in the cable is used to distinguish disk drives by the socket to which they are connected. All drives are installed with the same drive select address set, and the twist in the cable interchanges the drive select lines at the socket. The drive that is at the far end of the cable would also have a terminating resistor installed to maintain signal quality.[26]
More detailed descriptions of the interface signals including alternative meanings are contained in manufacturer's specifications for drives or host controllers.
When the controller and disk drive are assembled as one device, as it is the case with some external floppy disk drives, e.g., Commodore 1540 and USB floppy disk drives,[27] the internal floppy disk drive and its interface are unchanged, while the assembled device presents a different interface such as IEEE-488, parallel port or USB.
See main article: List of floppy disk formats. Many mutually incompatible floppy disk formats are possible; aside from the physical format on the disk, incompatible file systems are also possible.
Drive | Format | Capacity | Transfer speed [kbit/s] | Tracks | Comment | |||
---|---|---|---|---|---|---|---|---|
8-inch SD | 8-inch SD | 80 KB | 33.333 | 360 | 32 | 48 | Only on old controllers.[28] | |
5.25-inch SD | 5.25-inch SD | 160 KB | 125 | 40 | Only on old controllers. | |||
5.25-inch SSDD | 5.25-inch SSDD | 171 KB | 300 | 35 | 48[29] | Only on C1541 compatibles. | ||
5.25-inch SD | 5.25-inch SD | 180 KB | 150 | 40 | Only on old controllers. | |||
5.25-inch DD | 5.25-inch DD | 320/360/400 KB | 250 | 300 | 40 | 48 | [30] 8/9/10 512 byte sectors respectively. | |
5.25-inch DD | 5.25-inch QD (2DD) | 800 KB | 250 | 300 | 80 | 96 | [31] | |
5.25-inch HD | 5.25-inch DD | 360 KB | 300 | 360 | 40 | 48 | ||
5.25" HD | 5.25" HD | 1200 KB | 500 | 360 | 80 | 96 | Up to 83 tracks. Different biasing current.[32] [33] | |
5.25" HD | 5.25" HD | 720 KB | 300 | 360 | 80 | Up to 83 tracks. | ||
3.5" DD | 3.5" DD | 720 KB | 250 | 300 | 80 | 135 | Up to 83 tracks.[34] | |
3.5" DD | 3.5" DD | 800 KB | 394–590 | 80 | Used by Apple Macintosh.[35] | |||
3.5" DD | 3.5" DD | 800 KB | 250 | 300 | 80 | Used by Commodore 1581. | ||
3.5" DD | 3.5" DD | 880 KB | 250 | 300 | 80 | Up to 83 tracks. Used by Amiga computers. | ||
3.5" DD | 3.5" DD | 360 KB | 250 | 300 | 40 | |||
3.5" HD | 3.5" DD | 720 KB | 250 | 300 | 80 | Up to 83 tracks. | ||
3.5" HD | 3.5" HD | 1280 KB | 500 | 360 | 80 | 135 | Up to 83 tracks. "3mode" | |
3.5" HD | 3.5" HD | 1440 KB | 500 | 300 | 80 | 135 | Up to 83 tracks.[36] | |
3.5" HD | 3.5" HD | 1760 KB | 250 | 150 | 80 | Used by Amiga computers. | ||
3.5" ED | 3.5" ED | 2880 KB | 1000 | 300 | 80 | 135 | Up to 83 tracks.[37] |
Sides:
Density:
Primarily in Japan there are 3.5" high-density floppy drives that support three modes of disk formats instead of the normal two – 1440 KB (2 MB unformatted), 1.2 MB (1.6 MB unformatted) and 720 KB (1 MB unformatted). Originally, the high-density modes for 3.5" floppy drives in Japan only supported a capacity of 1.2 MB instead of the 1440 KB capacity that was used elsewhere.[39] While the more common 1440 KB format spun at 300 rpm, the 1.2 MB formats instead spun at 360 rpm, thereby closely resembling the geometries of either the 1.2 MB format with 80 tracks, 15 sectors per track, and 512 bytes per sector previously found on 5.25" high-density floppy disks or the 1.2 MB format with 77 tracks, 8 sectors per track, and 1,024 bytes per sector previously found on 8" double-density floppy disks. Later Japanese floppy drives incorporated support for both high-density formats (as well as the double-density format), hence the name 3-mode. Some BIOSes have a configuration setting to enable this mode for floppy drives supporting it.[40]