Write Sequence of Operation
1) The host selects an EPP register, places data on the SData bus and drives nIOW active.
2) The chip drives IOCHRDY inactive (low).
3) If WAIT is not asserted, the chip must wait until WAIT is asserted.
4) The chip places address or data on PData bus, clears PDIR, and asserts nWRITE.
5) Chip asserts nDATASTB or nADDRSTRB indicating that PData bus contains valid information, and the WRITE
signal is valid.
6) Peripheral deasserts nWAIT, indicating that any setup requirements have been satisfied and the chip may
begin the termination phase of the cycle.
7) A) The chip deasserts nDATASTB or nADDRSTRB, this marks the beginning of the termination
phase.
If it has not already done so, the
peripheral should latch the information byte now.
B) The chip latches the data from the SData bus for the PData bus and asserts (releases) IOCHRDY allowing
the host to complete the write cycle.
8) Peripheral asserts nWAIT, indicating to the host that any hold time requirements have been satisfied and
acknowledging the termination of the cycle.
9) Chip may modify nWRITE and nPDATA in preparation for the next cycle.
EPP 1.9 READ
The timing for a read operation (data) is shown in timing diagram EPP Read Data cycle. IOCHRDY is driven active
low at the start of each EPP read and is released when 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 complete
when nWAIT goes inactive high.
2) If the EPP bus is ready (nWAIT is inactive high) then the chip must wait for it to go active low before changing
the state of WRITE or before nDATASTB goes active. The read can complete once nWAIT is determined
inactive.
Read Sequence of Operation
1) The host selects an EPP register and drives nIOR active.
2) The chip drives IOCHRDY inactive (low).
3) If WAIT is not asserted, the chip must wait until WAIT is asserted.
4) The chip tri-states the PData bus and deasserts nWRITE.
5) Chip asserts nDATASTB or nADDRSTRB indicating that PData bus is tri-stated, PDIR is set and the nWRITE
signal is valid.
6) Peripheral drives PData bus valid.
7) Peripheral deasserts nWAIT, indicating that PData is valid and the chip may begin the termination phase of
the cycle.
8) A) The chip latches the data from the PData bus for the SData bus, deasserts
nADDRSTRB, this marks the beginning of the termination phase.
DATASTB or
B) The chip drives the valid data onto the SData bus and asserts (releases) IOCHRDY allowing the host to
complete the read cycle.
9) Peripheral tri-states the PData bus and asserts nWAIT, indicating to the host that the PData bus is tri-stated.
10) Chip may modify nWRITE, PDIR and nPDATA in preparation for the next cycle.
SMSC DS – FDC37N3869
Page 74
Rev. 10/25/2000
SMSC [ SMSC CORPORATION ]
