Figure 1: These images depict the degradation of serial data traffic as it makes its way from transmitter to receiver |
What does a typical high-speed serial channel look like? Referring to Figure 1, the signal typically enters the channel from a transmitter IC (at left). Right off the bat, there will be some amount of loss even within the IC package. The signal then traverses the system board, a backplane, and a board-to-board high-speed connector, perhaps a PCI Express CEM connector into which is plugged an add-in card (memory, graphics, or what have you). In each stage of this journey, the signal suffers further degradation.
By the time the signal reaches the receiver IC on the add-in card, where it takes a final hit from that IC's package, the signal has gone from the wide-open eye at top left in Figure 1 to the virtually closed eye at top right. At lower speeds, these effects are less prominent. But as data rates increase, it is imperative, even critical, to apply some techniques to improve signal performance at both ends of the channel. An important aspect of debugging high-speed serial links is to break up the signal into its constituent elements within the channel by visualizing and analyzing the signal at each point.
Prominent SI issues that can plague high-speed serial links are mainly of two types. Channel-related problems include:
Often, there's no single cause of havoc in a serial-data channel, but rather "death by a thousand cuts." It's common to find multiple effects happening at once and there's no single solution to remedy them all. They must be isolated and examined to find their root cause(s), which is why it's so important to be able to visualize the signal at all points in the link.
In subsequent posts, we'll begin looking at some of the channel-related issues in high-speed serial links.
By the time the signal reaches the receiver IC on the add-in card, where it takes a final hit from that IC's package, the signal has gone from the wide-open eye at top left in Figure 1 to the virtually closed eye at top right. At lower speeds, these effects are less prominent. But as data rates increase, it is imperative, even critical, to apply some techniques to improve signal performance at both ends of the channel. An important aspect of debugging high-speed serial links is to break up the signal into its constituent elements within the channel by visualizing and analyzing the signal at each point.
Prominent SI issues that can plague high-speed serial links are mainly of two types. Channel-related problems include:
- Electrical/conduction losses
- Via stubs that can cause cavity resonance effects
- Mode conversion, the term for situations in which there is some asymmetry between the two lines of a differential channel
- Channel-to-channel crosstalk
- Impedance mismatches resulting in ringing and/or reflections
Often, there's no single cause of havoc in a serial-data channel, but rather "death by a thousand cuts." It's common to find multiple effects happening at once and there's no single solution to remedy them all. They must be isolated and examined to find their root cause(s), which is why it's so important to be able to visualize the signal at all points in the link.
In subsequent posts, we'll begin looking at some of the channel-related issues in high-speed serial links.
1 comment:
Hi! Is there any further information about "Random jitter often stems from the clock/data recovery (CDR) circuitry, which also can introduce random noise" mentioned in the article?
Post a Comment