Noise Countermeasures Explained in Twenty Minutes

The following text was originally written for a particular occasion, but since it contains content with a high degree of public value, I decided to extract it and publish it separately.
I’ll write about things that might be useful, from how radiation occurs to clues for countermeasures and practical operational approaches. The content leans fairly practical, so I’ve kept it reasonably concise (whether that means 20 minutes of reading time depends on the reader). If you want to dig into the finer theoretical details of electromagnetism, consult a proper textbook.
Most of my foundational knowledge of electromagnetism comes from this textbook I used in university.
My hands-on experience with countermeasures against unwanted radiation is largely based on my time at a certain major company. (I spent many days holed up in anechoic chambers, over and over again…) The power supply circuits were often proprietary, and many products had board configurations that were effectively bolted-on extensions added after the fact — a fairly troublesome category of product for unwanted radiation countermeasures, and I think I gained a lot of experience working on them.
First, about radiation
“Unwanted radiation” is also called “unintentional radiation” — in other words, radio waves are being emitted that weren’t meant to be emitted.
Where does it come from? The answer is “everywhere in an electronic circuit,” to varying degrees. That said, in a system where current flows cleanly, almost no radiation occurs. Here, “flowing cleanly” means going out and coming back cleanly.
Any signal is established as a system in which current supplied from a power source is converted into some form and sent out somewhere, and once it’s caught at a distant point (where it’s read as a signal), that current returns to the power source via some other path.
Which path this system chooses is basically determined by wherever impedance is lowest. (The roots of this go down to quantum theory — if you’re interested, it’s worth studying; it’s fascinating.) But on a typical PCB, current can’t go back and forth that cleanly (it gets forced into detours, reflects off dead ends, and so on), so imbalances occur in current density.
When I was in the Bay Area I worked alongside an NVIDIA layout designer and saw his designs — he skillfully used traces at subtle angles that were neither vertical (90 degrees), horizontal (0 degrees), nor diagonal (45 degrees) as you commonly see on typical boards, along with gentle curved traces. That’s a design consideration aimed at minimizing imbalances in current density and avoiding unnecessary inductance or reflections.
When current density becomes imbalanced, some of the charge can’t cleanly return to the power source and jumps out looking for somewhere to go. Roughly speaking, this is the source of unwanted radiation. The charge that jumps out looks for a way back, via the lowest-impedance path. The point expected to have the lowest impedance relative to the negative side of the power supply is normally GND. So if there’s a GND near the area with imbalanced current density, the charge jumps there, and radiation ends up at a very low level as a result.
But if the impedance from GND to the power source isn’t as low as expected, or there’s no effective GND nearby, the electric field lines end up looping all the way out, and an electric field is generated — in other words, unwanted radiation is observed. To avoid this, common techniques applied to GND include:
- Putting a huge number of VIAs into GND
- Widening the GND area
- Making an inner layer a solid GND plane
- Placing GND on both sides of high-speed signals
Roughly speaking, all of these are measures to lower impedance so current returns cleanly.
So, for now, what can be said about radiation is:
- It doesn’t come out evenly from everywhere; it’s concentrated and stands out from some specific location (often described as “blowing out” from somewhere)
- Imbalances in current density are affected by every possible condition, so honestly they’re hard to read
Clues for countermeasures
What can actually be done about unwanted radiation hasn’t really changed much, no matter how the times change, no matter the age of AI and big data, no matter if a singularity arrives.
- Hit the source
- Strengthen power/GND countermeasures
- Assume radiation will occur and cover up the smell
Hitting the source
The idea here is to “hit” the source — the original oscillator or clock. This is an extremely fundamental countermeasure, so if you can pull it off, the countermeasure work is complete.
Concretely, “hitting” means:
- Reducing harmonics
- Reviewing traces and GND
The closer a waveform gets to a square wave, the more harmonics the signal produces. It’s common to see unwanted radiation failures at 20MHz or 30MHz even though the main clock is 10MHz. That’s due to harmonics. Generally, the higher the frequency, the harder it tends to be to deal with, so lower frequencies are always preferable. Therefore, dulling the waveform within an acceptable range can be an effective countermeasure.
Something similar happens when signal reflections (such as ringing) occur due to impedance mismatch.
Also, if harmonics remain, since current density distribution is frequency-dependent (because various impedances have frequency characteristics), you often end up in a whack-a-mole situation — “we hit the 3rd harmonic and the 5th showed up” — a classic occurrence in unwanted radiation countermeasures.
Concrete ideas for countermeasures:
- Insert an RC (or LC) into the clock or high-speed signal
- Insert a damping resistor or ferrite bead into the clock or high-speed signal (to prevent reflections)
When developing a product, it’s common to create a “clock table.” This compiles the frequencies of the source crystal or PLL, the clocks used for communication, and so on. It serves as a reference when actually tackling countermeasures.
Common examples generally include things like:
- USB (480MHz, 12MHz, etc.)
- SoC oscillators (tens of MHz)
- SDIO (~200MHz or so)
- Audio MCLK (24.576MHz, etc.)
In cases like this it’s preferable to limit your thinking to “things that appear externally as a signal.” Why? Because if that clock is blowing directly out of the silicon itself, countermeasures can only be taken internally — and the noise presumably exits externally via power/GND anyway, so that’s where you should be hitting it.
Oscillator systems
Places like oscillators are probably very simple circuit-wise. So what you need to watch for is:
- Whether the trace is efficiently connected over the shortest possible distance
- Whether the signal is bouncing back and forth between layers via vias
That’s about it. In other words, there isn’t much you can do in cases like this.
Also, when the generated clock is forced to travel a long route, it’s common to route it on an inner layer. This is a typical countermeasure to make it noise-resistant by sandwiching it between GND layers. There’s some debate about this — personally, I think there’s also a reasonable argument for keeping it on the surface, since that leaves room for countermeasures (such as adding a damping resistor or a capacitor to form a filter).
Communication systems
I touched on communication-related clocks above, but if radiation does occur, USB is probably the toughest case.
That’s because USB needs to maintain a clean eye pattern to guarantee communication performance. That means you can’t casually dull the signal (ruling out the easiest countermeasure).
Conversely, there are also cases where the USB communication itself is noisy and that’s where the radiation is blowing from. In such cases, reflections are almost always the root cause, and suppressing reflections kills two birds with one stone — “the waveform gets cleaner and communication errors decrease” and “unwanted radiation goes down.” For example, checking differential impedance with something like a TDR might reveal exactly where the reflections are occurring.
Communication systems very often consist of multiple signals sharing the same source and destination. That means the signals usually run in parallel. Generally, signals running in parallel are prone to noise coupling. For example, trouble can occur when an analog signal (such as audio) runs parallel to a clock and picks up noise. It’s the same idea. If you keep in mind which high-speed signals deserve some wariness, it’s good practice to keep them as far as possible from noise-sensitive signals, or, if that’s difficult, to design the board so that R or C components can be added later.
Strengthening power/GND countermeasures
What you need to think about is: “how do we return the noise generated in the power supply or signals to GND as gently as possible?”
Reviewing decoupling capacitor placement and values
In addition to the GND-strengthening measures already illustrated, “reviewing the placement and values of decoupling capacitors” is also a kind of GND-strengthening measure. Capacitor impedance has frequency characteristics — generally, small values pass high frequencies, while large values don’t pass them as well. Roughly speaking, the former helps reduce AC-type noise, and the latter helps reduce DC-type noise.
If you already know exactly which band is causing unwanted radiation failures, it can be effective to change the capacitor values specifically to “smoothly return to GND” in that band. That’s because changing impedance changes the current density distribution.
For example, MCUs often have multiple decoupling capacitors hanging off the same potential. Roughly speaking, those capacitors serve two roles: one is to support power supply on the DC side, and the other is to lower the power supply’s impedance against high-frequency noise. This type of decoupling capacitor is often connected to a sizeable GND nearby, so if that power rail is noisy, adjusting or adding decoupling capacitor values can sometimes lower the noise level.
Something in series with power/GND
Noise is current. So if you dissipate it as heat through a resistor, the noise itself disappears. That said, carelessly increasing an impedance component that’s active at the frequencies used for DC or communication can cause operational problems. If the noise frequency is far higher than the communication frequency, inserting a filter or a ferrite bead in series with power/GND to sharply cut that band can be very effective.
When applying this idea, you also need to pay attention to whether the noise is coming from outside that power system or being generated inside it. If it’s coming from outside, even if the noise frequency overlaps with the communication frequency, you can first cut it off sharply, then build a mechanism inside the power system to cover short-term power supply via adjustments to decoupling capacitor values. Happy ending. When doing this, it helps to think of a capacitor as something like a battery with a frequency-dependent internal resistance called impedance. In other words, for short-term, small-quantity supply, a smaller value is suitable, while for medium- to long-term, large-quantity supply, a larger value is suitable. Beyond that, it’s a matter of cut-and-try.
If an AC adapter, USB bus power, or switching power supply noise is the cause, hitting it there can be expected to bring levels down quite a bit. It’s preferable to think about this mainly from the perspective of what to do at the device’s entry point.
On the other hand, from the perspective of a power IC, it’s something to avoid at all costs for each IC to be contaminated with noise and feed that back into the power IC. Concretely, the simple solution is to cut it with something like an LC filter. And when you ask “which power rail is prone to getting contaminated?”, the usual suspects are the CPU, memory bus, DSP, FPGA, GPU, and so on.
Covering up the smell
The last resort. This is about after-the-fact countermeasures.
Shielding
This is the method used in many communication modules. Naturally it reduces noise, and it also makes it easy to satisfy the Radio Act’s requirement that a “module” be difficult to modify, which is why many modules come with shielding.
Sheet metal, if you’re able to add it, is the strongest noise countermeasure component there is. But be sure never to forget to connect that sheet metal to GND. Sheet metal left floating electrically acts as a new antenna or reflector. A classic example of a reflector being skillfully put to use is the Yagi antenna.
Making cables twisted pair
Twisted pair is effective when noise generated somewhere is riding on the cable. Cables are basically very capable antennas. Noise riding on a cable tends to go somewhere and cause trouble, so it should be removed. Detailed explanations of the twisted pair effect are all over the internet, so I’ll leave that to those sources. In short, it’s a Columbus’s-egg kind of trick: the electromotive force induced on the cable by noise is made to run in opposite directions at close range, so the two cancel each other out.
Other desperate measures
- Wrapping a ferrite core around the misbehaving signal line
- Changing the routing (if there’s sheet metal, attaching and securing it there)
- Sticking on RF absorber sheets here and there
- Electrically connecting dirty GND to a point close to earth ground
These kinds of measures often work quite well, but they tend to increase manual work or require expensive countermeasure parts, and are often not desirable as medium- to long-term solutions, so honestly they’re a dilemma.
What to do when starting countermeasures
Given the ideas for countermeasures described above, what you should do when starting is to clarify, as precisely as possible, which source oscillator corresponds to the frequency that’s failing. Units with multiple clocks at similar frequencies in several locations deserve particular caution.
The steps are:
- List the frequencies present on the board and narrow down candidates
- If it’s possible to stop a clock via software, try stopping it (or clocking it down)
- If it can’t be stopped, cut off the circuit by, for example, removing a component
A handy tool during this process is a portable simple spectrum analyzer. The one I use is this one (cheap, but surprisingly capable):
RF Explorer Spectrum Analyzer, compact handheld digital pocket-size spectrum analyzer (3G Combo)
Know-how for pinpointing the source ① “Take it apart”
If you’re using components where stopping the clock isn’t easy, you may have no choice but to observe things with everything running. With small devices or boards placed close together, you often can’t tell where it’s coming from.
In such cases, it’s effective to stretch out the cables and physically separate the boards. Take them out of the enclosure, lay the boards out on a desk, and scan over them with the spectrum analyzer. Of course, this doesn’t preserve strictly accurate conditions — it’s purely a way to pin down where the radio waves are blowing from.
Know-how for pinpointing the source ② “Hit it ‘directly’ with the spectrum analyzer”
A spectrum analyzer is generally understood to be something you attach an antenna to. That’s true, but there’s actually a different way to use it: attaching a probe instead (you can observe things normally this way). By directly probing a component or directly probing GND, you can see disturbances in current density in quite fine detail. The key points of caution are as follows:
- Use a probe made with high-frequency-capable coaxial cable
- Don’t touch the terminal directly — attach something like a 1pF leaded ceramic capacitor to the tip of the probe and touch the component through that (DC getting in will break the spectrum analyzer)
This might be a bit advanced.
Know-how for pinpointing the source ③ “Touch it by hand”
The human body is actually a fairly capable noise countermeasure component (it has capacitance, and in many cases is grounded), so sometimes you can observe radiation dropping just by touching something with your hand. If you find such a spot, that’s your countermeasure target.
Along similar lines, sometimes just touching a cable brings it down, or touching two specific points at once brings it down. These can be big hints for countermeasures.
Cautions when pinpointing the source
- Radio waves have polarization. You need to keep changing the antenna orientation and testing, or you can miss things
- Below 1GHz, you also need to be concerned about radiation in directions other than horizontal (such as radiation toward the floor). Above 1GHz, conversely, you don’t need to worry about anything other than horizontal
- Create a radio-quiet environment
What to think about after you’ve found where the radio waves are blowing from
Once you’ve found where radiation is coming from, before jumping straight to “okay, countermeasures!” there are a few things worth thinking through carefully.
Whether the blowing location matches the source location
The first very important point is whether the location where it’s blowing matches the location of the source oscillator.
If they match, the countermeasures available are quite limited. For example, if a processor’s internal clock is blowing directly out of the processor, often the only option is shielding (metal or RF absorber).
That said, you don’t see this much in recent CPUs and GPUs (manufacturers have already dealt with it), so basically all you need to keep in mind is that in this case, your options are very limited.
Communication path or power/GND
If it’s a communication path, you’re relatively in luck. For example, radiation blowing out of FFC cabling is quite common. In that case, wrapping it with copper foil tape as a shield can bring levels down quite a bit. If it’s a trace on the board, just applying copper foil connected to GND or an RF absorber sheet can resolve it cleanly.
In these cases, a stopgap countermeasure is relatively easy, but since the processing is labor-intensive or costly, you should basically fix the board eventually. For example, for cable routing, building an RC or LC filter near the connector, or inserting a countermeasure component like a common-mode choke, could make it disappear cleanly; for board traces, properly implementing guard GND or inner-layer GND could resolve it.
The most troublesome case is when it’s blowing from the power/GND system itself.
It seems to be coming from a broad area (multiple locations), and the power/GND plane is the culprit
When it’s coming from a plane, it’s genuinely troublesome. Here’s why:
- Hitting one spot usually makes another spot show up (whack-a-mole — it takes time to resolve)
- If your investigation has gotten to this point, it suggests a pattern where “we couldn’t hit the source” and additionally “it wasn’t coming from any one specific, easy-to-hit location.” In that case, the only options left are “spread it out” or “seal it off”
“Spread it out” means dispersing the noise as much as possible — building a tight connection structure for the power and GND, as already described above, so current flows as cleanly as possible. There’s no magic bullet that resolves this in one shot; it’s steady, incremental work (whack-a-mole).
Simulation is the classic approach used since ancient times to avoid falling into whack-a-mole.
Murata’s Femtet is a monster of a solution, yet it’s quite reasonably priced, I think. https://www.muratasoftware.com/
“Seal it off” is the “cover up the smell” approach already mentioned. No further comment needed.
There’s also a slightly unconventional option: “deliberately create an imbalance and hit it there.”
Concretely, this means cutting off the power/GND at high frequencies as much as possible. By doing so, you can limit where the noise can go, and then hit it there. However, each power/GND becomes weaker as a result, so doing this on a small board can leave you with no remaining options and stuck. It’s a tricky balance.
General remarks
Unwanted radiation countermeasures are often constrained by stage, schedule, budget, and so on. If you have time and budget to spare, remaking the board is the proper path. It’s not a bad idea to run a simulation at that stage either (ideally you’d do it from the very start, but it’s hard to justify the effort until the risk actually materializes). If you’ve foreseen the risk in advance (say, you’re carrying over the design of a board or module that gave you trouble before), I’ve personally done things like loading up the board with as many 0Ω resistors as I could think of, just in case. Then, if radiation turns out to be a failure, you swap those out for countermeasure components.
So, the cases where unwanted radiation countermeasures become a real headache are mostly ones lacking that kind of margin or advance preparation (which makes sense).
That tends to lead to a “let’s just slap stuff on everywhere and wing it!” approach (I did plenty of that myself when I was starting out), but knowing the principles and overall picture described above can be useful in several ways:
- Applying things precisely to where the radio waves are actually coming out (is it a plane? a cable?)
- Choosing what to apply based on whether you’re turning the noise into heat or returning it to GND
- If you’re aiming for shielding by expanding GND, being careful not to inadvertently create a spot where current density spikes
And so on. The countermeasure work itself will involve a certain amount of trial and error, but there’s a huge difference between groping around with this knowledge in your head versus groping around in the dark.
Bonus
L or R?
If you’re inserting something in series to suppress noise, the candidates are L (such as a ferrite bead) or R (a resistor).
L has frequency characteristics, which makes it well-suited to the goal of “cutting a specific frequency.” R itself can be a source of DC voltage drop, which at first glance makes it seem tricky to use.
However, when you use an L in series, an LC filter is formed whether you intend it or not, and whether or not there’s a decoupling capacitor present. That’s because the input capacitance of the IC downstream of the L, the board’s capacitance, and various other C’s are always attached. The frequency characteristics of an LC filter always show a resonance characteristic.
This means that at some point, the filter will act to amplify the noise instead (series resonance) — a case where you intended to weaken it at one location, but it ends up strengthened at another.
The trick for softening this effect is the ferrite bead. For example, with this Murata item https://www.murata.com/ja-jp/api/pdfdownloadapi?cate=cgsubChipFerriBead&partno=BLM03AG102SN1%23 the impedance characteristic looks like this.

If you bring this frequency close to the resonant frequency (by choosing a ferrite bead with that characteristic), the combined effect lets you cleanly cut the target frequency. Think it through properly, and cut it properly.
R, on the other hand, can be thought of very simply — just calculate the cutoff frequency and build an RC filter, and the noise drops off quite obediently. But that obedience is also its limit — you can’t do anything special with it (like creating a peak at a specific location).
Understand the pros and cons of each and use them accordingly.
Phased response across production lots
It’s a common story to roll out countermeasures progressively across production lots. You can probably imagine it easily: “The 1st lot ships next month, so the only countermeasure we can apply is RF absorber. But there’s about six months until the 2nd lot, so we can take proper countermeasures by then” — that kind of situation.
In that case, it can help to form two teams (or maybe just two people in charge) to tackle each piece, since the work involved is quite different. Short-term whack-a-mole is a battle of brute force and stamina. Long-term countermeasures, on the other hand, take an approach of solving things in one or two shots through careful calculation (including simulation) and redoing prototypes, rather than sheer number of attempts.
Skillfully combining both approaches, with an eye on timing, is know-how for the development field.
Originally published in Japanese at https://clazytech.com/2020/10/364/. Translated with LLM assistance and reviewed before publication.