LAN9115_08 datasheet(52/136 Pages) SMSC

Part #	LAN9115

Description	Highly Efficient Single-Chip 10/100 Non-PCI Ethernet Controller

Download	136 Pages

Scroll/Zoom	100%

Manufacturer	SMSC [SMSC Corporation]

Direct Link	http://www.smsc.com

Logo

52 / 136 page

Highly Efficient Single-Chip 10/100 Non-PCI Ethernet Controller

Datasheet

Revision 1.5 (07-11-08)

52

SMSC LAN9115

DATASHEET

The MIL operates in store-and-forward mode and has specific rules with respect to fragmented

packets. The total space consumed in the TX FIFO (MIL) must be limited to no more than 2KB - 3

DWORDs (2,036 bytes total). Any transmit packet that is so highly fragmented that it takes more space

than this must be un-fragmented (by copying to a Driver-supplied buffer) before the transmit packet

can be sent to the LAN9115.

One approach to determine whether a packet is too fragmented is to calculate the actual amount of

space that it will consume, and check it against 2,036 bytes. Another approach is to check the number

of buffers against a worst-case limit of 86 (see explanation below).

3.13.3.2

Calculating Worst-Case TX FIFO (MIL) Usage

The actual space consumed by a buffer consists only of any partial DWORD offsets in the first/last

DWORD of the buffer, plus all of the whole DWORDs in between. Any whole DWORD offsets and/or

alignments are stripped off before the buffer even gets into the TX data FIFO, and TX command words

are stripped off before the buffer is written to the TX FIFO, so none of those DWORDs count as space

consumed. The worst-case overhead for a TX buffer is 6 bytes, which assumes that it started on the

high byte of a DWORD and ended on the low byte of a DWORD. A TX packet consisting of 86 such

fragments would have an overhead of 516 bytes (6 * 86) which, when added to a 1514-byte max-size

transmit packet (1516 bytes, rounded up to the next whole DWORD), would give a total space

consumption of 2,032 bytes, leaving 4 bytes to spare; this is the basis for the "86 fragment" rule

mentioned above.

3.13.4

TX Status Format

TX status is passed to the host CPU through a separate FIFO mechanism. A status word is returned

for each packet transmitted. Data transmission is suspended if the TX status FIFO becomes full. Data

transmission will resume when the host reads the TX status and there is room in the FIFO for more

“TX Status” data.

The host can optionally choose to not read the TX status. The host can optionally ignore the TX status

by setting the “TX Status Discard Allow Overrun Enable” (TXSAO) bit in the TX Configuration Register

(TX_CFG). If this option is chosen TX status will not be written to the FIFO. Setting this bit high allows

the transmitter to continue operation with a full TX status FIFO. In this mode the status information is

still available in the TX status FIFO, and TX status interrupts still function. In the case of an overrun,

the TXSUSED counter will stay at zero and no further TX status will be written to the TX status FIFO

until the host frees space by reading TX status. If TXSAO is enabled, a TXE error will not be generated

if the TX status FIFO overruns. In this mode the host is responsible for re-synchronizing TX status in

the case of an overrun.

BITS

DESCRIPTION

31:16

Packet TAG. Unique identifier written by the host into the Packet Tag field of the TX command ‘B’

word. This field can be used by the host to correlate TX status words with the associated TX packets.

15

Error Status (ES). ). When set, this bit indicates that the Ethernet controller has reported an error.

This bit is the logical OR of bits 11, 10, 9, 8, 2, 1 in this status word.

14:12

Reserved. These bits are reserved. Always write zeros to this field to guarantee future compatibility.

11

Loss of Carrier. When set, this bit indicates the loss of carrier during transmission.

10

No Carrier. When set, this bit indicates that the carrier signal from the transceiver was not present

during transmission.

9

Late Collision. When set, indicates that the packet transmission was aborted after the collision

window of 64 bytes.

8

Excessive Collisions. When set, this bit indicates that the transmission was aborted after 16

collisions while attempting to transmit the current packet.

Similar Part No. - LAN9115_08

Manufacturer	Part #	Datasheet	Description
SMSC Corporation	LAN9115	1Mb / 131P	Highly Efficient Single- Chip 10/100 Non-PCI Ethernet Controller

More results

Similar Description - LAN9115_08

Manufacturer	Part #	Datasheet	Description
Microchip Technology	LAN9116	1,016Kb / 109P	Highly Efficient Single-Chip 10/100 Non-PCI Ethernet Controller 06/23/16
SMSC Corporation	LAN9115	219Kb / 7P	HIGHLY EFFICIENT SINGLE - CHIP 10/100 NON PCI ETHERNET CONTROLLER
	LAN9116	1Mb / 132P	Highly Efficient Single-Chip 10/100 Non-PCI Ethernet Controller
	LAN9116	1Mb / 126P	Highly Efficient Single-Chip 10/100 Non-PCI Ethernet Controller
	LAN9115	1Mb / 131P	Highly Efficient Single- Chip 10/100 Non-PCI Ethernet Controller
Microchip Technology	LAN9115	1Mb / 114P	Highly Efficient Single-Chip 10/100 Non-PCI Ethernet Controller 06/23/16
SMSC Corporation	LAN9117	1Mb / 136P	High Performance Single-Chip 10/100 Non-PCI Ethernet Controller
SMSC Corporation	LAN9118	1Mb / 129P	High Performance Single-Chip 10/100 Non-PCI Ethernet Controller
Microchip Technology	LAN9118	1,015Kb / 109P	High Performance Single-Chip 10/100 Non-PCI Ethernet Controller 06/23/16
Microchip Technology	LAN9117	1Mb / 114P	High Performance Single-Chip 10/100 Non-PCI Ethernet Controller 06/23/16

More results

LAN9115 Datasheet(PDF) 52 Page - SMSC Corporation

LAN9115 Datasheet(HTML) 52 Page - SMSC Corporation

Similar Part No. - LAN9115_08

Similar Description - LAN9115_08

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

Datasheet Download

Link URL