So you've got this little crystalline component on your hands, and you need to know what to hook it up to. Fair enough. It's one of those questions that sounds simple until you actually start looking into it, and then the terminology starts blurring together — oscillator, resonator, crystal, load capacitor — and suddenly you're wondering if you've accidentally wandered into a different field entirely.
Here's the short version: a microcrystalline unit (often just called a "crystal" or "crystal unit" in datasheets) should be connected to an oscillator circuit, typically inside a microcontroller or a dedicated oscillator IC. But the real answer is a little more interesting than that, and understanding why will save you a lot of headaches down the road.
What Is a Microcrystalline Unit, Really?
A microcrystalline unit is a tiny slab of quartz (or sometimes another piezoelectric material) that's been precisely cut to vibrate at a specific frequency when you apply a voltage across it. The "microcrystalline" part refers to the structure of the quartz itself — it's not a single perfect crystal, but rather a polycrystalline aggregate that's been engineered for stable, predictable resonance.
In practice, you usually just call it a crystal resonator or crystal oscillator component, and you find them in basically every electronic device that needs to keep track of time. Your microcontroller, your WiFi module, your Bluetooth chip — all of them have one somewhere.
The unit has two pins (or more, in surface-mount packages with extra pads for mechanical stability). Now, it doesn't do anything useful on its own. It's a passive component. It needs a circuit around it to actually oscillate.
Why the "What Connects to What" Question Even Matters
Here's what most people miss: a crystal isn't like a resistor or a capacitor where you can just stick it in a circuit and it behaves predictably. It's a resonant* device, which means it interacts with everything around it — the traces on the PCB, the input capacitance of the chip, the supply voltage, even the temperature.
If you connect a crystal to the wrong thing, or to the right thing but with the wrong supporting components, you'll get one of three problems:
- It won't oscillate at all — the circuit can't get going.
- It oscillates at the wrong frequency — your real-time clock drifts, your UART fails, your radio won't link up.
- It oscillates unstably — sometimes works, sometimes doesn't, especially across temperature.
This is why people ask the question. And this is why "just connect it to your microcontroller" isn't quite a complete answer, even though it's technically the right starting point.
What a Microcrystalline Unit Actually Connects To
Let's get specific.
The Oscillator Circuit Inside a Microcontroller
Most modern microcontrollers — STM32, ESP32, PIC, AVR, MSP430, you name it — have built-in oscillator circuitry. Plus, the datasheet will call it something like "external oscillator" or "HSE" (high-speed external) or "XOSC. " That built-in circuit is the actual oscillator. The crystal you solder on is just the frequency-determining element.
So when someone asks what to connect a microcrystalline unit to, the answer is: connect it to the oscillator pins of your microcontroller or IC, and add the supporting components the datasheet specifies.
Load Capacitors
Almost every crystal needs two external capacitors, one on each pin, going to ground. Now, these are called load capacitors* and their value is critical. The datasheet for the crystal will specify a load capacitance (often something like 12 pF or 18 pF), and you have to pick capacitors that, combined with the stray capacitance of your PCB and the input capacitance of the chip, match that value.
There's a common formula floating around — something like C_L = (C1 × C2) / (C1 + C2) + C_stray* — and it's worth understanding, even if you just ballpark it. Get this wrong and your crystal will be off by tens of ppm. And for a 32. Day to day, 768 kHz watch crystal, that can mean seconds of drift per day. For an 8 MHz system clock, it can mean your USB won't enumerate.
The Power and Ground Domain
The crystal connects to a circuit that needs a clean, stable power supply. Noise on the supply rail can couple into the oscillator and cause phase noise or jitter. In practice, this means you usually want a decoupling capacitor close to the IC's power pin, and you want the crystal traces to be short and surrounded by ground.
The PCB Itself
Here's the part that surprises beginners. Now, the trace length, trace width, and the ground plane underneath the crystal all affect how it behaves. Worth adding: " This isn't superstition. Which means most datasheets will say something like "keep traces under 5mm" or "use a guard ring around the crystal. The crystal is also "connected to" the PCB layout. It matters.
The Different Scenarios You'll Actually Encounter
Not all crystals connect the same way. Here's how to think about it in practice.
Scenario 1: A Bare Crystal + Microcontroller
This is the most common case. You have a two-pin crystal (like an HC-49 package or a small SMD like the ABRACON ABM3B), and you solder it directly to the two oscillator pins on your MCU. You add two load capacitors to ground, and you're done.
The microcrystalline unit connects to the MCU's oscillator input pins (often called OSC_IN and OSC_OUT, or XI and XO).
Scenario 2: A Crystal Inside an Oscillator Module
Sometimes you'll buy what's called a "crystal oscillator" — a complete module that has the crystal and the oscillator circuit baked into a single package, with one output pin that gives you a clean square wave. In that case, you don't need load capacitors. Even so, the microcrystalline unit is already connected to its oscillator circuit internally. You just connect the output to whatever chip needs a clock signal.
For more on this topic, read our article on is water more dense than oil or check out what happens when molecules lose energy.
This is more expensive but takes the design headache away.
Scenario 3: A 32.768 kHz Crystal for Real-Time Clocks
These are the watch crystals. They typically connect to a dedicated RTC oscillator inside your MCU or your RTC chip. The same rules apply — load capacitors, short traces — but the frequencies are much lower, which means the capacitors are usually a bit larger (around 6 to 12 pF, sometimes higher).
Scenario 4: Crystals for Radio Modules
If you're hooking up a crystal to a radio chip (an ESP32's WiFi section, an LoRa transceiver, etc.Because of that, ), the rules are even tighter. RF crystals need precise load capacitance, and the layout usually has to follow a reference design exactly. Deviating by a few millimeters of trace length can shift the frequency enough to fail regulatory certification.
Common Mistakes People Make With This
I see the same handful of problems over and over.
Using the wrong load capacitor value. Either too high (crystal oscillates slow) or too low (crystal oscillates fast or won't start). When in doubt, check the crystal's datasheet and use the parallel* load capacitance, not the series* one, unless your circuit is configured for series operation.
Running the crystal traces across the board. Keep them short and direct. Don't route them over noisy power planes.
Forgetting the decoupling capacitor on the MCU's power pin. The oscillator and the digital logic share a supply, and any noise on the supply will show up as jitter on the clock.
Using a crystal that doesn't match the IC's specifications. Some ICs want a fundamental-mode crystal, others want an overtone crystal. Some want a specific ESR (equivalent series resistance) range. If the datasheet says 50 ohms max ESR and you use a crystal that's 100 ohms, it might not start up at cold temperatures.
Not considering the crystal's drive level. Crystals have a maximum drive level (usually in microwatts or milliwatts). If your oscillator circuit overdrives the crystal, you can damage it over time. This is rare with modern MCUs, but it shows up in older designs or when people mess with the biasing.
Practical Tips That Actually Save You Time
Look, here's what I've learned from dealing with these things across a bunch of projects.
First, start with the reference design. If you're using a popular MCU or radio module, the manufacturer has a reference design with specific crystal part numbers. Buy that exact part, follow that exact layout, and you're 90% of the way there. Don't try to be a hero.
Second, use a crystal with a built-in load capacitor if your
frequency is low enough (usually 32.768 kHz, sometimes up to a few MHz). These come in tiny packages and save you two external capacitors plus the board space.
Third, always prototype before committing to a layout. Crystal oscillator circuits are one of those things that look great in simulation but fail in practice. Build a quick breakout, test it with an oscilloscope, check the frequency accuracy, and then* design the PCB.
Fourth, mind the temperature range. Standard crystals drift with temperature, often by tens of parts per million. If you're building something that needs to work outdoors or in a harsh environment, look for an oven-controlled crystal oscillator (OCXO) or a temperature-compensated one (TCXO). They're more expensive, but they keep your frequency stable.
Fifth, **check the startup time.Consider this: ** Some crystals take longer to stabilize than others, especially under cold conditions. If your MCU has a timeout on its oscillator startup, you might need to extend it or use a crystal with better startup characteristics.
How to Debug a Crystal That's Not Working
If your circuit isn't oscillating, here's a quick checklist:
- Verify the crystal is actually the right part. Sounds obvious, but I've seen people grab the wrong reel or misread a part number.
- Check the load capacitors. Are they the right value? Are they actually connected? A bad solder joint on a tiny cap is a common culprit.
- Measure the power supply. If the MCU or oscillator chip doesn't have clean power, it won't oscillate reliably.
- Look at the waveform with an oscilloscope. A good crystal oscillator produces a clean sine wave (or clipped sine) at the specified frequency. If you see a distorted waveform, or no waveform at all, something is wrong.
- Try a different crystal. Sometimes you just have a bad part. It happens.
If you've gone through all that and it still doesn't work, the problem is probably in the layout — long traces, missing ground plane, or capacitance that you didn't account for.
Wrapping Up
Crystals are one of those components that seem simple but have a lot of subtle behavior. Day to day, the good news is that for most everyday projects, you can get away with following the reference design and using a common crystal with standard load caps. But when you need precision, or when you're dealing with RF, the details matter.
The next time you're reaching for a crystal, take a second to check the datasheet, match the load capacitance, keep your traces short, and don't forget the decoupling. Your circuit will thank you, and you'll spend less time debugging and more time actually building the thing you wanted to build in the first place.
