VSC6134
Datasheet
Figure 29. Layout of the GCC FIFO Buffer
0
15
0
15
GCC
i
GCC
i
GCC
j
k
i
GCC
j
GCC
GCC
GCC
GCC
i
GCC
j
j
GCC
i
GCC
k
2 GCCs
3 GCCs
2.9.5.9
ODUk Experimental Overhead (EXP)
There is no on-chip monitoring of the EXP bytes.
2.9.5.10
2.9.5.11
ODUk Reserved Overhead (RES)
There is no on-chip monitoring of the RES bytes.
OPUk Payload Structure Identifier (PSI)
The PSI monitor stores the PSI bytes in the stack OPUk_PSI[127:0][15:0] at locations pointed to by
MFAS. The microprocessor may point to any byte in the stack by initializing the microprocessor stack
pointer OPUk_PSI_MPNT[4:0]. Each microprocessor read of or write to the stack automatically
increments the microprocessor stack pointer. (Writes to the stack are for testing purposes only.)
The live bits OPUk_PSI_PTL (payload type) and OPUk_PSI_RESL (reserved) indicate whether the
respective fields stored in the stack are valid (1) or invalid (0). A change of any field state sets the
respective status bit OPUk_PSI_PTS (payload type) and OPUk_PSI_RESS (reserved). The status bits
with their respective interrupt mask bits OPUk_PSI_PTM (payload type) and OPUk_PSI_RESM
(reserved) create maskable hardware interrupts.
A PSI trace is valid after n consecutive matches (that is, debounced n times), where n has a value of 1
through 8 and is set through register bits OPUk_PSI_MAT[2:0]. A PSI trace is invalid after m
consecutive mismatches, where m has a value of 1 through 8 and is set through register bits
OPUk_PSI_MIS[2:0].
Any one of the following conditions resets the debouncing and pauses PSI monitoring:
●
●
●
●
●
OOF when OTUk_OOFDBC_CTRL = 1
LOF
LOS
LOM
OTUk AIS
A zero-to-one transition on OPUk_PSI_INVD invalidates the entire PSI trace.
135 of 438
VMDS-10185 Revision 4.0
July 2006
VITESSE [ VITESSE SEMICONDUCTOR CORPORATION ]
