
IBM3209K3114
Advance
IBM Packet Routing Switch Serial Interface Converter
prssi.01
July 12, 2000
Functional Description
Page 9 of 142
3.2.1.2 Ingress Operation and Timing
Table 1: Ingress I/O Pin Description
Pin Name
Function
PE_RXCLK_OUT
(Output)
Receive Clock
(PE_RXCLK_OUT clock) is issued from two clock domains:
At POR it is connected to the microprocessor clock until the POR completes.
After POR completes, it is generated by either the smooth PLL clock out (derived from SWITCH_PLL X or
Y) or by an externally provided clock (for example the 50 - 125 MHz PE clock).
PE_RXCLK_OUT source is selected according to the programming of the
“
PE_RXCLK_OUT_source_l[1:0]
”
bits in the configuration table registers.
RXDATA[31:0]
(Input)
Receive Data is transferred from the PE device to the converter on a 32-bits word basis.
LSB
MSB
RXDATA[0]RXDATA[31]
RXPRTY
(Input)
Receive Data Parity Bit is the odd parity bit over the 32 RXDATA bits. The parity_check mode is enabled/
disabled by the RXPRTY_enb_l bit in the configuration table registers.
RXPAV
(Input, active high)
PE device asserts Receive Packet Available
when at least one complete packet is ready to be transmitted
on the bus. The signal remains asserted during the current packet transfer (packet level handshake) and
indicates,
in the cycle following the last word of the current packet
, if there is (RXPAV asserted) or is not
(RXPAV de-asserted) a new packet to transfer.
RXPAV must be asserted when operating in IBFC mode.
RXSOP
(Input, active high) the packet
’
s first 32-bits data word.
RXENB
(Output, active low)
The converter
asserts Receive Enable to indicate its readiness to receive at least one complete packet.
The signal remains asserted during the transfer of the current packet (packet level handshake) and, two
cycles before the end of the current packet transfer, indicates whether it is (RXENB asserted) or is not
(RXENB de-asserted) ready to receive a new complete packet. As this signal is pipelined, the PC devices
will respond at least two clock cycles after the RXENB is asserted or de-asserted
Figure 5: Ingress Timing for RXENB Deasserted by Converter for 1 Clock Cycle
Ingress Operation for 64-Byte Packet Flow Control
T0
T2
T4
T6
T8
T10
T12
T14
T16
T18
T20
T22
T24
NOP NOP NOP H1
H2
W1
W2
W3
W4
W5
W6
W7
W8
W9 W10 W11 W12 W13 W14 NOP H1
H2
W1
W2
W3
1 wait state
PE_RXCLK_OUT
RXDATA[31:0]
RXSOP
RXPAV
RXENB
Converter can again
accept a new packet
Converter cannot accept
a new packet