Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics

Dashboard
Notifications
Mark all as read
Q&A

ESD USB Shield Connection & Filtering

+2
−0

I have a handheld ARM Cortex M based device, which has a USB input port.

The product is battery powered and there is no metal chassis.

We are going through CE testing, and are having ESD issues at 4kV contact to the USB shield with reproducibility under IEC 61000-4-2.

On the data lines of the USB port, we have TVS diodes that are working and shunt the ESD to PCB GND plane and the Cortex can keep functioning. When we air discharge at 8kV to the USB port, that TVS diode is working and the unit keeps functioning.

However, when we ESD shock the shield of the USB connector 4kV Contact Discharge (as per the standard), we appear to have some kind of ground bounce that can lock-up the unit.

Because the shield is tied to PCB GND and we don't have a metal chassis, what kind of filtering could we to the shield traces to PCB GND on an updated PCB revision which could help?

Would an RC filter (series R, parallel C) on each shield trace work? I'm trying to think of a filter that would dissapte the ESD to some extent before it hits the PCB GND Plane.

The PCB is tightly populated and 6 layers, so there isn't a whole lot of room for like a discrete PCB GND moat.

It's kind of surprising that the TVS diodes dumping ESD into the GND plane don't affect the microcontroller; however, if the shield dumps ESD into the GND plane it has a very strong effect.

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment

It sounds like a layout problem, though it is of course impossible to say without seeing the PCB layout. Otherwise, the most common reason for failing ESD tests is that something isn't grounded that should be grounded. Also, how is the shield connected? Did you ground it at one side of the cable or both? Lundin‭ about 1 month ago

4 answers

+2
−0

A few months ago, I too was looking for answers on how to connect the USB shield with ESD in mind.

I always connect the shield through a resistor to ground and a capacitor to ground (100kΩ and 0.01uF). Pulsing ESD into the shield is a part of the test. The ESD will appear across the capacitor, so it has to absorb the ESD pulse and survive. Can a reasonably sized ceramic capacitor survive? This article: Ceramic capacitors for ESD Protection in Automotive Applications (Vishay, 2020) mentions that an automotive grade ceramic capacitor 0.01uF, rated for 200V, in 0805 package can survive ESD pulses. The article details to what level per IEC 61000-4-2.

Because the shield is tied to PCB GND, [...]

Is your USB shield tied directly to PCB ground? The shield shouldn't be connected directly to ground on the device side. The shield should be directly connected on one end (either end). The other end should be floating, or AC-coupled to GND, but not directly connected to GND. A typical USB host (laptop, hub, wall wart charger) has the direct connection between shield and its ground[1]. Thus, the host end is that one end where the shield is directly connected.


  1. Such design choice is forced on us device designers. We aren't in control of the host hardware. ↩︎

Why does this post require moderator attention?
You might want to add some details to your flag.

0 comments

+2
−0

Your question is impossible to answer without carefully looking at the layout and schematic.

However, from gut feel and experience, this smells like poor grounding design. Common mistakes:

  1. Not a single board-wide master ground plane.

  2. Too many large islands in the ground plane. The metric of how broken up a ground plane is, is the longest dimension of any hole, not the number of holes. Lots of little holes with ground plane flowing around them is better than the same area in a single hole. That's even worse if that large hole is long and thin (large maximum dimension relative to its area).

  3. Bypass caps not right up against the power and ground pins they are connected to.

  4. The ground return of a bypass cap running across the master ground plane instead of locally connecting to the ground pin of the part it is bypassing. Bypass caps shunt high frequency currents generated by the chip they are bypassing. If you run that current across the ground plane, you don't have a ground plane anymore but a center-fed patch antenna.

    Maybe you don't care about the small amount of extra radiation, but antennas always work both ways. A better antenna also makes the circuit more susceptible to incoming radiation, like that broad band EMP of a static discharge.

  5. Sensitive or high-impedance traces not properly handled. A good example is the reset line of a CMOS microcontroller. One little glitch can really ruin your day. You want to make sure that the line is held solidly high during normal operation. This means a decent pullup, possibly with a small cap to ground. If the line has to run across the board, like possibly to a programming header, then consider what it runs next to and what cross-talk it might pick up. In noise situations, a little filtering close to the micro might be in order. That might interfere with programming though. You have to look at this issue carefully.

Curious that you mention bypass caps in the context of ESD, since a discharge is a extreme spike event, unlike the average EMI. To what extent do they help against ESD, aren't they generally far too slow, compared to TVS diodes etc?

Proper bypass capacitors are fast. Their impedance at high frequency is more important than their bulk storage properties. This is why relatively small values like 100 nF work well for bypassing, although they would be useless as bulk capacitance back at the supply, even though that would put them between the exact same two nets.

