PDF
ZIP
-
-
-
-
-
The SMSC LPC47N227 is a 3.3V PC 99 and
ACPI 1.0b compliant Super I/O Controller. The
LPC47N227 implements the LPC interface, a pin
reduced ISA interface which provides the same
or better performance as the ISA/X-bus with a
substantial savings in pins used. The part also
includes 29 GPIO pins.
The LPC47N227 incorporates SMSC's true
CMOS 765B floppy disk controller, advanced
digital data separator, 16-byte data FIFO, two
16C550 compatible UARTs, one Multi-Mode
parallel port with ChiProtect circuitry plus EPP
and ECP support and one floppy direct drive
support. The LPC47N227 does not require any
external filter components, is easy to use and
offers lower system cost and reduced board
area. The LPC47N227 is software and register
compatible with SMSC's proprietary 82077AA
core.
The true CMOS 765B core provides 100%
compatibility with IBM PC/XT and PC/AT
architectures and provides data overflow and
underflow protection. The SMSC advanced
digital data separator incorporates SMSC's
patented data separator technology allowing for
ease of testing and use. The LPC47N227
supports both 1Mbps and 2Mbps data rates and
vertical recording operation at 1Mbps Data Rate.
The LPC47N227 also features a full 16-bit
internally decoded address bus, a Serial IRQ
interface with PCI nCLKRUN support, relocatable
options.
Both on-chip UARTs are compatible with the
NS16C550. One UART includes additional
support for a Serial Infrared Interface that
complies with IrDA v1.2 (Fast IR), HPSIR, and
ASKIR formats (used by Sharp and other PDAs),
as well as Consumer IR.
The parallel port is compatible with IBM PC/AT
architectures, as well as IEEE 1284 EPP and
ECP. The parallel port ChiProtect circuitry
prevents damage caused by an attached
powered printer when the LPC47N227 is not
powered.
The LPC47N227 incorporates sophisticated
power control circuitry (PCC). The PCC supports
multiple low power down modes. The
LPC47N227 also features Software Configurable
Logic (SCL) for ease of use. SCL allows
programmable system configuration of key
functions such as the FDC, parallel port, and
UARTs.
The LPC47N227 supports the ISA Plug-and-Play
Standard (Version 1.0a) and provides the
recommended functionaity to support Windows
`95/'98 and PC99. The I/O Address, DMA
Channel and Hardware IRQ of each device in the
LPC47N227 may be reprogrammed through the
internal configuration registers. There are 192
I/O address location options, a Serialized IRQ
interface, and three DMA channels.
GENERAL DESCRIPTION...................................................................................................................... 2
PIN CONFIGURATION............................................................................................................................ 4
DESCRIPTION OF PIN FUNCTIONS ..................................................................................................... 5
3.3 VOLT OPERATION / 5 VOLT TOLERANCE ...................................................................................14
Power Functionality..............................................................................................................................14
VTR Support .......................................................................................................................................14
Internal PWRGOOD ............................................................................................................................14
Trickle Power Functionality..................................................................................................................14
Maximum Current Values....................................................................................................................15
Power Management Events (PME/SCI) ..............................................................................................15
FLOPPY DISK CONTROLLER ..............................................................................................................21
SERIAL PORT (UART)...........................................................................................................................68
INFRARED INTERFACE ........................................................................................................................85
PARALLEL PORT..................................................................................................................................89
POWER MANAGEMENT .....................................................................................................................111
SERIAL IRQ .........................................................................................................................................115
PCI CLKRUN SUPPORT .....................................................................................................................119
GENERAL PURPOSE I/O ....................................................................................................................122
SYSTEM MANAGEMENT INTERRUPT (SMI) .....................................................................................128
PME SUPPORT....................................................................................................................................129
RUNTIME REGISTERS........................................................................................................................130
CONFIGURATION................................................................................................................................137
OPERATIONAL DESCRIPTION ..........................................................................................................172
DC Electrical Characteristics .............................................................................................................172
PACKAGE OUTLINE ...........................................................................................................................197
DRVDEN1
LAD1
LAD2
LAD3
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
_R
_
C
K
I
R
0
2
3
6
1
4
5
0
1
/
SYSO
2
/
n
I
O
74
73
72
71
70
69
68
67
66
65
64
63
62
61
60
59
58
57
56
55
54
53
52
51
PD6
PD5
PD4
PD3
PD2
PD1
PD0
nSLCTIN
nINIT
VCC
GP23/FDC_PP
IRMODE/IRRX3
IRTX2
IRRX2
VSS
GP22
GP21
GP20
GP17
GP16
GP15
VCC
GP14/IRQIN2
GP13/IRQIN1
DCD
bus.
cycle and termination of broken cycle.
Request
DMA/Bus Master request for the LPC
interface.
T
Reset.
(Note 2)
that the LPC47N227 should prepare for
power to be shut on the LPC interface.
clock status and to request that a stopped
clock be started.
to transfer LPC47N227 interrupts to the
host.
(Note 7)
wakeup.
CR0B, CR1F.
CR0B, CR1F.
changed since the last drive selection.
This input is inverted and read via bit 7 of
I/O address 3F7H. The nDSKCHG bit also
depends upon the state of the Force Disk
Change bits in the Force FDD Status
Change configuration register (see
subsection CR17 in the Configuration
section).
movement. A logic "1" on this pin means
outward motion, while a logic "0" means
inward motion.
movement of the head.
falling edge causes a flux transition on the
media.
current to flow through the write head. It
becomes active just prior to writing to the
diskette.
on this pin means side 0 will be accessed,
while a logic "0" means side 1 will be
accessed.
senses from the disk drive that the head is
positioned over the beginning of a track, as
marked by an index hole.
senses from the disk drive that the head is
positioned over the outermost track.
senses from the disk drive that a disk is
write protected. Any write command is
ignored. The nWRPRT bit also depends
upon the state of the Force Write Protect
bit in the Force FDD Status Change
configuration register (see subsection
CR17 in the Configuration section).
low active. Each falling edge represents a
flux transition of the encoded data.
Ready 1
Ready 2
serial port. Handshake signal which
notifies the UART that the modem is ready
to establish the communication link. The
CPU can monitor the status of nDSR
signal by reading bit 5 of Modem Status
Register (MSR). A nDSR signal state
change from low to high after the last MSR
read will set MSR bit 1 to a 1. If bit 3 of
Interrupt Enable Register is set, the
interrupt is generated when nDSR
changes state.
Note: Bit 5 of MSR is the complement of
nDSR.
Serial Port. Handshake output signal
notifies modem that the UART is ready to
transmit data. This signal can be
programmed by writing to bit 1 of the
Modem Control Register (MCR). The
hardware reset will reset the nRTS signal
to inactive mode (high). nRTS is forced
inactive during loop mode operation.
Send 1
Send 2
serial port. Handshake signal which
notifies the UART that the modem is ready
to receive data. The CPU can monitor the
status of nCTS signal by reading bit 4 of
Modem Status Register (MSR). A nCTS
signal state change from low to high after
the last MSR read will set MSR bit 0 to a 1.
If bit 3 of the Interrupt Enable Register is
set, the interrupt is generated when nCTS
changes state. The nCTS signal has no
effect on the transmitter.
Note: Bit 4 of MSR is the complement of
nCTS.
serial port. Handshake output signal notifies
modem that the UART is ready to establish data
communication link. This signal can be
programmed by writing to bit 0 of Modem Control
Register (MCR). The hardware reset will reset the
nDTR signal to inactive mode (high). nDTR is
forced inactive during loop mode operation.
(Note 8)
(Note 8)
Handshake signal which notifies the UART that the
telephone ring signal is detected by the modem.
The CPU can monitor the status of nRI signal by
reading bit 6 of Modem Status Register (MSR). A
nRI signal state change from low to high after the
last MSR read will set MSR bit 2 to a 1. If bit 3 of
Interrupt Enable Register is set, the interrupt is
generated when nRI changes state.
Note: Bit 6 of MSR is the complement of nRI.
port. Handshake signal which notifies the UART
that carrier signal is detected by the modem. The
CPU can monitor the status of nDCD signal by
reading bit 7 of Modem Status Register (MSR). A
nDCD signal state change from low to high after
the last MSR read will set MSR bit 3 to a 1. If bit 3
of Interrupt Enable Register is set, the interrupt is
generated when nDCD changes state.
Note: Bit 7 of MSR is the complement of nDCD.
Data.
data.
IRRX3
IR Receive 3.
FDC Direction
Control
(Note 4)
nDIR
This is used to initiate the printer when low.
Refer to Parallel Port description for use of this
pin in ECP and EPP mode.
See FDC Pin definition.
FDC Step Pulse
(Note 4)
nSTEP
the complement of bit 3 of the Printer Control
Register.
Refer to Parallel Port description for use of this pin
in ECP and EPP mode.
See FDC Pin definition.
FDC Index
nINDEX
See FDC Pin definition.
FDC Track 0
nTRK0
See FDC Pin definition.
FDC Write
Protected
nWRTPRT
See FDC Pin definition.
FDC Read Disk
Data
nRDATA
See FDC Pin definition.
FDC Disk
Change
nDSKCHG
See FDC Pin definition.
FDC Motor
On 0
nMTR0
See FDC Pin definition.
FDC Write Gate
nWGATE
that it has power on. Bit 4 of the Printer Status
Register reads the SLCT input. Refer to Parallel
Port description for use of this pin in ECP and EPP
mode.
See FDC Pin definition.
FDC Write Data
nWRDATA
indicating that the printer is out of paper. Bit 5 of
the Printer Status Register reads the PE input.
Refer to Parallel Port description for use of this pin
in ECP and EPP mode.
See FDC Pin definition.
FDC Motor On 1
nMTR1
indicating that the printer is not ready to receive
new data. Bit 7 of the Printer Status Register is the
complement of the BUSY input. Refer to Parallel
Port description for use of this pin in ECP and EPP
mode.
See FDC Pin definition.
FDC Drive
Select 1
nDS1
has received the data and is ready to accept new
data. Bit 6 of the Printer Status Register reads the
nACK input. Refer to Parallel Port description for
use of this pin in ECP and EPP mode.
See FDC Pin definition.
FDC Head
Select
nHDSEL
there is a error condition at the printer. Bit 3 of the
Printer Status register reads the nERR input. Refer
to Parallel Port description for use of this pin in
ECP and EPP mode.
See FDC Pin definition.
FDC Density
Select 0
(Note 4)
nDRVDEN0
automatically feed one line after each line is
printed. The nALF output is the complement of bit
1 of the Printer Control Register.
Refer to Parallel Port description for use of this pin
in ECP and EPP mode.
See FDC Pin definition.
FDC Drive
Select 0
(Note 4)
nDS0
the printer data into the printer. The nSTROBE
output is the complement of bit 0 of the Printer
Control Register.
Refer to Parallel Port description for use of this pin
in ECP and EPP mode.
See FDC Pin definition.
Purpose I/O
(Note 9)
GP30-GP37
GP40-GP47
GP10,
GP15-GP17,
GP20-GP22
(System Option)
(Note 5)
(Note 9)
(SYSOPT)
At the trailing edge of hardware reset the GP11 pin
is latched to determine the configuration base
address: 0 = Index Base I/O Address 02E Hex; 1 =
Index Base I/O Address 04E Hex.
System Mgt.
Interrupt
(Note 9)
nIO_SMI
Active low System Management Interrupt Output.
IRQ Input 1
(Note 9)
IRQIN1
External Interrupt Input. Steerable onto one of the
15 Serial IRQs.
IRQ Input 2
(Note 9)
IRQIN2
External Interrupt Input. Steerable onto one of the
15 Serial IRQs.
Floppy on
Parallel Port
(Note 9)
FDC_PP
Floppy on the Parallel Port Indication.
Note: The "n" as the first letter of a symbol indicates an "Active Low" signal.
Note 1: Buffer types per function on multiplexed pins are separated by a slash "/". Buffer types in
Note 3: The FDD output pins multiplexed in the PARALLEL PORT INTERFACE are OD drivers only and
section).
for configuration to 0x04E.
Note 8: Ring indicator pins nRI1 and nRI2 have input buffers into the wakeup logic that are powered by
Buffer Type Description
I
2)
Note 1. See the PCI Local Bus Specification, Revision 2.1, Section 4.2.2.
Note 2. See the PCI Local Bus Specification, Revision 2.1, Section 4.2.2. and 4.2.3.
TXD2, nRTS2, nDTR2
RXD2, nCTS2,
nDSR2, nDCD2, nRI2
nSTEP, DRVDEN0*,
nWGATE, HDSEL,
DRVDEN1*, nWDATA
nDSKCHG,
nINDEX,
nWRTPRT,
nRDATA
PORT 1
nDSR1, nDCD1, nRI1
GP12*, GP13*,
GP14*,
GP1[5:7],
GP2[0:2],
GP23*, GP24,
GP3[0:7],
GP4[0:7]
PORT/FDC
PE, nERROR, nACK
nINIT, nSTROBE
LAD1
LAD2
LAD3
FDC_PP*
The LPC47N227 is a 3.3 Volt part. It is intended
solely for 3.3V applications. Non-LPC bus pins
are 5V tolerant; that is, the input voltage is 5.5V
max, and the I/O buffer output pads are
backdrive protected.
The LPC interface pins are 3.3 V only. These
signals meet PCI DC specifications for 3.3V
signaling. These pins are:
LAD[3:0]
nLFRAME
nLDRQ
nLPCPD
The input voltage for all other pins is 5.5V max.
These pins include all non-LPC Bus pins and the
following pins:
nPCI_RESET
PCI_CLK
SER_IRQ
nCLKRUN
nIO_PME
Power Functionality
The LPC47N227 has two power planes: VCC
and VTR.
VCC Power
The LPC47N227 is a 3.3 Volt part. The VCC
supply is 3.3 Volts (nominal). See the
Operational Description Section and the
Maximum Current Values subsection.
VTR Support
The LPC47N227 requires a trickle supply (V
wake-up events in the PME interface when V
See the Operational Description Section. The
maximum VTR current that is required depends
on the functions that are used in the part. See
Trickle Power Functionality subsection and the
Maximum Current Values subsection. If the
LPC47N227 is not intended to provide wake-up
capabilities on standby current, V
components.
Note: If V
exceed 500mV.
Internal PWRGOOD
An internal PWRGOOD logical control is included
to minimize the effects of pin-state uncertainty in
the host interface as V
(active), V
internal PWRGOOD signal is "0" (inactive), V
interface is inactive; that is, LPC bus reads and
writes will not be decoded.
The LPC47N227 device pins nIO_PME, nRI1,
nRI2, and most GPIOs (as input) are part of the
PME interface and remain active when the
internal PWRGOOD signal has gone inactive,
provided V
Trickle Power Functionality
When the LPC47N227 is running under VTR
only, the PME wakeup events are active and (if
enabled) able to assert the nIO_PME pin active
low. The following lists the wakeup events:
The following requirements apply to all I/O pins
that are specified to be 5 volt tolerant.
VTR power (VCC=0), these pins may only
be configured as inputs. These pins have
input buffers into the wakeup logic that are
powered by VTR.
push-pull or open drain under VTR power
(VCC=0), are powered by VTR. This means
they will, at a minimum, source their
specified current from VTR even when VCC
is present. This applies to the nIO_PME pin
only.
The GPIOs that are used for PME wakeup inputs
are GP10-GP17, GP20-GP24, GP30-GP37.
Buffers are powered by VCC, but in the
protected (they do not impose a load on any
external VTR powered circuitry). They are
wakeup compatible as inputs under VTR
power. These pins have input buffers into
the wakeup logic that are powered by VTR.
GPIO function (or alternate function).
See the Table in the GPIO section for more
information.
The following list summarizes the blocks,
registers and pins that are powered by VTR.
GP30-GP37) as input
- nIO_PME as input
Maximum Current Values
See the "Operational Description" section for the
maximum current values.
The maximum VTR current, I
fixed state (i.e., 0V or 3.3V). The total maximum
current for the part is the unloaded value PLUS
the maximum current sourced by the pin that is
driven by VTR. The pin that is powered by VTR
(as output) is nIO_PME. This pin, if configured
as a push-pull output, will source a minimum of
6mA at 2.4V when driving.
The maximum VCC current, I
fixed state (i.e., 0V or 3.3V).
Power Management Events (PME/SCI)
The LPC47N227 offers support for Power
Management Events (PMEs), also referred to as
System Control Interrupt (SCI) events. The terms
PME and SCI are used synonymously
throughout this document to refer to the
indication of an event to the chipset via the
assertion of the nIO_PME output signal on pin
17. See the "PME Support" section. Do not
connect the nIO_PME pin to PCI PME pins.
Super I/O Registers
The address map, shown below in Table 1,
shows the addresses of the different blocks of
the Super I/O immediately after power up. The
base addresses of the FDC, serial and parallel
ports, runtime register block and configuration
register block can be moved via the configuration
registers. Some addresses are used to access
more than one register.
The host processor communicates with the
LPC47N227 through a series of read/write
registers via the LPC interface. The port
addresses for these registers are shown in Table
1. Register access is accomplished through I/O
cycles or DMA transfers. All registers are 8 bits
wide.
Base2+(0-7)
FIR and CIR
Base+(0-3)
Base+(0-7)
Base+(0-3), +(400-402)
Base+(0-7), +(400-402)
SPP
EPP
ECP
ECP+EPP+SPP
The following sub-sections specify the
implementation of the LPC bus.
The signals required for the LPC bus interface
are described in the table below. LPC bus
signals use PCI 33MHz electrical signal
characteristics.
data bus.
broken cycle
wakeup.
prepare for power to be shut on the LPC interface.
PCI_CLK be started.
LPC Cycles
The following cycle types are supported by the
LPC protocol.
The LPC47N227 ignores cycles that it does not
support.
Field Definitions
The data transfers are based on specific fields
that are used in various combinations, depending
on the cycle type. These fields are driven onto
the LAD[3:0] signal lines to communicate
address, control and data information over the
LPC bus between the host and the LPC47N227.
See the Low Pin
from Intel, Section 4.2 for definition of these
fields.
nLFRAME Usage
nLFRAME is used by the host to indicate the
start of cycles and the termination of cycles due
to an abort or time-out condition. This signal is
to be used by the LPC47N227 to know when to
monitor the bus for a cycle.
This signal is used as a general notification that
the LAD[3:0] lines contain information relative to
the start or stop of a cycle, and that the
LPC47N227 monitors the bus to determine
whether the cycle is intended for it. The use of
nLFRAME allows the LPC47N227 to enter a
lower power state internally. There is no need
for the LPC47N227 to monitor the bus when it is
inactive, so it can decouple its state machines
from the bus, and internally gate its clocks.
When the LPC47N227 samples nLFRAME
active, it immediately stops driving the LAD[3:0]
signal lines on the next clock and monitor the bus
for new cycle information.
The nLFRAME signal functions as described in
the Low Pin Count (LPC) Interface Specification
Revision 1.0.
I/O Read and Write Cycles
The LPC47N227 is the target for I/O cycles. I/O
cycles are initiated by the host for register or
FIFO accesses, and will generally have minimal
Sync times. The minimum number of wait-states
between bytes is 1. EPP cycles will depend on
the speed of the external device, and may have
much longer Sync times.
Data transfers are assumed to be exactly 1-byte.
If the CPU requested a 16 or 32-bit transfer, the
host will break it up into 8-bit transfers.
See the Low Pin Count (LPC) Interface
Specification Reference, Section 5.2, for the
sequence of cycles for the I/O Read and Write
cycles.
DMA Read and Write Cycles
from the host (main memory) to the LPC47N227.
DMA write cycles involve the transfer of data
from the LPC47N227 to the host (main memory).
Data will be coming from or going to a FIFO and
will have minimal Sync times. Data transfers
to/from the LPC47N227 are 1 byte.
See the Low Pin Count (LPC) Interface
Specification Reference, Section 6.4, for the field
definitions and the sequence of the DMA Read
and Write cycles.
DMA Protocol
DMA on the LPC bus is handled through the use
of the nLDRQ line from the LPC47N227 and
special encodings on LAD[3:0] from the host.
The DMA mechanism for the LPC bus is
described in the Low Pin Count (LPC)
Specification Revision 1.0.
CLOCKRUN Protocol
See the Low Pin Count (LPC) Interface
Specification Reference, Section 8.1.
LPCPD Protocol
The LPC47N227 will function properly if the
nLPCPD signal goes active and then inactive
again without nPCI_RESET becoming active.
This is a requirement for notebook power
management functions.
Although the LPC Bus spec 1.0 section 8.2
states, "After nLPCPD goes back inactive, the
LPC I/F will always be reset using nLRST", this
statement does not apply for mobile systems.
nLRST (nPCI_RESET) will not occur if the LPC
Bus power was not removed. For example,
when exiting a "light" sleep state (ACPI S1, APM
POS), nLRST (nPCI_RESET) will not occur.
When exiting a "deeper" sleep state (ACPI S3-
S5, APM STR, STD, soft-off), nLRST
(nPCI_RESET) will occur.
The nLPCPD pin is implemented as a "local"
powergood for the LPC interface in the
LPC47N227. It is not used as a global
powergood for the chip. It is used to reset the
LPC block and hold it in reset.
An internal powergood is implemented in
LPC47N227 to minimize power dissipation in the
entire chip.
Prior to going to a low-power state, the system
will assert the nLPCPD signal. It will go active at
least 30 microseconds prior to the LCLK
(PCI_CLK) signal stopping low and power being
shut to the other LPC I/F signals.
Upon recognizing nLPCPD active, the
LPC47N227 will tri-state the nLDRQ signal and
do so until nLPCPD goes back active.
Upon recognizing nLPCPD inactive, the
LPC47N227 will drive its nLDRQ signal high.
Specification Reference, Section 8.2.
SYNC Protocol
See the Low Pin Count (LPC) Interface
Specification Reference, Section 4.2.1.8 for a
table of valid SYNC values.
Typical Usage
The SYNC pattern is used to add wait states.
For read cycles, the LPC47N227 immediately
drives the SYNC pattern upon recognizing the
cycle. The host immediately drives the sync
pattern for write cycles. If the LPC47N227 needs
to assert wait states, it does so by driving 0101
or 0110 on LAD[3:0] until it is ready, at which
point it will drive 0000 or 1001. The LPC47N227
will choose to assert 0101 or 0110, but not switch
between the two patterns.
The data (or wait state SYNC) will immediately
follow the 0000 or 1001 value.
The SYNC value of 0101 is intended to be used
for normal wait states, wherein the cycle will
complete within a few clocks. The LPC47N227
uses a SYNC of 0101 for all wait states in a DMA
transfer.
The SYNC value of 0110 is intended to be used
where the number of wait states is large. This is
provided for EPP cycles, where the number of
wait states could be quite large (>1
microsecond). However, the LPC47N227 uses a
SYNC of 0110 for all wait states in an I/O
transfer.
The SYNC value is driven within 3 clocks.
The SYNC value is driven within 3 clocks. If the
host observes 3 consecutive clocks without a
valid SYNC pattern, it will abort the cycle.
The LPC47N227 does not assume any particular
timeout. When the host is driving SYNC, it may
have to insert a very large number of wait states,
depending on PCI latencies and retries.
SYNC Patterns and Maximum Number of
SYNCS
If the SYNC pattern is 0101, then the host
assumes that the maximum number of SYNCs is
8.
If the SYNC pattern is 0110, then no maximum
number of SYNCs is assumed. The LPC47N227
has protection mechanisms to complete the
cycle. This is used for EPP data transfers and
will utilize the same timeout protection that is in
EPP.
SYNC Error Indication
The LPC47N227 reports errors via the LAD[3:0]
= 1010 SYNC encoding.
If the host was reading data from the
LPC47N227, data will still be transferred in the
next two nibbles. This data may be invalid, but it
will be transferred by the LPC47N227. If the host
was writing data to the LPC47N227, the data had
already been transferred.
In the case of multiple byte cycles, such as DMA
cycles, an error SYNC terminates the cycle.
Therefore, if the host is transferring 4 bytes from
a device, if the device returns the error SYNC in
the first byte, the other three bytes will not be
transferred.
I/O and DMA cycles use a START field of 0000.
Reset Policy
The following rules govern the reset policy:
1) When nPCI_RESET goes inactive (high),
for 100usec prior to the removal of the reset
signal, so that everything is stable. This is
the same reset active time after clock is
stable that is used for the PCI bus.
ignores the nLDRQ signal.
nLDRQ signal inactive (high).
LPC Transfers
Wait State Requirements
I/O Transfers
The LPC47N227 inserts three wait states for an
I/O read and two wait states for an I/O write
cycle. A SYNC of 0110 is used for all I/O
transfers. The exception to this is for transfers
where IOCHRDY would be deasserted in an ISA
transfer (i.e., EPP or IrCC transfers) in which
case the sync pattern of 0110 is used and a large
number of syncs may be inserted (up to 330
which corresponds to a timeout of 10us).
DMA Transfers
The LPC47N227 inserts three wait states for a
DMA read and four wait states for a DMA write
cycle. A SYNC of 0101 is used for all DMA
transfers.
See the example timing for the LPC cycles in the
"Timing Diagrams" section.
The Floppy Disk Controller (FDC) provides the
interface between a host microprocessor and the
floppy disk drives. The FDC integrates the
functions of the Formatter/Controller, Digital Data
Separator, Write Precompensation and Data Rate
Selection logic for an IBM XT/AT compatible FDC.
The true CMOS 765B core guarantees 100% IBM
PC XT/AT compatibility in addition to providing
data overflow and underflow protection.
The FDC is compatible to the 82077AA using
SMSC's proprietary floppy disk controller core.
The LPC47N227 supports one floppy disk drive
directly through the FDC interface pins and two
parallel port pins. It can also be configured to
support one drive on the FDC interface pins and
one drive on the parallel port pins.
FDC Internal Registers
The Floppy Disk Controller contains eight internal
registers that facilitate the interfacing between the
host microprocessor and the disk drive. Table 2
shows the addresses required to access these
registers. Registers other than the ones shown are
not supported. The rest of the description
assumes that the primary addresses have been
selected.
3F1
3F2
3F3
3F4
3F4
3F5
3F6
3F7
3F7
371
372
373
374
374
375
376
377
377
R
R/W
Status Register B (SRB)
Digital Output Register (DOR)
Tape Drive Register (TDR)
Main Status Register (MSR)
Data Rate Select Register (DSR)
Data (FIFO)
Reserved
Digital Input Register (DIR)
Configuration Control Register (CCR)
Status Register A (SRA)
Address 3F0 READ ONLY
This register is read-only and monitors the state
of the internal interrupt signal and several disk
SRA can be accessed at any time when in PS/2
mode. In the PC/AT mode the data bus pins D0
- D7 are held in a high impedance state for a
read of address 3F0.
BIT 0 DIRECTION
Active high status indicating the direction of head movement. A logic "1" indicates inward direction; a logic
"0" indicates outward direction.
BIT 1 nWRITE PROTECT
Active low status of the WRITE PROTECT disk interface input. A logic "0" indicates that the disk is write
protected.
BIT 2 nINDEX
Active low status of the INDEX disk interface input.
BIT 3 HEAD SELECT
Active high status of the HDSEL disk interface input. A logic "1" selects side 1 and a logic "0" selects side
0.
BIT 4 nTRACK 0
Active low status of the TRK0 disk interface input.
BIT 5 STEP
Active high status of the STEP output disk interface output pin.
BIT 6 nDRV2
This function is not supported. This bit is always read as "1".
BIT 7 INTERRUPT PENDING
Active high bit indicating the state of the Floppy Disk Interrupt output.
PS/2 Model 30 Mode
BIT 0 nDIRECTION
Active low status indicating the direction of head movement. A logic "0" indicates inward direction; a logic
"1" indicates outward direction.
Active high status of the WRITE PROTECT disk interface input. A logic "1" indicates that the disk is write
protected.
BIT 2 INDEX
Active high status of the INDEX disk interface input.
BIT 3 nHEAD SELECT
Active low status of the HDSEL disk interface input. A logic "0" selects side 1 and a logic "1" selects side 0.
BIT 4 TRACK 0
Active high status of the TRK0 disk interface input.
BIT 5 STEP
Active high status of the latched STEP disk interface output pin. This bit is latched with the STEP output
going active, and is cleared with a read from the DIR register, or with a hardware or software reset.
BIT 6 DMA REQUEST
Active high status of the DMA request pending.
BIT 7 INTERRUPT PENDING
Active high bit indicating the state of the Floppy Disk Interrupt.
Status Register B (SRB)
Address 3F1 READ ONLY
This register is read-only and monitors the state of several disk interface pins in PS/2 and model 30 modes.
The SRB can be accessed at any time when in PS/2 mode. In the PC/AT mode the data bus pins D0 - D7
are held in a high impedance state for a read of address 3F1.
PS/2 Mode
1
BIT 0 MOTOR ENABLE 0
Active high status of the MTR0 disk interface output pin. This bit is low after a hardware reset and
unaffected by a software reset.
BIT 1 MOTOR ENABLE 1
Active high status of the MTR1 disk interface output pin. This bit is low after a hardware reset and
unaffected by a software reset.
BIT 2 WRITE GATE
Active high status of the WGATE disk interface output.
BIT 3 READ DATA TOGGLE
BIT 4 WRITE DATA TOGGLE
Every inactive edge of the WDATA input causes this bit to change state.
BIT 5 DRIVE SELECT 0
Reflects the status of the Drive Select 0 bit of the DOR (address 3F2 bit 0). This bit is cleared after a
hardware reset and it is unaffected by a software reset.
BIT 6 RESERVED
Always read as a logic "1".
BIT 7 RESERVED
Always read as a logic "1".
PS/2 Model 30 Mode
nDRV2
BIT 0 nDRIVE SELECT 2
The DS2 disk interface is not supported.
BIT 1 nDRIVE SELECT 3
The DS3 disk interface is not supported.
BIT 2 WRITE GATE
Active high status of the latched WGATE output signal. This bit is latched by the active going edge of
WGATE and is cleared by the read of the DIR register.
BIT 3 READ DATA
Active high status of the latched RDATA output signal. This bit is latched by the inactive going edge of
RDATA and is cleared by the read of the DIR register.
BIT 4 WRITE DATA
Active high status of the latched WDATA output signal. This bit is latched by the inactive going edge of
WDATA and is cleared by the read of the DIR register. This bit is not gated with WGATE.
BIT 5 nDRIVE SELECT 0
Active low status of the DS0 disk interface output.
BIT 6 nDRIVE SELECT 1
Active low status of the DS1 disk interface output.
BIT 7 nDRV2
Active low status of the DRV2 disk interface input. Note: This function is not supported.
Address 3F2 READ/WRITE
The DOR controls the drive select and motor enables of the disk interface outputs. It also contains the
enable for the DMA logic and a software reset bit. The contents of the DOR are unaffected by a software
reset. The DOR can be written to at any time.
MOT
BIT 0 and 1 DRIVE SELECT
These two bits are binary encoded for the drive selects, thereby allowing only one drive to be selected at
one time.
BIT 2 nRESET
A logic "0" written to this bit resets the Floppy disk controller. This reset will remain active until a logic "1" is
written to this bit. This software reset does not affect the DSR and CCR registers, nor does it affect the
other bits of the DOR register. The minimum reset duration required is 100ns, therefore toggling this bit by
consecutive writes to this register is a valid method of issuing a software reset.
BIT 3 DMAEN
PC/AT and Model 30 Mode:
Writing this bit to logic "1" will enable the DMA and interrupt functions. This bit being a logic "0" will disable
the DMA and interrupt functions. This bit is a logic "0" after a reset and in these modes.
PS/2 Mode: In this mode the DMA and interrupt functions are always enabled. During a reset, this bit will
be cleared to a logic "0".
BIT 4 MOTOR ENABLE 0
This bit controls the MTR0 disk interface output. A logic "1" in this bit will cause the output pin to go active.
BIT 5 MOTOR ENABLE 1
This bit controls the MTR1 disk interface output. A logic "1" in this bit will cause the output pin to go active.
The MTR2 disk interface output is not supported.
BIT 7 MOTOR ENABLE 3
The MTR3 disk interface output is not supported.
1
2DH
Tape Drive Register (TDR)
Address 3F3 READ/WRITE
The Tape Drive Register (TDR) is included for 82077 software compatibility and allows the user to assign
tape support to a particular drive during initialization. Any future references to that drive automatically
invokes tape support. The TDR Tape Select bits TDR.[1:0] determine the tape drive number. Table 5
illustrates the Tape Select Bit encoding. Note that drive 0 is the boot device and cannot be assigned tape
support. The remaining Tape Drive Register bits TDR.[7:2] are tristated when read. The TDR is
unaffected by a software reset.
0
1
1
1
0
1
2
3
Note: The LPC47N227 supports one floppy drive directly on the FDC interface pins and two floppy drives
on the Parallel Port.
Normal Floppy Mode
Enhanced Floppy Mode 2 (OS2)
Register 3F3 for Enhanced Floppy Mode 2 operation.
Note:
Data Rate Select Register (DSR)
Address 3F4 WRITE ONLY
This register is write only. It is used to program the data rate, amount of write precompensation, power
down status, and software reset. The data rate is programmed using the Configuration Control Register
(CCR) not the DSR, for PC/AT and PS/2 Model 30 applications. Other applications can set the data rate in
the DSR. The data rate of the floppy controller is the most recent write of either the DSR or CCR. The DSR
is unaffected by a software reset. A hardware reset will set the DSR to 02H, which corresponds to the
default precompensation setting and 250 Kbps.
S/W
BIT 0 and 1 DATA RATE SELECT
These bits control the data rate of the floppy controller. See Table 8 for the settings corresponding to the
individual data rates. The data rate select bits are unaffected by a software reset, and are set to 250 Kbps
after a hardware reset.
BIT 2 through 4 PRECOMPENSATION SELECT
These three bits select the value of write precompensation that will be applied to the WDATA output signal.
Table 7 shows the precompensation values for the combination of these bits settings. Track 0 is the
default starting track number to start precompensation. This starting track number can be changed by the
configure command.
BIT 5 UNDEFINED
Should be written as a logic "0".
BIT 6 LOW POWER
A logic "1" written to this bit will put the floppy controller into manual low power mode. The floppy controller
clock and data separator circuits will be turned off. The controller will come out of manual low power mode
after a software reset or access to the Data Register or Main Status Register.
BIT 7 SOFTWARE RESET
This active high bit has the same function as the DOR RESET (DOR bit 2) except that this bit is self
clearing.
Note: The DSR is Shadowed in the Floppy Data Rate Select Shadow Register, located in the
Configuration section (CR14).
001
010
011
100
101
110
000
83.34
166.67
208.33
250.00
41.7
62.5
83.3
Drive Rate Table (Recommended) 00 = 360K, 1.2M, 720K, 1.44M and 2.88M Vertical Format
01
2/1 MB 5.25" FDDS
2/1.6/1 MB 3.5" (3-MODE)
1 Mbps
300 Kbps
250 Kbps
125 ns
125 ns
Main Status Register (MSR)
Address 3F4 READ ONLY
The Main Status Register is a read-only register and indicates the status of the disk controller. The Main
Status Register can be read at any time. The MSR indicates when the disk controller is ready to receive
data via the Data Register. It should be read before each byte transferring to or from the data register
except in DMA mode. No delay is required when reading the MSR after a data transfer.
DMA
BUSY
BUSY
BIT 0 - 1 DRV x BUSY
These bits are set to 1s when a drive is in the seek portion of a command, including implied and overlapped
seeks and recalibrates.
BIT 4 COMMAND BUSY
This bit is set to a 1 when a command is in progress. This bit will go active after the command byte has
been accepted and goes inactive at the end of the results phase. If there is no result phase (Seek,
Recalibrate commands), this bit is returned to a 0 after the last command byte.
BIT 5 NON-DMA
This mode is selected in the SPECIFY command and will be set to a 1 during the execution phase of a
command. This is for polled data transfers and helps differentiate between the data transfer phase and the
reading of result bytes.
BIT 6 DIO
Indicates the direction of a data transfer once a RQM is set. A 1 indicates a read and a 0 indicates a write
is required.
Indicates that the host can transfer data if set to a 1. No access is permitted if set to a 0.
Data Register (FIFO)
Address 3F5 READ/WRITE
All command parameter information, disk data and result status are transferred between the host processor
and the floppy disk controller through the Data Register.
Data transfers are governed by the RQM and DIO bits in the Main Status Register.
The Data Register defaults to FIFO disabled mode after any form of reset. This maintains PC/AT hardware
compatibility. The default values can be changed through the Configure command (enable full FIFO
operation with threshold control). The advantage of the FIFO is that it allows the system a larger DMA
latency without causing a disk error. Table 11 gives several examples of the delays with a FIFO.
The data is based upon the following formula:
x
RATE
At the start of a command, the FIFO action is always disabled and command parameters are sent based
upon the RQM and DIO bit settings. As the command execution phase is entered, the FIFO is cleared of
any data to ensure that invalid data is not transferred.
An overrun or underrun will terminate the current command and the transfer of data. Disk writes will
complete the current sector by generating a 00 pattern and valid CRC. Reads require the host to remove
the remaining data so that the result phase may be entered.
8 bytes
8 bytes
8 bytes
Digital Input Register (DIR)
Address 3F7 READ ONLY
This register is read-only in all modes.
PC-AT Mode
DSK
BIT 0 - 6 UNDEFINED
The data bus outputs D0 - 6 are read as `0'.
BIT 7 DSKCHG
This bit monitors the pin of the same name and reflects the opposite value seen on the disk cable or the
value programmed in the Force FDD Status Change Register (CR17). See the Configuration section for
register description.
PS/2 Mode
DSK
BIT 0 nHIGH DENS
This bit is low whenever the 500 Kbps or 1 Mbps data rates are selected, and high when 250 Kbps and 300
Kbps are selected.
BITS 1 - 2 DATA RATE SELECT
These bits control the data rate of the floppy controller. See Table 8 for the settings corresponding to the
individual data rates. The data rate select bits are unaffected by a software reset, and are set to 250
Kbps after a hardware reset.
BITS 3 - 6 UNDEFINED
Always read as a logic "1"
This bit monitors the pin of the same name and reflects the opposite value seen on the disk cable or the
value programmed in the Force Disk Change Register (CR17). See the Configuration section for register
description.
Model 30 Mode
DSK
BITS 0 - 1 DATA RATE SELECT
These bits control the data rate of the floppy controller. See Table 8 for the settings corresponding to the
individual data rates. The data rate select bits are unaffected by a software reset, and are set to 250 Kbps
after a hardware reset.
BIT 2 NOPREC
This bit reflects the value of NOPREC bit set in the CCR register.
BIT 3 DMAEN
This bit reflects the value of DMAEN bit set in the DOR register bit 3.
BITS 4 - 6 UNDEFINED
Always read as a logic "0"
BIT 7 DSKCHG
This bit monitors the pin of the same name and reflects the opposite value seen on the disk cable or the
value programmed in the Force Disk Change Register (CR17). See the Configuration section for register
description.
Configuration Control Register (CCR)
Address 3F7 WRITE ONLY
PC/AT and PS/2 Modes
0 0 0 0 0 0
BIT 0 and 1 DATA RATE SELECT 0 and 1
These bits determine the data rate of the floppy controller. See Table 8 for the appropriate values.
BIT 2 - 7 RESERVED
Should be set to a logical "0".
0 0 0 0 0
BIT 0 and 1 DATA RATE SELECT 0 and 1
These bits determine the data rate of the floppy controller. See Table 8 for the appropriate values.
BIT 2 NO PRECOMPENSATION
This bit can be set by software, but it has no functionality. It can be read by bit 2 of the DSR when in Model
30 register mode. Unaffected by software reset.
BIT 3 - 7 RESERVED
Should be set to a logical "0"
Table 9 shows the state of the DENSEL pin. The DENSEL pin is set high after a hardware reset and is
unaffected by the DOR and the DSR resets.
Status Register Encoding
During the Result Phase of certain commands, the Data Register contains data bytes that give the status of
the command just executed.
error.
01 - Abnormal termination of command. Command
execution was started, but was not successfully
completed.
10 - Invalid command. The requested command could
not be executed.
11 - Abnormal termination caused by Polling.
Recalibrate command (used during a Sense Interrupt
Command).
Check
1. 80 step pulses in the Recalibrate command.
2. The Relative Seek command caused the FDC to
of the track (255D). Will be set if TC is not issued after
Read or Write Data command.
the data field of a sector.
service within the required time interval, resulting in data
overrun or underrun.
1. Read Data, Read Deleted Data command - the FDC
Address Mark
1. The FDC did not detect an ID address mark at the
from the nINDEX pin twice.
Read Data command - the FDC encountered a deleted
data address mark.
Read Deleted Data command - the FDC encountered a
data address mark.
Data Field
from the track address maintained inside the FDC.
equal to FF hex, which indicates a bad track with a hard
error according to the IBM soft-sectored format.
data address mark.
Protected
RESET
There are three sources of system reset on the FDC: the nPCI_RESET pin, a reset generated via a bit in
the DOR, and a reset generated via a bit in the DSR. At power on, a Power On Reset initializes the FDC.
All resets take the FDC out of the power down state.
All operations are terminated upon a nPCI_RESET, and the FDC enters an idle state. A reset while a disk
write is in progress will corrupt the data and CRC.
On exiting the reset state, various internal registers are cleared, including the Configure command
information, and the FDC waits for a new command. Drive polling will start unless disabled by a new
Configure command.
The nPCI_RESET pin is a global reset and clears all registers except those programmed by the Specify
command. The DOR reset bit is enabled and must be cleared by the host to exit the reset state.
DOR Reset vs. DSR Reset (Software Reset)
These two resets are functionally the same. Both will reset the FDC core, which affects drive status
information and the FIFO circuits. The DSR reset clears itself automatically while the DOR reset requires
the host to manually clear it. DOR reset has precedence over the DSR reset. The DOR reset is set
automatically upon a pin reset. The user must manually clear this reset bit in the DOR to exit the reset
state.
MODES OF OPERATION
The FDC has three modes of operation, PC/AT mode, PS/2 mode and Model 30 mode. These are
determined by the state of the Interface Mode bits (MFM and IDENT) in CR03[5,6].
PC/AT mode
The PC/AT register set is enabled, the DMA enable bit of the DOR becomes valid (controls the interrupt
and DMA functions), and DENSEL is an active high signal.
PS/2 mode
This mode supports the PS/2 models 50/60/80 configuration and register set. The DMA bit of the DOR
becomes a "don't care". The DMA and interrupt functions are always enabled, and DENSEL is active low.
Model 30 mode
This mode supports PS/2 Model 30 configuration and register set. The DMA enable bit of the DOR
becomes valid (controls the interrupt and DMA functions), and DENSEL is active low.
DMA Transfers
DMA transfers are enabled with the Specify command and are initiated by the FDC by activating a DMA
request cycle. DMA read, write and verify cycles are supported. The FDC supports two DMA transfer
modes: single Transfer and Burst Transfer. Burst mode is enabled via CR05-Bit[2]. See the Configuration
section.
Controller Phases
For simplicity, command handling in the FDC can be divided into three phases: Command, Execution, and
Result. Each phase is described in the following sections.
Command Phase
After a reset, the FDC enters the command phase and is ready to accept a command from the host. For
each of the commands, a defined set of command code bytes and parameter bytes has to be written to the
FDC before the command phase is complete. (Please refer to Table 16 for the command set descriptions).
These bytes of data must be transferred in the order prescribed.
Before writing to the FDC, the host must examine the RQM and DIO bits of the Main Status Register.
RQM and DIO must be equal to "1" and "0" respectively before command bytes may be written. RQM is
set false by the FDC after each write cycle until the received byte is processed. The FDC asserts RQM
again to request each parameter byte of the command unless an illegal command condition is detected.
After the last parameter byte is received, RQM remains "0" and the FDC automatically enters the next
phase as defined by the command definition.
Command" condition.
Execution Phase
All data transfers to or from the FDC occur during the execution phase, which can proceed in DMA or non-
DMA mode as indicated in the Specify command.
After a reset, the FIFO is disabled. Each data byte is transferred by a read/write or DMA cycle depending
on the DMA mode. The Configure command can enable the FIFO and set the FIFO threshold value.
The following paragraphs detail the operation of the FIFO flow control. In these descriptions, <threshold> is
defined as the number of bytes available to the FDC when service is requested from the host and ranges
from 1 to 16. The parameter FIFOTHR, which the user programs, is one less and ranges from 0 to 15.
A low threshold value (i.e. 2) results in longer periods of time between service requests, but requires faster
servicing of the request for both read and write cases. The host reads (writes) from (to) the FIFO until
empty (full), then the transfer request goes inactive. The host must be very responsive to the service
request. This is the desired case for use with a "fast" system.
A high value of threshold (i.e. 12) is used with a "sluggish" system by affording a long latency period after a
service request, but results in more frequent service requests.
Non-DMA Mode - Transfers from the FIFO to the Host
The interrupt and RQM bit in the Main Status Register are activated when the FIFO contains (16-
<threshold>) bytes or the last bytes of a full sector have been placed in the FIFO. The interrupt can be
used for interrupt-driven systems, and RQM can be used for polled systems. The host must respond to the
request by reading data from the FIFO. This process is repeated until the last byte is transferred out of the
FIFO. The FDC will deactivate the interrupt and RQM bit when the FIFO becomes empty.
Non-DMA Mode - Transfers from the Host to the FIFO
The interrupt and RQM bit in the Main Status Register are activated upon entering the execution phase of
data transfer commands. The host must respond to the request by writing data into the FIFO. The interrupt
and RQM bit remain true until the FIFO becomes full. They are set true again when the FIFO has
<threshold> bytes remaining in the FIFO. The FDC enters the result phase after the last byte is taken by
the FDC from the FIFO (i.e. FIFO empty condition).
DMA Mode - Transfers from the FIFO to the Host
The FDC generates a DMA request cycle when the FIFO contains (16 - <threshold>) bytes, or the last byte
of a full sector transfer has been placed in the FIFO. The DMA controller responds to the request by
reading data from the FIFO. The FDC will deactivate the DMA request when the FIFO becomes empty by
generating the proper sync for the data transfer.
DMA Mode - Transfers from the Host to the FIFO.
The FDC generates a DMA request cycle when entering the execution phase of the data transfer
commands. The DMA controller responds by placing data in the FIFO. The DMA request remains active
until the FIFO becomes full. The DMA request cycle is reasserted when the FIFO has <threshold> bytes
required.
Data Transfer Termination
The FDC supports terminal count explicitly through the TC cycle and implicitly through the
underrun/overrun and end-of-track (EOT) functions. For full sector transfers, the EOT parameter can
define the last sector to be transferred in a single or multi-sector transfer.
If the last sector to be transferred is a partial sector, the host can stop transferring the data in mid-sector,
and the FDC will continue to complete the sector as if a TC cycle was received. The only difference
between these implicit functions and TC cycle is that they return "abnormal termination" result status. Such
status indications can be ignored if they were expected.
Note that when the host is sending data to the FIFO of the FDC, the internal sector count will be complete
when the FDC reads the last byte from its side of the FIFO. There may be a delay in the removal of the
transfer request signal of up to the time taken for the FDC to read the last 16 bytes from the FIFO. The
host must tolerate this delay.
Result Phase
The generation of the interrupt determines the beginning of the result phase. For each of the commands, a
defined set of result bytes has to be read from the FDC before the result phase is complete. These bytes
of data must be read out for another command to start.
RQM and DIO must both equal "1" before the result bytes may be read. After all the result bytes have been
read, the RQM and DIO bits switch to "1" and "0" respectively, and the CB bit is cleared, indicating that the
FDC is ready to accept the next command.
Command Set/Descriptions
Commands can be written whenever the FDC is in the command phase. Each command has a unique
set of needed parameters and status results. The FDC checks to see that the first byte is a valid
command and, if valid, proceeds with the command. If it is invalid, an interrupt is issued. The user
sends a Sense Interrupt Status command which returns an invalid command error. Refer to Table 16
for explanations of the various symbols used. Table 17 lists the required parameters and the results
associated with each command that the FDC is capable of performing.
Perpendicular Mode Command. A "1" indicates a perpendicular
drive.
relative seek. If set to a 1, the head will step in toward the spindle.
0 0 Drive 0
0 1 Drive 1
bytes transferred in disk read/write commands. The sector size (N =
0) is set to 128. If the actual sector (on the diskette) is larger than
DTL, the remainder of the actual sector is read but is not passed to
the host during read commands; during write commands, the
remainder of the actual sector is written with all zero bytes. The CRC
check code is calculated with the actual sector. When N is not zero,
DTL has no meaning and should be set to FF HEX.
becomes SC (number of sectors per track).
FIFO (default).
read or write command that requires the C parameter in the
command phase. A "0" disables the implied seek.
VCO synchronization field).
field.
initializing a read or write operation. Refer to the Specify command
for actual delays.
command for actual delays.
the CONFIGURE COMMAND can be reset to their default values by
a "software Reset". (A reset caused by writing to the appropriate bits
of either the DSR or DOR)
density (FM) mode.
mode, the FDC treats a complete cylinder under head 0 and 1 as a
single track. The FDC operates as this expanded track started at the
first sector under head 0 and ended at the last sector under head 1.
With this flag set, a multitrack read or write operation will
automatically continue to the first sector under head 1 when the FDC
finishes operating on the last sector under head 0.
transferred is determined by the DTL parameter. Otherwise the sector
size is (2 raised to the "N'th" power) times 128. All values up to "07"
hex are allowable. "07"h would equal a sector size of 16k. It is the
user's responsibility to not select combinations that are not possible
with the drive.
N SECTOR
07 16K
mode. In this mode, the host is interrupted for each data transfer.
When set to 0, the FDC operates in DMA mode.
modified if OW is set to 1. OW id defined in the Lock command.
Status command.
is enabled.
Number
this parameter specifies the sector number of the first sector to be
read or written.
Seek command.
Per Track
command. The number of sectors per track to be verified during a
Verify command when EC is set.
automatically be skipped during the execution of Read Data. If Read
Deleted is executed, only sectors with a deleted address mark will be
accessed. When set to "0", the sector is read or written the same as
the read and write commands.
the 1 Mbit data rate. Refer to the SPECIFY command for actual
delays.
ST1
ST2
ST3
Status 1
Status 2
Status 3
command has been executed. This status information is available to
the host during the result phase after command execution.
drives.
Instruction Set
Command execution.
FDD and system.
mand execution.
Command execution.
Command execution.
FDD and system.
mand execution.
Command execution.
Command execution.
FDD and system.
mand execution.
Command execution.
prior to Command
execution.
the FDD and system.
Command execution.
after Command
execution.
prior to Command
execution.
the FDD and system.
FDC reads all of
cylinders' contents from
index hole to EOT.
Command execution.
after Command
execution.
prior to Command
execution.
place.
Command execution.
after Command
execution.
Each Sector
Repeat:
cylinder
Command execution
Interrupt.
of each seek operation.
FDD
proper cylinder on
diskette.
Information
placed in
FIFO
information on the
Cylinder is stored in Data
Register
R
R
R
R
R
ST1
ST2
H
R
N
Command execution.
(NoOp - FDC goes into Stand-
by State)
SC is returned if the last command that was issued was the Format command. EOT is returned if the last
command was a Read or Write.
Note: These bits are used internally only. They are not reflected in the Drive Select pins. It is the user's
responsibility to maintain correspondence between these bits and the Drive Select pins (DOR).
All of the Read Data, Write Data and Verify type commands use the same parameter bytes and return the
same results information, the only difference being the coding of bits 0-4 in the first byte.
An implied seek will be executed if the feature was enabled by the Configure command. This seek is
completely transparent to the user. The Drive Busy bit for the drive will go active in the Main Status
Register during the seek portion of the command. If the seek portion fails, it is reflected in the results status
normally returned for a Read/Write Data command. Status Register 0 (ST0) would contain the error code
and C would contain the cylinder on which the seek failed.
Read Data
A set of nine (9) bytes is required to place the FDC in the Read Data Mode. After the Read Data command
has been issued, the FDC loads the head (if it is in the unloaded state), waits the specified head settling
time (defined in the Specify command), and begins reading ID Address Marks and ID fields. When the
sector address read off the diskette matches with the sector address specified in the command, the FDC
reads the sector's data field and transfers the data to the FIFO.
After completion of the read operation from the current sector, the sector address is incremented by one
and the data from the next logical sector is read and output via the FIFO. This continuous read function is
called "Multi-Sector Read Operation". Upon receipt of the TC cycle, or an implied TC (FIFO
overrun/underrun), the FDC stops sending data but will continue to read data from the current sector, check
the CRC bytes, and at the end of the sector, terminate the Read Data Command.
N determines the number of bytes per sector (see Table 18 below). If N is set to zero, the sector size is set
to 128. The DTL value determines the number of bytes to be transferred. If DTL is less than 128, the FDC
transfers the specified number of bytes to the host. For reads, it continues to read the entire 128-byte
sector and checks for CRC errors. For writes, it completes the 128-byte sector by filling in zeros. If N is not
set to 00 Hex, DTL should be set to FF Hex and has no impact on the number of bytes transferred.
01
02
03
256 bytes
512 bytes
The amount of data which can be handled with a single command to the FDC depends upon MT (multi-
track) and N (number of bytes/sector).
The Multi-Track function (MT) allows the FDC to read data from both sides of the diskette. For a particular
cylinder, data will be transferred starting at Sector 1, Side 0 and completing the last sector of the same
track at Side 1.
If the host terminates a read or write operation in the FDC, the ID information in the result phase is
dependent upon the state of the MT bit and EOT byte. Refer to Table 19.
Interval (specified in the Specify command) has elapsed. If the host issues another command before the
head unloads, then the head settling time may be saved between subsequent reads.
If the FDC detects a pulse on the nINDEX pin twice without finding the specified sector (meaning that the
diskette's index hole passes through index detect logic in the drive twice), the FDC sets the IC code in
Status Register 0 to "01" indicating abnormal termination, sets the ND bit in Status Register 1 to "1"
indicating a sector not found, and terminates the Read Data Command.
After reading the ID and Data Fields in each sector, the FDC checks the CRC bytes. If a CRC error
occurs in the ID or data field, the FDC sets the IC code in Status Register 0 to "01" indicating abnormal
termination, sets the DE bit flag in Status Register 1 to "1", sets the DD bit in Status Register 2 to "1" if
CRC is incorrect in the ID field, and terminates the Read Data Command. Table 20 describes the effect
of the SK bit on the Read Data command execution and results. Except where noted in Table 20, the C
or R value of the sector address is automatically incremented (see Table 22)
1
0
1
0
1
1
2
2
3
3
256 x 52 = 13,312
512 x 15 = 7,680
512 x 30 = 15,360
1024 x 8 = 8,192
1024 x 16 = 16,384
26 at side 1
15 at side 0 or 1
15 at side 1
8 at side 0 or 1
16 at side 1
incremented. Next
sector not
searched for.
not read
("skipped").
This command is the same as the Read Data command, only it operates on sectors that contain a Deleted
Data Address Mark at the beginning of a Data Field.
Table 21 describes the effect of the SK bit on the Read Deleted Data command execution and results.
Except where noted in Table 21, the C or R value of the sector address is automatically incremented (see
Table 22).
Deleted Data
Normal Data
Deleted Data
incremented. Next
sector not
searched for.
Normal
termination.
Normal
termination. Sector
not read
("skipped").
Normal
termination.
Read A Track
This command is similar to the Read Data command except that the entire data field is read continuously
from each of the sectors of a track. Immediately after encountering a pulse on the nINDEX pin, the FDC
starts to read all data fields on the track as continuous blocks of data without regard to logical sector
numbers. If the FDC finds an error in the ID or DATA CRC check bytes, it continues to read data from the
track and sets the appropriate error bits at the end of the command. The FDC compares the ID information
read from each sector with the specified value in the command and sets the ND flag of Status Register 1 to
a "1" if there no comparison. Multi-track or skip operations are not allowed with this command. The MT and
SK bits (bits D7 and D5 of the first command byte respectively) should always be set to "0".
This command terminates when the EOT specified number of sectors has not been read. If the FDC does
not find an ID Address Mark on the diskette after the second occurrence of a pulse on the nINDEX pin,
then it sets the IC code in Status Register 0 to "01" (abnormal termination), sets the MA bit in Status
Register 1 to "1", and terminates the command.
Write Data
After the Write Data command has been issued, the FDC loads the head (if it is in the unloaded state),
waits the specified head load time if unloaded (defined in the Specify command), and begins reading ID
fields. When the sector address read from the diskette matches the sector address specified in the
command, the FDC reads the data from the host via the FIFO and writes it to the sector's data field.
After writing data into the current sector, the FDC computes the CRC value and writes it into the CRC field
at the end of the sector transfer. The Sector Number stored in "R" is incremented by one, and the FDC
continues writing to the next data field. The FDC continues this "Multi-Sector Write Operation". Upon
receipt of a terminal count signal or if a FIFO over/under run occurs while a data field is being written, then
the remainder of the data field is filled with zeros. The FDC reads the ID field of each sector and checks
the CRC bytes. If it detects a CRC error in one of the ID fields, it sets the IC code in Status Register 0 to
"01" (abnormal termination), sets the DE bit of Status Register 1 to "1", and terminates the Write Data
command.
The Write Data command operates in much the same manner as the Read Data command. The following
items are the same. Please refer to the Read Data Command for details:
Transfer Capacity
EN (End of Cylinder) bit
ND (No Data) bit
Head Load, Unload Time Interval
ID information when the host terminates the command
Definition of DTL when N = 0 and when N does not = 0
Write Deleted Data
This command is almost the same as the Write Data command except that a Deleted Data Address Mark
is written at the beginning of the Data Field instead of the normal Data Address Mark. This command is
typically used to mark a bad sector containing an error on the floppy disk.
The Verify command is used to verify the data stored on a disk. This command acts exactly like a Read
Data command except that no data is transferred to the host. Data is read from the disk and CRC is
computed and checked against the previously-stored value.
Because data is not transferred to the host, the TC cycle cannot be used to terminate this command. By
setting the EC bit to "1", an implicit TC will be issued to the FDC. This implicit TC will occur when the
SC value has decremented to 0 (an SC value of 0 will verify 256 sectors). This command can also be
terminated by setting the EC bit to "0" and the EOT value equal to the final sector to be checked. If EC is
set to "0", DTL/SC should be programmed to 0FFH. Refer to Table 22 and Table 23 for information
concerning the values of MT and EC versus SC and EOT value.
Definitions:
# Sectors Per Side = Number of formatted sectors per each side of the disk.
# Sectors Remaining = Number of formatted sectors left which can be read, including side 1 of the disk if
MT is set to "1".
Result Phase Valid
Result Phase Invalid
Result Phase Valid
Result Phase Invalid
Result Phase Valid
Result Phase Invalid
Result Phase Valid
Result Phase Invalid
Note: If MT is set to "1" and the SC value is greater than the number of remaining formatted sectors on
Side 0, verifying will continue on Side 1 of the disk.
Format A Track
The Format command allows an entire track to be formatted. After a pulse from the nINDEX pin is
detected, the FDC starts writing data on the disk including gaps, address marks, ID fields, and data fields
per the IBM System 34 or 3740 format (MFM or FM respectively). The particular values that will be written
to the gap and data field are controlled by the values programmed into N, SC, GPL, and D which are
specified by the host during the command phase. The data field of the sector is filled with the data byte
specified by D. The ID field for each sector is supplied by the host; that is, four data bytes per sector are
needed by the FDC for C, H, R, and N (cylinder, head, sector number and sector size respectively).
After formatting each sector, the host must send new values for C, H, R and N to the FDC for the next
sector on the track. The R value (sector number) is the only value that must be changed by the host after
each sector is formatted. This allows the disk to be formatted with nonsequential sector addresses
(interleaving). This incrementing and formatting continues for the whole track until the FDC encounters a
pulse on the nINDEX pin again and it terminates the command.
Table 24 contains typical values for gap fields which are dependent upon the size of the sector and the
number of sectors on each track. Actual values can vary due to drive electronics.
Y
D
E
C
O
R
C
R
C
00
00
Y
D
E
C
O
R
C
00
R
C
Y
D
E
C
O
R
C
R
C
128
512
2048
4096
00
02
03
04
05
10
08
04
02
01
10
18
46
C8
19
30
87
FF
256
2048
4096
01
02
03
04
05
10
09
04
02
01
C8
50
F0
FF
256
512
1
2
09
05
0F
2A
3A
2
3
09
05
1B
54
74
between data field and ID field of contiguous sections.
GPL2 = suggested GPL value in Format A Track command.
*PC/AT values (typical)
**PS/2 values (typical). Applies with 1.0 MB and 2.0 MB drives.
NOTE: All values except sector size are in hex.
Control commands differ from the other commands in that no data transfer takes place. Three commands
generate an interrupt when complete: Read ID, Recalibrate, and Seek. The other control commands do
not generate an interrupt.
Read ID
The Read ID command is used to find the present position of the recording heads. The FDC stores the
values from the first ID field it is able to read into its registers. If the FDC does not find an ID address mark
on the diskette after the second occurrence of a pulse on the nINDEX pin, it then sets the IC code in Status
Register 0 to "01" (abnormal termination), sets the MA bit in Status Register 1 to "1", and terminates the
command.
The following commands will generate an interrupt upon completion. They do not return any result bytes. It
is highly recommended that control commands be followed by the Sense Interrupt Status command.
Otherwise, valuable interrupt status information will be lost.
Recalibrate
This command causes the read/write head within the FDC to retract to the track 0 position. The FDC
clears the contents of the PCN counter and checks the status of the nTRK0 pin from the FDD. As long as
the nTRK0 pin is low, the DIR pin remains 0 and step pulses are issued. When the nTRK0 pin goes high,
the SE bit in Status Register 0 is set to "1" and the command is terminated. If the nTR0 pin is still low after
79 step pulses have been issued, the FDC sets the SE and the EC bits of Status Register 0 to "1" and
terminates the command. Disks capable of handling more than 80 tracks per side may require more than
one Recalibrate command to return the head back to physical Track 0.
The Recalibrate command does not have a result phase. The Sense Interrupt Status command must be
issued after the Recalibrate command to effectively terminate it and to provide verification of the head
position (PCN). During the command phase of the recalibrate operation, the FDC is in the BUSY state, but
during the execution phase it is in a NON-BUSY state. At this time, another Recalibrate command may be
issued, and in this manner parallel Recalibrate operations may be done on up to four drives at once. Upon
power up, the software must issue a Recalibrate command to properly initialize all drives and the controller.
Seek
The read/write head within the drive is moved from track to track under the control of the Seek command.
The FDC compares the PCN, which is the current head position, with the NCN and performs the following
operation if there is a difference:
The rate at which step pulses are issued is controlled by SRT (Stepping Rate Time) in the Specify
command. After each step pulse is issued, NCN is compared against PCN, and when NCN = PCN the SE
bit in Status Register 0 is set to "1" and the command is terminated. During the command phase of the
seek or recalibrate operation, the FDC is in the BUSY state, but during the execution phase it is in the
NON-BUSY state. At this time, another Seek or Recalibrate command may be issued, and in this manner,
parallel seek operations may be done on up to four drives at once.
Note that if implied seek is not enabled, the read and write commands should be preceded by:
1) Seek command - Step to the proper track
2) Sense Interrupt Status command - Terminate the Seek command
4) Issue Read/Write command.
The Seek command does not have a result phase. Therefore, it is highly recommended that the Sense
Interrupt Status command is issued after the Seek command to terminate it and to provide verification of
the head position (PCN). The H bit (Head Address) in ST0 will always return to a "0". When exiting
POWERDOWN mode, the FDC clears the PCN value and the status information to zero. Prior to issuing
the POWERDOWN command, it is highly recommended that the user service all pending interrupts through
the Sense Interrupt Status command.
Sense Interrupt Status
An interrupt signal is generated by the FDC for one of the following reasons:
1. Upon entering the Result Phase of:
2. End of Seek, Relative Seek, or Recalibrate command
3. FDC requires a data transfer during the execution phase in the non-DMA mode
The Sense Interrupt Status command resets the interrupt signal and, via the IC code and SE bit of
Status Register 0, identifies the cause of the interrupt.
1
00
Normal termination of Seek or
Recalibrate command
Abnormal termination of Seek
or Recalibrate command
The Seek, Relative Seek, and Recalibrate commands have no result phase. The Sense Interrupt Status
command must be issued immediately after these commands to terminate them and to provide verification
of the head position (PCN). The H (Head Address) bit in ST0 will always return a "0". If a Sense Interrupt
Status is not issued, the drive will continue to be BUSY and may affect the operation of the next command.
Sense Drive Status
Sense Drive Status obtains drive status information. It has not execution phase and goes directly to the
result phase from the command phase. Status Register 3 contains the drive status information.
Specify
The Specify command sets the initial values for each of the three internal times. The HUT (Head
Unload Time) defines the time from the end of the execution phase of one of the read/write commands
pulses. Note that the spacing between the first and second step pulses may be shorter than the
remaining step pulses. The HLT (Head Load Time) defines the time between when the Head Load
signal goes high and the read/write operation starts. The values change with the data rate speed
selection and are documented in Table 26. The values are the same for MFM and FM.
The choice of DMA or non-DMA operations is made by the ND bit. When this bit is "1", the non-DMA
mode is selected, and when ND is "0", the DMA mode is selected. In DMA mode, data transfers are
signaled by the DMA request cycles. Non-DMA mode uses the RQM bit and the interrupt to signal data
transfers.
Configure
The Configure command is issued to select the special features of the FDC. A Configure command
need not be issued if the default values of the FDC meet the system requirements.
1
..
F
..
60
..
120
240
400
480
1
15
2
1
1.67
30
4
2
01
02
7F
..
2
..
127
4
..
254
6.7
423
8
508
Configure Default Values:
EIS - No Implied Seeks
EFIFO - FIFO Disabled
POLL - Polling Enabled
FIFOTHR - FIFO Threshold Set to 1 Byte
PRETRK - Pre-Compensation Set to Track 0
EIS - Enable Implied Seek. When set to "1", the FDC will perform a Seek operation before executing a
read or write command. Defaults to no implied seek.
EFIFO - A "1" disables the FIFO (default). This means data transfers are asked for on a byte-by-byte basis.
Defaults to "1", FIFO disabled. The threshold defaults to "1".
POLL - Disable polling of the drives. Defaults to "0", polling enabled. When enabled, a single interrupt is
generated after a reset. No polling is performed while the drive head is loaded and the head unload delay
has not expired.
FIFOTHR - The FIFO threshold in the execution phase of read or write commands. This is programmable
from 1 to 16 bytes. Defaults to one byte. A "00" selects one byte; "0F" selects 16 bytes.
PRETRK - Pre-Compensation Start Track Number. Programmable from track 0 to 255. Defaults to track 0.
A "00" selects track 0; "FF" selects track 255.
Version
The Version command checks to see if the controller is an enhanced type or the older type (765A). A value
of 90 H is returned as the result byte.
Relative Seek
The command is coded the same as for Seek, except for the MSB of the first byte and the DIR bit.
DIR Head Step Direction Control
RCN
1
Step Head In
The Relative Seek command differs from the Seek command in that it steps the head the absolute number
of tracks specified in the command instead of making a comparison against an internal register. The Seek
command is good for drives that support a maximum of 256 tracks. Relative Seeks cannot be overlapped
with other Relative Seeks. Only one Relative Seek can be active at a time. Relative Seeks may be
overlapped with Seeks and Recalibrates. Bit 4 of Status Register 0 (EC) will be set if Relative Seek
attempts to step outward beyond Track 0.
As an example, assume that a floppy drive has 300 useable tracks. The host needs to read track 300 and
the head is on any track (0-255). If a Seek command is issued, the head will stop at track 255. If a Relative
Seek command is issued, the FDC will move the head the specified number of tracks, regardless of the
internal cylinder position register (but will increment the register). If the head was on track 40 (d), the
maximum track that the FDC could position the head on using Relative Seek will be 295 (D), the initial track
+ 255 (D). The maximum count that the head can be moved with a single Relative Seek command is 255
(D).
The internal register, PCN, will overflow as the cylinder number crosses track 255 and will contain 39 (D).
The resulting PCN value is thus (RCN + PCN) mod 256. Functionally, the FDC starts counting from 0 again
as the track number goes above 255 (D). It is the user's responsibility to compensate FDC functions
(precompensation track number) when accessing tracks greater than 255. The FDC does not keep track
that it is working in an "extended track area" (greater than 255). Any command issued will use the current
PCN value except for the Recalibrate command, which only looks for the TRACK0 signal. Recalibrate will
return an error if the head is farther than 79 due to its limitation of issuing a maximum of 80 step pulses.
The user simply needs to issue a second Recalibrate command. The Seek command and implied seeks
will function correctly within the 44 (D) track (299-255) area of the "extended track area". It is the user's
responsibility not to issue a new track position that will exceed the maximum track that is present in the
extended area.
To return to the standard floppy range (0-255) of tracks, a Relative Seek should be issued to cross the
track 255 boundary.
A Relative Seek can be used instead of the normal Seek, but the host is required to calculate the difference
between the current head location and the new (target) head location. This may require the host to issue a
Read ID command to ensure that the head is physically on the track that software assumes it to be.
Different FDC commands will return different cylinder results which may be difficult to keep track of with
software without the Read ID command.
Perpendicular Mode
The Perpendicular Mode command should be issued prior to executing Read/Write/Format commands that
access a disk drive with perpendicular recording capability. With this command, the length of the Gap2
field and VCO enable timing can be altered to accommodate the unique requirements of these drives.
Table 27 describes the effects of the WGATE and GAP bits for the Perpendicular Mode command. Upon
a reset, the FDC will default to the conventional mode (WGATE = 0, GAP = 0).
Selection of the 500 Kbps and 1 Mbps perpendicular modes is independent of the actual data rate selected
in the Data Rate Select Register. The user must ensure that these two data rates remain consistent.
The Gap2 and VCO timing requirements for perpendicular recording type drives are dictated by the design
of the read/write head. In the design of this head, a pre-erase head precedes the normal read/write head
by a distance of 200 micrometers. This works out to about 38 bytes at a 1 Mbps recording density.
Whenever the write head is enabled by the Write Gate signal, the pre-erase head is also activated at the
same time. Thus, when the write head is initially turned on, flux transitions recorded on the media for the
first 38 bytes will not be preconditioned with the pre-erase head since it has not yet been activated. To
accommodate this head activation and deactivation time, the Gap2 field is expanded to a length of 41
bytes. The Format Fields table illustrates the change in the Gap2 field size for the perpendicular format.
On the read back by the FDC, the controller must begin synchronization at the beginning of the sync field.
For the conventional mode, the internal PLL VCO is enabled (VCOEN) approximately 24 bytes from the
start of the Gap2 field. But, when the controller operates in the 1 Mbps perpendicular mode (WGATE = 1,
GAP = 1), VCOEN goes active after 43 bytes to accommodate the increased Gap2 field size. For both
cases, and approximate two-byte cushion is maintained from the beginning of the sync field for the
purposes of avoiding write splices in the presence of motor speed variation.
For the Write Data case, the FDC activates Write Gate at the beginning of the sync field under the
conventional mode. The controller then writes a new sync field, data address mark, data field, and CRC.
With the pre-erase head of the perpendicular drive, the write head must be activated in the Gap2 field to
insure a proper write of the new sync field. For the 1 Mbps perpendicular mode (WGATE = 1, GAP = 1), 38
bytes will be written in the Gap2 space. Since the bit density is proportional to the data rate, 19 bytes will be
written in the Gap2 field for the 500 Kbps perpendicular mode (WGATE = 1, GAP =0).
It should be noted that none of the alterations in Gap2 size, VCO timing, or Write Gate timing affect normal
program flow. The information provided here is just for background purposes and is not needed for normal
operation. Once the Perpendicular Mode command is invoked, FDC software behavior from the user
standpoint is unchanged.
The perpendicular mode command is enhanced to allow specific drives to be designated Perpendicular
recording drives. This enhancement allows data transfers between Conventional and Perpendicular drives
without having to issue Perpendicular mode commands between the accesses of the different drive types,
nor having to change write pre-compensation values.
When both GAP and WGATE bits of the PERPENDICULAR MODE COMMAND are both programmed to
"0" (Conventional mode), then D0, D1, D2, D3, and D4 can be programmed independently to "1" for that
drive to be set automatically to Perpendicular mode. In this mode the following set of conditions also apply:
1. The GAP2 written to a perpendicular drive during a write operation will depend upon the programmed
3. For D0-D3 programmed to "0" for conventional mode drives any data written will be at the currently
Note: Bits D0-D3 can only be overwritten when OW is programmed as a "1".If either GAP or WGATE is a
Software and hardware resets have the following effect on the PERPENDICULAR MODE COMMAND:
1. "Software" resets (via the DOR or DSR registers) will only clear GAP and WGATE bits to "0". D0-D3
WRITE DATA
0
1
Perpendicular
(500 Kbps)
Reserved
(Conventional)
Perpendicular
(1 Mbps)
22 Bytes
In order to protect systems with long DMA latencies against older application software that can disable the
FIFO the LOCK Command has been added. This command should only be used by the FDC routines, and
application software should refrain from using it. If an application calls for the FIFO to be disabled then the
CONFIGURE command should be used.
The LOCK command defines whether the EFIFO, FIFOTHR, and PRETRK parameters of the
CONFIGURE command can be RESET by the DOR and DSR registers. When the LOCK bit is set to logic
"1" all subsequent "software RESETS by the DOR and DSR registers will not change the previously set
parameters to their default values. All "hardware" RESET from the nPCI_RESET pin will set the LOCK bit
to logic "0" and return the EFIFO, FIFOTHR, and PRETRK to their default values. A status byte is
returned immediately after issuing a LOCK command. This byte reflects the value of the LOCK bit set by
the command byte.
Enhanced DUMPREG
The DUMPREG command is designed to support system run-time diagnostics and application software
development and debug. To accommodate the LOCK command and the enhanced PERPENDICULAR
MODE command the eighth byte of the DUMPREG command has been modified to contain the additional
data from these two commands.
Compatibility
The LPC47N227 was designed with software compatibility in mind. It is a fully backwards- compatible
solution with the older generation 765A/B disk controllers. The FDC also implements on-board registers for
compatibility with the PS/2, as well as PC/AT and PC/XT, floppy disk controller subsystems. After a
hardware reset of the FDC, all registers, functions and enhancements default to a PC/AT, PS/2 or PS/2
Model 30 compatible operating mode, depending on how the IDENT and MFM bits are configured by the
system BIOS.
ACE registers and the NS16C550A. The UARTS perform serial-to-parallel conversion on received
characters and parallel-to-serial conversion on transmit characters. The data rates are independently
programmable from 460.8K baud down to 50 baud. The character options are programmable for 1 start; 1,
1.5 or 2 stop bits; even, odd, sticky or no parity; and prioritized interrupts. The UARTs each contain a
programmable baud rate generator that is capable of dividing the input clock or crystal by a number from 1
Registers for information on disabling, power down and changing the base address of the UARTs. The
interrupt from a UART is enabled by programming OUT2 of that UART to a logic "1". OUT2 being a logic
"0" disables that UART's interrupt. The second UART also supports IrDA 1.2 (4Mbps), HP-SIR, ASK-IR
and Consumer IR infrared modes of operation.
Register Description
Addressing of the accessible registers of the Serial Port is shown below. The base addresses of the serial
ports are defined by the configuration registers (see Configuration section). The Serial Port registers are
located at sequentially increasing addresses above these base addresses. The LPC47N227 contains two
serial ports, each of which contain a register set as described below.
The following section describes the operation of the registers.
Receive Buffer Register (RB)
and received first. Received data is double buffered; this uses an additional shift register to receive the
serial data stream and convert it to a parallel 8 bit word which is transferred to the Receive Buffer register.
The shift register is not accessible.
Transmit Buffer Register (TB)
Address Offset = 0H, DLAB = 0, WRITE ONLY
This register contains the data byte to be transmitted. The transmit buffer is double buffered, utilizing an
additional shift register (not accessible) to convert the 8 bit data word to a serial format. This shift register is
loaded from the Transmit Buffer when the transmission of the previous byte is complete.
Interrupt Enable Register (IER)
Address Offset = 1H, DLAB = 0, READ/WRITE
The lower four bits of this register control the enables of the five interrupt sources of the Serial Port
interrupt. It is possible to totally disable the interrupt system by resetting bits 0 through 3 of this register.
Similarly, setting the appropriate bits of this register to a high, selected interrupts can be enabled. Disabling
the LPC47N227. All other system functions operate in their normal manner, including the Line Status and
MODEM Status Registers. The contents of the Interrupt Enable Register are described below.
Bit 0
This bit enables the Received Data Available Interrupt (and timeout interrupts in the FIFO mode) when set
to logic "1".
Bit 1
This bit enables the Transmitter Holding Register Empty Interrupt when set to logic "1".
Bit 2
This bit enables the Received Line Status Interrupt when set to logic "1". The error sources causing the
interrupt are Overrun, Parity, Framing and Break. The Line Status Register must be read to determine the
source.
Bit 3
This bit enables the MODEM Status Interrupt when set to logic "1". This is caused when one of the Modem
Status Register bits changes state.
Bits 4 through 7
These bits are always logic "0".
FIFO Control Register (FCR)
Address Offset = 2H, DLAB = X, WRITE
This is a write only register at the same location as the IIR. This register is used to enable and clear the
FIFOs, set the RCVR FIFO trigger level. Note: DMA is not supported. The UART1 and UART2 FCR's are
shadowed in the UART1 FIFO Control Shadow Register (CR15) and UART2 FIFO Control Shadow
Register (CR16). See the Configuration section for description on these registers.
Setting this bit to a logic "1" enables both the XMIT and RCVR FIFOs. Clearing this bit to a logic "0"
disables both the XMIT and RCVR FIFOs and clears all bytes from both FIFOs. When changing from FIFO
Mode to non-FIFO (16450) mode, data is automatically cleared from the FIFOs. This bit must be a 1 when
other bits in this register are written to or they will not be properly programmed.
Bit 1
Setting this bit to a logic "1" clears all bytes in the RCVR FIFO and resets its counter logic to 0. The shift
register is not cleared. This bit is self-clearing.
Bit 2
Setting this bit to a logic "1" clears all bytes in the XMIT FIFO and resets its counter logic to 0. The shift
register is not cleared. This bit is self-clearing.
Bit 3
Writing to this bit has no effect on the operation of the UART. DMA modes are not supported in this chip.
Bit 4,5
Reserved
Bit 6,7
These bits are used to set the trigger level for the RCVR FIFO interrupt.
Interrupt Identification Register (IIR)
Address Offset = 2H, DLAB = X, READ
By accessing this register, the host CPU can determine the highest priority interrupt and its source. Four
levels of priority interrupt exist. They are in descending order of priority:
1. Receiver Line Status (highest priority)
2. Received Data Ready
3. Transmitter Holding Register Empty
4. MODEM Status (lowest priority)
Information indicating that a prioritized interrupt is pending and the source of that interrupt is stored in the
Interrupt Identification Register (refer to Interrupt Control Table). When the CPU accesses the IIR, the
Serial Port freezes all interrupts and indicates the highest priority pending interrupt to the CPU. During this
CPU access, even if the Serial Port records new interrupts, the current indication does not change until
access is completed. The contents of the IIR are described below.
This bit can be used in either a hardwired prioritized or polled environment to indicate whether an interrupt
is pending. When bit 0 is a logic "0", an interrupt is pending and the contents of the IIR may be used as a
pointer to the appropriate internal service routine. When bit 0 is a logic "1", no interrupt is pending.
Bits 1 and 2
These two bits of the IIR are used to identify the highest priority interrupt pending as indicated by the
Interrupt Control Table.
Bit 3
In non-FIFO mode, this bit is a logic "0". In FIFO mode this bit is set along with bit 2 when a timeout
interrupt is pending.
Bits 4 and 5
These bits of the IIR are always logic "0".
Bits 6 and 7
These two bits are set when the FIFO CONTROL Register bit 0 equals 1.
Parity Error,
Framing Error or
Break Interrupt
Status Register
Available
Buffer or the FIFO
drops below the
trigger level.
Timeout
Indication
Have Been
Removed From or
Input to the RCVR
FIFO during the
last 4 Char times
and there is at
least 1 char in it
during this time
Receiver Buffer
Register
Register Empty
Holding Register
Empty
Register (if Source
of Interrupt) or
Writing the
Transmitter
Holding Register
Ring Indicator or
Data Carrier
Detect
MODEM Status
Register
Address Offset = 3H, DLAB = 0, READ/WRITE
This register contains the format information of the serial line. The bit definitions are:
Bits 0 and 1
These two bits specify the number of bits in each transmitted or received serial character. The encoding of
bits 0 and 1 is as follows:
The Start, Stop and Parity bits are not included in the word length.
0
1
1
1
0
1
6 Bits
7 Bits
8 Bits
Bit 2
This bit specifies the number of stop bits in each transmitted or received serial character. The following
table summarizes the information.
Note: The receiver will ignore all stop bits beyond the first, regardless of the number used in transmitting.
Bit 3
Parity Enable bit. When bit 3 is a logic "1", a parity bit is generated (transmit data) or checked (receive
data) between the last data word bit and the first stop bit of the serial data. (The parity bit is used to
generate an even or odd number of 1s when the data word bits and the parity bit are summed).
Bit 4
Even Parity Select bit. When bit 3 is a logic "1" and bit 4 is a logic "0", an odd number of logic "1"'s is
transmitted or checked in the data word bits and the parity bit. When bit 3 is a logic "1" and bit 4 is a logic
"1" an even number of bits is transmitted and checked.
Stick Parity bit. When parity is enabled it is used in conjunction with bit 4 to select Mark or Space Parity.
When LCR bits 3, 4 and 5 are 1 the Parity bit is transmitted and checked as 0 (Space Parity). If bits 3 and
5 are 1 and bit 4 is a 0, then the Parity bit is transmitted and checked as 1 (Mark Parity). If bit 5 is 0 Stick
Parity is disabled.
Bit 6
Set Break Control bit. When bit 6 is a logic "1", the transmit data output (TXD) is forced to the Spacing or
logic "0" state and remains there (until reset by a low level bit 6) regardless of other transmitter activity.
This feature enables the Serial Port to alert a terminal in a communications system.
Bit 7
Divisor Latch Access bit (DLAB). It must be set high (logic "1") to access the Divisor Latches of the Baud
Rate Generator during read or write operations. It must be set low (logic "0") to access the Receiver Buffer
Register, the Transmitter Holding Register, or the Interrupt Enable Register.
Modem Control Register (MCR)
Address Offset = 4H, DLAB = X, READ/WRITE
This 8 bit register controls the interface with the MODEM or data set (or device emulating a MODEM). The
contents of the MODEM control register are described below.
Bit 0
This bit controls the Data Terminal Ready (nDTR) output. When bit 0 is set to a logic "1", the nDTR output
is forced to a logic "0". When bit 0 is a logic "0", the nDTR output is forced to a logic "1".
Bit 1
This bit controls the Request To Send (nRTS) output. Bit 1 affects the nRTS output in a manner identical
to that described above for bit 0.
Bit 2
This bit controls the Output 1 (OUT1) bit. This bit does not have an output pin and can only be read or
written by the CPU.
Bit 3
Output 2 (OUT2). This bit is used to enable an UART interrupt. When OUT2 is a logic "0", the serial port
interrupt output is forced to a high impedance state - disabled. When OUT2 is a logic "1", the serial port
interrupt outputs are enabled.
Bit 4
This bit provides the loopback feature for diagnostic testing of the Serial Port. When bit 4 is set to logic "1",
the following occur:
1. The TXD is set to the Marking State(logic "1").
2. The receiver Serial Input (RXD) is disconnected.
3. The output of the Transmitter Shift Register is "looped back" into the Receiver Shift Register input.
4. All MODEM Control inputs (nCTS, nDSR, nRI and nDCD) are disconnected.
5. The four MODEM Control outputs (nDTR, nRTS, OUT1 and OUT2) are internally connected to the four
This feature allows the processor to verify the transmit and receive data paths of the Serial Port. In the
diagnostic mode, the receiver and the transmitter interrupts are fully operational. The MODEM Control
Interrupts are also operational but the interrupts' sources are now the lower four bits of the MODEM Control
Register instead of the MODEM Control inputs. The interrupts are still controlled by the Interrupt Enable
Register.
Bits 5 through 7
These bits are permanently set to logic zero.
Line Status Register (LSR)
Address Offset = 5H, DLAB = X, READ/WRITE
Bit 0
Data Ready (DR). It is set to a logic "1" whenever a complete incoming character has been received and
transferred into the Receiver Buffer Register or the FIFO. Bit 0 is reset to a logic "0" by reading all of the
data in the Receive Buffer Register or the FIFO.
Bit 1
Overrun Error (OE). Bit 1 indicates that data in the Receiver Buffer Register was not read before the next
character was transferred into the register, thereby destroying the previous character. In FIFO mode, an
overrunn error will occur only when the FIFO is full and the next character has been completely received in
the shift register, the character in the shift register is overwritten but not transferred to the FIFO. The OE
indicator is set to a logic "1" immediately upon detection of an overrun condition, and reset whenever the
Line Status Register is read.
Bit 2
Parity Error (PE). Bit 2 indicates that the received data character does not have the correct even or odd
parity, as selected by the even parity select bit. The PE is set to a logic "1" upon detection of a parity error
and is reset to a logic "0" whenever the Line Status Register is read. In the FIFO mode this error is
associated with the particular character in the FIFO it applies to. This error is indicated when the
associated character is at the top of the FIFO.
Bit 3
Framing Error (FE). Bit 3 indicates that the received character did not have a valid stop bit. Bit 3 is set to a
logic "1" whenever the stop bit following the last data bit or parity bit is detected as a zero bit (Spacing
level). The FE is reset to a logic "0" whenever the Line Status Register is read. In the FIFO mode this
error is associated with the particular character in the FIFO it applies to. This error is indicated when the
associated character is at the top of the FIFO. The Serial Port will try to resynchronize after a framing error.
To do this, it assumes that the framing error was due to the next start bit, so it samples this 'start' bit twice
and then takes in the 'data'.
Break Interrupt (BI). Bit 4 is set to a logic "1" whenever the received data input is held in the Spacing state
(logic "0") for longer than a full word transmission time (that is, the total time of the start bit + data bits +
parity bits + stop bits). The BI is reset after the CPU reads the contents of the Line Status Register. In the
FIFO mode this error is associated with the particular character in the FIFO it applies to. This error is
indicated when the associated character is at the top of the FIFO. When break occurs only one zero
character is loaded into the FIFO. Restarting after a break is received, requires the serial data (RXD) to be
logic "1" for at least 1/2 bit time.
Note: Bits 1 through 4 are the error conditions that produce a Receiver Line Status Interrupt whenever any
of the corresponding conditions are detected and the interrupt is enabled.
Bit 5
Transmitter Holding Register Empty (THRE). Bit 5 indicates that the Serial Port is ready to accept a new
character for transmission. In addition, this bit causes the Serial Port to issue an interrupt when the
Transmitter Holding Register interrupt enable is set high. The THRE bit is set to a logic "1" when a
character is transferred from the Transmitter Holding Register into the Transmitter Shift Register. The bit is
reset to logic "0" whenever the CPU loads the Transmitter Holding Register. In the FIFO mode this bit is
set when the XMIT FIFO is empty, it is cleared when at least 1 byte is written to the XMIT FIFO. Bit 5 is a
read only bit.
Bit 6
Transmitter Empty (TEMT). Bit 6 is set to a logic "1" whenever the Transmitter Holding Register (THR) and
Transmitter Shift Register (TSR) are both empty. It is reset to logic "0" whenever either the THR or TSR
contains a data character. Bit 6 is a read only bit. In the FIFO mode this bit is set whenever the THR and
TSR are both empty.
Bit 7
This bit is permanently set to logic "0" in the 450 mode. In the FIFO mode, this bit is set to a logic "1" when
there is at least one parity error, framing error or break indication in the FIFO. This bit is cleared when the
LSR is read if there are no subsequent errors in the FIFO.
Modem Status Register (MSR)
Address Offset = 6H, DLAB = X, READ/WRITE
This 8 bit register provides the current state of the control lines from the MODEM (or peripheral device). In
addition to this current state information, four bits of the MODEM Status Register (MSR) provide change
information. These bits are set to logic "1" whenever a control input from the MODEM changes state. They
are reset to logic "0" whenever the MODEM Status Register is read.
Bit 0
Delta Clear To Send (DCTS). Bit 0 indicates that the nCTS input to the chip has changed state since the
last time the MSR was read.
Bit 1
Delta Data Set Ready (DDSR). Bit 1 indicates that the nDSR input has changed state since the last time
the MSR was read.
Bit 2
"1".
Bit 3
Delta Data Carrier Detect (DDCD). Bit 3 indicates that the nDCD input to the chip has changed state.
Note: Whenever bit 0, 1, 2, or 3 is set to a logic "1", a MODEM Status Interrupt is generated.
Bit 4
This bit is the complement of the Clear To Send (nCTS) input. If bit 4 of the MCR is set to logic "1", this bit
is equivalent to nRTS in the MCR.
Bit 5
This bit is the complement of the Data Set Ready (nDSR) input. If bit 4 of the MCR is set to logic "1", this
bit is equivalent to DTR in the MCR.
Bit 6
This bit is the complement of the Ring Indicator (nRI) input. If bit 4 of the MCR is set to logic "1", this bit is
equivalent to OUT1 in the MCR.
Bit 7
This bit is the complement of the Data Carrier
Detect (nDCD) input. If bit 4 of the MCR is set to logic "1", this bit is equivalent to OUT2 in the MCR.
Scratchpad Register (SCR)
Address Offset =7H, DLAB =X, READ/WRITE
This 8 bit read/write register has no effect on the operation of the Serial Port. It is intended as a scratchpad
register to be used by the programmer to hold data temporarily.
Programmable Baud Rate Generator (AND Divisor Latches DLH, DLL)
The Serial Port contains a programmable Baud Rate Generator that is capable of dividing the internal PLL
clock by any divisor from 1 to 65535. The internal PLL clock is divided down to generate a 1.8462MHz
frequency for Baud Rates less than 38.4k, a 1.8432MHz frequency for 115.2k, a 3.6864MHz frequency for
230.4k and a 7.3728MHz frequency for 460.8k. This output frequency of the Baud Rate Generator is 16x
the Baud rate. Two 8 bit latches store the divisor in 16 bit binary format. These Divisor Latches must be
loaded during initialization in order to insure desired operation of the Baud Rate Generator. Upon loading
either of the Divisor Latches, a 16 bit Baud counter is immediately loaded. This prevents long counts on
initial load. If a 0 is loaded into the BRG registers the output divides the clock by the number 3. If a 1 is
loaded the output is the inverse of the input oscillator. If a two is loaded the output is a divide by 2 signal
with a 50% duty cycle. If a 3 or greater is loaded the output is low for 2 bits and high for the remainder of
the count. The input clock to the BRG is a 1.8462 MHz clock.
Table 30 shows the baud rates possible.
Effect Of The Reset on Register File
The Reset Function Table (Table 31) details the effect of the Reset input on each of the registers of the
Serial Port.
FIFO Interrupt Mode Operation
interrupts occur as follows:
A. The receive data available interrupt will be issued when the FIFO has reached its programmed trigger
When RCVR FIFO and receiver interrupts are enabled, RCVR FIFO timeout interrupts occur as follows:
A. A FIFO timeout interrupt occurs if all the following conditions exist:
At least one character is in the FIFO.
The most recent serial character received was longer than 4 continuous character times ago. (If 2 stop bits
are programmed, the second one is included in this time delay).
The most recent CPU read of the FIFO was longer than 4 continuous character times ago.
This will cause a maximum character received to interrupt issued delay of 160 msec at 300 BAUD with a 12
bit character.
B. Character times are calculated by using the RCLK input for a clock signal (this makes the delay
When the XMIT FIFO and transmitter interrupts are enabled (FCR bit 0 = "1", IER bit 1 = "1"), XMIT
interrupts occur as follows:
A. The transmitter holding register interrupt (02H) occurs when the XMIT FIFO is empty; it is cleared as
FIFO while servicing this interrupt) or the IIR is read.
in the transmitter FIFO since the last THRE=1. The transmitter interrupt after changing FCR0 will be
immediate, if it is enabled.
Character timeout and RCVR FIFO trigger level interrupts have the same priority as the current received
data available interrupt; XMIT FIFO empty has the same priority as the current transmitter holding register
empty interrupt.
FIFO Polled Mode Opertion
With FCR bit 0 = "1" resetting IER bits 0, 1, 2 or 3 or all to zero puts the UART in the FIFO Polled Mode of
operation. Since the RCVR and XMITTER are controlled separately, either one or both can be in the polled
mode of operation. In this mode, the user's program will check RCVR and XMITTER status via the LSR.
LSR definitions for the FIFO Polled Mode are as follows:
Bit 0=1 as long as there is one byte in the RCVR FIFO.
when in the interrupt mode, the IIR is not affected since EIR bit 2=0.
Bit 5 indicates when the XMIT FIFO is empty.
Bit 6 indicates that both the XMIT FIFO and shift register are empty.
Bit 7 indicates whether there are any errors in the RCVR FIFO.
There is no trigger level reached or timeout condition indicated in the FIFO Polled Mode, however, the
RCVR and XMIT FIFOs are still fully capable of holding characters.
Note
RTSB RESET
RCVR FIFO
FCR1*FCR0/_FCR0
FCR1*FCR0/_FCR0
DLAB = 0
(Note 1)
DLAB = 0
Only)
DLAB = 0
Received
Data
Available
Interrupt
(ERDAI)
Transmitter
Holding
Register
Empty
Interrupt
(ETHREI)
Interrupt
Pending
Bit
Select Bit 0
(WLS0)
Select Bit 1
(WLS1)
Terminal
Ready
(DTR)
Send (RTS)
(DR)
Error (OE)
(DCTS)
Set Ready
(DDSR)
DLAB = 1
DLAB = 1
Note 1: Bit 0 is the least significant bit. It is the first bit serially transmitted or received.
Note 2: When operating in the XT mode, this bit will be set any time that the transmitter shift register is
empty.
Receiver Line
Status
Interrupt
(ELSI)
MODEM
Status
Interrupt
(EMSI)
(Note 5)
Enabled
(Note 5)
Reset
Select (Note
6)
MSB
Stop Bits
(STB)
(PEN)
Select (EPS)
Access Bit
(DLAB)
(Note 3)
(Note 3)
(PE)
(FE)
Interrupt (BI)
Holding
Register
(THRE)
Empty (TEMT)
(Note 2)
FIFO (Note 5)
Ring Indicator
(TERI)
Carrier Detect
(DDCD)
(CTS)
Ready (DSR)
(RI)
Detect (DCD)
Note 4: When operating in the XT mode, this register is not available.
Note 5: These bits are always zero in the non-FIFO mode.
Note 6: Writing a one to this bit has no effect. DMA modes are not supported in this chip.
Note 7: The UART1 and UART2 FCR's are shadowed in the UART1 FIFO Control Shadow Register
FIFO Mode Operation
GENERAL
The RCVR FIFO will hold up to 16 bytes regardless of which trigger level is selected.
TX AND RX FIFO Operation
The Tx portion of the UART transmits data through TXD as soon as the CPU loads a byte into the Tx FIFO.
The UART will prevent loads to the Tx FIFO if it currently holds 16 characters. Loading to the Tx
FIFO will again be enabled as soon as the next character is transferred to the Tx shift register. These
capabilities account for the largely autonomous operation of the Tx.
The UART starts the above operations typically with a Tx interrupt. The chip issues a Tx interrupt
whenever the Tx FIFO is empty and the Tx interrupt is enabled, except in the following instance. Assume
that the Tx FIFO is empty and the CPU starts to load it. When the first byte enters the FIFO the Tx FIFO
empty interrupt will transition from active to inactive. Depending on the execution speed of the service
routine software, the UART may be able to transfer this byte from the FIFO to the shift register before the
CPU loads another byte. If this happens, the Tx FIFO will be empty again and typically the UART's
interrupt line would transition to the active state. This could cause a system with an interrupt control unit to
record a Tx FIFO empty condition, even though the CPU is currently servicing that interrupt. Therefore,
after the first byte has been loaded into the FIFO the UART will wait one serial character
transmission time before issuing a new Tx FIFO empty interrupt. This one character Tx interrupt
delay will remain active until at least two bytes have the Tx FIFO empties after this condition, the Tx
been loaded into the FIFO, concurrently. When interrupt will be activated without a one character
delay.
Rx support functions and operation are quite different from those described for the transmitter. The Rx
FIFO receives data until the number of bytes in the FIFO equals the selected interrupt trigger level. At that
time if Rx interrupts are enabled, the UART will issue an interrupt to the CPU. The Rx FIFO will continue to
store bytes until it holds 16 of them. It will not accept any more data when it is full. Any more data entering
the Rx shift register will set the Overrun Error flag. Normally, the FIFO depth and the programmable trigger
levels will give the CPU ample time to empty the Rx FIFO before an overrun occurs.
One side-effect of having a Rx FIFO is that the selected interrupt trigger level may be above the data level
in the FIFO. This could occur when data at the end of the block contains fewer bytes than the trigger level.
No interrupt would be issued to the CPU and the data would remain in the UART. To prevent the
software from having to check for this situation the chip incorporates a timeout interrupt.
The timeout interrupt is activated when there is a least one byte in the Rx FIFO, and neither the CPU nor
the Rx shift register has accessed the Rx FIFO within 4 character times of the last byte. The timeout
interrupt is cleared or reset when the CPU reads the Rx FIFO or another character enters it.
These FIFO related features allow optimization of CPU/UART transactions and are especially useful
given the higher baud rate capability (256 kbaud).
The LPC47N227 infrared interface provides a two-way wireless communications port using infrared as
the transmission medium. Several infrared protocols have been provided in this implementation
including IrDA v1.2 (SIR/FIR), ASKIR, and Consumer IR (FIGURE 2). For more information consult the
SMSC Infrared Communication Controller (IRCC) specification.
The IrDA v1.0 (SIR) and ASKIR formats are driven by the ACE registers found in UART2. The UART2
registers are described in "Serial Port (UART)" section. The base address for UART2 is programmed in
CR25, the UART2 Base Address Register (see section CR25 subsection in the Configuration seciton).
The IrDA V1.2 (FIR) and Consumer IR formats are driven by the SCE registers. Descriptions of these
registers can be found in the SMSC Infrared Communications Controller Specification. The Base
Address for the SCE registers is programmed in CR2B, the SCE Base Address Register (see CR28
subsection in the Configuration section).
IrDA SIR/FIR and ASKIR
IrDA SIR (v1.0) specifies asynchronous serial communication at baud rates up to 115.2Kbps. Each byte
is sent serially LSB first beginning with a zero value start bit. A zero is signaled by sending a single
infrared pulse at the beginning of the serial bit time. A one is signaled by the absence of an infrared
pulse during the bit time. Please refer to "Timing Diagrams" section for the parameters of these pulses
and the IrDA waveforms.
IrDA FIR (v1.2) includes IrDA v1.0 SIR and additionally specifies synchronous serial communications at
data rates up to 4Mbps.
Data is transferred LSB first in packets that can be up to 2048 bits in length. IrDA v1.2 includes
.576Mbps and 1.152Mbps data rates using an encoding scheme that is similar to SIR. The 4Mbps data
rate uses a pulse position modulation (PPM) technique.
The ASKIR infrared allows asynchronous serial communication at baud rates up to 19.2Kbps. Each
byte is sent serially LSB first beginning with a zero value start bit. A zero is signaled by sending a
500KHz carrier waveform for the duration of the serial bit time. A one is signaled by the absence of
carrier during the bit time. Refer to "Timing Diagrams" section for the parameters of the ASKIR
waveforms.
Consumer IR
The LPC47N227 Consumer IR interface is a general-purpose Amplitude Shift Keyed encoder/decoder
with programmable carrier and bit-cell rates that can emulate many popular TV Remote encoding
formats; including, 38KHz PPM, PWM and RC-5. The carrier frequency is programmable from 1.6MHz
to 6.25KHz. The bit-cell rate range is 100KHz to 390Hz.
pin (IR Mode) to program the data rate, while the other has a second Rx data pin (IRRX3). The
LPC47N227 uses Pin 63 for these functions. Pin 63 has IR Mode and IRRX3 as its first and second
alternate function, respectively. These functions are selected through CR29 as shown in Table 33.
Note
The FAST bit is used to select between the SIR mode and FIR mode receiver, regardless of the
transceiver type. If FAST = 1, the FIR mode receiver is selected; if FAST = 0, the SIR mode receiver is
selected (Table 34).
If the Half Duplex option is chosen there is an IR Half Duplex Time-out that constrains IRCC direction
mode changes. This time-out starts as each bit is transferred and prevents direction mode changes
until the time-out expires. The timer is restarted whenever new data arrives in the current direction
mode. For example, if data is loaded into the transmit buffer while a character is being received, the
transmission will not start until the last bit has been received and the time-out expires. If the start bit of
another character is received during this time-out, the timer is restarted after the new character is
received. The Half Duplex Time-out is programmable from 0 to 25.5ms in 100
IR Transmit Pins
The TXD2 and IRTX2 pins default to output, low on VCC POR and hard reset. These pins are not
powered by VTR. These pins function as described below.
Following a VCC POR, the TXD2 and IRTX2 pins will be output and low. They will remain low until one
of the following conditions are met.
IRTX2 Pin (CR0A bits [7:6]=01):
This pin will remain low following a VCC POR until serial port 2 is enabled by setting the UART2
the IRCC block (if IR is enabled through the IR Option Register for Serial Port 2).
/IRRX3
1. This pin will remain low following a VCC POR until serial port 2 is enabled by setting the UART2
serial port 2 (if COM is enabled through CR0C Register for Serial Port 2).
the IRCC block (if IR is enabled through the CR0C Register for Serial Port 2).
The IRTX2 and TXD2 pins will be driven low whenever serial port 2 is disabled (UART2 power down bit
is cleared).
Note that bits[7,6] of CR0A can be used to override this functionality of driving the IRTX2 and TXD2 pins
low when UART2 is powered down. If these bits are set to `11', then the IRTX (TXD2) and IRTX2 pins
are high-z.
The LPC47N227 incorporates an IBM XT/AT compatible parallel port. This supports the optional PS/2 type
bi-directional parallel port (SPP), the Enhanced Parallel Port (EPP) and the Extended Capabilities Port
(ECP) parallel port modes. Refer to the Configuration Registers for information on disabling, power down,
changing the base address of the parallel port, and selecting the mode of operation.
The LPC47N227 also provides a mode for support of the floppy disk controller on the parallel port.
The parallel port also incorporates SMSC's ChiProtect circuitry, which prevents possible damage to the
parallel port due to printer power-up.
The functionality of the Parallel Port is achieved through the use of eight addressable ports, with their
associated registers and control gating. The control and data port are read/write by the CPU, the status port
is read/write in the EPP mode. The address map of the Parallel Port is shown below
The bit map of these registers is:
PORT
PORT
PORT
PORT 0
PORT 1
PORT 2
PORT 3
Note 2: These registers are only available in EPP mode.
nAckReverse(3)
HostAck(3)
nPeriphRequest(3)
nReverseRqst(3)
(1) = Compatible Mode
(3) = High Speed Mode
Note:
This document is available from Microsoft.
IBM XT/AT Compatible, Bi-Directional And EPP Modes
Data Port
ADDRESS OFFSET = 00H
The Data Port is located at an offset of '00H' from the base address. The data register is cleared at
initialization by RESET. During a WRITE operation, the Data Register latches the contents of the internal
data bus. The contents of this register are buffered (non inverting) and output onto the PD0 - PD7 ports.
During a READ operation in SPP mode, PD0 - PD7 ports are buffered (not latched) and output to the host
CPU.
Status Port
ADDRESS OFFSET = 01H
The Status Port is located at an offset of '01H' from the base address. The contents of this register are
latched for the duration of a read cycle. The bits of the Status Port are defined as follows:
BIT 0 TMOUT - TIME OUT
This bit is valid in EPP mode only and indicates that a 10 usec time out has occurred on the EPP bus. A
logic zero means that no time out error has occurred; a logic 1 means that a time out error has been
detected.
The means of clearing the TIMEOUT bit is controlled by the TIMEOUT_SELECT bit as follows. The
TIMEOUT_SELECT bit is located at bit 2 of CR21.
read of the EPP Status Register (default)
TIMEOUT bit.
The TIMEOUT bit is cleared on PCI_RESET regardless of the state of the TIMEOUT_SELECT bit.
BITS 1, 2 - are not implemented as register bits, during a read of the Printer Status Register these bits are
a low level.
BIT 3 nERR - nERROR
The level on the nERROR input is read by the CPU as bit 3 of the Printer Status Register. A logic 0 means
an error has been detected; a logic 1 means no error has been detected.
BIT 4 SLCT - PRINTER SELECTED STATUS
The level on the SLCT input is read by the CPU as bit 4 of the Printer Status Register. A logic 1 means the
printer is on line; a logic 0 means it is not selected.
BIT 5 PE - PAPER END
The level on the PE input is read by the CPU as bit 5 of the Printer Status Register. A logic 1 indicates a
paper end; a logic 0 indicates the presence of paper.
BIT 6 nACK - nACKNOWLEDGE
The level on the nACK input is read by the CPU as bit 6 of the Printer Status Register. A logic 0 means
that the printer has received a character and can now accept another. A logic 1 means that it is still
processing the last character or has not received the data.
BIT 7 nBUSY - nBUSY
The complement of the level on the BUSY input is read by the CPU as bit 7 of the Printer Status Register.
A logic 0 in this bit means that the printer is busy and cannot accept a new character. A logic 1 means that
it is ready to accept the next character.
Control Port
ADDRESS OFFSET = 02H
The Control Port is located at an offset of '02H' from the base address. The Control Register is initialized
by the RESET input, bits 0 to 5 only being affected; bits 6 and 7 are hard wired low.
BIT 0 STROBE - STROBE
This bit is inverted and output onto the nSTROBE output.
BIT 1 AUTOFD - AUTOFEED
This bit is inverted and output onto the nAUTOFD output. A logic 1 causes the printer to generate a line
feed after each line is printed. A logic 0 means no autofeed.
This bit is output onto the nINIT output without inversion.
BIT 3 SLCTIN - PRINTER SELECT INPUT
This bit is inverted and output onto the nSLCTIN output. A logic 1 on this bit selects the printer; a logic 0
means the printer is not selected.
BIT 4 IRQE - INTERRUPT REQUEST ENABLE
The interrupt request enable bit when set to a high level may be used to enable interrupt requests from the
Parallel Port to the CPU. An interrupt request is generated on the IRQ port by a positive going nACK input.
When the IRQE bit is programmed low the IRQ is disabled.
BIT 5 PCD - PARALLEL CONTROL DIRECTION
Parallel Control Direction is not valid in printer mode. In printer mode, the direction is always out regardless
of the state of this bit. In bi-directional, EPP or ECP mode, a logic 0 means that the printer port is in output
mode (write); a logic 1 means that the printer port is in input mode (read).
Bits 6 and 7 during a read are a low level, and cannot be written.
EPP Address Port
ADDRESS OFFSET = 03H
The EPP Address Port is located at an offset of '03H' from the base address. The address register is
cleared at initialization by RESET. During a WRITE operation, the contents of the internal data bus DB0-
DB7 are buffered (non inverting) and output onto the PD0 - PD7 ports. An LPC I/O write cycle causes an
EPP ADDRESS WRITE cycle to be performed, during which the data is latched for the duration of the EPP
write cycle. During a READ operation, PD0 - PD7 ports are read. An LPC I/O read cycle causes an EPP
ADDRESS READ cycle to be performed and the data output to the host CPU, the deassertion of
ADDRSTB latches the PData for the duration of the read cycle. This register is only available in EPP
mode.
EPP Data Port 0
ADDRESS OFFSET = 04H
The EPP Data Port 0 is located at an offset of '04H' from the base address. The data register is cleared at
initialization by RESET. During a WRITE operation, the contents of the internal data bus DB0-DB7 are
buffered (non inverting) and output onto the PD0 - PD7 ports. An LPC I/O write cycle causes an EPP
DATA WRITE cycle to be performed, during which the data is latched for the duration of the EPP write
cycle. During a READ operation, PD0 - PD7 ports are read. An LPC I/O read cycle causes an EPP READ
cycle to be performed and the data output to the host CPU, the deassertion of DATASTB latches the PData
for the duration of the read cycle. This register is only available in EPP mode.
EPP Data Port 1
ADDRESS OFFSET = 05H
The EPP Data Port 1 is located at an offset of '05H' from the base address. Refer to EPP DATA PORT 0
for a description of operation. This register is only available in EPP mode.
EPP Data Port 2
The EPP Data Port 2 is located at an offset of '06H' from the base address. Refer to EPP DATA PORT 0
for a description of operation. This register is only available in EPP mode.
EPP Data Port 3
ADDRESS OFFSET = 07H
The EPP Data Port 3 is located at an offset of '07H' from the base address. Refer to EPP DATA PORT 0
for a description of operation. This register is only available in EPP mode.
EPP 1.9 Operation
When the EPP mode is selected in the configuration register, the standard and bi-directional modes are
also available. If no EPP Read, Write or Address cycle is currently executing, then the PDx bus is in the
standard or bi-directional mode, and all output signals (STROBE, AUTOFD, INIT) are as set by the SPP
Control Port and direction is controlled by PCD of the Control port.
In EPP mode, the system timing is closely coupled to the EPP timing. For this reason, a watchdog timer is
required to prevent system lockup. The timer indicates if more than 10usec have elapsed from the start of
the EPP cycle to nWAIT being deasserted (after command). If a time-out occurs, the current EPP cycle is
aborted and the time-out condition is indicated in Status bit 0.
During an EPP cycle, if STROBE is active, it overrides the EPP write signal forcing the PDx bus to always
be in a write mode and the nWRITE signal to always be asserted.
Software Constraints
Before an EPP cycle is executed, the software must ensure that the control register bit PCD is a logic "0"
(i.e., a 04H or 05H should be written to the Control port). If the user leaves PCD as a logic "1", and
attempts to perform an EPP write, the chip is unable to perform the write (because PCD is a logic "1") and
will appear to perform an EPP read on the parallel bus, no error is indicated.
EPP 1.9 Write
The timing for a write operation (address or data) is shown in timing diagram EPP Write Data or Address
cycle. The chip inserts wait states into the LPC I/O write cycle until it has been determined that the write
cycle can complete. The write cycle can complete under the following circumstances:
1. If the EPP bus is not ready (nWAIT is active low) when nDATASTB or nADDRSTB goes active then
determined inactive.
Write Sequence of operation
1. The host initiates an I/O write cycle to the selected EPP register.
2. If WAIT is not asserted, the chip must wait until WAIT is asserted.
3. The chip places address or data on PData bus, clears PDIR, and asserts nWRITE.
4. Chip asserts nDATASTB or nADDRSTRB indicating that PData bus contains valid information, and
b) The chip latches the data from the internal data bus for the PData bus and drives the sync that
indicates that no more wait states are required followed by the TAR to complete the write cycle.
EPP 1.9 Read
The timing for a read operation (data) is shown in timing diagram EPP Read Data cycle. The chip inserts
wait states into the LPC I/O read cycle until it has been determined that the read cycle can complete. The
read cycle can complete under the following circumstances:
1 If the EPP bus is not ready (nWAIT is active low) when nDATASTB goes active then the read can
2. If the EPP bus is ready (nWAIT is inactive high) then the chip must wait for it to go active low before
is determined inactive.
Read Sequence of Operation
1. The host initiates an I/O read cycle to the selected EPP register.
2. If WAIT is not asserted, the chip must wait until WAIT is asserted.
3. The chip tri-states the PData bus and deasserts nWRITE.
4. Chip asserts nDATASTB or nADDRSTRB indicating that PData bus is tri-stated, PDIR is set and the
6. Peripheral deasserts nWAIT, indicating that PData is valid and the chip may begin the termination
EPP 1.7 Operation
When the EPP 1.7 mode is selected in the configuration register, the standard and bi-directional modes are
also available. If no EPP Read, Write or Address cycle is currently executing, then the PDx bus is in the
standard or bi-directional mode, and all output signals (STROBE, AUTOFD, INIT) are as set by the SPP
Control Port and direction is controlled by PCD of the Control port.
In EPP mode, the system timing is closely coupled to the EPP timing. For this reason, a watchdog timer is
required to prevent system lockup. The timer indicates if more than 10usec have elapsed from the start of
the EPP cycle to the end of the cycle. If a time-out occurs, the current EPP cycle is aborted and the time-
out condition is indicated in Status bit 0.
Software Constraints
set to zero. Also, bit D5 (PCD) is a logic "0" for an EPP write or a logic "1" for and EPP read.
EPP 1.7 Write
The timing for a write operation (address or data) is shown in timing diagram EPP 1.7 Write Data or
Address cycle. The chip inserts wait states into the I/O write cycle when nWAIT is active low during the
EPP cycle. This can be used to extend the cycle time. The write cycle can complete when nWAIT is
inactive high.
Write Sequence of Operation
1. The host sets PDIR bit in the control register to a logic "0". This asserts nWRITE.
2. The host initiates an I/O write cycle to the selected EPP register.
3. The chip places address or data on PData bus.
4. Chip asserts nDATASTB or nADDRSTRB indicating that PData bus contains valid information, and
EPP 1.7 Read
The timing for a read operation (data) is shown in timing diagram EPP 1.7 Read Data cycle. The chip
inserts wait states into the I/O read cycle when nWAIT is active low during the EPP cycle. This can be
used to extend the cycle time. The read cycle can complete when nWAIT is inactive high.
Read Sequence of Operation
1. The host sets PDIR bit in the control register to a logic "1". This deasserts nWRITE and tri-states the
3. Chip asserts nDATASTB or nADDRSTRB indicating that PData bus is tri-stated, PDIR is set and the
6. The Peripheral deasserts nWAIT, indicating that PData is valid and the chip may begin the termination
8. Peripheral
through with no inversion, Same as SPP).
acknowledgement from the device that the transfer of data is
completed. It is driven active as an indication that the device is
ready for the next transfer.
operation.
is reset to its initial operational mode.
write operation.
Note 1: SPP and EPP can use 1 common register.
Note 2: nWrite is the only EPP output that can be over-ridden by SPP control port during an EPP cycle.
Extended Capabilities Parallel Port
ECP provides a number of advantages, some of which are listed below. The individual features are
explained in greater detail in the remainder of this section.
High performance half-duplex forward and reverse channel Interlocked handshake, for fast reliable transfer
Optional single byte RLE compression for improved throughput (64:1) Channel addressing for low-cost
peripherals Maintains link and data layer separation Permits the use of active output drivers permits the use
of adaptive signal timing Peer-to-peer capability.
Vocabulary
The following terms are used in this document:
assert: When a signal asserts it transitions to a "true" state, when a signal deasserts it transitions to a
reverse: Peripheral to Host communication
Pword: A port word; equal in size to the width of the LPC interface. For this implementation, PWord is
always 8 bits.
1
These terms may be considered synonymous:
HostAck, nAutoFd
nPeriphRequest, nFault
nReverseRequest, nInit
nAckReverse, PError
ECPMode, nSelectln
HostClk, nStrobe
Reference Document: IEEE 1284 Extended Capabilities Port Protocol and ISA Interface Standard, Rev
1.14, July 14, 1993. This document is available from Microsoft.
The bit map of the Extended Parallel Port registers is:
Note 1: These registers are available in all modes.
Note 2: All FIFOs use one common 16 byte FIFO.
Note 3: The ECP Parallel Port Config Reg B reflects the IRQ and DMA channel selected by the
ECP Implementation Standard
This specification describes the standard interface to the Extended Capabilities Port (ECP). All LPC
devices supporting ECP must meet the requirements contained in this section or the port will not be
supported by Microsoft. For a description of the ECP Protocol, please refer to the IEEE 1284 Extended
Capabilities Port Protocol and ISA Interface Standard, Rev. 1.14, July 14, 1993. This document is available
from Microsoft.
Description
The port is software and hardware compatible with existing parallel ports so that it may be used as a
standard LPT port if ECP is not required. The port is designed to be simple and requires a small number of
gates to implement. It does not do any "protocol" negotiation, rather it provides an automatic high
burst-bandwidth channel that supports DMA for ECP in both the forward and reverse directions.
Small FIFOs are employed in both forward and reverse directions to smooth data flow and improve the
maximum bandwidth requirement. The size of the FIFO is 16 bytes deep. The port supports an automatic
handshake for the standard parallel port to improve compatibility mode transfer speed.
The port also supports run length encoded (RLE) decompression (required) in hardware. Compression is
accomplished by counting identical bytes and transmitting an RLE byte that indicates how many times the
next byte is to be repeated. Decompression simply intercepts the RLE byte and repeats the following byte
the specified number of times. Hardware support for compression is optional.
the asserting edge (handshakes with Busy).
handshakes with nAutoFd in reverse.
signal handshakes with nStrobe in the forward direction. In the reverse
direction this signal indicates whether the data lines contain ECP command
information or data. The peripheral uses this signal to flow control in the
forward direction. It is an "interlocked" handshake with nStrobe. PeriphAck
also provides command information in the reverse direction.
(nAckReverse)
forward). The peripheral drives this signal low to acknowledge
nReverseRequest. It is an "interlocked" handshake with nReverseRequest.
The host relies upon nAckReverse to determine when it is permitted to
drive the data bus.
(HostAck)
with nAck in the reverse direction. In the forward direction this signal
indicates whether the data lines contain ECP address or data. The host
drives this signal to flow control in the reverse direction. It is an "interlocked"
handshake with nAck. HostAck also provides command information in the
forward phase.
(nPeriphRequest)
mechanism for peer-to-peer communication. This signal is valid only in the
forward direction. During ECP Mode the peripheral is permitted (but not
required) to drive this pin low to request a reverse transfer. The request is
merely a "hint" to the host; the host has ultimate control over the transfer
direction. This signal would be typically used to generate an interrupt to the
host CPU.
pin is driven low to place the channel in the reverse direction. The
peripheral is only allowed to drive the bi-directional data bus while in ECP
Mode and HostAck is low and nSelectIn is high.
Register Definitions
The register definitions are based on the standard IBM addresses for LPT. All of the standard printer ports
are supported. The additional registers attach to an upper bit decode of the standard LPT port definition to
avoid conflict with standard ISA devices. The port is equivalent to a generic parallel port interface and may
be operated in that mode. The port registers vary depending on the mode field in the ecr. The table below
lists these dependencies. Operation of the devices in modes other that those specified is undefined.
Note 1: These addresses are added to the parallel port base address as selected by configuration register
110 Test
Data And ecpAFifo Port
ADDRESS OFFSET = 00H
Modes 000 and 001 (Data Port)
The Data Port is located at an offset of '00H' from the base address. The data register is cleared at
initialization by RESET. During a WRITE operation, the Data Register latches the contents of the data bus.
The contents of this register are buffered (non inverting) and output onto the PD0 - PD7 ports. During a
READ operation, PD0 - PD7 ports are read and output to the host CPU.
Mode 011 (ECP FIFO - Address/RLE)
A data byte written to this address is placed in the FIFO and tagged as an ECP Address/RLE. The
hardware at the ECP port transmits this byte to the peripheral automatically. The operation of this register
is ony defined for the forward direction (direction is 0). Refer to the ECP Parallel Port Forward Timing
Diagram, located in the Timing Diagrams section of this data sheet .
ADDRESS OFFSET = 01H
The Status Port is located at an offset of '01H' from the base address. Bits 0 - 2 are not implemented as
register bits, during a read of the Printer Status Register these bits are a low level. The bits of the Status
Port are defined as follows:
BIT 3 nFault
The level on the nFault input is read by the CPU as bit 3 of the Device Status Register.
BIT 4 Select
The level on the Select input is read by the CPU as bit 4 of the Device Status Register.
BIT 5 PError
The level on the PError input is read by the CPU as bit 5 of the Device Status Register. Printer Status
Register.
BIT 6 nAck
The level on the nAck input is read by the CPU as bit 6 of the Device Status Register.
BIT 7 nBusy
The complement of the level on the BUSY input is read by the CPU as bit 7 of the Device Status Register.
Device Control Register (DCR)
ADDRESS OFFSET = 02H
The Control Register is located at an offset of '02H' from the base address. The Control Register is
initialized to zero by the RESET input, bits 0 to 5 only being affected; bits 6 and 7 are hard wired low.
BIT 0 STROBE - STROBE
This bit is inverted and output onto the nSTROBE output.
BIT 1 AUTOFD - AUTOFEED
This bit is inverted and output onto the nAUTOFD output. A logic 1 causes the printer to generate a line
feed after each line is printed. A logic 0 means no autofeed.
BIT 2 nINIT - nINITIATE OUTPUT
This bit is output onto the nINIT output without inversion.
BIT 3 SELECTIN
This bit is inverted and output onto the nSLCTIN output. A logic 1 on this bit selects the printer; a logic 0
means the printer is not selected.
BIT 4 ackIntEn - INTERRUPT REQUEST ENABLE
The interrupt request enable bit when set to a high level may be used to enable interrupt requests from
the Parallel Port to the CPU due to a low to high transition on the nACK input. Refer to the description of
the interrupt under Operation, Interrupts.
BIT 5 DIRECTION
If mode=000 or mode=010, this bit has no effect and the direction is always out regardless of the state of
this bit. In all other modes, Direction is valid and a logic 0 means that the printer port is in output mode
(write); a logic 1 means that the printer port is in input mode (read).
BITS 6 and 7 during a read are a low level, and cannot be written.
cFifo (Parallel Port Data FIFO)
ADDRESS OFFSET = 400h
Mode = 010
Bytes written or DMAed from the system to this FIFO are transmitted by a hardware handshake to the
peripheral using the standard parallel port protocol. Transfers to the FIFO are byte aligned. This mode is
only defined for the forward direction.
ecpDFifo (ECP Data FIFO)
ADDRESS OFFSET = 400H
Mode = 011
Bytes written or DMAed from the system to this FIFO, when the direction bit is 0, are transmitted by a
hardware handshake to the peripheral using the ECP parallel port protocol. Transfers to the FIFO are byte
aligned.
Data bytes from the peripheral are read under automatic hardware handshake from ECP into this FIFO
when the direction bit is 1. Reads or DMAs from the FIFO will return bytes of ECP data to the system.
tFifo (Test FIFO Mode)
ADDRESS OFFSET = 400H
Mode = 110
Data bytes may be read, written or DMAed to or from the system to this FIFO in any direction. Data in the
tFIFO will not be transmitted to the to the parallel port lines using a hardware protocol handshake.
However, data in the tFIFO may be displayed on the parallel port data lines.
The tFIFO will not stall when overwritten or underrun. If an attempt is made to write data to a full tFIFO, the
new data is not accepted into the tFIFO. If an attempt is made to read data from an empty tFIFO, the last
data byte is re-read again. The full and empty bits must always keep track of the correct FIFO state. The
tFIFO will transfer data at the maximum ISA rate so that software may generate performance metrics.
The FIFO size and interrupt threshold can be determined by writing bytes to the FIFO and checking the full
and serviceIntr bits.
The writeIntrThreshold can be determined by starting with a full tFIFO, setting the direction bit to 0 and
emptying it a byte at a time until serviceIntr is set. This may generate a spurious interrupt, but will indicate
that the threshold has been reached.
The readIntrThreshold can be determined by setting the direction bit to 1 and filling the empty tFIFO a byte
at a time until serviceIntr is set. This may generate a spurious interrupt, but will indicate that the threshold
has been reached.
Data bytes are always read from the head of tFIFO regardless of the value of the direction bit. For example
if 44h, 33h, 22h is written to the FIFO, then reading the tFIFO will return 44h, 33h, 22h in the same order as
was written.
ADDRESS OFFSET = 400H
Mode = 111
This register is a read only register. When read, 10H is returned. This indicates to the system that this is
an 8-bit implementation. (PWord = 1 byte)
cnfgB (Configuration Register B)
ADDRESS OFFSET = 401H
Mode = 111
BIT 7 compress
This bit is read only. During a read it is a low level. This means that this chip does not support hardware
RLE compression. It does support hardware de-compression!
BIT 6 intrValue
Returns the value of the interrupt to determine possible conflicts.
BITS [5:3] Parallel Port IRQ (read-only)
Refer to Table 40B.
BITS [2:0] Parallel Port DMA (read-only)
Refer to Table 40C.
ecr (Extended Control Register)
ADDRESS OFFSET = 402H
Mode = all
This register controls the extended ECP parallel port functions.
BITS 7,6,5
These bits are Read/Write and select the Mode.
BIT 4 nErrIntrEn
Read/Write (Valid only in ECP Mode)
1: Disables the interrupt generated on the asserting edge of nFault.
0: Enables an interrupt pulse on the high to low edge of nFault. Note that an interrupt will be generated if
being lost in the time between the read of the ecr and the write of the ecr.
BIT 3 dmaEn
Read/Write
1: Enables DMA (DMA starts when serviceIntr is 0).
0: Disables DMA unconditionally.
BIT 2 serviceIntr
Read/Write
1: Disables DMA and all of the service interrupts.
0: Enables one of the following 3 cases of interrupts. Once one of the 3 service interrupts has occurred
this bit to a 1 will not cause an interrupt.
FIFO.
BIT 1 full
Read
0: The FIFO has at least 1 free byte.
BIT 0 empty
Read only
1: The FIFO is completely empty.
0: The FIFO contains at least 1 byte of data.
000: Standard Parallel Port Mode . In this mode the FIFO is reset and common collector drivers
will not tri-state the output drivers in this mode.
in the data register. All drivers have active pull-ups (push-pull).
the FIFO. FIFO data is automatically transmitted using the standard parallel port protocol.
Note that this mode is only useful when direction is 0. All drivers have active pull-ups
(push-pull).
and bytes written to the ecpAFifo are placed in a single FIFO and transmitted automatically to
the peripheral using ECP Protocol. In the reverse direction (direction is 1) bytes are moved
from the ECP parallel port and packed into bytes in the ecpDFifo. All drivers have active
pull-ups (push-pull).
110: Test Mode. In this mode the FIFO may be written and read, but the data will not be
Operation
Mode Switching/Software Control
Software will execute P1284 negotiation and all operation prior to a data transfer phase under programmed
I/O control (mode 000 or 001). Hardware provides an automatic control line handshake, moving data
between the FIFO and the ECP port only in the data transfer phase (modes 011 or 010).
Setting the mode to 011 or 010 will cause the hardware to initiate data transfer. If the port is in mode 000 or
001 it may switch to any other mode. If the port is not in mode 000 or 001 it can only be switched into
mode 000 or 001. The direction can only be changed in mode 001.
Prior to ECP operation the Host must negotiate on the parallel port to determine if the peripheral supports
the ECP protocol. This is a somewhat complex negotiation carried out under program control in mode 000.
After negotiation, it is necessary to initialize some of the port bits. The following are required:
Set Direction = 0, enabling the drivers.
Set strobe = 0, causing the nStrobe signal to default to the deasserted state.
Set autoFd = 0, causing the nAutoFd signal to default to the deasserted state.
Set mode = 011 (ECP Mode)
ECP address/RLE bytes or data bytes may be sent automatically by writing the ecpAFifo or ecpDFifo
respectively.
Note that all FIFO data transfers are byte wide and byte aligned. Address/RLE transfers are byte-wide and
only allowed in the forward direction.
The host may switch directions by first switching to mode = 001, negotiating for the forward or reverse
channel, setting direction to 1 or 0, then setting mode = 011. When direction is 1 the hardware shall
handshake for each ECP read data byte and attempt to fill the FIFO. Bytes may then be read from the
ecpDFifo as long as it is not empty.
ECP transfers may also be accomplished (albeit slowly) by handshaking individual bytes under program
control in mode = 001, or 000.
Termination from ECP Mode
Termination from ECP Mode is similar to the termination from Nibble/Byte Modes. The host is permitted to
terminate from ECP Mode only in specific well-defined states. The termination can only be executed while
the bus is in the forward direction. To terminate while the channel is in the reverse direction, it must first be
transitioned into the forward direction.
Command/Data
ECP Mode supports two advanced features to improve the effectiveness of the protocol for some
applications. The features are implemented by allowing the transfer of normal 8 bit data or 8 bit commands.
When in the forward direction, normal data is transferred when HostAck is high and an 8 bit command is
transferred when HostAck is low.
The most significant bit of the command indicates whether it is a run-length count (for compression) or a
channel address.
When in the reverse direction, normal data is transferred when PeriphAck is high and an 8 bit command is
transferred when PeriphAck is low. The most significant bit of the command is always zero. Reverse
channel addresses are seldom used and may not be supported in hardware.
0011 0X00 only)
Data Compression
The ECP port supports run length encoded (RLE) decompression in hardware and can transfer
compressed data to a peripheral. Run length encoded (RLE) compression in hardware is not supported.
To transfer compressed data in ECP mode, the compression count is written to the ecpAFifo and the data
byte is written to the ecpDFifo.
Compression is accomplished by counting identical bytes and transmitting an RLE byte that indicates how
many times the next byte is to be repeated. Decompression simply intercepts the RLE byte and repeats
the following byte the specified number of times. When a run-length count is received from a peripheral, the
subsequent data byte is replicated the specified number of times. A run-length count of zero specifies that
only one byte of data is represented by the next data byte, whereas a run-length count of 127 indicates that
the next byte should be expanded to 128 bytes. To prevent data expansion, however, run-length counts of
zero should be avoided.
Pin Definition
The drivers for nStrobe, nAutoFd, nInit and nSelectIn are open-collector in mode 000 and are push-pull in
all other modes.
LPC Connections
The interface can never stall causing the host to hang. The width of data transfers is strictly controlled on
an I/O address basis per this specification. All FIFO-DMA transfers are byte wide, byte aligned and end on
a byte boundary. (The PWord value can be obtained by reading Configuration Register A, cnfgA, described
in the next section). Single byte wide transfers are always possible with standard or PS/2 mode using
program control of the control signals.
Interrupts
The interrupts are enabled by serviceIntr in the ecr register.
serviceIntr = 1 Disables the DMA and all of the service interrupts.
serviceIntr = 0 Enables the selected interrupt condition. If the interrupting condition is valid, then the
occur during Programmed I/O if the number of bytes removed or added from/to the FIFO
does not cross the threshold.
An interrupt is generated when:
1. For DMA transfers: When serviceIntr is 0, dmaEn is 1 and the DMA TC cycle is received.
2. For Programmed I/O:
are writeIntrThreshold or more free bytes in the FIFO.
readIntrThreshold or more bytes in the FIFO.
FIFO Operation
The FIFO threshold is set in the chip configuration registers. All data transfers to or from the parallel port
can proceed in DMA or Programmed I/O (non-DMA) mode as indicated by the selected mode. The FIFO is
used by selecting the Parallel Port FIFO mode or ECP Parallel Port Mode. (FIFO test mode will be
addressed separately.) After a reset, the FIFO is disabled. Each data byte is transferred by a
Programmed I/O cycle or DMA cycle depending on the selection of DMA or Programmed I/O mode.
The following paragraphs detail the operation of the FIFO flow control. In these descriptions, <threshold>
ranges from 1 to 16. The parameter FIFOTHR, which the user programs, is one less and ranges from 0 to
15.
A low threshold value (i.e. 2) results in longer periods of time between service requests, but requires faster
servicing of the request for both read and write cases. The host must be very responsive to the service
request. This is the desired case for use with a "fast" system. A high value of threshold (i.e. 12) is used
with a "sluggish" system by affording a long latency period after a service request, but results in more
frequent service requests.
DMA Transfers
DMA transfers are always to or from the ecpDFifo, tFifo or CFifo. DMA utilizes the standard PC DMA
services. To use the DMA transfers, the host first sets up the direction and state as in the programmed I/O
case. Then it programs the DMA controller in the host with the desired count and memory address. Lastly it
sets dmaEn to 1 and serviceIntr to 0. The ECP requests DMA transfers from the host by encoding the
nLDRQ pin. The DMA will empty or fill the FIFO using the appropriate direction and mode. When the
terminal count in the DMA controller is reached, an interrupt is generated and serviceIntr is asserted,
disabling DMA. In order to prevent possible blocking of refresh requests a DMA cycle shall not be
requested for more than 32 DMA cycles in a row. The FIFO is enabled directly by the host initiating a DMA
cycle for the requested channel, and addresses need not be valid. An interrupt is generated when a TC
cycle is received. (Note: The only way to properly terminate DMA transfers is with a TC cycle.)
DMA may be disabled in the middle of a transfer by first disabling the host DMA controller. Then setting
serviceIntr to 1, followed by setting dmaEn to 0, and waiting for the FIFO to become empty or full.
Restarting the DMA is accomplished by enabling DMA in the host, setting dmaEn to 1, followed by setting
serviceIntr to 0.
DMA Mode - Transfers from the FIFO to the Host
(Note: In the reverse mode, the peripheral may not continue to fill the FIFO if it runs out of data to transfer,
even if the chip continues to request more data from the peripheral.)
The ECP requests a DMA cycle whenever there is data in the FIFO. The DMA controller responds to the
request by reading data from the FIFO. The ECP stop requesting DMA cycles when the FIFO becomes
empty or when a TC cycle is received, indicating that no more data is required. If the ECP stops requesting
DMA cycles due to the FIFO going empty, then a DMA cycle is requested again as soon as there is one
byte in the FIFO. If the ECP stops requesting DMA cycles due to the TC cycle, then a DMA cycle is
requested again when there is one byte in the FIFO, and serviceIntr has been re-enabled.
Programmed I/O Mode or Non-DMA Mode
The ECP or parallel port FIFOs may also be operated using interrupt driven programmed I/O. Software can
determine the writeIntrThreshold, readIntrThreshold, and FIFO depth by accessing the FIFO in Test Mode.
Programmed I/O transfers are to the ecpDFifo at 400H and ecpAFifo at 000H or from the ecpDFifo located
at 400H, or to/from the tFifo at 400H. To use the programmed I/O transfers, the host first sets up the
direction and state, sets dmaEn to 0 and serviceIntr to 0.
The ECP requests programmed I/O transfers from the host by activating the interrupt. The programmed I/O
will empty or fill the FIFO using the appropriate direction and mode.
Note: A threshold of 16 is equivalent to a threshold of 15. These two cases are treated the same.
Programmed I/O - Transfers from the FIFO to the Host
In the reverse direction an interrupt occurs when serviceIntr is 0 and readIntrThreshold bytes are available
in the FIFO. If at this time the FIFO is full it can be emptied completely in a single burst, otherwise
readIntrThreshold bytes may be read from the FIFO in a single burst.
readIntrThreshold =(16-<threshold>) data bytes in FIFO
An interrupt is generated when serviceIntr is 0 and the number of bytes in the FIFO is greater than or equal
to (16-<threshold>). (If the threshold = 12, then the interrupt is set whenever there are 4-16 bytes in the
FIFO). The host must respond to the request by reading data from the FIFO. This process is repeated
until the last byte is transferred out of the FIFO. If at this time the FIFO is full, it can be completely emptied
in a single burst, otherwise a minimum of (16-<threshold>) bytes may be read from the FIFO in a single
burst.
Programmed I/O - Transfers from the Host to the FIFO
In the forward direction an interrupt occurs when serviceIntr is 0 and there are writeIntrThreshold or more
bytes free in the FIFO. At this time if the FIFO is empty it can be filled with a single burst before the empty
bit needs to be re-read. Otherwise it may be filled with writeIntrThreshold bytes.
writeIntrThreshold =
An interrupt is generated when serviceIntr is 0 and the number of bytes in the FIFO is less than or equal to
<threshold>. (If the threshold = 12, then the interrupt is set whenever there are 12 or less bytes of data in
the FIFO.) The host must respond to the request by writing data to the FIFO. If at this time the FIFO is
empty, it can be completely filled in a single burst, otherwise a minimum of (16-<threshold>) bytes may be
written to the FIFO in a single burst. This process is repeated until the last byte is transferred into the FIFO.
Parallel Port Floppy Disk Controller
The Floppy Disk Control signals are available optionally on the parallel port pins. When this mode is
selected, the parallel port is not available. There are two modes of operation, PPFD1 and PPFD2.
These modes can be selected in the Parallel and Serial Extended Setup Register (CR04). PPFD1 has
only drive 1 on the parallel port pins; PPFD2 has drive 0 and 1 on the parallel port pins. See the
Configuration section for description of the register. The FDC_PP pin can be used to switch the parallel
port pins between the FDC and the parallel port functions. See the following sub-section.
The following parallel port pins are read as follows by a read of the parallel port register:
1. Data Register (read) = last Data Register (write)
3. Status Register reads: nBUSY = 0, PE = 0, SLCT = 0, nACK = 1, nERR = 1
The following FDC pins are all in the high impedence state when the PPFDC is actually selected by the
drive select register:
1. nWDATA, DENSEL, nHDSEL, nWGATE, nDIR, nSTEP, nDS1, nDS0, nMTR0, nMTR1.
2. If PPFDx is selected, then the parallel port can not be used as a parallel port until "Normal" mode is
selected.
The FDC signals are muxed onto the Parallel Port pins as shown in Table 43.
For ACPI compliance the FDD pins that are multiplexed onto the Parallel Port function independently of
the state of the Parallel Port controller. For example, if the FDC is enabled onto the Parallel Port the
multiplexed FDD interface functions normally regardless of the Parallel Port Power control, CR01.2.
Table 42 illustrates this functionality.
4 70 PD2 I/O nWP I
5 71 PD3 I/O
8
11 79 BUSY I nMTR1
17 67
FDC on Parallel Port Pin
The "floppy on the parallel port" pin function, FDC_PP, is muxed onto GP23. This pin function can be
used to switch the parallel port pins between the FDC and the parallel port. The FDC_PP pin can
generate a PME and an SMI by enabling GP23 in the appropriate PME and SMI enable registers (bit 5
of PME_EN2 and bit 4 of SMI_EN2 see the Runtime Registers section). This pin generates an SMI
and PME on both a low-to-high and a high-to-low edge.
The pin function for GP23 and the polarity of GP23 is selected through GPIO Polarity Register 2. When
the FDC_PP function is selected, the pin must also be selected as an input via bit 3 of the GPIO
Direction Register 2.
If the Floppy_PP bits, CR21 bits[1:0] = 01 or 10, and the FDC_PP function is selected on GP23, then
the default functionality (non-inverted polarity) for this pin is as follows: when the pin is low, the parallel
port pins are used for a floppy disk controller; when the pin is high, the parallel port pins are used for a
parallel port. The polarity bit controls the state of the pin.
If the Floppy_PP bits, CR21 bits[1:0]=00 then the pin is not used to switch the parallel port pins between
the FDC and the parallel port, even if the FDC_PP function is selected on GP23. See the Configuration
section for register description.
Note: When the floppy is selected on the parallel port, the parallel port IRQ, SMI and the parallel port
DRQ will not come out of the part.
Power management capabilities are provided for the following logical devices: floppy disk, UART 1, UART
2 and the parallel port. For each logical device, two types of power management are provided: direct
powerdown and auto powerdown.
FDC Power Management
Direct power management is controlled by Bit[3] in CR00. Refer to the Configuration section for more
information.
Auto Power Management is enabled by Bit[7] in CR07. When set, this bit allows FDC to enter powerdown
when all of the following conditions have been met:
1. The motor enable pins of register 3F2H are inactive (zero).
2. The part must be idle; MSR=80H and INT = 0 (INT may be high even if MSR = 80H due to polling
4. The Auto powerdown timer (10msec) must have timed out.
An internal timer is initiated as soon as the auto powerdown command is enabled. The part is then
powered down when all the conditions are met.
Disabling the auto powerdown mode cancels the timer and holds the FDC block out of auto powerdown.
DSR From Powerdown
If DSR powerdown is used when the part is in auto powerdown, the DSR powerdown will override the auto
powerdown. However, when the part is awakened from DSR powerdown, the auto powerdown will once
again become effective.
Wake Up From Auto Powerdown
If the part enters the powerdown state through the auto powerdown mode, then the part can be awakened
by reset or by appropriate access to certain registers.
If a hardware or software reset is used then the part will go through the normal reset sequence. If the
access is through the selected registers, then the FDC resumes operation as though it was never in
powerdown. Besides activating the nPCI_RESET pin or one of the software reset bits in the DOR or DSR,
the following register accesses will wake up the part:
1. Enabling any one of the motor enable bits in the DOR register (reading the DOR does not awaken the
3. A read or write to the Data register.
Once awake, the FDC will reinitiate the auto powerdown timer for 10 ms. The part will powerdown again
when all the powerdown conditions are satisfied.
Register Behavior
Table 44 illustrates the AT and PS/2 (including Model 30) configuration registers available and the type of
access permitted. In order to maintain software transparency, access to all the registers must be
results in the part remaining in powerdown state or exiting it.
Access to all other registers is possible without awakening the part. These registers can be accessed
during powerdown without changing the status of the part. A read from these registers will reflect the true
status as shown in the register description in the FDC description. A write to the part will result in the part
retaining the data and subsequently reflecting it when the part awakens. Accessing the part during
powerdown may cause an increase in the power consumption by the part. The part will revert back to its
low power mode when the access has been completed.
Pin Behavior
The LPC47N227 is specifically designed for systems in which power conservation is a primary concern.
This makes the behavior of the pins during powerdown very important.
The pins of the LPC47N227 can be divided into two major categories: system interface and floppy disk
drive interface. The floppy disk drive pins are disabled so that no power will be drawn through the part as a
result of any voltage applied to the pin within the part's power supply range. Most of the system interface
pins are left active to monitor system accesses that may wake up the part.
Note 1: Writing to the DOR or DSR does not wake up the part, however, writing any of the motor enable
bits or doing a software reset (via DOR or DSR reset bits) will wake up the part.
System Interface Pins
Table 45 gives the state of the interface pins in the powerdown state. Pins unaffected by the powerdown
are labeled "Unchanged".
FDD Interface Pins
All pins in the FDD interface which can be connected directly to the floppy disk drive itself are either
DISABLED or TRISTATED.
Pins used for local logic control or part programming are unaffected. Table 46 depicts the state of the
floppy disk drive interface pins in the powerdown state.
UART Power Management
Direct power management is controlled by CR02. Refer to the Configuration section for more information.
Auto Power Management is enabled by the UART1 and UART2 enable bits in CR07. When set, these bits
allow the following auto power management operations:
1. The transmitter enters auto powerdown when the transmit buffer and shift register are empty.
2. The receiver enters powerdown when the following conditions are all met:
changes.
Exit Auto Powerdown
The transmitter exits powerdown on a write to the XMIT buffer. The receiver exits auto powerdown when
RXDx changes state.
Parallel Port
information.
Auto Power Management is enabled by Bit[4] in CR07 . When set, this bit allows the ECP or EPP logical
parallel port blocks to be placed into powerdown when not being used.
1. EPP is not enabled in the configuration registers.
2. EPP is not selected through ecr while in ECP mode.
The ECP logic is in powerdown under any of the following conditions:
1. ECP is not enabled in the configuration registers.
2
Exit Auto Powerdown
The parallel port logic can change powerdown modes when the ECP mode is changed through the ecr
register or when the parallel port mode is changed through the configuration registers.
The LPC47N227 supports the serial interrupt to transmit interrupt information to the host system. The
serial interrupt scheme adheres to the Serial IRQ Specification for PCI Systems, Version 6.0. The
PCI_CLK, SER_IRQ and nCLKRUN pins are used for this interface. The Serial IRQ/CLKRUN Enable
bit D7 in CR29 activates the serial interrupt interface.
Timing Diagrams For SER_IRQ Cycle
A)
Note 1: Start Frame pulse can be 4-8 clocks wide depending on the location of the device in the PCI
bridge hierarchy in a synchronous bridge design.
B)
Note 1: Stop pulse is 2 clocks wide for Quiet mode, 3 clocks wide for Continuous mode.
Note 2: There may be none, one or more Idle states during the Stop Frame.
Note 3: The next SER_IRQ cycle's Start Frame pulse may or may not start immediately after the turn-
around clock of the Stop Frame.
There are two modes of operation for the SER_IRQ Start Frame.
1) Quiet (Active) Mode: Any device may initiate a Start Frame by driving the SER_IRQ low for one
clock, while the SER_IRQ is Idle. After driving low for one clock the SER_IRQ is immediately tri-stated
without at any time driving high. A Start Frame may not be initiated while the SER_IRQ is Active. The
SER_IRQ is Idle between Stop and Start Frames. The SER_IRQ is Active between Start and Stop
Frames. This mode of operation allows the SER_IRQ to be Idle when there are no IRQ/Data transitions
which should be most of the time.
Once a Start Frame has been initiated the Host Controller will take over driving the SER_IRQ low in the
next clock and will continue driving the SER_IRQ low for a programmable period of three to seven
clocks. This makes a total low pulse width of four to eight clocks. Finally, the Host Controller will drive
the SER_IRQ back high for one clock, then tri-state.
Any SER_IRQ Device (i.e., The LPC47N227) which detects any transition on an IRQ/Data line for which
it is responsible must initiate a Start Frame in order to update the Host Controller unless the SER_IRQ
is already in an SER_IRQ Cycle and the IRQ/Data transition can be delivered in that SER_IRQ Cycle.
2) Continuous (Idle) Mode: Only the Host controller can initiate a Start Frame to update IRQ/Data line
information. All other SER_IRQ agents become passive and may not initiate a Start Frame. SER_IRQ
will be driven low for four to eight clocks by Host Controller. This mode has two functions. It can be
used to stop or idle the SER_IRQ or the Host Controller can operate SER_IRQ in a continuous mode by
initiating a Start Frame at the end of every Stop Frame.
An SER_IRQ mode transition can only occur during the Stop Frame. Upon reset, SER_IRQ bus is
defaulted to Continuous mode, therefore only the Host controller can initiate the first Start Frame.
Slaves must continuously sample the Stop Frames pulse width to determine the next SER_IRQ Cycle's
mode.
SER_IRQ Data Frame
Once a Start Frame has been initiated, the LPC47N227 will watch for the rising edge of the Start Pulse
and start counting IRQ/Data Frames from there. Each IRQ/Data Frame is three clocks: Sample phase,
Recovery phase, and Turn-around phase. During the Sample phase the LPC47N227 drives the
SER_IRQ low, if and only if, its last detected IRQ/Data value was low. If its detected IRQ/Data value is
high, SER_IRQ is left tri-stated. During the Recovery phase the LPC47N227 drives the SER_IRQ high,
if and only if, it had driven the SER_IRQ low during the previous Sample Phase. During the Turn-
around Phase the LPC47N227 tri-states the SER_IRQ. The LPC47N227 will drive the SER_IRQ line
low at the appropriate sample point if its associated IRQ/Data line is low, regardless of which device
initiated the Start Frame.
The Sample Phase for each IRQ/Data follows the low to high transition of the Start Frame pulse by a
number of clocks equal to the IRQ/Data Frame times three, minus one. (e.g. The IRQ5 Sample clock is
the sixth IRQ/Data Frame, (6 x 3) - 1 = 17th clock after the rising edge of the Start Pulse).
5 IRQ4 14
6 IRQ5 17
7 IRQ6 20
8 IRQ7 23
9 IRQ8 26
The SER_IRQ data frame supports IRQ2 from a logical device on Period 3, which can be used for the
System Management Interrupt (nSMI). When using Period 3 for IRQ2 the user should mask off the SMI
via the SMI Enable Register. Likewise, when using Period 3 for nSMI the user should not configure any
logical devices as using IRQ2.
SER_IRQ Period 14 is used to transfer IRQ13. Logical devices FDC, Parallel Port, Serial Port 1, Serial
Port 2 have IRQ13 as a choice for their primary interrupt.
The SMI is enabled onto the SMI frame of the Serial IRQ via bit 6 of SMI Enable Register 2 and onto the
nIO_SMI pin via bit 7 of the SMI Enable Register 2.
Stop Cycle Control
Once all IRQ/Data Frames have completed the Host Controller will terminate SER_IRQ activity by
initiating a Stop Frame. Only the Host Controller can initiate the Stop Frame. A Stop Frame is indicated
when the SER_IRQ is low for two or three clocks. If the Stop Frame's low time is two clocks then the
next SER_IRQ Cycle's sampled mode is the Quiet mode; and any SER_IRQ device may initiate a Start
Frame in the second clock or more after the rising edge of the Stop Frame's pulse. If the Stop Frame's
low time is three clocks then the next SER_IRQ Cycle's sampled mode is the Continuos mode; and only
the Host Controller may initiate a Start Frame in the second clock or more after the rising edge of the
Stop Frame's pulse.
Latency
Latency for IRQ/Data updates over the SER_IRQ bus in bridge-less systems with the minimum Host
supported IRQ/Data Frames of seventeen, will range up to 96 clocks (3.84
IRQ/Data updates from the secondary or tertiary buses will be a few clocks longer for synchronous
buses, and approximately double for asynchronous buses.
Any serialized IRQ scheme has a potential implementation issue related to IRQ latency. IRQ latency
could cause an EOI or ISR Read to precede an IRQ transition that it should have followed. This could
cause a system fault. The host interrupt controller is responsible for ensuring that these latency issues
are mitigated. The recommended solution is to delay EOIs and ISR Reads to the interrupt controller by
the same amount as the SER_IRQ Cycle latency in order to ensure that these events do not occur out
of order.
AC/DC Specification Issue
All SER_IRQ agents must drive / sample SER_IRQ synchronously related to the rising edge of PCI bus
clock. The SER_IRQ pin uses the electrical specification of PCI bus. Electrical parameters will follow
PCI spec. section 4, sustained tri-state.
Reset and Initialization
The SER_IRQ bus uses nPCI_RESET as its reset signal. The SER_IRQ pin is tri-stated by all agents
while nPCI_RESET is active. With reset, SER_IRQ Slaves are put into the (continuous) IDLE mode.
The Host Controller is responsible for starting the initial SER_IRQ Cycle to collect system's IRQ/Data
default values. The system then follows with the Continuous/Quiet mode protocol (Stop Frame pulse
width) for subsequent SER_IRQ Cycles. It is Host Controller's responsibility to provide the default
values to 8259's and other system logic before the first SER_IRQ Cycle is performed. For SER_IRQ
system suspend, insertion, or removal application, the Host controller should be programmed into
Continuous (IDLE) mode first. This is to guarantee SER_IRQ bus is in IDLE state before the system
configuration changes.
Routable IRQ Inputs
The routable IRQ input (IRQINx) functions are on pins 51 (IRQIN1) and 52 (IRQIN2), muxed onto GP13
and GP14 respectively as inputs. The IRQINx pin's IRQ time slot in the Serial IRQ stream is selected
via a 4-bit control register for each IRQIN function (CR29 for IRQIN1, CR2A for IRQIN2). A value of
0000 disables the IRQ function.
The part is able to generate a PME and an SMI from both of the IRQ inputs through the GPIO bits in the
PME and SMI status and enable registers. The edge is programmable through the polarity bit of the
GPIO control register.
User Note: In order to use an IRQ for one of the IRQINx inputs that are muxed on the GPIO pins, the
corresponding IRQ must not be used for any of the devices in the LPC47N227. Otherwise contention
may occur.
Overview
The LPC47N227 supports the PCI nCLKRUN signal. nCLKRUN is used to indicate the PCI clock status
as well as to request that a stopped clock be started. The LPC47N227 nCLKRUN signal is on
TQFP/STQFP pin number 28. See FIGURE 3 for an example of a typical system implementation using
nCLKRUN.
If the LPC47N227 SIRQ_CLKRUN_EN signal is disabled, it will disable the nCLKRUN support related to
nLDRQ in addition to disabling the SER_IRQ and the nCLKRUN associated with SER_IRQ.
nCLKRUN is an open drain output and an input. Refer to the PCI Mobile Design Guide Rev 1.0 for a
description of the nCLKRUN function.
nCLKRUN for Serial IRQ
The LPC47N227 supports the PCI nCLKRUN signal for the Serial IRQs. If an SIO interrupt occurs while
the PCI clock is stopped, nCLKRUN is asserted before the serial interrupt signal is driven active.
See "Using nCLKRUN" section below for more details.
nCLKRUN for nLDRQ
nCLKRUN support is also provided in the LPC47N227 for the nLDRQ signal. If a device requests DMA
service while the PCI clock is stopped, nCLKRUN is asserted to restart the PCI clock. This is required
to drive the nLDRQ signal active.
See "Using nCLKRUN" section for more details.
Using nCLKRUN
If nCLKRUN is sampled "high", the PCI clock is stopped or stopping. If nCLKRUN is sampled "low", the
PCI clock is starting or started (running). If a device in the LPC47N227 asserts or de-asserts an
interrupt or asserts a DMA request, and nCLKRUN is sampled "high", the LPC47N227 requests the
restoration of the clock by asserting the nCLKRUN signal asynchronously (Table 47). The LPC47N227
holds nCLKRUN low until it detects two rising edges of the clock. After the second clock edge, the
LPC47N227 disables the open drain driver (FIGURE 4).
The LPC47N227 will not assert nCLKRUN under any conditions if SIRQ_CLKRUN_EN is inactive ("0").
The SIRQ_CLKRUN_EN bit is D7 in CR29.
The LPC47N227 will not assert nCLKRUN if it is already driven low by the central resource; i.e., the PCI
CLOCK GENERATOR in FIGURE 3. The LPC47N227 will not assert nCLKRUN unless the line has
been deasserted for two successive clocks; i.e., before the clock was stopped (FIGURE 4).
Note
asynchronously to the PCI Clock and regardless of the Serial IRQ mode; i.e., "continuous" or "quiet".
Note
Note 1: The signal "ANY IRQ CHANGE/DRQ ASSERTION" is the same as "CHANGE/ASSERTION" in
SER_IRQ/DMA cycle. For example, if "ANY IRQ CHANGE/DRQ ASSERTION" is asserted
before nCLKRUN is de-asserted (not shown in FIGURE 4), the LPC47N227 must assert
nCLKRUN as needed until the SER_IRQ/DMA cycle has completed.
STOPS
DRIVING
nCLKRUN
The LPC47N227 provides a set of flexible Input/Output control functions to the system designer through
the 29 independently programmable General Purpose I/O pins (GPIO). The GPIO pins can perform
basic I/O and many of them can be individually enabled to generate an SMI and a PME.
GPIO Pins
The following pins include GPIO functionality as defined in the table below.
Function
PME/SMI
Each GPIO port has a 1-bit data register. GPIOs are controlled by GPIO control registers located in the
Configuration section. The data register for each GPIO port is represented as a bit in one of the 8-bit
GPIO DATA Registers, GP1 to GP4. The bits in these registers reflect the value of the associated
GPIO pin as follows. Pin is an input: The bit is the value of the GPIO pin. Pin is an output: The value
written to the bit goes to the GPIO pin. Latched on read and write. The GPIO data registers are located
in the Runtime Register block; see the Runtime Registers section. The GPIO ports with their alternate
functions and configuration state register addresses are listed in Table 49.
Note 1: The GPIO Data Registers are located at the offset shown from the RUNTIME REGISTERS
BLOCK address.
Each GPIO port has an 8-bit control register that controls the behavior of the pin. These registers are
defined in the Configuration section of this specification.
Each GPIO port may be configured as either an input or an output. If the pin is configured as an output,
it can be programmed as open-drain or push-pull. Inputs and outputs can be configured as non-
inverting or inverting. GPIO Direction Registers determine the port direction, GPIO Polarity Registers
determine the signal polarity, and GPIO Output Type Register determines the output driver type select.
The GPIO Output Type Register applies to certain GPIOs (GP12-GP17 and GP20). The GPIO
Direction, Polarity and Output Type Registers control the GPIO pin when the pin is configured for the
GPIO function and when the pin is configured for the alternate function for all pins.
The basic GPIO configuration options are summarized in Table 50.
GPIO Operation
The operation of the GPIO ports is illustrated in FIGURE 5.
Configuration
Register bit-1
(Polarity)
Configuration
Register bit-0
(Input/Output)
details.
When a GPIO port is programmed as an input, reading it through the GPIO data register latches either
the inverted or non-inverted logic value present at the GPIO pin. Writing to a GPIO port that is
programmed as an input has no effect (Table 51).
When a GPIO port is programmed as an output, the logic value or the inverted logic value that has been
written into the GPIO data register is output to the GPIO pin. Reading from a GPIO port that is
programmed as an output returns the last value written to the data register (Table 51).
REGISTER
The LPC47N227 provides 21 GPIOs that can directly generate a PME. See the table in the next
section. The GPIO Polarity Registers in the Configuration section select the edge on these GPIO pins
that will set the associated status bit in the PME_STS1 PME_STS3 registers. The default is the low-
to-high edge. If the corresponding enable bit in the PME_EN1 PME_EN3 registers and the PME_EN
bit in the PME_EN register is set, a PME will be generated. These registers are located in the Runtime
Registers Block, which is located at the address contained in the configuration registers CR30. The
GPIOs that can directly generate an SMI. See the table in the next section.
GPIO PME and SMI Functionality
The following GPIOs are dedicated wakeup GPIOs with a status and enable bit in the PME status and
enable registers:
GP20-GP24
GP30-GP37
This following is the list of PME status and enable registers for their corresponding GPIOs:
PME_STS1 and PME_EN1 for GP10-GP17
PME_STS2 and PME_EN2 for GP20-GP24
PME_STS3 and PME_EN3 for GP30-GP37
The following GPIOs can directly generate an SMI and have a status and enable bit in the SMI status
and enable registers.
GP10-GP17
The following SMI status and enable registers for these GPIOs:
SMI_STS1 and SMI_EN1 for GP10-17
SMI_STS2 and SMI_EN2 for GP23-GP24
Note 1: Since GP12 can be used to generate an SMI and as the nIO_SMI output, do not enable GP12
selected on the GP12 pin. Use GP12 to generate an SMI event only if the SMI output is
enabled on the Serial IRQ stream.
The LPC47N227 implements a "group" nIO_SMI output pin. The System Management Interrupt is a
non-maskable interrupt with the highest priority level used for OS transparent power management. The
nSMI group interrupt output consists of the enabled interrupts from Super I/O Device Interrupts (Parallel
Port, Serial Port 1 and 2 and FDC) and many of the GPIOs pins. The GP12/nIO_SMI pin, when selected
for the nIO_SMI function, can be programmed to be active high or active low via bit 2 in the GPIO
Polarity Register 1 (CR32). The nIO_SMI pin function defaults to active low. The output buffer type of
the pin can be programmed to be open-drain or push-pull via GPIO Output Type Register (CR39).
The interrupts are enabled onto the group nSMI output via the SMI Enable Registers 1 and 2. The
nSMI output is then enabled onto the nIO_SMI output pin via bit[7] in the SMI Enable Register 2. The
SMI output can also be enabled onto the serial IRQ stream (IRQ2) via Bit[6] in the SMI Enable Register
2.
SMI Registers
The SMI event bits for the GPIOs events are located in the SMI status and Enable registers 1 and 2.
The polarity of the edge used to set the status bit and generate an SMI is controlled by the GPIO
Polarity Registers located in the Configuration section. For non-inverted polarity (default) the status bit
is set on the low-to-high edge. Status bits for the GPIOs are cleared on a write of `1'.
The SMI logic for the GPIO events is implemented such that the output of the status bit for each event is
combined with the corresponding enable bit in order to generate an SMI.
The SMI event bits for the super I/O devices are located in the SMI status and enable register 1 and 2.
All of these status bits are cleared at the source; these status bits are not cleared by a write of `1'. The
SMI logic for these events is implemented such that each event is directly combined with the
corresponding enable bit in order to generate an SMI.
See the "Runtime Registers" section for the definition of the SMI status and enable registers.
See PME register description in the Runtime Registers Section.
Runtime Registers Block Summary
The runtime registers are located at the address programmed in the Runtime Register Block Base
Address configuration register located in CR30. The part performs 16-bit address qualification on the
Runtime Register Base Address (bits[11:0] are decoded and bits[15:12] must be zero). The runtime
register block may be located within the range 0x0100-0x0FFF on 16-byte boundaries. Decodes are
disabled if the Runtime Register Base Address is located below 0x100. These registers are powered by
VTR.
Note: Hard Reset: nPCI_RESET pin asserted.
Note: Reserved bits return 0 on read.
Note 1: The parallel port interrupt defaults to 1 when the parallel port power bit is cleared. When the
Default = 0x00
on VTR POR
= 0 (default)
= 1 Set when LPC47N227 would normally assert the
PME_En bit. Set when a bit in a PME Wake Status
register and its associated enable bit set.
PME_Status is not affected by Vcc POR, SOFT RESET
or HARD RESET.
Writing a "1" to PME_Status will clear it and cause the
LPC47N227 to stop asserting nIO_PME, if enabled.
Writing a "0" to PME_Status has no effect.
Default = 0x00
on VTR POR
= 0 nIO_PME signal assertion is disabled (default)
= 1 Enables LPC47N227 to assert nIO_PMEsignal
Bit[7:1] Reserved
PME_En is not affected by Vcc POR, SOFT RESET or
HARD RESET
Default = 0x00
on VTR POR
This register indicates the state of the individual PME
wake sources, independent of the individual source
enables or the PME_En bit.
If the wake source has asserted a wake event, the
associated PME Wake Status bit will be a "1".
Bit[0] GP10
Bit[1] GP11
Bit[2] GP12
Bit[3] GP13
Bit[4] GP14
Bit[5] GP15
Bit[6] GP16
Bit[7] GP17
The PME Wake Status register is not affected by Vcc
POR, SOFT RESET or HARD RESET.
Writing a "1" to Bit[7:0] will clear it. Writing a "0" to any
bit in PME Wake Status Register has no effect.
Default = 0x00
on VTR POR
This register indicates the state of the individual PME
wake sources, independent of the individual source
enables or the PME_En bit.
If the wake source has asserted a wake event, the
associated PME Wake Status bit will be a "1".
Bit[0] RI1
Bit[1] RI2
Bit[2] GP20
Bit[3] GP21
Bit[4] GP22
Bit[5] GP23
Bit[6] GP24
Bit[7] Reserved
The PME Wake Status register is not affected by Vcc
POR, SOFT RESET or HARD RESET.
Writing a "1" to Bit[7:0] will clear it. Writing a "0" to any
bit in PME Wake Status Register has no effect.
Default = 0x00
on VTR POR
This register indicates the state of the individual PME
wake sources, independent of the individual source
enables or the PME_En bit.
If the wake source has asserted a wake event, the
associated PME Wake Status bit will be a "1".
Bit[0] GP30
Bit[1] GP31
Bit[2] GP32
Bit[3] GP33
Bit[4] GP34
Bit[5] GP35
Bit[6] GP36
Bit[7] GP37
The PME Wake Status register is not affected by Vcc
POR, SOFT RESET or HARD RESET.
Writing a "1" to Bit[7:0] will clear it. Writing a "0" to any
bit in PME Wake Status Register has no effect.
Default = 0x00
on VTR POR
This register is used to enable individual LPC47N227
PME wake sources onto the nIO_PME wake bus.
When the PME Wake Enable register bit for a wake
source is active ("1"), if the source asserts a wake event
so that the associated status bit is "1" and the PME_En
bit is "1", the source will assert the nIO_PME signal.
When the PME Wake Enable register bit for a wake
source is inactive ("0"), the PME Wake Status register
will indicate the state of the wake source but will not
assert the nIO_PME signal.
Bit[0] GP10
Bit[1] GP11
Bit[2] GP12
Bit[3] GP13
Bit[4] GP14
Bit[5] GP15
Bit[6] GP16
Bit[7] GP17
The PME Wake Enable register is not affected by Vcc
POR, SOFT RESET or HARD RESET.
Default = 0x00
on VTR POR
This register is used to enable individual LPC47N227
PME wake sources onto the nIO_PME wake bus.
When the PME Wake Enable register bit for a wake
source is active ("1"), if the source asserts a wake event
so that the associated status bit is "1" and the PME_En
bit is "1", the source will assert the nIO_PME signal.
When the PME Wake Enable register bit for a wake
source is inactive ("0"), the PME Wake Status register
will indicate the state of the wake source but will not
assert the nIO_PME signal.
Bit[0] RI1
Bit[1] RI2
Bit[2] GP20
Bit[3] GP21
Bit[4] GP22
Bit[5] GP23
Bit[6] GP24
Bit[7] Reserved
The PME Wake Enable register is not affected by Vcc
POR, SOFT RESET or HARD RESET.
Default = 0x00
on VTR POR
This register is used to enable individual LPC47N227
PME wake sources onto the nIO_PME wake bus.
When the PME Wake Enable register bit for a wake
source is active ("1"), if the source asserts a wake event
so that the associated status bit is "1" and the PME_En
bit is "1", the source will assert the nIO_PME signal.
When the PME Wake Enable register bit for a wake
source is inactive ("0"), the PME Wake Status register
will indicate the state of the wake source but will not
assert the nIO_PME signal.
Bit[0] GP30
Bit[1] GP31
Bit[2] GP32
Bit[3] GP33
Bit[4] GP34
Bit[5] GP35
Bit[6] GP36
Bit[7] GP37
The PME Wake Enable register is not affected by Vcc
POR, SOFT RESET or HARD RESET.
Default = 0x00
on VTR POR
This register is used to read the status of the SMI inputs.
The following bits are cleared on a write of `1'.
Bit[0] GP10
Bit[1] GP11
Bit[2] GP12
Bit[3] GP13
Bit[4] GP14
Bit[5] GP15
Bit[6] GP16
Bit[7] GP17
Default = 0x01
on VTR POR
Bit 0 is set to `1'
on VCC POR,
VTR POR and
HARD RESET
This register is used to read the status of the SMI inputs.
The bits[3:0] must be cleared at their source. Bits[5:4]
are cleared on a write of `1'.
Bit[0] PINT. The parallel port interrupt defaults to `1'
when the parallel port activate bit is cleared. When the
parallel port is activated, PINT follows the nACK input.
Bit[1] U2INT
Bit[2] U1INT
Bit[3] FINT
Bit[4] GP23
Bit[5] GP24
Bit[7:6] Reserved
Default = 0x00
on VTR POR
This register is used to enable the different interrupt
sources onto the internal group nSMI signal.
1=Enable
0=Disable
Bit[0] GP10
Bit[1] GP11
Bit[2] GP12
Bit[3] GP13
Bit[4] GP14
Bit[5] GP15
Bit[6] GP16
Bit[7] GP17
Default = 0x00
on VTR POR
This register is used to enable the different interrupt
sources onto the internal group nSMI signal, and the
internal group nSMI signal onto the nIO_SMI GPI/O pin or
the serial IRQ stream on IRQ2.
1=Enable
0=Disable
Bit[0] EN_PINT
Bit[1] EN_U2INT
Bit[2] EN_U1INT
Bit[3] EN_FINT
Bit[4] GP23
Bit[5] GP24
Bit[6] EN_SMI_S (Enable group nSMI signal onto serial
IRQ2)
Bit[7] EN_SMI (Enable group nSMI signal onto nIO_SMI
pin)
Default = 0x00
on VTR POR
Bit[0]GP10
Bit[1]GP11
Bit[2]GP12
Bit[3]GP13
Bit[4]GP14
Bit[5]GP15
Bit[6]GP16
Bit[7]GP17
Default = 0x00
on VTR POR
Bit[0]GP20
Bit[1]GP21
Bit[2]GP22
Bit[3]GP23
Bit[4]GP24
Bit[7:5]Reserved
Default = 0x00
on VTR POR
Bit[0]GP30
Bit[1]GP31
Bit[2]GP32
Bit[3]GP33
Bit[4]GP34
Bit[5]GP35
Bit[6]GP36
Bit[7]GP37
Default = 0x00
on VTR POR
Bit[0]GP40
Bit[1]GP41
Bit[2]GP42
Bit[3]GP43
Bit[4]GP44
Bit[5]GP45
Bit[6]GP46
Bit[7]GP47
Note: Reserved bits return 0 on read.
The configuration of the LPC47N227 is programmed through hardware selectable Configuration Access
Ports that appear when the chip is placed into the configuration state. The LPC47N227 logical device
blocks, if enabled, will operate normally in the configuration state.
Configuration Access Ports
The Configuration Access Ports are the CONFIG PORT, the INDEX PORT, and the DATA PORT
(Table 54). The base address of these registers is controlled by the GP11/SYSOPT pin and by the
Configuration Port Base Address registers CR12 and CR13. To determine the configuration base
address at power-up, the state of the GP11/SYSOPT pin is latched by the falling edge of a hardware
reset. If the latched state is a 0, the base address of the Configuration Access Ports is located at
address 0x02E; if the latched state is a 1, the base address is located at address 0x04E. The base
address is relocatable via CR12 and CR13.
Note
Configuration State
The configuration registers are used to select programmable chip options. The LPC47N227 operates in
two possible states: the run state and the configuration state. After power up by default the chip is in the
run state. To program the configuration registers, the configuration state must be explicitly enabled.
Programming the configuration registers typically follows this sequence:
1. Enter the Configuration State,
2. Program the Configuration Register(s),
3. Exit the Configuration State.
Entering the Configuration State
To enter the configuration state write the Configuration Access Key to the CONFIG PORT. The
Configuration Access Key is one byte of 55H data. The LPC47N227 will automatically activate the
Configuration Access Ports following this procedure.
Configuration Register Programming
The LPC47N227 contains configuration registers CR00-CR39. After the LPC47N227 enters the
configuration state, configuration registers can be programmed by first writing the register index number
(00 - 39H) to the Configuration Select Register (CSR) through the INDEX PORT and then writing or
reading the configuration register contents through the DATA PORT. Configuration register access
remains enabled until the configuration state is explicitly exited.
To exit the configuration state, write one byte of AAH data to the CONFIG PORT. The LPC47N227 will
automatically deactivate the Configuration Access Ports following this procedure, at which point
configuration register access cannot occur until the configuration state is explicitly re-enabled.
Programming Example
The following is a configuration register programming example written in Intel 8086 assembly language.
;----------------------------.
; ENTER CONFIGURATION STATE |
;----------------------------'
MOV
OUT DX,AL
;----------------------------.
; CONFIGURE REGISTER CR0-CRx |
;----------------------------'
MOV DX,02EH
MOV AL,00H
OUT
MOV AL,3FH
OUT DX,AL
MOV DX,02EH
OUT
MOV AL,9FH
OUT DX,AL
; Repeat for all CRx registers
;
;-----------------------------.
; EXIT CONFIGURATION STATE |
;-----------------------------'
MOV DX,02EH
MOV AX,AAH
OUT DX,AL
Configuration Select Register (CSR)
The Configuration Select Register can only be accessed when the LPC47N227 is in the configuration
state. The CSR is located at the INDEX PORT address and must be initialized with configuration
register index before the register can be accessed using the DATA PORT.
The configuration registers are set to their default values at power up (Table 55) and are RESET as
indicated in Table 55 and the register descriptions that follow.
En
alternate function on the GPIO.
CR00
CR00 can only be accessed in the configuration state and after the CSR has been initialized to 00H.
level on this bit puts the FDC in low power mode.
that a valid configuration cycle has occurred. The control software
must take care to set this bit at the appropriate times. Set to zero
after power up. This bit has no effect on any other hardware in the
chip.
NOTE
address registers the logical device's base address must be set below 100h. Devices that are powered
down but still reside at a valid I/O base address will participate in Plug-and-Play range checking.
CR01 can only be accessed in the configuration state and after the CSR has been initialized to 01H.
A low level on this bit puts the Parallel Port in low power mode.
Printer Mode (Default). A low level on this bit enables the Extended
Parallel port modes. Refer to Bits 0 and 1 of CR4
CR39 (Default). A low level on this bit disables the reading and
writing of CR00 CR39. Note: once the Lock CRx bit is set to "0",
this bit can only be set to "1" by a hard reset or power-up reset.
NOTE
address registers the logical device's base address must be set below 100h. Devices that are powered
down but still reside at a valid I/O base address will participate in Plug-and-Play range checking.
CR02 can only be accessed in the configuration state and after the CSR has been initialized to 02H.
Port (Default). A low level on this bit places the Primary Serial Port
into Power Down Mode.
Serial Port, including the SCE/FIR block (Default). A low level on
this bit places the Secondary Serial Port including the SCE/FIR
block into Power Down Mode.
NOTE
address registers the logical device's base address must be set below 100h. Devices that are powered
down but still reside at a valid I/O base address will participate in Plug-and-Play range checking.
CR03 can only be accessed in the configuration state and after the CSR has been initialized to 03H.
DRIVE REGISTER (TDR) for more information on
these modes.
mode.
1
0
0
0
1
0
AT Mode (Default)
Reserved
PS/2
Model 30
NOTE
CR04 can only be accessed in the configuration state and after the CSR has been initialized to 04H.
(default)
support (default). A high level on this bit enables MIDI support.
support (default). A high level on this bit enables MIDI support.
1 = EPP 1.7
Note
CR05 can only be accessed in the configuration state and after the CSR has been initialized to 05H.
Control
(R/W)
1 = FDC Outputs are push-pull.
(R/W)
1 = FDC Outputs Tri-State.
transfers (default).
1 = Non-Burst mode enabled.
1= swap drives and motor select 0 and 1 of the FDC on the
parallel port.
as follows if CR03.4 is 0 the DRVDEN1 output pin assumes the value of the DRVDEN1
function, if CR03.4 is 1 the DRVDEN1 output pin stays high. If the FDC Output Control is
inactive the DRVDEN1 Control will have no affect on the DRVDEN1 output pin.
TRISTATED
CR06 can only be accessed in the configuration state and after the CSR has been initialized to 06H.
CR06 holds the floppy disk drive type IDs for up to four floppy disk drives (see Table 6 Drive Type ID
in the Floppy Disk Controller).
CR07
CR07 can only be accessed in the configuration state and after the CSR has been initialized to 07H.
CR07 controls auto power management and the floppy boot drive.
0 = Drive A (default)
1 = Drive B
Port. The function is:
0 = Auto powerdown disabled (default)
1 = Auto powerdown enabled
This bit is reset to the default state by POR or a hardware reset.
The function is:
0 = Auto powerdown disabled (default)
1 = Auto powerdown enabled
This bit is reset to the default state by POR or a hardware reset.
The function is:
0 = Auto powerdown disabled (default)
1 = Auto powerdown enabled
This bit is reset to the default state by POR or a hardware reset.
Disk. The function is:
0 = Auto powerdown disabled (default)
1 = Auto powerdown enabled
This bit is reset to the default state by POR or a hardware reset.
CR08
Register CR08 is reserved. The default value of this register after power up is 00H.
CR09
CR09 can only be accessed in the configuration state and after the CSR has been initialized to 09H.
CR09 is a test control register and all bits must be treated as Reserved. Note: all test modes are
reserved for SMSC use. Activating test mode registers may produce undesired results.
CR0A
CR0A can only be accessed in the configuration state and after the CSR has been initialized to 0AH.
CR0A defines the FIFO threshold for the ECP mode parallel port. Bits [5:4] are Reserved. Reserved
Bits cannot be written and return 0 when read. Bits [7:6] are the IR OUTPUT MUX bits and are reset to
the default state by a POR and a hardware reset.
These bits are used to select IR Output Mux Mode.
That is, depending on the mode of
Serial Port 2, use Pins 92, 94-100
for COM signals or use RXD2 and
TXD2 (pins 95 and 96) for IR.
When Serial Port 2 is inactive
(Power Down bit = 0), then TXD2
pin is low. The IRTX2 pin is low.
use IRRX2, IRTX2 (pins 61, 62).
When Serial Port 2 is inactive
(Power Down bit = 0), then IRTX2
pin is low. The TXD2 pin is low.
are High-Z, regardless of mode of
UART2 and state of UART2
powerdown bit.
CR0B
CR0B can only be accessed in the configuration state and after the CSR has been initialized to 0BH.
CR0B indicates the Drive Rate table (Table 68) used for each drive. Refer to section CR1F for the
Drive Type register.
CR0C
CR0C can only be accessed in the configuration state and after the CSR has been initialized to 0CH.
CR0C controls the operating mode of the UART. This register is reset to the default state by a POR or
a hardware reset.
1 = RX input active low.
1 = TX output active low (default).
1 = Half duplex
0 = Full duplex (default)
0 0 0
1 = High speed enabled
0 = Standard (default)
1 = High speed enabled
0 = Standard (default)
CR0D
CR0D can only be accessed in the configuration state and after the CSR has been initialized to 0DH.
This register is read only. CR0D contains the LPC47N227 Device ID. The default value of this register
after power up is 5AH on VCC POR.
CR0E
CR0E can only be accessed in the configuration state and after the CSR has been initialized to 0EH.
This register is read only. CR0E contains the current LPC47N227 Chip Revision Level starting at 00H.
CR0F
CR0F can only be accessed in the configuration state and after the CSR has been initialized to 0FH.
CR0F is a test control register and all bits must be treated as Reserved. Note: all test modes are
reserved for SMSC use. Activating test mode registers may produce undesired results.
CR10 can only be accessed in the configuration state and after the CSR has been initialized to 10H.
CR10 is a test control register and all bits must be treated as Reserved. NOTE: All test modes are
reserved for SMSC use. Activating test mode registers may produce undesired results.
CR11
CR11 can only be accessed in the configuration state and after the CSR has been initialized to 11H.
CR11 is a test control register and all bits must be treated as Reserved. NOTE: all test modes are
reserved for SMSC use. Activating test mode registers may produce undesired results.
CR12 - CR13
CR12 and CR13 are the LPC47N227 Configuration Ports base address registers (Table 73 and Table
74). These registers are used to relocate the Configuration Ports base address beyond the power-up
defaults determined by the SYSOPT pin programming.
CR12 contains the Configuration Ports base address bits A[7:0]. CR13 contains the Configuration Ports
base address bits A[10:8]. The address bits A[15:11] must be `00000' to access the configuration port.
The Configuration Ports base address is relocatable on even-byte boundaries; i.e., A0 = `0'.
At power-up the Configuration Ports base address is determined by the SYSOPT pin programming. To
relocate the Configuration Ports base address after power-up, first write the lower address bits of the
changes the Configuration Ports base address.
0x4E
2 A2
3 A3
4 A4
5 A5
6 A6
7 A7
Note: The Configuration Ports Base Address is relocatable on even-byte boundaries; i.e., A0 = "0".
0x00
1 A9
2 A10
Note:
CR14 can only be accessed in the configuration state and after the CSR has been initialized to 14H.
CR14 shadows the bits in the write-only FDC run-time DSR register.
low power mode.
is self clearing.
CR15
CR15 can only be accessed in the configuration state and after the CSR has been initialized to 15H.
CR15 shadows the bits in the write-only UART1 run-time FCR register.
FIFOs
resets its counter logic to 0. This bit is self clearing.
These bits are used to set the trigger level for the RCVR FIFO
interrupt.
CR16 can only be accessed in the configuration state and after the CSR has been initialized to 16H.
CR16 shadows the bits in the write-only UART2 run-time FCR register. See CR15 for register
description.
CR17
CR17 can only be accessed in the configuration state and after the CSR has been initialized to 17H.
CR17 is the Force FDD Status Change register.
0-1
FDD nDSKCHG input active when the appropriate drive has been
selected. FORCE DSKCHG1 and FORCE DSKCHG0 can be
written to a 1 but are not clearable by software. FORCE
DSKCHG1 is cleared on (nSTEP AND nDS1), FORCE DSKCHG0
is cleared on (nSTEP AND nDS0). Note: The DSK CHG bit in the
Floppy DIR register, Bit 7 = (nDS0 AND FORCE DSKCHG0) OR
(nDS1 AND FORCE DSKCHG1) OR nDSKCHG.
Setting either of the Force Disk Change bits active (1) forces the
FDD nDSKCHG input active when the appropriate drive has been
selected.
Bit[0] Force Change for FDC0
0=Inactive
1=Active
Bit[1] Force Change for FDC1
0=Inactive
1=Active
has been selected. The FORCE WRTPRT function applies to the
nWRTPRT pin in the FDD Interface as well as the nWRTPRT pin
in the Parallel Port FDC.
Note: The
CR18 - CR1E registers are reserved. Reserved registers cannot be written and return 0 when read.
The default value of these registers after power up is 00H on VCC POR.
CR1F
CR1F can only be accessed in the configuration state and after the CSR has been initialized to 1FH.
CR1F indicates the floppy disk Drive Type for each of four floppy disk drives. The floppy disk Drive
Type is used to map the three FDC DENSEL, DRATE1 and DRATE0 outputs onto two Super I/O output
pins DRVDEN1 and DRVDEN0 (Table 79).
2/1 MB 5.25" FDDS
2/1.6/1 MB 3.5" (3-MODE)
CR20
CR20 can only be accessed in the configuration state and after the CSR has been initialized to 20H.
CR20 is used to select the base address of the floppy disk controller (FDC). The FDC base address
can be set to 96 locations on 8 byte boundaries from 100H - 3F8H. To disable the FDC set ADR9 and
ADR8 to zero. Set CR20.[1:0] to 00b when writing the FDC Base Address.
FDC Address Decoding: address bits A[15:10] must be `000000' to access the FDC registers. A[3:0]
are decoded as 0XXXb.
3 ADR5
4 ADR6
5 ADR7
6 ADR8
7 ADR9
CR21
CR21 can only be accessed in the configuration state and after the CSR has been initialized to 21H.
CR21 is the Floppy on Parallel Port Pin register.
on the parallel port, the FDC_PP pin
function is not used.
PP as follows: (non-inverted polarity) when
the pin is low, the parallel port pins are used
for a floppy disk controller: drive 0 is on FDC
pins, drive 1 is on parallel port pins.
PP as follows: (non-inverted polarity) when
the pin is low, the parallel port pins are used
for a floppy disk controller: drive 0 is on
parallel port pins and drive 1 is on parallel
port pins.
Status register. If the TIMEOUT_SELECT bit is cleared (`0'), the
TIMEOUT bit is cleared on the trailing edge of the read of the EPP
Status Register (default).
If the TIMEOUT_SELECT bit is set (`1'), the TIMEOUT bit is
cleared on a write of `1' to the TIMEOUT bit.
CR22
bits. CR22 is part of the ECP DMA/IRQ Software Indicators described in the ECP cnfgB register. CR22
is read/write. Note: all of the ECP DMA/IRQ Software Indicators, including CR22, are software-only.
Writing these bits does not affect the ECP hardware DMA or IRQ channels that are configured in CR26
and CR27.
CR23
CR23 can only be accessed in the configuration state and after the CSR has been initialized to 23H.
CR23 is used to select the base address of the parallel port. If EPP is not enabled, the parallel port can
be set to 192 locations on 4-byte boundaries from 100H - 3FCH; if EPP is enabled, the parallel port can
be set to 96 locations on 8-byte boundaries from 100H - 3F8H. To disable the parallel port, set ADR9
and ADR8 to zero.
Parallel Port Address Decoding: address bits A[15:10] must be `000000' to access the Parallel Port
when in Compatible, Bi-directional, or EPP modes. A10 is active when in ECP mode.
1 ADR3
2 ADR4
3 ADR5
4 ADR6
5 ADR7
6 ADR8
7 ADR9
CR24 can only be accessed in the configuration state and after the CSR has been initialized to 24H.
CR24 is used to select the base address of Serial Port 1 (UART1). The serial port can be set to 96
locations on 8-byte boundaries from 100H - 3F8H. To disable Serial Port 1, set ADR9 and ADR8 to
zero. Set CR24.0 to 0 when writing the UART1 Base Address.
Serial Port 1 Address Decoding: address bits A[15:10] must be `000000' to access UART1 registers.
A[2:0] are decoded as XXXb.
2 ADR4
3 ADR5
4 ADR6
5 ADR7
6 ADR8
7 ADR9
CR25
CR25 can only be accessed in the configuration state and after the CSR has been initialized to 25H.
CR25 is used to select the base address of Serial Port 2 (UART2). Serial Port 2 can be set to 96
locations on 8-byte boundaries from 100H - 3F8H. To disable Serial Port 2, set ADR9 and ADR8 to
zero. Set CR25.0 to 0 when writing the UART2 Base Address.
Serial Port 2 Address Decoding: address bits A[15:10] must be `000000' to access UART2 registers.
A[2:0] are decoded as XXXb.
2 ADR4
3 ADR5
4 ADR6
5 ADR7
6 ADR8
7 ADR9
CR26 can only be accessed in the configuration state and after the CSR has been initialized to 26H.
CR26 is used to select the DMA for the FDC (Bits 4 - 7) and the Parallel Port (bits 0 - 3). Any unselected
DMA Request output (DRQ) is in tristate.
0001 DMA1
0010 DMA2
0011 DMA3
0100 RESERVED
....
....
1111 NONE
CR27
CR27 can only be accessed in the configuration state and after the CSR has been initialized to 27H.
CR27 is used to select the IRQ for the FDC (Bits 4 - 7) and the Parallel Port (bits 3 - 0). Any unselected
IRQ output (registers CR27 - CR29) is in tri-state.
0001 IRQ_1
0010 IRQ_2
0011 IRQ_3
0100 IRQ_4
0101 IRQ_5
0110 IRQ_6
0111 IRQ_7
1000 IRQ_8
1001 IRQ_9
1010 IRQ_10
1011 IRQ_11
1100 IRQ_12
1101 IRQ_13
1110 IRQ_14
1111 IRQ_15
CR28
CR28 can only be accessed in the configuration state and after the CSR has been initialized to 28H.
CR28 is used to select the IRQ for Serial Port 1 (bits 7 - 4) and for Serial Port 2 (bits 3 - 0). Refer to the
IRQ encoding for CR27 (Table 90). Any unselected IRQ output (registers CR27 - CR29) is in tristate.
Shared IRQs are not supported in the LPC47N227.
encoding for CR27 (Table 90).
encoding for CR27 (Table 90).
