
R
Chapter 14
Special Design Considerations
This chapter describes the unique design considerations associated with implementing the Ethernet
Power Management
No power management considerations are recommended for the Ethernet
•Writing to the PCS Configuration Register 0 (if using the core with the optional Management Interface). The
•Asserting the Power Down bit in the configuration_vector (if using the core without the optional Management Interface). The
Startup Sequencing
IEEE 802.3 clause 22.2.4.1.6 states that by default, a PHY should
•If you are using the core with the optional Management Interface, it is necessary to write to the PCS Configuration Register 0 to take the core out of the isolate state.
•If using the core without the optional Management interface, it is the responsibility of the client to ensure that the isolate input signal in the configuration_vector is asserted at
Loopback
This section details the implementation of the loopback feature. Loopback mode is enabled or disabled by either the “MDIO Management Interface,” page 115, or by the “Optional Configuration Vector,” page 151.
Core with the TBI
There is no physical loopback path in the core. Placing the core into loopback has the effect of asserting logic 1 on the ewrap signal of the TBI (see
Ethernet | www.xilinx.com | 197 |