A missing clock does not immediately identify a faulty crystal. First establish whether the source is oscillating, whether the IC has accepted it, and whether the clock has reached its destination. Then investigate supply, configuration, loading, oscillation margin and assembly with a repeatable restart test.
What does crystal oscillator startup time mean?
Specify the start event and the acceptance condition. A measurement from an enable command to a ready flag includes different delays from one taken between a local supply threshold and a valid clock output.
- Passive crystal with an MCU or ASIC: the IC supplies the active oscillator circuit. Resonator buildup, clock detection and any qualification timer are separate parts of the sequence.[1]
- Packaged XO or TCXO: distinguish power-on startup, standby recovery and output-enable delay. Some devices disable the output buffer while keeping the oscillator running; the selected part’s control-pin definition determines the behavior.[6]
- OCXO: output transitions can be present before the frequency meets the warm-up requirement. Check the specified settling criterion, reference frequency and ambient conditions.[7]
A downstream PLL can add lock time. Determine when it receives an acceptable reference and how the system releases the clock to consumers.
Why startup and clock readiness are different
The active circuit reinforces a small initial disturbance near resonance. Amplitude grows when the circuit supplies enough energy to overcome resonator losses, then settles as the amplifier limits its gain.[2] Frequency, losses, loading, amplifier behavior and operating conditions all influence the result; Q alone is insufficient to predict startup.
ST AN2867 illustrates millisecond-scale startup for MHz circuits and 1–5 seconds for 32.768 kHz circuits.[3] These are design examples, not acceptance limits for every board. Compare your result with the applicable device specification and restart conditions.
Match the symptom to the next check
Use these observations to choose a test. Each symptom can have several causes.
| Observed symptom | Investigate | Next useful check |
|---|---|---|
| No packaged-oscillator output | Local supply, control pin, pinout, output load or damage | Capture voltage at the supply pin and confirm the required enable level, termination and receiver interface. |
| Clock exists, system remains inactive | Reset, source selection, routing, bypass mode or PLL state | Read clock and reset status and inspect an available buffered clock output. |
| Intermittent power-on or cold-start failure | Oscillation margin, supply ramp or temperature-dependent behavior | Repeat defined restarts after temperature soak while capturing the local supply. |
| Failure appears after assembly | Soldering, contamination, incorrect placement or mechanical damage | Inspect pads and joints; compare the installed parts and a known-good board. |
| Probe changes the behavior | Probe capacitance, grounding or coupled interference | Compare a buffered observation point with the IC vendor’s approved probing method. |
| Failure occurs only after sleep | Stopped domains, restart mode, qualification or firmware sequence | Record which oscillator remains powered and when the source is enabled and selected again. |
Successful code execution does not prove that the external crystal is operating. A supported fallback clock can keep the MCU running with different timing; confirm the active source.[4]
Measure startup without disturbing the oscillator
- Capture the start event. Trigger on the specified local supply threshold or enable transition, alongside a clock output or supported status signal.
- Define a valid endpoint. Check the receiving circuit’s amplitude, frequency and continuity requirements. One visible edge does not establish a usable clock.
- Prefer a buffered clock observation point. A passive probe can substantially load a sensitive crystal node. If pin probing is necessary, follow the vendor’s method and account for probe capacitance.[5]
- Interpret status correctly. A ready flag includes its detection rules; a firmware GPIO can add polling and software latency. Neither automatically measures resonator buildup directly.
- Repeat the intended restart. Document off-time, residual supply voltage, reset state and sleep configuration. A reset or short power interruption may leave the oscillator running.
For a packaged oscillator, verify the specified output load during measurement. An oscilloscope’s 50 Ω input can be inappropriate for an output intended to drive a CMOS capacitive load.
Correct the actual failure mechanism
Check power, assembly and clock configuration
Measure supply ramp, droop and ripple at the device. Verify decoupling, ground, pin assignments, solder joints, reset and control levels. Select crystal mode for a passive resonator or the documented external-clock mode for an oscillator module. Check relevant device errata before changing components.
Match the crystal, loading and drive
Confirm frequency range, fundamental or overtone mode, maximum ESR, specified load capacitance and drive rating. Include fitted capacitors, internal programmable loading, pin capacitance and PCB parasitics in the load model. The FCom crystal matching guide and Pierce oscillator design guide cover these design checks.
Changing load capacitors can shift both operating frequency and startup margin. Increasing drive may exceed the crystal’s rating. After any adjustment, check frequency and crystal drive using the vendor’s measurement procedure; crystal-pin voltage alone does not establish dissipated power.
Test startup margin from a stopped state
Where the IC vendor specifies a series-resistance test, add a low-parasitic test resistor in series with the crystal. For each value, return the circuit to the defined stopped state and attempt a fresh startup. Record the largest consistently passing value and the first failing value under the tested conditions.[5]
Startup allowance and stop allowance are different. Increasing resistance while the circuit is already running tests whether it can sustain oscillation. That result cannot replace a test of whether it starts from rest. Remove the added test resistance when returning to the intended production circuit.
Use the IC supplier’s resistance, ESR and safety-factor definitions together. Do not interchange motional resistance and loaded ESR without the required model conversion. Margin criteria are device-specific: ST AN2867, for example, distinguishes its HSE and LSE oscillator requirements.[3]
Recheck layout and firmware after changes
Keep crystal connections short and follow the IC vendor’s grounding, guard and routing guidance. Investigate leakage from residue or humidity and coupling from nearby switching signals. Repeat measurements after cleaning, rework or layout changes.
A longer timeout can accommodate a healthy source that reliably starts within the new deadline. It cannot restore missing oscillation margin. Use startup assistance or temporary drive settings only when documented for the selected IC, then verify the transition to normal operation.
Validate the fix across operating conditions
Use a test matrix covering supply limits and realistic ramps, temperature extremes after soak, complete power cycles, reset and sleep recovery. Include several boards and component lots where practical. Log restart count, failures and the longest observed interval, together with the measurement endpoints.
Recheck steady-state frequency, crystal drive, power and receiver compatibility. An observed maximum from a finite test set is evidence for those conditions, not a guaranteed production maximum.
For tight wake-up deadlines, compare restarting the source with retaining an active reference and controlling its output. Evaluate total energy and the selected device’s documented behavior. Changing to a TCXO or OCXO does not by itself guarantee faster system readiness.
Does the crystal determine startup time by itself?
No. A passive crystal works with the IC’s amplifier and the board’s loading, supply and layout. A replacement must match the complete oscillator circuit.
Why can a longer software delay appear to fix the issue?
It may allow additional buildup or qualification time, or hide intermittent failures during limited testing. Repeat genuine restarts and confirm a valid clock before accepting the change.
Is output-enable time the same as startup time?
Only if the datasheet defines it that way. A buffer-only enable operation and recovery from a stopped oscillator have different starting states.
Does an OCXO output prove warm-up is complete?
No. Check the warm-up frequency criterion and conditions separately from output availability.
Get support for crystal matching and startup
Browse FCom quartz crystal resonators, 32.768 kHz tuning-fork crystals and packaged crystal oscillators according to the circuit type.
Send FCom the troubleshooting details: part and IC numbers, schematic, layout, capacitor values, clock settings, supply and temperature conditions, startup captures, probe details and restart procedure. Include the required time to a valid clock and the number of failures observed.
Technical references
- Microchip — PIC32 Oscillator Start-up Timer, clock qualification and PLL delay.
- Microchip AN826 — Crystal Oscillator Basics and Crystal Selection (PDF), oscillator operation and crystal parameters.
- STMicroelectronics AN2867 — Guidelines for oscillator design (PDF; revision 24, February 2026), startup, loading, drive and safety factor.
- Microchip — 8-bit PIC and AVR MCU Design and Troubleshooting (PDF), clock configuration, reset and measurement checks.
- Texas Instruments SLAA322D — MSP430 32-kHz Crystal Oscillators (PDF), probing, layout and separate startup/stop allowance tests.
- Epson — SG3225VEN device and SGxxxxVEN family datasheet (PDF), an example of separate power-on and output-enable timing.
- NDK — NH26M26LC OCXO datasheet (PDF), frequency stabilization criterion and timing diagram.