
Downloaded by khaled shehab of siliconexpert on Thursday, 24 June, 2004 02:49:08 AM
TBS™ Device Errata
Released
Proprietary and Confidential to PMC-Sierra, Inc., and for its customers’ internal use. 9
Document No.: PMC-2021842 Issue 2
2.1.2 Workarounds
To address this issue, we recommend forcing the RW8D/RP8D/RA8D decoder block to re-align
after a transmitting device is reset, and to verify that the TBS goes back to frame alignment.
Additionally, it should be verified that the RW8D/RP8D/RA8D eventually returns to frame
alignment following any change of character alignment state. Again, forcing the
RW8D/RP8D/RA8D decoder blocks to re-align if frame alignment is not restored is the
recommended approach. Re-alignment can be forced by inserting a traffic pattern that causes a
high density of LCVs on the receiver or by manually forcing the RW8D/RP8D/RA8D out of
character alignment. Each of these possible workaround individually solve the problem and
have been verified:
• Manually force the RW8D/RP8D/RA8D out of character alignment by setting the
RW8D/RP8D/RA8D FOCA bit high on the TBS link (Bit 0 of Registers 0x160, 0x170, and
0x180). This will cause the state machine in the TBS to search for a new alignment without
relying on receiving LCVs. After forcing out of character alignment, the OFAV should be
monitored. If the TSE does not go to frame alignment after two frames, the FOCA bit
should be set high again. Note that the FOCA bit should be set low first before setting high
as this bit is only effective during a low to high transition.
• Have the TBS source non-repeating traffic such as non-constant live or PRBS traffic. When
the TBS sources non-repeating traffic, it sends this traffic to the TSE, which in turn sends
the traffic back to the TBS. After the TBS receives the non-repeating traffic, any character
misalignment between the TSE and TBS will cause the TBS to detect LCV errors. There
will be enough LCV error density to force the TBS to hunt for a new character alignment.
• Enable Test Pattern Insertion on the TSE link (Bit 3 of Registers 0xNB0, 0xNB8, 0xNC0,
and 0xNC8). The TSE can be configured to send a specific 10B code to the TBS. By
sending an invalid 10B code (e.g. 0000000000b), the TBS will detect LCVs on every
character received and will be forced to hunt for a new character alignment. Once the Test
Pattern Insertion is disabled and normal traffic resumes, the RW8D/RP8D/RA8D will align
to the new character alignment of the normal traffic.
2.1.3 Performance With Workaround
The TBS will have the same character alignment as the transmitting device. The transmitting
device may be the TSE or another 8B/10B serial capable device such as another TBS or
S/UNI® MACH48 device. LCV Interrupts will not be triggered. This behavior will only occur
when sending a constant repeating pattern (e.g. zero pattern) initially when a transmitting device
is reset, and will not occur when sending live or PRBS traffic.
2.1.4 Performance Without Workaround
Occasionally, the TBS and the transmitting device (TSE or another 8B/10B serial capable
device) will not have the same character alignment after the transmitting device has re-
initialized. This causes erred traffic and LCV Interrupts. The TBS and the transmitting device
will not be correctly character aligned until non-constant live or PRBS traffic is passing through
the system. After this, the LCV interrupts will disappear. This behavior will only occur when
sending a constant repeating pattern (e.g. zero pattern) initially when a transmitting device is
reset, and will not occur when sending live or PRBS traffic.