LAN9215-MT SMSC, LAN9215-MT Datasheet - Page 119
![CONTROLLER, ENET, NON-PCI, 100TQFP](/photos/19/0/190054/42334689_sml.jpg)
LAN9215-MT
Manufacturer Part Number
LAN9215-MT
Description
CONTROLLER, ENET, NON-PCI, 100TQFP
Manufacturer
SMSC
Specifications of LAN9215-MT
Data Rate
100Mbps
No. Of Ports
2
Ethernet Type
IEEE 802.3 / 802.3u
Supply Current
40mA
Supply Voltage Range
2.97V To 3.63V
Operating Temperature Range
0°C To +70°C
Digital Ic Case Style
TQFP
Interface Type
HBI
Rohs Compliant
Yes
Lead Free Status / RoHS Status
Lead free / RoHS Compliant
Available stocks
Company
Part Number
Manufacturer
Quantity
Price
Company:
Part Number:
LAN9215-MT
Manufacturer:
BROADCOM
Quantity:
450
Company:
Part Number:
LAN9215-MT
Manufacturer:
Standard
Quantity:
1 643
Company:
Part Number:
LAN9215-MT
Manufacturer:
SMSC
Quantity:
9
Part Number:
LAN9215-MT
Manufacturer:
SMSC
Quantity:
20 000
Highly Efficient 10/100 Ethernet Controller with HP Auto-MDIX
Chapter 6 Timing Diagrams
SMSC LAN9215
6.1
6.1.1
Read Cycles:
Write Cycles:
The LAN9215 supports the following host cycles:
Special Restrictions on Back-to-Back Write/Read Cycles
It is important to note that there are specific restrictions on the timing of back-to-back write-read
operations. These restrictions concern reading the control registers after any write cycle to the
LAN9215 device. In many cases there is a required minimum delay between writing to the LAN9215,
and the subsequent side effect (change in the control register value). For example, when writing to the
TX Data FIFO, it takes up to 135ns for the level indication to change in the TX_FIFO_INF register.
In order to prevent the host from reading stale data after a write operation, minimum wait periods must
be enforced. These periods are specified in
processor is required to wait the specified period of time after any write to the LAN9215 before reading
the resource specified in the table. These wait periods are for read operations that immediately follow
any write cycle. Note that the required wait period is dependant upon the register being read after the
write.
Performing "dummy" reads of the BYTE_TEST register is a convenient way to guarantee that the
minimum write-to-read timing restriction is met.
are required before reading the register indicated. The number of BYTE_TEST reads in this table is
based on the minimum timing for Tcycle (165ns). For microprocessors with slower busses the number
of reads may be reduced as long as the total time is equal to, or greater than the time specified in the
table. Note that dummy reads of the BYTE_TEST register are not required as long as the minimum
time period is met.
Host Interface Timing
PIO Reads (nCS or nRD controlled)
PIO Burst Reads (nCS or nRD controlled)
RX Data FIFO Direct PIO Reads (nCS or nRD controlled)
RX Data FIFO Direct PIO Burst Reads (nCS or nRD controlled)
PIO writes (nCS and nWR controlled)
TX Data FIFO direct PIO writes (nCS or nWR controlled)
DATASHEET
119
Table 6.1, "Read After Write Timing
Table 6.1
also shows the number of dummy reads that
Revision 1.2 (03-29-06)
Rules". The host