suppliers of PBRC4.30BR(37) and PDF data of PBRC4.30BR(37)

The deserializer stays in lock until it cannot detect the same data boundary (starUstop bits) for four consecutive cycles. Then the deserializer goes out of lock and hunts for the new data boundary (starUstop bits). In the event of loss of synchronization, the LOCKB pin output goes inactive and the outputs (including RX_CLK) enter a high-impedance state. The user's system should monitor the LOCKB pin in order to detect a loss of synchronization. Upon detection of loss of lock, sending SYNC patterns for resynchronization is desirable if reestablishing lock within a specific time is critical. However, the deserializer can lock to random data as previously noted. LOCKB is held inactive for at least nine cycles after loss of lock is detected.