Xilinx UG194 Virtex-5 FPGA Embedded Tri-Mode Ethernet MAC ...

More documents

Recommendations

Info

Chapter 1: Introduction Preamble For transmission, this field is automatically inserted by the Ethernet MAC. The preamble field was historically used for synchronization and contains seven bytes with the pattern 0x55, transmitted from left to right. For reception, this field is always stripped from the incoming frame, before the data is passed to the client. The Ethernet MAC can receive Ethernet frames, even if the preamble does not exist, as long as a valid start of frame is available. Start of Frame Delimiter The start of frame delimiter field marks the start of the frame and must contain the pattern 0xD5. For transmission on the physical interface, this field is automatically inserted by the Ethernet MAC. For reception, this field is always stripped from the incoming frame before the data is passed to the client. Destination Address The least significant bit of the destination address determines if the address is an individual/unicast (0) or group/multicast (1) address. Multicast addresses are used to group logically related stations. The broadcast address (destination address field is all 1s) is a multicast address that addresses all stations on the LAN. The Ethernet MAC supports transmission and reception of unicast, multicast, and broadcast packets. This field is the first field of the Ethernet frame that is always provided in the packet data for transmissions and is always retained in the receive packet data. Source Address For transmission, the source address of the Ethernet frame should be provided by the client because it is unmodified by the Ethernet MAC. The unicast address for the Ethernet MAC is used as the source address when the Ethernet MAC creates pause control frames. The source address field is always retained in the receive packet data. Length/Type The value of this field determines if it is interpreted as a length or a type field, as defined by the IEEE 802.3 standard. A value of 1536 decimal or greater is interpreted by the Ethernet MAC as a type field. When used as a length field, the value in this field represents the number of bytes in the following data field. This value does not include any bytes that can be inserted in the pad field following the data field. A length/type field value of 0x8100 hex indicates that the frame is a VLAN frame, and a value of 0x8808 hex indicates a pause MAC control frame. For transmission, the Ethernet MAC does not perform any processing of the length/type field. For reception, if this field is a length field, the Ethernet MAC receive engine interprets this value and removes any padding in the pad field (if necessary). If the field is a length field and length/type checking is enabled, the Ethernet MAC compares the length against the actual data field length and flags an error if a mismatch occurs. If the field is a type field, the Ethernet MAC ignores the value and passes it along with the packet data with no further processing. The length/type field is always retained in the receive packet data. 22 www.xilinx.com TEMAC User Guide UG194 (v1.10) February 14, 2011 R
R Data Pad FCS Ethernet Protocol Overview The data field can vary from 0 to 1500 bytes in length for a normal frame. The Ethernet MAC can handle jumbo frames of any length. This field is always provided in the packet data for transmissions and is always retained in the receive packet data. The pad field can vary from 0 to 46 bytes in length. This field is used to ensure that the frame length is at least 64 bytes in length (the preamble and SFD fields are not considered part of the frame for this calculation), which is required for successful CSMA/CD operation. The values in this field are used in the frame check sequence calculation but are not included in the length field value, if it is used. The length of this field and the data field combined must be at least 46 bytes. If the data field contains 0 bytes, the pad field is 46 bytes. If the data field is 46 bytes or more, the pad field has 0 bytes. For transmission, this field can be inserted automatically by the Ethernet MAC or can be supplied by the client. If the pad field is inserted by the Ethernet MAC, the FCS field is calculated and inserted by the Ethernet MAC. If the pad field is supplied by the client, the FCS can be either inserted by the Ethernet MAC or provided by the client, as indicated by a configuration register bit. For reception, if the length/type field has a length interpretation, any pad field in the incoming frame is not be passed to the client, unless the Ethernet MAC is configured to pass the FCS field on to the client. The value of the FCS field is calculated over the destination address, source address, length/type, data, and pad fields using a 32-bit Cyclic Redundancy Check (CRC), as defined in IEEE Std 802.3-2002 para. 3.2.8: G(x) = x32 + x26 + x23 + x22 + x16 + x12 + x11 + x10 + x8 + x7 + x5 + x4 + x2 + x1 + x0 The CRC bits are placed in the FCS field with the x31 term in the left-most bit of the first byte, and the x0 term is the right-most bit of the last byte (i.e., the bits of the CRC are transmitted in the order x31 , x30 ,..., x1 , x0 ). For transmission, this field can be either inserted automatically by the Ethernet MAC or supplied by the client, as indicated by a configuration register bit. For reception, the incoming FCS value is verified on every frame. If an incorrect FCS value is received, the Ethernet MAC indicates to the client that it has received a bad frame. The FCS field can either be passed on to the client or be dropped by the Ethernet MAC, as indicated by a configuration register bit. Frame Transmission and Interframe Gap Frames are transmitted over the Ethernet medium with an interframe gap, as specified by IEEE Std 802.3. For full-duplex systems, the minimum IFG is 96 bit times (9.6 µs for 10 Mb/s, 0.96 µs for 100 Mb/s, and 96 ns for 1 Gb/s). For half-duplex systems, the minimum IFG is 208 bit times and 144 bit times for RGMII and MII respectively. The defined IFG is a minimum and can be increased with a resulting decrease in throughput. The process for frame transmission is different for half-duplex and full-duplex systems. TEMAC User Guide www.xilinx.com 23 UG194 (v1.10) February 14, 2011
Page 1 and 2: Virtex-5 FPGA Embedded Tri-Mode Eth
Page 3 and 4: Date Version Revision 08/08/07 (con
Page 5 and 6: Date Version Revision 10/01/09 1.9
Page 7 and 8: Table of Contents Guide Contents .
Page 9 and 10: R Chapter 5: MDIO Interface Introdu
Page 11 and 12: R About This Guide Guide Contents P
Page 13 and 14: R Additional Support Resources User
Page 15 and 16: R Typographical Online Document Use
Page 17 and 18: Introduction Key Features R Chapter
Page 19 and 20: R Typical Ethernet Application Over
Page 21: R Number of Bytes Physical Sublayer
Page 25 and 26: R Using the Embedded Ethernet MAC T
Page 27 and 28: R Ethernet MAC Overview Chapter 2 T
Page 29 and 30: Generic Host Bus DCR Bus R Flow Con
Page 31 and 32: R Ethernet MAC Primitive Ethernet M
Page 33 and 34: R Ethernet MAC Signal Descriptions
Page 35 and 36: R Table 2-3: Receive Client Interfa
Page 37 and 38: R DCR Bus Signals Table 2-6: DCR Bu
Page 39 and 40: R Table 2-8: PHY Data and Control S
Page 41 and 42: R Table 2-12: PCS/PMA Signals Table
Page 43 and 44: R Table 2-16: Mode Configuration At
Page 45 and 46: R Table 2-17: MAC Configuration Att
Page 47 and 48: R Table 2-17: MAC Configuration Att
Page 49 and 50: R Table 2-18: Physical Interface At
Page 51 and 52: R Client Interface Chapter 3 This c
Page 53 and 54: R Normal Frame Transmission CLIENTE
Page 55 and 56: R CLIENTEMAC#TXCLIENTCLKIN CLIENTEM
Page 57 and 58: R CLIENTEMAC#TXCLIENTCLKIN CLIENTEM
Page 59 and 60: R Normal Frame Transmission PHYEMAC
Page 61 and 62: R CLIENTEMAC#TXCLIENTCLKIN PHYEMAC#
Page 63 and 64: R CLIENTEMAC#TXCLIENTCLKIN PHYEMAC#
Page 65 and 66: R Frame Reception with Errors CLIEN
Page 67 and 68: R Receive (RX) Client: 8-Bit Interf
Page 69 and 70: R Receive (RX) Client: 16-Bit Inter
Page 71 and 72: R Address Filtering Address Filteri
Page 73 and 74:
R CLIENTEMAC#RXCLIENTCLKIN Flow Con
Page 75 and 76:
R Transmitting a PAUSE Control Fram
Page 77 and 78:
R Operation Figure 3-30 illustrates
Page 79 and 80:
R Ethernet MAC Block EMAC#CLIENTTXS
Page 81 and 82:
R Table 3-3: Bit Definitions for th
Page 83 and 84:
R CLIENTEMAC#RXCLIENTCLKIN EMAC#CLI
Page 85 and 86:
R Host/DCR Bus Interfaces This chap
Page 87 and 88:
HOSTCLK HOSTMIIMSEL HOSTREQ HOSTOPC
Page 89 and 90:
R Table 4-3: Receiver Configuration
Page 91 and 92:
R Table 4-5: Flow Control Configura
Page 93 and 94:
R Table 4-7: RGMII/SGMII Configurat
Page 95 and 96:
R Table 4-9: Unicast Address (Word
Page 97 and 98:
R Table 4-13: Address Filter Mode 0
Page 99 and 100:
R HOSTCLK HOSTMIIMSEL HOSTOPCODE[1]
Page 101 and 102:
R HOSTCLK HOSTMIIMSEL HOSTREQ HOSTO
Page 103 and 104:
R Using the DCR Bus The directly ad
Page 105 and 106:
R Table 4-18: DCR Control Register
Page 107 and 108:
R Using the DCR Bus The IRENABLE_e#
Page 109 and 110:
R // Write to the cntlReg_e1 regist
Page 111 and 112:
DCR Offset 0x1 MSB R Using the DCR
Page 113 and 114:
R Using the DCR Bus // EMAC Managem
Page 115 and 116:
R MDIO Interface Chapter 5 This cha
Page 117 and 118:
MDC MDIO R MDIO Transactions Introd
Page 119 and 120:
R MDIO Implementation in the Ethern
Page 121 and 122:
Generic Host Bus DCR Bus R PHYEMAC#
Page 123 and 124:
R 1000BASE-X PCS/PMA Management Reg
Page 125 and 126:
R Table 5-4: Status Register (Regis
Page 127 and 128:
R 1000BASE-X PCS/PMA Management Reg
Page 129 and 130:
R Table 5-13: Vendor-Specific Regis
Page 131 and 132:
R 2, 3 “PHY Identifier (Registers
Page 133 and 134:
1.2 SGMII Link Status R Table 5-16:
Page 135 and 136:
R Table 5-22: SGMII Auto-Negotiatio
Page 137 and 138:
R Physical Interface Chapter 6 This
Page 139 and 140:
R GMII / MII RGMII SGMII Introducti
Page 141 and 142:
TX CLIENT LOGIC RX CLIENT LOGIC R M
Page 143 and 144:
R Gigabit Media Independent Interfa
Page 145 and 146:
GTX_CLK R IBUFG TX CLIENT LOGIC RX
Page 147 and 148:
GTX_CLK R IBUFG BUFG TX Client Logi
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
R Reduced Gigabit Media Independent
Page 155 and 156:
Page 157 and 158:
GTX_CLK TX Client Logic RX Client L
Page 159 and 160:
GTX_CLK TX Client Logic RX Client L
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
FPGA R PCS/PMA Sublayer MAC TX Inte
Page 167 and 168:
R Ethernet MAC to RocketIO Serial T
Page 169 and 170:
TX and RX Client Logic R 1000BASE-X
Page 171 and 172:
R 1000BASE-X PCS/PMA REFCLKOUT outp
Page 173 and 174:
R DCM BUFG CLKFB CLK0 CLKIN CLKFX B
Page 175 and 176:
R 1000BASE-X PCS/PMA IEEE Std 802.3
Page 177 and 178:
R 1000BASE-X PCS/PMA Ethernet MAC.
Page 179 and 180:
FPGA R Introduction to the SGMII Im
Page 181 and 182:
R RX Elastic Buffer Implementations
Page 183 and 184:
R Serial Gigabit Media Independent
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
R Ethernet MAC (PCS/PMA Sublayer) E
Page 191 and 192:
TX and RX Client Logic R SGMII Cloc
Page 193 and 194:
Page 195 and 196:
DCM CLKFB CLK0 CLKIN CLKDV CLKDV_DI
Page 197 and 198:
Page 199 and 200:
R Interfacing to a Statistics Block
Page 201 and 202:
R Using the DCR Bus to Access Stati
Page 203 and 204:
R Pinout Guidelines Appendix A Xili
Page 205 and 206:
R Ethernet MAC Clocks Appendix B Th
Page 207 and 208:
TX Client Logic RX Client Logic R
Page 209 and 210:
R Clock Enables Clock Connections t
Page 211 and 212:
R Receiver Clock Clock Definitions
Page 213 and 214:
R GMII (Byte PHY) Mode Clock Defini
Page 215 and 216:
R Clock Definitions and Frequencies
Page 217 and 218:
R Virtex-4 to Virtex-5 FPGA Enhance
Page 219 and 220:
R Clock Enables Modifications Relat
Page 221 and 222:
R Additional Attributes Table C-2:
Page 223 and 224:
R Appendix D Differences between So
show all

Xilinx UG194 Virtex-5 FPGA Embedded Tri-Mode Ethernet MAC ...

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

Delete template?

Save as template?