## Archive for **March 8th, 2017**

## Via Stubs Demystified

We worry about via stubs in high-speed designs because they cause unwanted resonant frequency nulls which appear in the insertion loss plot (IL) of the channel. But are all via stubs bad? Well, as with most answers relating to signal integrity, “*It depends*.”

If one of these frequency nulls happen to line up at or near the Nyquist frequency of the bit- rate (i.e. 1/2 of the bit-rate), the received eye will be devastated, resulting in a high bit-error-ratio (BER), or even link failure.

Figure 1 shows simulation results of two backplane channels. On the left are measured SDD21 insertion loss and eye diagram of a 10 GB/s, non-return-to-zero (NRZ) signal, with short through vias and long stubs ~ 270 mils. On the right, shows measured SDD21 IL and eye diagram of a channel with long through vias and shorter stubs ~ 65 mils

Because the ¼ -wave resonant null occurs at a frequency ~ 4. 4 GHz, this is near the Nyquist frequency for 10 GB/s. As can be seen, the eye is totally closed for the long stub case. But when the shorter stub case is simulated, the eye is open with plenty of margin.

So how does a via stub cause ¼ -wave resonance? This question can be explained with the aid of Figure 2. Starting on the left, we see a via with two sections. The through (thru) part is the top portion connecting a device pin to an inner layer trace of a printed circuit board (PCB). The stub portion is the lower portion and is an open circuit.

On the right a sinusoidal signal is injected into the pin at the top of the via and travels along the thru portion until it reaches the junction of the internal trace and stub. At that point, the signal splits. Some of it travels along the trace, and the rest continues down the stub. Once it reaches the bottom, it reflects back up. When it reaches the trace junction, it splits again with a portion traveling along the trace and the rest back to the source.

If *f _{ }*is the frequency of a sine wave, and the time delay (TD) through the stub portion equals a ¼ -wavelength, then when it reflects at the bottom and reaches the junction again, it will be delayed by ½ a cycle and cancels most of the original signal.

Figure 2 Illustration of a ¼ -wave resonance of a stub. If *f* = frequency where TD = ¼ wavelength, then when 2TD = ½ cycle minimum signal received.

Resonance nulls occurs at the fundamental frequency ( *f _{o}*) and at every odd harmonic. If you know the length of the stub (in inches) and the effective dielectric constant (

*Dk*), surrounding the via hole structure, the resonant frequency can be predicted by:

_{eff}Equation 1

Where: *f _{o}* is the ¼ -wave resonant frequency (GHz);

*c*is the speed of light (~11.8 in/ns);

*Stub_length*is inches.

You will find that* Dk _{eff} *is not the same as the bulk

*Dk*published in laminate manufacturers’ data sheets. It is typically higher. A higher

*Dk*increases phase delay through the via resulting in a lower resonant frequency.

_{eff}One reason is excess capacitance from the via pads as well as the via barrel’s proximity to the clearance hole openings (also known as anti-pads) in plane layers. The other is because of the anisotropic nature of the laminate material.

For the example in Figure 1, the ¼ -wave resonant frequency of the long via stub is ~ 4.4 GHz. With a stub length of ~ 270 mils, this gives a *Dk _{eff} *of 6.16, which is considerably higher than the published bulk

*Dk*of 3.65. When you model a via in an electro-magnetic (EM) 3D field solver, it automatically accounts for the excess capacitance, but you will still need to compensate for the anisotropic nature of the dielectric.

A material is anisotropic when there are different values for parallel (x-y) vs perpendicular (z) measured values for dielectric constant. Dielectric constant and loss tangent, as published in manufacturers’ data sheets, report perpendicular measured values. For FR-4 fiberglass reinforced laminates, anisotropy can range from 15% -25% higher. The bad news is these numbers are not readily available from data sheets.

For differentially driven vias with plane layers evenly distributed throughout the entire stackup, *Dk _{eff} *can be roughly estimated by:

Equation 2

Where: *Dk _{xy}* is the dielectric constant adjusted for anisotropy (15%-25% higher);

*Dk*is the bulk dielectric constant from data sheets;

_{z}*s*is via-via spacing;

*drill*

*Ø*is drill diameter;

*H and W*are anti-pad shape dimensions as shown in Figure 3 .

Figure 3 Anti-pad parameters for Equation 2.

The effects of via stubs can be mitigated by: using blind or buried vias; back-drilling; or by using thru vias only (i.e. from top layer to bottom layer). Practically, the shortest stub that can be achieved by back-drilling is on the order of 5 to 10 mils.

