Xilinx LOGICORE UG144 - Manual (Page 32)

32 www.xilinx.com 1-Gigabit Ethernet MAC v8.5 User Guide
UG144 April 24, 2009
Chapter 3: Generating the Core R
-- DISCONTINUED PRODUCT --
Component Name
The component name is used as the base name of the output files generated for the core.
Names must begin with a letter and must be composed from the following characters:
a through z, 0 through 9 and “_”.
Management Interface
Select this option to include the optional Management Interface (see “Using the Optional
Management Interface,” on page 77 ). If this option is not selected, the core is generated
with a replacement configuration vector (see “Access without the Management Interface,”
on page 90 ). The default is to use the Management Interface.
Address Filter
Select this option to include the optional Address Filter. This prevents the reception of
frames that are not addressed to this MAC (see
“Address Filter,” on page 44 ). The default
is to use the Address Filter.
Number of Address Table Entries
The Address Filter can be instantiated with an address table that holds up to 4 additional
valid addresses. You may select an integer between 0 and 4 to define the number of
addresses that are present in the table.
This option is only available when the Management Interface and Address Filter have been
selected. The default is to use 4 address table entries.
Physical Interface
Depending on the target Xilinx FPGA architecture, it may be possible to select from two
different physical interface choices for the core:
• GMII . See Chapter 7, “Implementing External GMII”
• RGMII . See Chapter 7, “Implementing External RGMII”
The choice of physical interface determines the content of the example design delivered
with the core. The external GMII or RGMII is added in the HDL top-level design file. There
is no change in the core netlist for this option. The default is the GMII physical interface.
Parameter Values in the XCO File
XCO file parameter names and their values are identical to the names and values shown in
the GUI, except that underscore characters (_) are used instead of spaces. The text in an
XCO file is not case-sensitive.
Table 3-1 defines the XCO file parameters and values and summarizes the GUI defaults.
The following is an example of the CSET parameters in an XCO file.
CSET component_name = abc123
CSET physical_interface = gmii
CSET management_interface = true
CSET address_filter = true
CSET no_of_address_table_entries = 4