LAN9220 datasheet(44/142 Pages) MICROCHIP

44 / 142 page

LAN9220

DS00002417A-page 44

 2006-2017 Microchip Technology Inc.

3.12.2.2

TX Command ‘B’

3.12.3

TX DATA FORMAT

The TX data section begins at the third DWORD in the TX buffer (after TX command ‘A’ and TX command ‘B’). The

location of the first byte of valid buffer data to be transmitted is specified in the “Data Start Offset” field of the TX com-

mand ‘A’ word. Table 3-14, "TX DATA Start Offset", shows the correlation between the setting of the LSB’s in the “Data

Start Offset” field and the byte location of the first valid data byte. Additionally, transmit buffer data can be offset by up

to 7 additional DWORDS as indicated by the upper three MSB’s (5:2) in the “Data Start Offset” field.

TX data is contiguous until the end of the buffer. The buffer may end on a byte boundary. Unused bytes at the end of

the packet will not be sent to the MIL for transmission.

The Buffer End Alignment field in TX command ‘A’ specifies the alignment that must be maintained for the associated

buffer. End alignment may be specified as 4-, 16-, or 32-byte. The host processor is responsible for adding the additional

data to the end of the buffer. The hardware will automatically remove this extra data.

3.12.3.1

TX Buffer Fragmentation Rules

Transmit buffers must adhere to the following rules:

• Each buffer can start and end on any arbitrary byte alignment

• The first buffer of any transmit packet can be any length

• Middle buffers (i.e., those with First Segment = Last Segment = 0) must be greater than, or equal to 4 bytes in

length

• The final buffer of any transmit packet can be any length

TABLE 3-13:

TX COMMAND 'B' FORMAT

Bits

Description

31:16

Packet Tag. The host should write a unique packet identifier to this field. This identifier is added to

the corresponding TX status word and can be used by the host to correlate TX status words with

their corresponding packets.

Note:

The use of packet tags is not required by the hardware. This field can be used by the LAN

software driver for any application. Packet Tags is one application example.

Reserved. This bit is reserved. Always write zeros to this bit to provide future compatibility.

TX Checksum Enable (CK). When this bit is set in conjunction with the first segment (FS) bit in TX

Command ‘A’ and the TX checksum offload engine enable bit (TXCOE_EN) in the COE_CR—

Checksum Offload Engine Control Register, the TX checksum offload engine (TXCOE) will calculate

a L3 checksum for the associated frame.

Add CRC Disable. When set, the automatic addition of the CRC is disabled.

Disable Ethernet Frame Padding. When set, this bit prevents the automatic addition of padding to

an Ethernet frame of less than 64 bytes. The CRC field is also added despite the state of the Add

CRC Disable field.

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

10:0

Packet Length (bytes). This field indicates the total number of bytes in the current packet. This

length does not include the offset or padding. If the Packet Length field does not match the actual

number of bytes in the packet the Transmitter Error (TXE) flag will be set.

TABLE 3-14:

TX DATA START OFFSET

Data Start Offset [1:0]:

First TX Data Byte:

D[31:24]

D[23:16]

D[15:8]

D[7:0]

LAN9220 датащи(PDF) 44 Page - Microchip Technology

LAN9220 датащи(HTML) 44 Page - Microchip Technology

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

датащи скачать

ссылки URL