Xilinx is providing this product documentation, hereinafter “Information,” to you “AS IS” with no warranty of any kind, express or implied.
Xilinx makes no representation that the Information, or any particular implementation thereof, is free from any claims of infringement. You
are responsible for obtaining any rights you may require for any implementation based on the Information. All specifications are subject to
change without notice. XILINX EXPRESSLY DISCLAIMS ANY WARRANTY WHATSOEVER WITH RESPECT TO THE ADEQUACY OF
THE INFORMATION OR ANY IMPLEMENTATION BASED THEREON, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OR
REPRESENTATIONS THAT THIS IMPLEMENTATION IS FREE FROM CLAIMS OF INFRINGEMENT AND ANY IMPLIED WARRANTIES
OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Except as stated herein, none of the Information may be copied,
reproduced, distributed, republished, downloaded, displayed, posted, or transmitted in any form or by any means including, but not limited
to, electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of Xilinx.
Appendix B: Core Verification, Compliance, and Interoperability
Appendix C: Calculating DCM Phase-Shifting
Appendix D: Core Latency
14www.xilinx.com1-Gigabit Ethernet MAC v8.5 User Guide
UG144 April 24, 2009
-- DISCONTINUED PRODUCT --
R
About This Guide
The LogiCORE™ IP 1-Gigabit Ethernet MAC User Guide provides information about
generating the core, customizing and simulating the core utilizing the provided example
design, and running the design files through implementation using the Xilinx tools.
Guide Contents
This guide contains the following chapters:
•Preface, “About this Guide” introduces the organization and purpose of the guide
and the conventions used in this document.
•Chapter 1, “Introduction” describes the core and related information, including
recommended design experience, additional resources, technical support, and
submitting feedback to Xilinx.
•Chapter 2, “Core Architecture” provides an overview of the core and discusses the
Physical/Client signal interfaces.
•Chapter 3, “Generating the Core” describes the graphical user interface options used
to generate the core.
•Chapter 4, “Designing with the Core” through Chapter 8, “Configuration and Status”
describe design parameters, including how to initialize the core, generate and
consume core packets, and how to operate the Management Interface.
•Chapter 9, “Constraining the Core” describes the constraints associated with the core.
•Chapter 10, “Clocking and Resetting” discusses special design considerations
associated with clock management logic, including the Gigabit Media Independent
Interface (GMII) and Reduced Gigabit Media Independent Interface (RGMII) options.
•Chapter 11, “Interfacing to Other Cores” describes how to interface the 1-Gigabit
Ethernet MAC core to the Ethernet 1000BASE-X PCS/PMA or SGMII core and the
Ethernet Statistics core.
•Chapter 12, “Implementing Your Design” provides instructions for how to set up
synthesis, simulation, and implementation environments and how to generate a
bitstream through the design flow.
•Appendix A, “Using the Client-Side FIFO” describes the FIFO provided in the
example design that accompanies the GEMAC core.
•Appendix B, “Core Verification, Compliance, and Interoperability” describes how the
core was verified and certified for compliance.
•Appendix C, “Calculating DCM Phase-Shifting” provides information about how to
calculate the system timing requirements when using DCMs with the core.
•Appendix D, “Core Latency” describes the latency of the core.
Preface
1-Gigabit Ethernet MAC v8.5 User Guidewww.xilinx.com15
UG144 April 24, 2009
-- DISCONTINUED PRODUCT --
R
Conventions
Typographical
Preface: About This Guide
This document uses the following conventions. An example illustrates each convention.
The following typographical conventions are used in this document:
ConventionMeaning or UseExample
Messages, prompts, and
Courier font
Courier bold
Italic font
program files that the system
displays
Literal commands you enter in
a syntactical statement
Variables in a syntax
statement for which you must
supply values
References to other manualsSee the User Guide for details.
speed grade: - 100
ngdbuild design_name
See the Development System
Reference Guide for more
information.
Emphasis in text
Dark Shading
Square brackets [ ]
Braces { }
Vertical bar |
Vertical ellipsis
.
.
.
Horizontal ellipsis . . .Omitted repetitive material
Notations
Items that are not supported
or reserved
An optional entry or
parameter. However, in bus
specifications, such as
bus[7:0], they are required.
A list of items from which you
must choose one or more
Separates items in a list of
choices
Repetitive material that has
been omitted
The prefix ‘0x’ or the suffix ‘h’
indicate hexadecimal notation
An ‘_n’ means the signal is
active low
If a wire is drawn so that it
overlaps the pin of a symbol,
the two nets are not connected.
This feature is not supported
ngdbuild [option_name]
design_name
lowpwr ={on|off}
lowpwr ={on|off}
IOB #1: Name = QOUT’
IOB #2: Name = CLKIN’
.
.
.
allow block block_name
loc1 loc2 ... locn;
A read of address
0x00112975 returned
45524943h.
usr_teof_n is active low.
16www.xilinx.com1-Gigabit Ethernet MAC v8.5 User Guide
UG144 April 24, 2009
Conventions
Online Document
-- DISCONTINUED PRODUCT --
R
The following linking conventions are used in this document:
ConventionMeaning or UseExample
Blue text
Blue, underlined text
List of Acronyms
The following table describes acronyms used in this manual.
AcronymSpelled Out
CLBConfigurable Logic Block
DCMDigital Clock Manager
DDRDouble Data Rate
FCSFrame Check Sequence
FPGAField Programmable Gate Array.
GBICGigabit Interface Converter
GbpsGigabit per second
Cross-reference link to a
location in the current
document
Hyperlink to a website (URL)
See the section “Additional
Resources” for details.
See “Title Formats” in
Chapter 1 for details.
Go to w
latest speed files.
ww.xilinx.com for the
GEMACGigabit Ethernet Media Access Controller
GMIIGigabit Media Independent Interface
HDLHardware Description Language
IOInput/Output
IOBInput/Output Block
IPIntellectual Property
ISE®Integrated Software Environment
LSWLeast Significant Word
MACMedia Access Controller
MDIOManagement Data Input/Output
MHzMega Hertz
MMDMDIO Managed Device
msmilliseconds
MSWMost Significant Word
1-Gigabit Ethernet MAC v8.5 User Guidewww.xilinx.com17
UG144 April 24, 2009
-- DISCONTINUED PRODUCT --
R
Preface: About This Guide
AcronymSpelled Out
NCDNative Circuit Description
NGCNative Generic Circuit
NGDNative Generic Database
nsnanoseconds
PCBPrinted Circuit Board
PCSPhysical Coding Sublayer
PHYphysical-side interface
PMAPhysical Medium Attachment
PMDPhysical Medium Dependent
RGMIIReduced Gigabit Media Independent Interface
SGMIISerial Gigabit Media Independent Interface
VHDLVHSIC Hardware Description Language
(VHSIC an acronym for Very High-Speed
Integrated Circuits).
VCSVerilog Compiled Simulator
VLANVirtual LAN (Local Area Network)
18www.xilinx.com1-Gigabit Ethernet MAC v8.5 User Guide
UG144 April 24, 2009
R
Introduction
The 1-Gigabit Ethernet MAC (GEMAC) core is a fully verified solution that supports
Verilog-HDL and VHDL. In addition, the example design provided with the core is
provided in both Verilog and VHDL.
This chapter introduces the GEMAC core and provides other related information,
including recommended design experience, additional resources, technical support, and
ways to submit feedback to Xilinx.
-- DISCONTINUED PRODUCT --
Chapter 1
About the Core
The GEMAC core is a Xilinx CORE Generator™ IP core, included in the latest IP Update on
the Xilinx IP Center. For detailed information about the core, see the GEMAC product
page. For information about licensing options, see Chapter 2, “Licensing the Core,” in the
1-Gigabit Ethernet MAC Getting Started Guide.
Recommended Design Experience
Although the GEMAC core is a fully verified solution, the challenge associated with
implementing a complete design varies, depending on the configuration and functionality
of the application. For best results, previous experience building high performance,
pipelined FPGA designs using Xilinx implementation software and user constraint files
(UCFs) is recommended.
Contact your local Xilinx representative for a closer review and estimation for your specific
requirements.
Additional Core Resources
For detailed information and updates about the GEMAC core, see the following
documents, located on the GEMAC product page
•1-Gigabit Ethernet MAC Data Sheet
•1-Gigabit Ethernet MAC Getting Started Guide
.
After generating the core, the 1-Gigabit Ethernet MAC Release Notes are available from the
document directory.
Related Xilinx Ethernet Products and Services
See the Ethernet Products and Services page.
1-Gigabit Ethernet MAC v8.5 User Guidewww.xilinx.com19
UG144 April 24, 2009
R
Specifications
•IEEE 802.3 2005
•Reduced Gigabit Media Independent Interface (RGMII) version 2.0
Technical Support
For technical support, see support.xilinx.com/. Questions are routed to a team of engineers
with expertise using the GEMAC core.
Xilinx will provide technical support for use of this product as described in the 1-Gigabit Ethernet MAC User Guide and the 1-Gigabit Ethernet MAC Getting Started Guide. Xilinx
cannot guarantee timing, functionality, or support of this product for designs that do not
follow these guidelines.
Feedback
Xilinx welcomes comments and suggestions about the GEMAC core and the
documentation supplied with the core.
-- DISCONTINUED PRODUCT --
Chapter 1: Introduction
GEMAC Core
For comments or suggestions about the GEMAC core, please submit a WebCase from
s
upport.xilinx.com/. Be sure to include the following information:
•Product name
•Core version number
•Explanation of your comments
Document
For comments or suggestions about this document, please submit a WebCase from
s
upport.xilinx.com/. Be sure to include the following information:
•Document title
•Document number
•Page number(s) to which your comments refer
•Explanation of your comments
20www.xilinx.com1-Gigabit Ethernet MAC v8.5 User Guide
UG144 April 24, 2009
-- DISCONTINUED PRODUCT --
R
Core Architecture
This chapter describes the GEMAC core architecture, including the major functional blocks
and all interfaces.
System Overview
Figure 2-1 illustrates a block diagram of the GEMAC core with all the major functional
blocks and interfaces. Descriptions of the functional blocks and interfaces are provided in
the sections that follow.
Chapter 2
Client
Tr ansmitter
Interface
Client
Receiver
Interface
Client
Management
Interface
Gigabit Ethernet MAC Core
Client Interface
Optional
Address
Filter
ConfigurationMDIO
Tr ansmit Engine
Flow Control
Receive Engine
Optional Management
GMII Block
To Physical
Sublayers
Figure 2-1:Block Diagram
1-Gigabit Ethernet MAC v8.5 User Guidewww.xilinx.com21
UG144 April 24, 2009
R
Core Components
Transmit Engine
The Transmit Engine accepts Ethernet frame data from the Client Transmitter Interface,
adds the preamble field to the start of the frame, adds padding bytes (if required) to ensure
that the frame meets the minimum frame length requirements, and adds the frame check
sequence (when configured to do so). The transmitter also ensures that the inter-frame
spacing between successive frames is at least the minimum specified. The frame is then
converted into a format that is compatible with the GMII and sent to the GMII Block.
Receive Engine
The Receive Engine accepts Ethernet frame data from the GMII Block, removes the
preamble field at the start of the frame, removes padding bytes and Frame Check Sequence
(if required, and when configured to do so). The receiver also performs error detection on
the received frame using information such as the frame check sequence field, received
GMII error codes, and legal frame size boundaries.
-- DISCONTINUED PRODUCT --
Chapter 2: Core Architecture
Flow Control
The Flow Control block is designed to clause 31 of the IEEE 802.3-2005 standard. The MAC
may be configured to send pause frames and to act upon their reception. These two
behaviors can be configured independently.
Address Filter
The Address Filter checks the address of incoming frames into the receiver. If the Address
Filter is enabled, the device will not pass frames that do not contain one of a set of known
addresses to the client.
Management Interface
The optional processor-independent Management Interface has standard address, data,
and control signals. It may be used as is, or you can apply a logical shim to interface to
common bus architectures. See Chapter 8, “Configuration and Status.”
This interface is used to access the following blocks.
•Configuration Register After power up or reset, the client may reconfigure the core
parameters from their defaults. Configuration changes can be written at any time.
•MDIO Interface The Management Interface is also used to access the MDIO interface
of the GEMAC core; this interface is typically connected to the MDIO port of a
physical layer device (PHY) to access its configuration and status registers. The MDIO
format is defined in IEEE802.3 clause 22.
GMII Block
This implements GMII style signaling for the physical interface of the core and is typically
attached to a physical layer device (PHY), either off-chip or internally integrated.
22www.xilinx.com1-Gigabit Ethernet MAC v8.5 User Guide
UG144 April 24, 2009
Core Interfaces
Core Interfaces
GMAC Core with Optional Management Interface
Figure 2-2 shows the pinout for the GEMAC core using the optional Management
Interface. The interface is unchanged, regardless of whether the optional Address Filter is
included.
Client Side InterfacePhysical Side Interface (GMII)
-- DISCONTINUED PRODUCT --
R
gtx_clk domain
tx_ifg_delay[7:0]
tx_statistics_vector[31:0]
tx_statistics_valid
pause_val[15:0]
gmii_rx_clk domain
rx_statistics_vector[27:0]
rx_statistics_valid
host_clk domain
host_opcode[1:0]
host_wr_data[31:0]
host_rd_data[31:0]
gtx_clk
tx_data[7:0]
tx_data_valid
tx_ack
tx_underrun
pause_req
rx_data[7:0]
rx_data_valid
rx_good_frame
rx_bad_frame
host_clk
host_addr[9:0]
host_miim_sel
host_req
host_miim_rdy
gmii_txd[7:0]
gmii_tx_en
gmii_tx_er
gmii_rx_clk
gmii_rxd[7:0]
gmii_rx_dv
gmii_rx_er
mdc
mdio_in
mdio_out
mdio_tri
reset
Figure 2-2:Component Pinout for MAC with Optional Management Interface
1-Gigabit Ethernet MAC v8.5 User Guidewww.xilinx.com23
UG144 April 24, 2009
-- DISCONTINUED PRODUCT --
R
Chapter 2: Core Architecture
GMAC Core Without Management Interface and With Address Filter
Figure 2-3 shows the pinout for the GEMAC core when the optional Management Interface
is omitted and the optional Address Filter is included in the core.
The configuration_vector[67:0] input provides the method for configuration of
the core, and mac_unicast_address[47:0] input provides the method of setting the
unicast address used by the Address Filter.
Client Side InterfacePhysical Side Interface (GMII)
gtx_clk domain
tx_data[7:0]
tx_data_valid
tx_ifg_delay[7:0]
tx_underrun
tx_statistics_vector[31:0]
tx_statistics_valid
pause_req
pause_val[15:0]
gmii_rx_clk domain
rx_data[7:0]
rx_data_valid
rx_good_frame
rx_bad_frame
rx_statistics_vector[27:0]
rx_statistics_valid
mac_unicast_address[47:0]
configuration_vector[67:0]
gtx_clk
gmii_txd[7:0]
gmii_tx_en
gmii_tx_er
tx_ack
gmii_rx_clk
gmii_rxd[7:0]
gmii_rx_dv
gmii_rx_er
reset
Figure 2-3:Component Pinout for MAC without Optional Management Interface
and with Optional Address Filter
24www.xilinx.com1-Gigabit Ethernet MAC v8.5 User Guide
UG144 April 24, 2009
Core Interfaces
GEMAC Core Without Management Interface and Without Address Filter
-- DISCONTINUED PRODUCT --
R
Figure 2-4 shows the pinout for the GEMAC core when the optional Management Interface
is omitted and the optional Address Filter is omitted.
The configuration_vector[67:0] input provides the method for configuration of
the core.
Client Side InterfacePhysical Side Interface (GMII)
gtx_clk domain
tx_ifg_delay[7:0]
tx_statistics_vector[31:0]
tx_statistics_valid
pause_val[15:0]
gmii_rx_clk domain
rx_data_valid
rx_good_frame
rx_bad_frame
rx_statistics_vector[27:0]
rx_statistics_valid
gtx_clk
tx_data[7:0]
tx_data_valid
tx_ack
tx_underrun
pause_req
rx_data[7:0]
gmii_txd[7:0]
gmii_tx_en
gmii_tx_er
gmii_rx_clk
gmii_rxd[7:0]
gmii_rx_dv
gmii_rx_er
configuration_vector[67:0]
reset
Figure 2-4:Component Pinout for MAC without Optional Management Interface or Optional Address Filter
1-Gigabit Ethernet MAC v8.5 User Guidewww.xilinx.com25
UG144 April 24, 2009
R
All ports of the core are internal connections in FPGA fabric. An HDL example design is
delivered with the core that will add IBUFs, OBUFs, and IOB flip-flops to the external
signals of the Gigabit Media Independent Interface (GMII) or Reduced Gigabit Media
Independent Interface (RGMII).
All clock management logic is placed in this example design, which allows for more
flexibility in implementation (for example, in designs using multiple cores). This example
design is provided in both VHDL and Verilog. For more information about example
designs, see the 1-Gigabit Ethernet MAC Getting Started Guide.
Client Side Interface
Transmitter Interface
Tab le 2- 1 describes the client-side transmitter signals of the GEMAC core. These signals are
used to transmit data from the client logic into the core. See “Transmitting Outbound
Frames,” on page 47.
The Transmitter Interface is designed to be connected to internal device logic only.
Attempting to add external ports to this interface will result in a breakdown of the
handshaking protocol used by this interface.
-- DISCONTINUED PRODUCT --
Chapter 2: Core Architecture
Table 2-1:Transmitter Client Interface Signal Pins
SignalDirection
Clock
Domain
Description
gtx_clkInputn/aClock signal provided to the core at
125 MHz. Tolerance must be
within IEEE 802.3-2005
specification. This clock signal is
used by all of the transmitter logic.
tx_data[7:0]Inputgtx_clkFrame data to be transmitted is
supplied on this port.
tx_data_validInputgtx_clkControl signal for tx_data port.
tx_ifg_delay[7:0]Inputgtx_clkControl signal for configurable
Inter Frame Gap adjustment.
tx_ackOutputgtx_clkHandshaking signal asserted when
the current data on tx_data has
been accepted.
tx_underrunInputgtx_clkAsserted by clien t to fo rce GEMA C
core to corrupt the current frame.
tx_statistics_vector[31:0]Outputgtx_clkProvides statistical information
about the last frame transmitted.
tx_statistics_validOutputgtx_clkAsserted at end of frame
transmission, indicating that the
tx_statistics_vector is valid.
26www.xilinx.com1-Gigabit Ethernet MAC v8.5 User Guide
UG144 April 24, 2009
Core Interfaces
-- DISCONTINUED PRODUCT --
R
Receiver Interface
Tab le 2- 2 describes the client-side receiver signals of the GEMAC core. These signals are
used by to transfer data to the client. See “Receiving Inbound Frames,” on page 39.
Table 2-2:Receive Client Interface Signal Pins
SignalDirectionClock DomainDescription
rx_data[7:0]Outputgmii_rx_clkFrame data received is
supplied on this port.
rx_data_validOutputgmii_rx_clkControl signal for the rx_data
port.
rx_good_frameOutputgmii_rx_clkAsserted at end of frame
reception to indicate that the
frame should be processed by
the MAC client.
rx_bad_frameOutputgmii_rx_clkAsserted at end of frame
reception to indicate that the
frame should be discarded by
the MAC client.
rx_statistics_validOutputgmii_rx_clkAsserted at end of frame
reception, indicating that the
rx_statistics_vector is valid.
Flow Control Interface
Tab le 2- 3 describes the signals used by the client to request a flow control action from the
transmit engine. See “Using Flow Control,” on page 53.
Table 2-3:Flow Control Interface Signal Pinout
SignalDirectionClock DomainDescription
pause_reqInputgtx_clkPause request. sends a pause
frame down the link.
pause_val[15:0]Inputgtx_clkPause value; inserted into the
parameter field of the
transmitted pause frame.
1-Gigabit Ethernet MAC v8.5 User Guidewww.xilinx.com27
UG144 April 24, 2009
-- DISCONTINUED PRODUCT --
R
Management Interface (Optional)
Tab le 2- 4 describes the optional signals used by the client to access the management
features of the GEMAC core. See “Using the Optional Management Interface,” on page 77.
Table 2-4:Optional Management Interface Signal Pinout
Chapter 2: Core Architecture
SignalDirection
Clock
Domain
Description
host_clkInputn/aClock for the Management
Interface; must be 10 MHz or
above.
host_opcode[1:0]Inputhost_clkDefines operation to be performed
over MDIO interface. Bit 1 is also
used as a read/write control
signal for configuration register
access.
host_addr[9:0]Inputhost_clkAddress of register to be accessed.
host_wr_data[31:0]Inputhost_clkData to write to register .
host_rd_data[31:0]Outputhost_clkData read from register.
host_miim_selInputhost_clkWhen asserted, the MDIO
interface is accessed. When not
asserted, the configuration
registers are accessed.
host_reqInputhost_clkUsed to signal a transaction on the
MDIO interface.
host_miim_rdyOutputhost_clkWhen high, the MDIO interface
has completed any pending
transaction and is ready for a new
transaction.
MAC Unicast Address (Optional)
Tab le 2- 5 describes the alternative method of access to the unicast address registers when
the optional Management Interface is not present.
Table 2-5:Optional MAC Unicast Address Signal Pinout
SignalDirectionDescription
mac_unicast_address[47:0]InputUsed to assess the MAC unicast
address registers when the
Management Interface is not used
Note: All bits are registered on input but may be treated as asynchronous inputs.
28www.xilinx.com1-Gigabit Ethernet MAC v8.5 User Guide
UG144 April 24, 2009
Core Interfaces
-- DISCONTINUED PRODUCT --
R
Configuration Vector (Optional)
Tab le 2- 6 describes the alternative to the optional Management Interface signals. The
Configuration Vector uses direct inputs to the core to replace the functionality of the MAC
configuration bits. See “Access without the Management Interface,” on page 90.
Table 2-6:Optional Configuration Vector Signal Pinout
SignalDirectionDescription
configuration_vector[67:0]InputUsed to replace the functionality of
the MAC Configuration Registers
when the Management Interface is
not used
Note: All bits are registered on input but may be treated as asynchronous inputs.
Asynchronous Reset
Tab le 2- 7 describes the asynchronous reset signal for the entire core.
Table 2-7:Reset Signal
SignalDirectionClock DomainDescription
resetInputn/aAsynchronous reset for entire core
Physical Side Interface
GMII
Tab le 2- 8 describes the GMII-style interface signals of the core. See Chapter 7, “Using the
Physical Side Interface.”
Table 2-8:GMII Interface Signal Pinout
SignalDirectionClock DomainDescription
gmii_txd[7:0]Outputgtx_clkTransmit data from MAC
gmii_tx_enOutputgtx_clk Transmit control signal from MAC
gmii_tx_erOutputgtx_clkTransmit control signal from MAC
gmii_rx_clkInputn/aReceive clock from external PHY (125
gmii_rxd[7:0]Inputgmii_rx_clkReceived data to MAC
gmii_rx_dvInputgmii_rx_clkReceived control signal to MAC
MHz)
gmii_rx_erInputgmii_rx_clkReceived control signal to MAC
1-Gigabit Ethernet MAC v8.5 User Guidewww.xilinx.com29
UG144 April 24, 2009
R
MDIO Interface
-- DISCONTINUED PRODUCT --
Chapter 2: Core Architecture
Tab le 2- 9 describes the MDIO Interface signals. See “Using the MDIO interface,” on page
76.
Table 2-9:MDIO Interface Signal Pinout
SignalDirection
Clock
Domain
Description
mdcOutputhost_clkManagement Clock: programmable
frequency derived from host_clk.
mdio_in
1
Inputhost_clkInput data signal for communication with
PHY configuration and status. Tie high if
unused.
mdio_out
1
Outputhost_clkOutput data signal for communication
with PHY configuration and status.
mdio_tri
1
Outputhost_clkTristate control for MDIO signals; 0 signals
that the value on mdio_out should be
asserted onto the MDIO bus.
1. mdio_in, mdio_outandmdio_trican be connected to a Tri-state buffer to create a bi-directionalmdio
signal suitable for connection to an external PHY.
30www.xilinx.com1-Gigabit Ethernet MAC v8.5 User Guide
UG144 April 24, 2009
Loading...
+ 108 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.