In the frequency domain, chips look like high frequency current sources between their power and ground pins. The purpose of a bypass cap is to shunt that current to keep it local and the loop small. When done right with proper layout (see #4 above), this keeps the high frequency currents off the much larger loop from the power supply, thru the chip, and back.

I once specified a particular model of 100 pF cap for bypassing a RF chip. After digging thru a bunch of ceramic capacitor datasheets, I found this cap to have lower impedance at the RF frequency than others, even though most of those others had significantly higher capacitance.

All real-world capacitors stop acting like capacitors above some frequency. Since bypass caps deal with high frequencies, they need to still work like capacitors at those frequencies. In our real world with real engineering tradeoffs, that usually means small ceramic caps up to 1 µF, and often lower. The 100 µF to multiple mF caps on the power supply are to store significant energy. They would be useless, however, for bypassing.

Take a look at a datasheet for a 100 µF electrolytic and a 1 µF ceramic. Compare the impedance versus frequency graphs. The 100 µF starts out with 100 times lower impedance, but quickly hits its minimum point with the impedance going back up after that. Note that the 1 µF ceramic keeps going lower in impedance, inversely proportional to the frequency over a much wider frequency range. The result is that the 1 µF has lower impedance to those frequencies that a bypass capacitor needs to address.


Your no 4 is fascinating. So, do you say that the cap should be connected to the ground pin of the part, and this later not connected to the the master ground, or do you say that the cap should be connected very close to the ground pin of the part, while this later may be connected to the master ground.

The latter. The chip still needs to be connected to ground solidly.

The bypass cap also needs to be connected solidly between the chip's power and ground pins. The point I was making is that the current thru the bypass cap should not run across the ground plane. Keep the nasty high frequency currents local and with a small loop area.

A good way to achieve this is to place and route the bypass cap connections with as short and straight traces as reasonably possible. Then put a via close to the ground pin so that the pin is connected to the board-wide ground. Since this via is a single-point connection, the loop current thru the chip and the bypass cap don't flow thru the via. The via is for the lower frequency power supply return current (after the bypass cap has shunted the high frequency current), and the general return currents from signals and the like.

Why does this post require moderator attention?
You might want to add some details to your flag.

6 comments

Curious that you mention bypass caps in the context of ESD, since a discharge is a extreme spike event, unlike the average EMI. To what extent do they help against ESD, aren't they generally far too slow, compared to TVS diodes etc? Lundin‭ about 1 month ago

@Lundin. Wha..? a cap is slow? it cannot help with ESD events? don't we have always V = Q/C, where Q is very small for ESD events? oh of course, if the cap has a high ESR, it may be too slow. Michaël Bensimhoun‭ about 1 month ago

@Olin. Your no 4 is fascinating. So, do you say that the cap should be connected to the ground pin of the part, and this later not connected to the the master ground, or do you say that the cap should be connected very close to the ground pin of the part, while this later may be connected to the master ground. Michaël Bensimhoun‭ about 1 month ago

@Michaël Bensimhoun‭ I don't know, hence the question. I was thinking of aluminium electrolytes but I guess the cap chemistry matters a lot? Lundin‭ about 1 month ago

I do lot of EMC testing, and agree with all these rules of thumbs, but specifically we are targetting the shield. The GND'ing is pretty much locked in place. I know much blood has spilt on the shield to GND plane discussion. (Also, bypass caps for ESD is a real thing...). We have a series 0402 footprint on the shield lines to GND [not my design, I'm involved on the ESD side], and I'm wondering on an RC or some other filter specifically. leroy105‭ about 1 month ago

Show 1 more comments
+1
−0

It's kind of surprising that the TVS diodes dumping ESD into the GND plane don't affect the microcontroller; however, if the shield dumps ESD into the GND plane it has a very strong effect.

That's what makes me think that the answer of Nick Alexeev is very relevant: the TVS diode has a small capacitance, and apparently, this capacitance absorbs much of the ESD shock, like the RC combination in Nick Alexeev answer. It would be interesting to try improving this RC combination by the following:

USB_grounding

Note: the RC network in Nick Alexeev's answer recalls me the so called "RC snubber" circuit.

Why does this post require moderator attention?
You might want to add some details to your flag.

0 comments

+0
−0

Curious about this because I have one of these coming up myself. I implemented an isolated USB (for other reasons, 24V system with some HV in it too) but customer pushing to take out the isolation.

Can you at least share a relevant portion of the schematic, including both USB and VDD?

I would think you want a low impedance connection betw. Shield and GND (short+fat, not long+skinny), try to prevent USB-VDD from becoming return path (but with battery power that may be unrelated). Go beyond minimum capacitance on your local VDD... ESD must eventually find way back to both Shield and GND. Want sensitive stuff out of that path. However VDD is typically in that path! (via TVS, including steering diodes inside chips). The way to resolve that is with layout...

Why does this post require moderator attention?
You might want to add some details to your flag.

0 comments

Sign up to answer this question »

This community is part of the Codidact network. We have other communities too — take a look!

You can also join us in chat!

Want to advertise this community? Use our templates!