09.12.2012 Views

RM0090: Reference manual - STMicroelectronics

RM0090: Reference manual - STMicroelectronics

RM0090: Reference manual - STMicroelectronics

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>RM0090</strong> Ethernet (ETH): media access control (MAC) with DMA controller<br />

Figure 329. Address field format<br />

MSB 46-bit address U/L I/G LSB<br />

Bit transmission order (right to left)<br />

I/G = 0 Individual address<br />

I/G = 1 Group address<br />

U/L = 0 Globally administered address<br />

U/L = 1 Locally administered address<br />

ai15628<br />

● QTag Prefix: 4-byte field inserted between the Source address field and the MAC Client<br />

Length/Type field. This field is an extension of the basic frame (untagged) to obtain the<br />

tagged MAC frame. The untagged MAC frames do not include this field. The extensions<br />

for tagging are as follows:<br />

– 2-byte constant Length/Type field value consistent with the Type interpretation<br />

(greater than 0x0600) equal to the value of the 802.1Q Tag Protocol Type (0x8100<br />

hexadecimal). This constant field is used to distinguish tagged and untagged MAC<br />

frames.<br />

– 2-byte field containing the Tag control information field subdivided as follows: a 3bit<br />

user priority, a canonical format indicator (CFI) bit and a 12-bit VLAN Identifier.<br />

The length of the tagged MAC frame is extended by 4 bytes by the QTag Prefix.<br />

● MAC client length/type: 2-byte field with different meaning (mutually exclusive),<br />

depending on its value:<br />

– If the value is less than or equal to maxValidFrame (0d1500) then this field<br />

indicates the number of MAC client data bytes contained in the subsequent data<br />

field of the 802.3 frame (length interpretation).<br />

– If the value is greater than or equal to MinTypeValue (0d1536 decimal, 0x0600)<br />

then this field indicates the nature of the MAC client protocol (Type interpretation)<br />

related to the Ethernet frame.<br />

Regardless of the interpretation of the length/type field, if the length of the data field is<br />

less than the minimum required for proper operation of the protocol, a PAD field is<br />

added after the data field but prior to the FCS (frame check sequence) field. The<br />

length/type field is transmitted and received with the higher-order byte first.<br />

For length/type field values in the range between maxValidLength and minTypeValue<br />

(boundaries excluded), the behavior of the MAC sublayer is not specified: they may or<br />

may not be passed by the MAC sublayer.<br />

● Data and PAD fields: n-byte data field. Full data transparency is provided, it means that<br />

any arbitrary sequence of byte values may appear in the data field. The size of the PAD,<br />

if any, is determined by the size of the data field. Max and min length of the data and<br />

PAD field are:<br />

– Maximum length = 1500 bytes<br />

– Minimum length for untagged MAC frames = 46 bytes<br />

– Minimum length for tagged MAC frames = 42 bytes<br />

When the data field length is less than the minimum required, the PAD field is added to<br />

match the minimum length (42 bytes for tagged frames, 46 bytes for untagged frames).<br />

● Frame check sequence: 4-byte field that contains the cyclic redundancy check (CRC)<br />

value. The CRC computation is based on the following fields: source address,<br />

Doc ID 018909 Rev 3 912/1416

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!