
PM5317 SPECTRA-9953 Telecom Standard Product Data Sheet
Release
Proprietary and Confidential to PMC-Sierra, Inc., and for its customers’ internal use.
Document No.: PMC-2000741, Issue 5
489
17.2.4
DLL Reset
While the DLL should be transparent to the user in normal mode, if the sysclk input glitches,
there is a possibility that the DLL will seize, and that the system side of the Spectra-9953 will
not have the proper timings. For this reason, the DLL can be programmed to issue an interrupt
in the event of errors (Register 004CH, bit 2). When such an interrupt occurs, DLL should be
reset by writing to Register 004EH, after which the system side will operate normally.
17.3 Programming the SPECTRA-9953 Configuration Registers
The SPECTRA-9953 Receive and Transmit configuration registers are used to set each STS-
12/STM-4 slice in one of the following modes:
Mode 1: Master Slice Processing a Concatenated or Channelized STS-12/STM-4
SONET/SDH Stream. When processing a concatenated STS-12c/STM-4c, all TSB level
payload configuration registers are ignored. When channelized STS-12/STM-4 streams are
being processed, the functional block (TSB) level configuration registers are used to define
the payload type that constitutes the STS-12/STM-4. Each TSB must be configured in this
case.
Mode 2: Slave Slice Processing Part of a Concatenated STS-N*12c. In this case, all TSB-
level configuration registers are ignored.
17.4 Interrupt Service Routine
The SPECTRA-9953 device will assert INTB to logic 0 when a condition that is configured to
produce an interrupt occurs. To find which condition caused this interrupt to occur, use the
following procedure:
1. Read the registers 0020-002F to find the functional block(s) that caused the interrupt.
2. Find the register address of the corresponding block that caused the interrupt and read its
Interrupt Status registers. The interrupt functional block and interrupt source identification
register bits from step 1 are cleared once these register(s) have been read and the
interrupt(s) identified.
3. Service the interrupt(s).
4. If the INTB pin is still logic 0, then there are still interrupts to be serviced and steps 1 to 3
need to be repeated. Otherwise, all interrupts have been serviced. Wait for the next
assertion of INTB.