FDC37B727-NS Standard Microsystems (SMSC), FDC37B727-NS Datasheet - Page 36

• Manufacturer Part Number: FDC37B727-NS
• Manufacturer: Standard Microsystems (SMSC)

Specifications of FDC37B727-NS

• Pin Count: 128
• Lead Free Status / RoHS Status: Compliant

Non-DMA Mode - Transfers from the Host to the
FIFO
The FINT pin 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 FINT pin 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 FINT pin will also be deactivated if
TC and nDACK both go inactive. 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 activates the DDRQ pin 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 must respond to the
request by reading data from the FIFO. The FDC
will deactivate the DDRQ pin when the FIFO
becomes empty.
nDACK goes active for the last byte of a data
transfer (or on the active edge of nIOR, on the last
byte, if no edge is present on nDACK). A data
underrun may occur if FDRQ is not removed in
time to prevent an unwanted cycle.
DMA Mode - Transfers from the Host to the FIFO.
The FDC activates the FDRQ pin when entering
the execution phase of
FDRQ goes inactive after
the data transfer
36
commands. The DMA controller must respond by
activating the nDACK and nIOW pins and placing
data in the FIFO. FDRQ remains active until the
FIFO becomes full. FDRQ is again set true when
the FIFO has <threshold> bytes remaining in the
FIFO. The FDC will also deactivate the FDRQ pin
when TC becomes true (qualified by nDACK),
indicating that no more data is required. FDRQ
goes inactive after nDACK goes active for the last
byte of a data transfer (or on the active edge of
nIOW of the last byte, if no edge is present on
nDACK). A data overrun may occur if FDRQ is
not removed in time to prevent an unwanted cycle.
Data Transfer Termination
The FDC supports terminal count explicitly through
the
underrun/overrun
functions.
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 hardware TC was
received.
implicit functions and TC 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.
TC
pin
The only difference between these
For full sector transfers, the EOT
and
and
implicitly
end-of-track
through
(EOT)
the