S/UNI®-ATLAS-3200 Telecom Standard Product Data Sheet
Preliminary
Pin Name
OCIF_PAR
Type
Output
Pin No Function
(A) RPU_PAR
(B) TLU_PAR
(C) RPP_PAR
(A) Parity over data bus (programmable to odd or even)
(B) Parity over data bus (programmable to odd or even)
(C) Parity over data bus (programmable to odd or even)
The receive parity (RPP_PAR) signal indicates the parity
calculated over the RPP_DAT bus. RPP_PAR is valid whenever
RPP_VAL or RPP_SX are asserted.
(D) TLP_PAR
(D) Parity over data bus (programmable to odd or even)
The transmit parity (TLP_PAR) signal indicates the parity
calculated over the TLP_DAT bus. TLP_PAR is considered valid
only when TLP_ENB or TLP_SX is asserted.
OCIF_SOC_SOP
(A) RPU_SOC
Output
(A) Start of cell. Active high signal asserted to indicate the start of
cell position. It is expected that, in case of loss of
synchronization, that RPU_SOC will serve to resynchronize the
interface.
(B) TLU_SOC
(C) RPP_SOP
(B) Start of cell. Active high signal asserted to indicate the start of
cell position. It is expected that, in case of loss of
synchronization, that TLU_SOC will serve to resynchronize the
interface.
(C) Start of packet. RPP_SOP is used to delineate the packet
boundaries on the RPP_DAT bus. When RPP_SOP is high, the
start of the packet is present on the RPP_DAT bus.
RPP_SOP is required to be present at the start of every packet
and is considered valid when RPP_VAL is asserted..
(D) TLP_SOP
(D) Start of packet. TLP_SOP is used to delineate the packet
boundaries on the TLP_DAT bus. When TLP_SOP is high, the
start of the packet is present on the TLP_DAT bus.
TLP_SOP is required to be present at the beginning of every
packet and is considered valid only when TLP_ENB is asserted.
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-1990553, Issue 4
54
PMC [ PMC-SIERRA, INC ]
