Intel® IXP45X and Intel® IXP46X Product Line of Network
3.9.1Signal Interface
Table 16. | UTOPIA Signal Recommendations | ||||
|
|
|
|
|
|
|
|
| Input/ | Pull |
|
| Name |
| Up/ | Recommendations | |
|
|
| Output | Down |
|
|
|
|
|
|
|
|
|
|
|
| UTOPIA Transmit clock input. Also known as UTP_TX_CLK. |
UTP_OP_CLK |
| I | Yes | When this interface/signal is enabled and is not being used in a system design, the | |
|
|
|
|
| interface/signal should be pulled high with a |
|
|
|
|
|
|
|
|
|
|
| UTOPIA flow control output signal. Also known as the TXENB_N signal. |
UTP_OP_FCO |
| O | Yes | When this interface/signal is enabled and is not being used in a system design, the | |
|
|
|
|
| interface/signal should be pulled high with a |
|
|
|
|
|
|
|
|
|
|
| Start of Cell. Also known as TX_SOC. |
UTP_OP_SOC |
| O | Yes | When this interface/signal is enabled and is not being used in a system design, the | |
|
|
|
|
| interface/signal should be pulled low with a |
|
|
|
| ||
UTP_OP_DATA[7:0] | O | No | UTOPIA output data. | ||
|
|
|
|
|
|
|
|
|
|
| Transmit PHY address bus. |
UTP_OP_ADDR[4:0] | I/O | Yes | When this interface/signal is enabled and is not being used in a system design, the | ||
|
|
|
|
| interface/signal should be pulled high with a |
|
|
|
|
|
|
|
|
|
|
| UTOPIA Output data flow control input: Also known as the TXFULL/CLAV signal. |
UTP_OP_FCI |
| I | Yes | When this interface/signal is enabled and is not being used in a system design, the | |
|
|
|
|
| interface/signal should be pulled high with a |
|
|
|
|
|
|
|
|
|
|
| UTOPIA Receive clock input. Also known as UTP_RX_CLK. |
UTP_IP_CLK |
| I | Yes | When this interface/signal is enabled and is not being used in a system design, the | |
|
|
|
|
| interface/signal should be pulled high with a |
|
|
|
|
|
|
|
|
|
|
| UTOPIA Input Data flow control input signal. Also known as RXEMPTY/CLAV. |
UTP_IP_FCI |
| I | Yes | When this interface/signal is enabled and is not being used in a system design, the | |
|
|
|
|
| interface/signal should be pulled high with a |
|
|
|
|
|
|
|
|
|
|
| Start of Cell. Also known as RX_SOC |
UTP_IP_SOC |
| I | Yes | When this interface/signal is enabled and is not being used in a system design, the | |
|
|
|
|
| interface/signal should be pulled high with a |
|
|
|
|
|
|
|
|
|
|
| UTOPIA input data. Also known as RX_DATA. |
UTP_IP_DATA[7:0] | I | Yes | When this interface/signal is enabled and is not being used in a system design, the | ||
|
|
|
|
| interface/signal should be pulled high with a |
|
|
|
| ||
UTP_IP_ADDR[4:0] | I/O | No | Receive PHY address bus. | ||
|
|
|
|
|
|
|
|
|
|
| UTOPIA Input Data Flow Control Output signal: Also known as the RX_ENB_N. |
UTP_IP_FCO |
| O | Yes | When this interface/signal is enabled and is not being used in a system design, the | |
|
|
|
|
| interface/signal should be pulled high with 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 | ||||
| |||||
|
|
|
|
|
|
3.9.2Device Connection
The following example shown in Figure 13 shows a typical interface to an ADSL Framer via the UTOPIA bus. Notice that depending on the framer used some control signals might be required which can be derived from the Expansion bus or the GPIO signals.
Intel® IXP45X and Intel® IXP46X Product Line of Network Processors |
|
HDD | February 2007 |
42 | Document Number: 305261; Revision: 004 |