EVB9311 SMSC, EVB9311 Datasheet - Page 123

• Manufacturer Part Number: EVB9311
• Description: EVALUATION BOARD LAN9311-NU
• Manufacturer: SMSC
• Series: 0133r

Specifications of EVB9311

• Main Purpose: Interface, Ethernet
• Embedded: No
• Utilized Ic / Part: LAN9311
• Primary Attributes: 2 Ports, 100BASE-TX/10BASE-T, Managed
• Secondary Attributes: 2 PHYs with HP Auto-MDIX, Auto- Flow Control, 32-bit CRC, MDI/MDI-X
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Other names: 638-1076

Two Port 10/100 Managed Ethernet Switch with 16-Bit Non-PCI CPU Interface
Datasheet
SMSC LAN9311/LAN9311i
9.8
TX_FIF_SZ
10
11
12
13
14
2
3
4
5
6
7
8
9
Data is queued for transmission by writing it into the TX Data FIFO. Each packet to be transmitted
may be divided among multiple buffers. Each buffer starts with a two DWORD TX command (TX
command ‘A’ and TX command ‘B’). The TX command instructs the LAN9311/LAN9311i on the
handling of the associated buffer. Packet boundaries are delineated using control bits within the TX
command.
The host provides a 16-bit Packet Tag field in the TX command. The Packet Tag value is appended
to the corresponding TX status DWORD. All Packet Tag fields must have the same value for all buffers
in a given packet. If tags differ between buffers in the same packet the TXE error will be asserted. Any
value may be chosen for a Packet Tag as long as all tags in the same Packet are identical. Packet
Tags also provide a method of synchronization between transmitted packets and their associated
status. Software can use unique Packet Tags to assist with validating matching status completions.
Note: The use of Packet Tags is not required by the hardware. This field can be used by the LAN
The Packet Length field in the TX command specifies the number of bytes in the associated packet.
All Packet Length fields must have the same value for all buffers in a given packet. Hardware
compares the Packet Length field and the actual amount of data received by the Ethernet controller.
If the actual packet length count does not match the Packet Length field as defined in the TX
command, the Transmitter Error (TXE) flag is asserted.
The LAN9311/LAN9311i can be programmed to start payload transmission of a buffer on a byte
boundary by setting the “Data Start Offset” field in the TX command. The “Data Start Offset” field points
to the actual start of the payload data within the first 8 DWORDs of the buffer. Data before the “Data
Start Offset” pointer will be ignored. When a packet is split into multiple buffers, each successive buffer
may begin on any arbitrary byte.
TX Data Path Operation
software driver for any application. Packet Tags is only one application example.
TX DATA FIFO
SIZE (BYTES)
10752
11776
12800
13824
1536
2560
3584
4608
5632
6656
7680
8704
9728
Table 9.9 Valid TX/RX FIFO Allocations
TX STATUS FIFO
DATASHEET
SIZE (BYTES)
512
512
512
512
512
512
512
512
512
512
512
512
512
123
RX DATA FIFO
SIZE (BYTES)
13440
12480
10560
11520
9600
8640
7680
6720
5760
4800
3840
2880
1920
RX STATUS FIFO
Revision 1.7 (06-29-10)
SIZE (BYTES)
896
832
768
704
640
576
512
448
384
320
256
192
128