How to: pick the right frequency for your oscillator

Try to think of the crystal oscillator as the "heartbeat" of your MCU, without a steady, reliable pulse (namely, the clock), the processor's "brain" simply can’t function. Most of the time, your design process is straightforward because the MCU manufacturer has already done the heavy lifting. If you check the datasheet, you’ll typically find a recommended part number or a list of specific requirements for frequency, Equivalent Series Resistance (ESR), and load capacitance (CL). When you're shopping for a crystal, you’ll see everything from 32.768 kHz to 50 MHz. So, how do you choose? It’s not always "faster is better."

Communication needs

First, look at your communication needs. This is the biggest trap. If you are using UART or CAN bus, you need a frequency that can be divided perfectly to hit standard baud rates (like 115,200 bps). If your clock speed is slightly off, your data will come out as gibberish. This is why frequencies like 7.3728 MHz or 14.7456 MHz exist, they actually divide perfectly into standard communication speeds with 0% error.

Power consumption

Next, you should consider power consumption. In the world of MCUs, Current = Frequency. If you run your chip at 48 MHz instead of 8 MHz, you’re going to drain your battery much faster. If your project just reads a temperature sensor once a minute, a high MHz crystal is just wasting energy.

MCU's limits

Finally, check your MCU's Limits. Every datasheet has a "Maximum Operating Frequency" section. Some chips can hit 100 MHz, but only if the voltage is high enough (e.g., 3.3V). If you’re running on a 1.8V battery, the silicon literally can't "flip" its internal gates fast enough, and you might be limited to a much lower MHz.

A little practical tip: you can start by identifying your fastest peripheral (USB usually needs 48 MHz, for example). If you don't have high-speed needs, pick the lowest frequency that keeps your code responsive.

#mcu# #layout# #pcb design# #frequency#