
Hardware Design 
Table 10.  | MII NPE C Signal Recommendations (Sheet 2 of 2) | ||||||
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | Name | 
  | 
  | Type | Pull  | 
  | 
  | 
  | 
  | 
  | Up/  | Recommendations  | ||
  | 
  | 
  | 
  | Field  | |||
  | 
  | 
  | 
  | 
  | Down  | 
  | |
  | 
  | 
  | 
  | 
  | 
  | 
  | |
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | Externally supplied receive clock:  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | • 25 MHz for 100 Mbps operation  | 
  | ETHC_rxclk  | 
  | 
  | I  | Yes  | • 2.5 MHz for 10 Mbps  | |
  | 
  | 
  | 
  | 
  | 
  | 
  | This MAC contains hardware hashing capabilities that are local to the interface.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | Should be pulled high through a   | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | Receive data bus from PHY, data sampled synchronously, with respect to ETHC_RXCLK.  | 
  | ETHC_rxdATA[3:0]  | 
  | I  | Yes  | This MAC contains hardware hashing capabilities that are local to the interface.  | ||
  | 
  | 
  | 
  | 
  | 
  | 
  | Should be pulled high through a   | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | Receive data valid is used to inform the MII interface about data that is being sent by  | 
  | ETHC_rxdv  | 
  | 
  | I  | Yes  | the Ethernet PHY  | |
  | 
  | 
  | This MAC contains hardware hashing capabilities that are local to the interface.  | ||||
  | 
  | 
  | 
  | 
  | 
  | 
  | |
  | 
  | 
  | 
  | 
  | 
  | 
  | Should be pulled high through a   | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | Asserted by the PHY when a collision is detected by the PHY. This MAC contains  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | hardware hashing capabilities that are local to the interface.  | 
  | ETHC_col  | 
  | 
  | I  | Yes  | Should be pulled high through a   | |
  | 
  | 
  | When this interface is disabled through the   | ||||
  | 
  | 
  | 
  | 
  | 
  | 
  | Expansion Bus Controller chapter of the Intel® IXP43X Product Line of Network  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | Processors Developer’s Manual) and is not being used a system design, this interface/  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | signal is not required for any connection.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | Asserted by the PHY when the transmit medium or receive medium are active.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | |
  | ETHC_crs  | 
  | 
  | I  | Yes  | throughout the duration of collision condition. PHY asserts CRS asynchronously and  | |
  | 
  | 
  | |||||
  | 
  | 
  | 
  | 
  | 
  | 
  | This MAC contains hardware hashing capabilities that are local to the interface.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | Should be pulled high through a   | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | Notes:  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 1.  | Features disabled/enabled by Soft Fuse must be done during the   | |||||
  | 
  | being disabled without asserting a system reset. | |||||
  | 2.  | Features disabled by a specific part number, do not require   | |||||
  | 
  | unconnected. | 
  | 
  | 
  | ||
  | 3.  | Features enabled by a specific part number — and required to be Soft   | |||||
  | 
  | ||||||
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
Table 11.  | MAC Management Signal Recommendations - NPE A and NPE C | |||
  | 
  | 
  | 
  | 
  | 
  | Name | Type | Pull  | 
  | 
  | Up/  | Recommendations  | ||
  | Field  | |||
  | 
  | Down  | 
  | |
  | 
  | 
  | 
  | |
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | NPE A and NPE C  | 
  | 
  | 
  | 
  | Management data input output. Provides the write data to both PHY devices connected to  | 
  | ETH_mdio  | IO  | Yes  | each MII interface. An external   | 
  | ETHC_MDIO to properly quantify the external PHYs used in the system. For specific  | |||
  | 
  | 
  | 
  | |
  | 
  | 
  | 
  | implementation, see the IEEE 802.3 specification.  | 
  | 
  | 
  | 
  | Should be pulled high through a   | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | NPE A and NPE C  | 
  | ETH_mdc | O  | No  | Management data clock. Management data interface clock is used to clock the MDIO signal as  | 
  | an output and sample the MDIO as an input. The ETHC_MDC is an input on power up and can  | |||
  | 
  | 
  | 
  | be configured to be an output through Intel APIs documented in the Intel® IXP400 Software  | 
  | 
  | 
  | 
  | Programmer’s Guide  | 
  | 
  | 
  | 
  | 
  | 
3.5.2Device Connection, MII
Figure 6 is a typical example of an Ethernet PHY device interfacing to one of the MACs via the MII hardware protocol.
  | Intel® IXP43X Product Line of Network Processors  | 
April 2007 | HDG | 
Document Number: 316844; Revision: 001US  | 31  |