You need exactly two external capacitors (or zero if using the MCU's internal bank). The PCB routing is shorter. The cost is 1/10th of a BICFIC.

This requires software calibration. If your firmware doesn't trim the oscillator, you get 2% error. But for 95% of IoT sensors, that is fine. For the other 5% (USB or CAN bus), stick with a real oscillator. Alternative #3: The Programmable Clock Generator (For the "One BOM Fits All" Strategy) If you are tired of stocking 47 different BICFIC frequencies, the new alternative is the fractional-N PLL clock generator. Parts like the Skyworks Si5351 (old) or the newer Texas Instruments LMK3H0102 (very new) are game changers.

If you need 32.768 kHz for a Real Time Clock (RTC), you are stuck with a crystal or a specialized MEMS RTC. Nothing beats quartz for low-frequency precision.

Modern MCUs (STM32U5, Raspberry Pi RP2040, ESP32-C6) have radically improved their internal Pierce gate circuits. Five years ago, using the internal oscillator was noisy. Today, with auto-gain control and integrated load capacitance (some now have internal programmable capacitor banks up to 25pF), the external BICFIC is obsolete.

You can drop a SiT8008 (programmable) directly onto the pads of a standard BICFIC footprint (often 2.5mm x 2.0mm or 2.0mm x 1.6mm). The difference? No quartz blank means no EMI hot spots radiating from the can lid.

Search for "HSE oscillator gain" or "Low-power crystal bypass." If your MCU supports "low drive" mode, you can use a cheap raw crystal. If it supports "external clock input," you can feed it a MEMS clock.

If "new" means "better reliability," MEMS wins. However, for ultra-low phase noise (radar or high-end audio), MEMS still lags slightly behind the best quartz. Alternative #2: The "Naked Crystal" + Pierce Gate (The Zero-Cost Alternative) This isn't a product; it's a topology shift. Many engineers asking for a bicfic alternative new actually don't need an integrated oscillator. They just think they do.