
SMSC LAN91C111
| PARAMETER | MIN | TYP | MAX | UNITS |
|
|
|
|
|
|
t11 | nCYCLE Hold after LCLK Rising | 3 |
|
| ns |
|
|
|
|
| |
|
|
|
|
|
|
t16 | W/nR Setup to nCYCLE Active | 0 |
|
| ns |
|
|
|
|
|
|
t20 | Data Hold from LCLK Rising | 4 |
|
| ns |
| (Read) |
|
|
|
|
|
|
|
|
|
|
t21 | nSRDY Delay from LCLK Rising |
|
| 7 | ns |
|
|
|
|
|
|
t23 | nRDYRTN Setup to LCLK Rising | 3 |
|
| ns |
|
|
|
|
|
|
t24 | nRDYRTN Hold after LCLK Rising | 3 |
|
| ns |
|
|
|
|
|
|
3.6.4Read Cycle Address Phase – Cycle Start
As with the Write Cycle, the Address Bus, AEN, and the Byte Enable lines
3.6.5Read Cycle Delay Phase
Unlike the Write Cycle, there is a delay required during read operations to allow the LAN91C111 to fetch the required data. This phase occurs immediately after the address phase and is completed in one LCLK cycle. During this time the Data Bus is not required to be stable, nor is the address bus.
3.6.6Read Cycle Data Phase – Cycle End
As the timing diagram represents, the read data is presented from the LAN91C111 on the data bus and it is guaranteed to be stable at the rising edge when nSRDY (translated to nLRDY for the
3.6.7VL-Burst Mode Operation
Burst Mode operations as defined by the VESA standard are not supported by the LAN91C111 device in
3.7Direct Data Register Access interface (nDATACS)
Another option available for design engineers to connect to the LAN91C111 is through a direct interface. This interface is controlled using the nDATACS pin and allows a designer to connect a controller directly to the LAN91C111 Data Register by bypassing the internal BIU decoders. This section will discuss in some detail the information necessary to accomplish this interface. This interface is always
The LAN91C111 offers the design engineer several options as to how this mode of operation can be implemented. The choices are between synchronous and asynchronous, burst and
Revision 1.0 | 14 | SMSC AN 9.6 |
APPLICATION NOTE