You’re an embedded developer, not a PCB layout engineer. I get it.
You write firmware, debug protocols, maybe spin a test board every few months. And when you do, you expect it to just work.
But too often, the board comes back, you power it up, and… something’s off. I2C has glitches. The ADC reads noisy. The prototype works, but the second batch behaves differently.
After reviewing hundreds of designs sent to our PCBA shop, I’ve seen the same five mistakes again and again – even from experienced developers.
Here’s what they are, why they happen, and how to fix them before you hit “order”.
1. Decoupling capacitors: close is not close enough
What I see:
A 0.1µF capacitor placed 15mm away from the IC power pin. “It’s on the same net, right?”
Why it fails:
Every millimeter of trace adds inductance. At high frequencies (especially with modern MCUs running at hundreds of MHz), that inductance kills the capacitor’s ability to supply instantaneous current. The result: voltage droop, logic glitches, and EMI.
Fix:
- Place the smallest-value capacitor (usually 0.1µF or 0.01µF) as close as possible to the power pin – within 2-3mm.
- Put the capacitor on the same layer as the IC, not on the back side (unless you use a very short via).
- Connect it with a short, wide trace directly to the pin and its return via.
Pro tip: The capacitor’s loop area matters more than its exact value. Keep the power‑to‑ground loop tiny.
2. Floating inputs – the silent killer
What I see:
Unused pins on a microcontroller or sensor left completely unconnected. “I’ll configure them as outputs in software.”
Why it fails:
Before your firmware boots, those pins are in a high‑impedance state. They can float to an indeterminate voltage, oscillate, couple noise, and even cause the device to latch up or draw excess current. I’ve seen perfectly good boards fail self‑tests because a single unused input was picking up 50Hz hum.
Fix:
- Tie unused inputs to GND or VCC through a resistor (typically 10kΩ).
- Or configure them as outputs in software before any delay loops. But hardware pulldowns are safer.
Exception: Some pins (like RESET, JTAG, boot configuration) have specific requirements – check the datasheet.
3. Power supply sequencing ignored – or guessed
What I see:
A board with multiple voltage rails (3.3V, 1.8V, 1.2V) powered from separate regulators. The developer assumes they’ll all rise at the same time. They don’t.
Why it fails:
Many modern MCUs, FPGAs, and SoCs have strict sequencing requirements. If the core voltage arrives before the I/O voltage (or vice versa), the device may latch up, fail to boot, or suffer long‑term reliability damage. Power‑on reset circuits might not help if the ramp rates are mismatched.
Fix:
- Read the power sequencing table in the datasheet. It’s there for a reason.
- Use a power sequencer IC (e.g., TPS3808, LM3880) or design the enable pins of your regulators to follow the required order.
- If the design is simple, add a low‑dropout diode and a capacitor to delay one rail. Not perfect, but better than guessing.
Quick test: Probe each power rail with an oscilloscope at power‑up. Look for cross‑conduct or unexpected spikes.
4. Forgotten return current path – the invisible trace
What I see:
A neat four‑layer stackup: top signal, inner GND, inner power, bottom signal. Then the developer runs a high‑speed clock trace across a split in the ground plane – or worse, switches layers without a nearby return via.
Why it fails:
Current always returns to its source via the path of least impedance. At high frequencies, that path is directly under the signal trace (lowest loop inductance). If you cut the reference plane (e.g., a gap for isolation), the return current has to detour – creating a large loop that radiates EMI and couples noise into other signals.
Fix:
- Never route high‑speed signals ( >10 MHz) over a split in the ground plane.
- When switching layers, place a ground via within 1‑2mm of the signal via to give the return current a short path.
- For two‑layer boards (no internal plane), route critical signals with a ground trace alongside (coplanar waveguide) or flood copper and stitch with vias.
Golden rule: Think of every signal trace as the top half of a loop. The bottom half is the return path – don’t break it.
5. Selecting the wrong PCB finish (HASL vs. ENIG vs. others)
What I see:
A developer chooses the cheapest finish – HASL (Hot Air Solder Leveling) – for a fine‑pitch component or an edge‑card connector. Then they wonder why the board won’t solder properly or the gold fingers wear out.
Why it fails:
HASL leaves an uneven surface (up to 25µm variation) that causes tombstoning on 0402/0201 passives and poor coplanarity on QFNs/BGAs. For edge‑card connectors, HASL is too soft and oxidizes quickly.
Fix – match finish to application:
Advice for developers: For most prototype boards with QFPs, QFNs, or BGAs, pay the extra for ENIG. It’s flat, solderable, and reliable. For simple through‑hole boards, HASL is fine.
Bonus: The “it worked in simulation” trap
Simulation is great. But it doesn’t know about your real PCB’s parasitics – via inductance, trace capacitance, copper roughness, or the fact that your ground plane has slots for connectors.
One real‑world example:
A developer simulated a 24‑bit ADC with a clean reference voltage. On the actual board, the same reference had 10mV of ripple because the return path crossed a power‑plane split. The simulation never caught it.
How to avoid:
- Build a minimal test board (or an evaluation module) before committing to a complex design.
- If you can’t afford two spins, add extra test points and 0‑ohm resistor jumpers to isolate sections.
- Review your layout with a checklist (like the one at the end of this article).
PCB layout checklist for embedded developers
Use this before sending Gerbers to your manufacturer:
Final thought
You don’t need to be a PCB design expert. But avoiding these five mistakes will save you weeks of debugging, reduce board spins, and help your firmware run as intended – not as the hardware accidentally allows.
At AnyPCBA, we focus on small‑to‑medium batch PCB fabrication and PCBA assembly. If you’re unsure about your layout, or just want a second pair of eyes, feel free to share your design with us. We don’t charge for design reviews – we give honest, practical feedback based on real manufacturing experience.
👉 AnyPCBA – small‑to‑medium batch PCB & PCBA
https://www.anypcba.com/
Top comments (0)