As a rule of thumb, we usually strive to have an interconnect bandwidth (BW) to be five times the Nyquist frequency of the bit-rate. Since a ¼-wave resonant null behaves somewhat like a notch filter, depending on the high-frequency roll-off due to Q-factor, frequencies near resonance will be attenuated. For that reason a good rule of thumb to follow is making sure the first null should occur at the 7^{th} harmonic, or higher, of the Nyquist frequency to maintain the integrity of the 5^{th} harmonic frequency component that makes up the risetime of a signal.

With this in mind, for a given baud-rate (*Baud*) in GBd/s, the maximum stub length (*l _{max}*), in inches can be estimated by:

Equation 3

For NRZ signaling, the baud-rate is equal to the bit rate. But for pulse-amplitude modulation (PAM-4) signaling, which has 2 symbols per bit time, the baud-rate is ½ of that. Thus a 56 GB/s PAM-4 signal has a baud-rate of 28 GBd/s, and the Nyquist frequency is 14 GHz, which happens to be the same as 28 GB/s NRZ signalling.

Figure 4 presents a chart of maximum stub length vs baud-rate based on Equation 3, using a *Dk _{eff}* = 6.16 (blue) vs 3.65 (red). It shows us the higher the baud-rate, the more the stub length becomes an issue, especially past 10 GBd/s. We also get a feel for the sensitivity of stub length to

*Dk*. Even though there is ~ 70% difference in

_{eff }*Dk*, there is only ~ 30% delta in stub lengths for the same baud-rate. This means that even if we use the bulk

_{eff}*Dk*published in data sheets, we are probably not dead in the water.

If the respective stub length is greater than this, it does not mean there is a show stopper. Depending on how much longer means the eye opening at the receiver will be degraded and we lose margin. We see this by the example in Figure 1. Even though the stub lengths in the channel were almost double the value at 10 GBd/s from the chart, there is still plenty of eye opening.

Figure 4 Chart showing estimated maximum stub length vs baud-rate with *Dk _{eff}* of 6.16 (red) vs 3.65 (blue) based on Equation 3

To further explore design space and test out the rule of thumb, a generic circuit model was built using Keysight ADS with the ability to vary the via stub lengths

Referring to the chart, at 28 GBd/s, the maximum stub length should be 12 mils, assuming a *Dk _{eff} *of 6.16. Figure 5 shows simulation results for NRZ signalling. As can be seen, there was a difference of only 17 mV in eye height (1.5%), and no extra jitter for 12 mil stubs compared to 5 mil stubs.

Figure 5 Eye diagrams comparison with BER at 10E-12 for stub lengths of 5 mils vs 12 mils. Modeled and simulated with Keysight ADS.

But if we use the exact same channel model, and use the generic PAM-4 IBIS AMI model from Keysight Technologies, we can see the results plotted in Figure 6. On the left are the eye openings with 5 mil stubs and the right with 12 mil stubs. In this case, there was an average reduction of ~7 mV (6%) in eye heights, and 0.24 ps (2%) in eye widths at BER 10E-12 across all three eyes.

Figure 6 PAM-4, 28 GBd/s (56 GB/s) eye height and width comparison at BER of 10E-12 for 5 mil vs 12 mil stub lengths. Modeled and simulated with Keysight ADS.

Because PAM-4 signalling has three smaller eyes, that are one-third the size of an NRZ eye for the same amplitude, it is more sensitive to channel impairments. From the above examples, we can see NRZ had only 1.5% reduction in eye height compared to 6% for PAM-4. Similarly there was no increase in jitter for NRZ compared to 2% increase for PAM-4 when stub lengths changed from 5 mils to 12 mils.

What this says is maintaining a BW to 5 times Nyquist rule of thumb, when estimating via stub lengths, is quite conservative for NRZ signalling. There is almost the same BW as the channel with 5 mil stub, which was the original objective. But because PAM-4 is more sensitive to impairments, it shows there is less margin.

In summary then, rules of thumb and related equations are a good way to reinforce your intuitions or to give you an answer sooner rather than later. They help you know what to expect before you take any measurements or perform any simulations. But they should never be used to sign off on any high-speed design.

Because every system will have different impairments affecting BER, the only way to know how much margin you have is by modeling the via with a 3-D EM field solver, based on the actual stackup and simulating the entire channel complete with crosstalk, if margins are tight. This is even more critical for data rates above 10 GBd/s.

So to answer the original question, “*are all via stubs bad*”? Well, the answer is it still depends. For NRZ signalling, there is more leeway than for PAM-4. But you now have a practical way to quickly quantify the answer if you know the stub length, baud-rate and delay through the via.