4
Gigabit Ethernet PCS IP Core
Lattice Semiconductor for LatticeECP2M
Figure 4. Typical Receive Timing Diagram
Auto-Negotiation State Machine
The auto-negotiation state machine implements the link configuration functions described in clause 37 of IEEE
802.3 specification, including checking link readiness, determining duplex mode, and negotiating flow control. A
typical timing diagram is shown below.
Figure 5. Typical Auto-Negotiation Timing Diagram
Signal Descriptions
Table 1. GbE PCS IP Core Input and Output Signals
Signal Name
I/O Description
Clock Signals
tx_clk_125
In
Transmit Clock
– 125 MHz clock source for transmit state machine. Incoming GMII
transmit data is sampled on rising edge of this clock. Outgoing 8-bit code group trans-
mit data is launched on the rising edge of this clock.
rx_clk_125
In
Receive Clock
– 125 MHz clock source for receive state machine and the synchroni-
zation state machine. Incoming signals are sampled on the rising edge of the clock.
Outgoing signals are launched on the rising edge of this clock.
GMII Signals
tx_d[7:0]
In
Transmit Data
– Incoming GMII data.
tx_en
In
Transmit Enable
– Active high signal, asserts when incoming data is valid.
tx_er
In
Transmit Error
– Active high signal, used to denote transmission errors and carrier
extension on incoming GMII data port.
rx_d[7:0]
Out
Receive Data
– Outgoing GMII data.
rx_dv
Out
Receive Data Valid
– Active high signal, asserts when outgoing data is valid.
rx_er
Out
Receive Error
– Active high signal, used to denote transmission errors and carrier
extension on outgoing GMII data port.
8-Bit Code Group Signals
tx_data[7:0]
Out
8b Transmit Data
– 8-bit code group data after passing through transmit state
machine.
tx_kcntl
Out
8b Transmit K Control
– Denotes whether current code group is data or control.
1=control 0=data
rx_d
rx_dv
rx_data
rx_kcntl
preamble SFD Dest Add Src Add Len/Type Data FCS
IDLE preamble SFD Dest Add Src Add Len/Type Data FCS SPD IDLE EPD
mr_page_rx
power up reset
mr_adv_ability
mr_an_complete
mr_lp_adv_ability
0x0020
0x4020 0x0000
5
Gigabit Ethernet PCS IP Core
Lattice Semiconductor for LatticeECP2M
correct_disp
Out
Corrects Disparity
– Asserted during inter-packet gaps to ensure that negative dispar-
ity IDLE ordered-sets are transmitted by the LatticeECP2M embedded SERDES /PCS.
1=correct disparity, 0=normal
xmit_autoneg
Out
Auto-negotiation Transmitting
This signal asserts when the IP core’s auto negotia-
tion state machine is active. The signal is used by the LatticeECP2M embedded SER-
DES/PCS to occasionally insert idle ordered sets into its receive path (eight ordered
sets every 2048 clocks). This facilitates proper operation of the embedded clock toler-
ance compensation circuit. 1=autoneg is active, 0=autoneg is not active
rx_data[7:0]
In
8b Receive Data
– 8-bit code group data presented to the receive state machine.
rx_kcntl
In
8b Receive K Control
– Denotes whether current code group is data or control.
1=control 0=data
rx_err_decode_mode
In
Receive Error Control Mode
The embedded SERDES block of the LatticeECP2M
FPGAs has two modes of interpreting errors, decoded and normal. In decoded mode,
the three signals (
rx_even
,
rx_cv_err
,
rx_disp_err
) are used to decode 1-of-8 error
conditions. In decoded mode, the IP core responds to the following errors:
100 = Coding Violation Error
111 = Disparity Error
All other error codes are ignored by the IP core. In normal mode, the three error signals
(
rx_even
,
rx_cv_err
,
rx_disp_err
) behave normally. The
rx_err_decode_mode
signal should be set high for decode mode, and low for normal mode.
rx_even
In
Rx Even
This signal is only used when error decoding mode is active. Otherwise, the
signal should be tied low.
rx_cv_err
In
Rx Coding Violation Error
– In normal mode, an active high signal denoting a coding
violation error in the receive data path. In decode mode, used to decode 1 of 8 error
conditions.
rx_disp_err
In
Rx Disparity Error
– In normal mode, an active high signal denoting a disparity error in
the receive data path. In decode mode, used to decode 1 of 8 error conditions.
signal_detect
In
Signal Detect
– Denotes status of GbE PCS RX physical link. 1=signal is good; 0=loss
of receive signal
Management Signals
mr_adv_ability[15:0]
In
Advertised Ability
– Configuration status transmitted by PCS during auto negotiation
process.
mr_an_enable
In
Auto Negotiation Enable
– Active high signal that enables auto negotiation state
machine to function.
mr_main_reset
In
Main Reset
– Active high signal that forces all PCS state machines to reset.
mr_restart_an
In
Auto Negotiation Restart
– Active high signal that forces auto negotiation process to
restart.
mr_an_complete
Out
Auto Negotiation Complete
– Active high signal that indicates that the auto negotia-
tion process is completed.
mr_lp_adv_ability[15:0]
Out
Link Partner Advertised Ability
– Configuration status received from partner PCS
entity during the auto negotiating process. The bit definitions are the same as
described above for the
mr_adv_ability
port.
mr_page_rx
Out
Auto Negotiation Page Received
– Active high signal that asserts while the auto
negotiation state machine is in the
Complete_Acknowledge
state.
Miscellaneous Signals
rst_n
In
Reset
– Active low global reset
debug_link_timer_short
In
Debug Link Timer Mode
– Active high signal that forces the auto negotiation link timer
to run much faster than normal. This mode is provided for debug purposes (e.g.,allow-
ing simulations to run through the auto negotiation process much faster that the nor-
mal).
Table 1. GbE PCS IP Core Input and Output Signals (Continued)
Signal Name I/O Description
6
Gigabit Ethernet PCS IP Core
Lattice Semiconductor for LatticeECP2M
Core Generation
The GbE PCS IP core is available for download from the Lattice website at www.latticesemi.com. The IP files are
automatically installed using ispUPDATE technology in any directory of your choosing.
The ispLEVER IPexpress GUI window for the GbE PCS IP core is shown in Figure 6. To generate a specific IP core
configuration you must specify:
Project Path
– Path to directory where the generated IP files will be loaded.
File Name
“username” designation given to the generated IP core and corresponding folders and files.
Design Entry type
Verilog HDL.
Device Family
– Device family to which IP is to be targeted. Only families that support the particular core are
listed.
Part Name
– Specific targeted part within the selected Device Family.
Note that if IPexpress is called from within an existing project, Project Path, Design Entry, Device Family and Part
Name default to the specified project parameters. Please refer to the IPexpress on-line help for further information.
Figure 6. IPexpress Dialog Box
To create a custom configuration, click on the
Customize
button to display the GbE PCS IP core Configuration
GUI, shown in Figure 7. From this window you may start the core generation process.

GBE-PCS-PM-U1

Mfr. #:
Manufacturer:
Lattice
Description:
Programmable Logic IC Development Tools Gigabit Ethernet PCS ECP2M
Lifecycle:
New from this manufacturer.
Delivery:
DHL FedEx Ups TNT EMS
Payment:
T/T Paypal Visa MoneyGram Western Union

Products related to this Datasheet