DP83916 datasheet(12/96 Pages) NSC

12 / 96 page

20 TransmitReceive IEEE 8023 Frame Format (Continued)

ets from reaching a node There are three types of address

formats supported by the SONIC-16 Physical Multicast

and Broadcast

Physical Address

The physical address is a unique ad-

dress that corresponds only to a single node All physical

addresses have the LSB of the first byte of the address set

to ‘‘0’’ These addresses are compared to the internally

stored CAM (Content Addressable Memory) address en-

tries All bits in the destination address must match an entry

in the CAM in order for the SONIC-16 to accept the packet

Multicast Address

Multicast addresses which have the

LSB of the first byte of the address set to ‘‘1’’ are treated

similarly as Physical addresses ie

they must match an

entry in the CAM This allows perfect filtering of Multicast

packet’s and eliminates the need for a hashing algorithm for

mapping Multicast packets

Broadcast Address

If the address consists of all 1’s it is a

Broadcast address indicating that the packet is intended for

all nodes

The SONIC-16 also provides a promiscuous mode which

allows reception of all physical address packets Physical

Multicast Broadcast and promiscuous address modes can

be selected via the Receive Control register

23 SOURCE ADDRESS

The source address is the physical address of the sending

node Source addresses cannot be multicast or broadcast

addresses This field must be passed to the SONIC-16’s

transmit buffer from the system software During transmis-

sion the SONIC-16 compares the Source address with its

internal CAM address entries before monitoring the CRC of

the self-received packet If the source address of the packet

transmitted does not match a value in the CAM the packet

monitored bad flag (PMB) will be set in the transmit status

field of the transmit descriptor (see Sections 3512 and

434) The SONIC-16 does not provide Source Address in-

sertion However a transmit descriptor fragment containing

only the Source Address may be created for each packet

(See Section 351)

24 LENGTHTYPE FIELD

For IEEE 8023 type packets this field indicates the number

of bytes that are contained in the data field of the packet

For Ethernet I and II networks this field indicates the type of

packet The SONIC-16 does not operate on this field

25 DATA FIELD

The data field has a variable octet length ranging from 46 to

1500 bytes as defined by the Ethernet specification Mes-

sages longer than 1500 bytes need to be broken into multi-

ple packets for IEEE 8023 networks Data fields shorter

than 46 bytes require appending a pad to bring the com-

plete frame length to 64 bytes If the data field is padded

the number of valid bytes are indicated in the length field

The SONIC-16 does not append pad bytes for short packets

during transmission nor check for oversize packets during

reception However the user’s driver software can easily

append the pad by lengthening the TXpktpkt

size field

and TXpktfrag

size field(s) to at least 64 bytes (see Sec-

tion 351) While the Ethernet specification defines the

maximum number of bytes in the data field the SONIC-16

can transmit and receive packets up to 64k bytes

26 FCS FIELD

The Frame Check Sequence (FCS) is a 32-bit CRC field

calculated and appended to a packet during transmission to

allow detection of error-free packets During reception an

error-free packet results in a specific pattern in the CRC

generator The AUTODIN II (X32 a X26 a X23 a X22 a

X16 a X12 a X11 a X10 a X8 a X7 a X5 a X4 a

X2 a X1 a 1) polynomial is used for the CRC calculations

The SONIC-16 may optionally append the CRC sequence

during transmission and checks the CRC both during nor-

mal reception and self-reception during a transmission (see

Section 121)

27 MAC (MEDIA ACCESS CONTROL) CONFORMANCE

The SONIC-16 is designed to be compliant to the IEEE

8023 MAC Conformance specification The SONIC-16 im-

plements most of the MAC functions in silicon and provides

hooks for the user software to handle the remaining func-

tions The MAC Conformance specifications are summa-

rized in Table 2-1

TABLE 2-1 MAC Conformance Specifications

Conformance

Test Name

Support By

SONIC User Driver

Notes

-16

Software

Minimum Frame Size

Maximum Frame Size

Address Generation

Address Recognition

Pad Length Generation

Start Of Frame Delimiter

Length Field

Preamble Generation

Order of Bit Transmission

Inconsistent Frame Length

Non-Integral Octet Count

Incorrect Frame Check

Sequence

Frame Assembly

FCS Generation and Insertion

Carrier Deference

Interframe Spacing

Collision Detection

Collision Handling

Collision Backoff and

Retransmission

FCS Validation

Frame Disassembly

Back-to-Back Frames

Flow Control

Attempt Limit

Jam Size (after SFD)

Jam Size (in Preamble)

Note 1

The SONIC-16 provides the byte count of the entire packet in the

RXpktbyte

count (see Section 343) The user’s driver software may per-

form further filtering of the packet based upon the byte count

Note 2

The SONIC-16 does not provide Source Address insertion however

a transmit descriptor fragment containing only the Source Address may be

created for each packet See Section 351

Note 3

The SONIC-16 does not provide Pad generation however the us-

er’s driver software can easily append the Pad by lengthening the

TXpktpkt

size field and TXpktfrag

size field(s) to at least 64 bytes See

Section 351

DP83916 датащи(PDF) 12 Page - National Semiconductor (TI)

DP83916 датащи(HTML) 12 Page - National Semiconductor (TI)

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

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

ссылки URL