Real Time with… AltiumLive Europe 2020: Eric Bogatin’s ‘Unlearning’ Keynote

Reading time ( words)

I admit to not being a Star Wars freak, but I am impressed by Yoda’s iconic wisdom and philosophy and intrigued by his advice that, “You must unlearn what you have learned.” Attending Dr. Eric Bogatin’s keynote at the AltiumLive Europe 2020 Virtual Summit was an enlightening experience and left me in no doubt of Dr. Bogatin’s iconic status in our industry. I was fascinated not only by his technical knowledge of signal integrity but also by his unique lateral-thinking approach both to managing it and teaching it.

Dr. Bogatin considered that Yoda’s advice applied just as well to some aspects of circuit board design as it did to mastering the Force. There were many myths and myth-conceptions about the best design practices for circuit board layout, which were “legacy code”—inherited practices based on older technologies that had been superseded by newer versions.

“It is time to rethink legacy code,” Dr. Bogatin declared. “The notions we have been carrying a round for many years may no longer be the best recommendations to follow,” as he listed a series of examples: the myth of three capacitor values, the myth of copper pour, the myth of split ground planes, the myth of power planes, the myth that stripline traces don’t radiate, the myth of ferrites on power rails, the myth of ninety-degree bends, and the myth of matched-length traces. He chose to discuss in detail the first two myth-conceptions on this list in the context of power integrity and signal integrity.

“Once connectivity is established, interconnects just screw things up!” The connectivity of a PCB was basically a netlist defined in the schematic and told nothing about the actual performance of the interconnects. The schematic portrayed them as ideal conductors. It was not until the schematic was turned into a physical layout that the effects of the interconnects became apparent; unfortunately, the only thing they could do was screw things up. They could never add performance to the system—only noise. One of his students had commented that “interconnects suck” and that the mission of the designer was to “make them suck less.”

He looked at two aspects of how interconnects could screw-up system performance and what could be done to “minimise how much they sucked.” His first example was power integrity, which encompassed at least 12 different problems. He chose one to explore: switching noise on the power rail, which occurred when the system changed state and illustrated the effect with a simple schematic of a voltage regulator module. When the schematic interconnects became physical conductors on a circuit board, those conductors added inductance as the inputs/outputs were switching, causing switching noise. The inductance could be reduced by using decoupling capacitors.

An alternative to simulation was to build a physical model and measure it. Dr. Bogatin showed a simple example to illustrate where to place the decoupling capacitor, demonstrate how it worked, and measure the effect of different values and positions, with the objective of minimising the residual loop inductance to the device and hence minimising the switching noise. How do you choose the decoupling capacitor? His advice was to select it on the basis of how much it could reduce inductance.


“If the goal is to provide low loop inductance, use small physical size capacitors because they have low loop inductance at high frequency.” Popular design guidelines recommended that when adding decoupling capacitors to the pads of an IC, three different values should be used in parallel: a 0.1-microfarad, a 1.0-microfarad, and a 10-microfarad, with the small one to give low loop inductance and the largest to give sufficient charge storage capacity.

But this concept belonged to the days of through-hole components and did not necessarily apply to SMT. The present reality was that high-frequency impedance was not about capacitance but about lead inductance and a high-frequency capacitor simply had low loop inductance. In the case of surface-mounted capacitors, his examples of 0.1-, 1.0-, and 10-microfarad components all had the same body size and no leads; therefore, they all had the same loop inductance.


The amount of capacitance was not about body size or loop inductance. The quality of a capacitor was solely about the loop inductance it contained when it was mounted into the board and not about the amount of capacitance. With surface-mount capacitors, it was absolutely not true that three different capacitors were needed because the 10-microfarad capacitor, if chosen correctly, could have just as low a loop inductance as the 0.1-microfarad capacitor. Low loop inductance was the key feature being designing for, with as much capacitance as possible within the chosen body size. Multiple capacitors could be used if necessary as long as they were large enough to damp-out parallel resonances, but there was absolutely no need to use three different values. That was legacy code, although he still saw many examples in current designs.

Dr. Bogatin’s second topic related to the common practice of copper-pouring on signal layers after routing all the signal lines and connecting the copper pour to the ground net in the belief that it would result in lower crosstalk or less electromagnetic interference. He demonstrated why it was not a good thing to do and gave simulated examples of the consequences by measuring the crosstalk between widely-spaced transmission lines. The first example had no copper pour between the lines. The second had a full copper pour, electrically floating, the third had a full copper pour tied to earth with a series of closely spaced via holes.


With no copper between the lines, there was very slight crosstalk. Floating copper between the lines made it slightly worse. Grounding the copper gave very slightly less crosstalk, but the differences were minimal. Changing to a signal with a shorter rise time, there came a point where it matched the resonant frequency of the floating copper and greatly increased the crosstalk compared with the no-copper example.

The grounded copper again gave a minimal reduction in crosstalk. And that was with a high density of grounding vias. If the number of vias was reduced, the crosstalk approached that of the floating-copper example. All this demonstrated that copper fill was not solving a crosstalk problem but potentially creating one. Legacy code again! “It’s never too late to rethink legacy code and unlearn what we have learned.”

Dr. Bogatin remains iconic in the electronics design community as a leading technical authority and a wise mentor. His teaching skill strikes a balance between over-simplification “signal integrity for tiny tots” and over-complication “blinding you with science.”

And, by the way, another famous quote from Yoda is, “Always pass on what you have learned.”



Suggested Items

Why We Simulate

04/29/2021 | Bill Hargin, Z-zero
When Bill Hargin was cutting his teeth in high-speed PCB design some 25 years ago, speeds were slow, layer counts were low, dielectric constants and loss tangents were high, design margins were wide, copper roughness didn’t matter, and glass-weave styles didn’t matter. Dielectrics were called “FR-4” and their properties didn’t matter much. A fast PCI bus operated at just 66 MHz. Times have certainly changed.

DFM 101: PCB Materials

04/30/2021 | Anaya Vardya, American Standard Circuits
One of the biggest challenges facing PCB designers is understanding the cost drivers in the PCB manufacturing process. This article is the first in a series that will discuss these cost drivers (from the PCB manufacturer’s perspective) and the design decisions that will impact product reliability.

Eliminating ‘Garbage In, Garbage Out’ With Checks and Balances

03/26/2021 | Nick Barbin, Optimum Design Associates
The proverbial saying “garbage in, garbage out” holds true in the electronic product development world. PCB designers stand squarely in the middle of a busy information intersection flowing with inputs and outputs. Missing or bad information at the beginning of a design project will undoubtedly lead to board re-spins, increased costs, and most importantly, a delayed product release. The same can be said about the PCB designer who doesn’t provide a fully checked and comprehensive data package to the downstream manufacturers, i.e., “throwing it over the fence.”

Copyright © 2021 I-Connect007. All rights reserved.