Root cause analysis and solutions for the most common problem in embedded development

The problem that every developer knows

The circuit is fully assembled, the microcontroller boots - but the real-time clock does not run. The 32,768 kHz crystal does not oscillate. Or even worse: sometimes it oscillates and sometimes not. Or it swings on, but then stops sporadically.

This problem is one of the most frequent and at the same time most frustrating error patterns in embedded development. The 32,768 kHz clock crystal is an electrically sensitive component that works in conjunction with a weak oscillator circuit - and this interaction can be disrupted by numerous factors.

This article systematically analyses the most common causes of oscillation problems with 32,768 kHz quartz crystals and provides specific practical solutions.

Give us a call!Contact us by e-mail!Call me back!

1. the ESR of the quartz is too high for the oscillator circuit

Frequency: Very high - the No. 1 cause

The ESR (Equivalent Series Resistance) is the effective series resistance of the crystal at the resonant frequency. It is the most important - and most frequently underestimated - parameter when selecting a 32.768 kHz crystal.

The oscillator circuit in the microcontroller must generate enough energy to make the quartz oscillate. The value of the negative resistance (|-R|) of the oscillator circuit must be significantly greater than the ESR of the crystal. This ratio is known as the oscillation margin:

Oscillation Margin = |-R| / ESR

This factor should be at least 5, preferably 10 or higher. If it is below 3, the oscillation is unsafe. In the automotive sector, an SF >=10 is generally required.

Why is this particularly critical at 32,768 kHz?

In contrast to MHz crystals (typical ESR: 20-60 Ω), 32.768 kHz crystals have an ESR in the kiloohm range:

Housing size	Type. ESR (max.)	Rating
3.2 x 1.5 mm / 2-pad	70 kΩ	Uncritical for most MCUs
2.0 x 1.2 mm / 2-pad	80 kΩ	Limiting for weak drivers
1.6 x 1.0 mm / 2-pad	90 kΩ	Critical - only for MCUs with strong drivers
1.2 x 1.0 mm / 2-pad	100 kΩ	Very critical - carefully check the swing-back safety

At the same time, the 32,768 kHz oscillator stages in modern MCUs are deliberately optimised for minimum power consumption. The typical negative resistance in many low-power MCUs is only 200-500 kΩ.

Solution:

Use a crystal with the lowest possible ESR. Prefer the 3.2 x 1.5 mm housing with max. 50 kΩ. LRT resonant crystals (Low ESR Resonator Technology) offer significantly lower ESR values than standard crystals, even in smaller housings.

2. incorrect load capacity (load capacity mismatch)

Frequency: Very high

Each 32,768 kHz crystal is specified for a certain load capacitance (CL) - typically 4 pF, 6 pF, 7 pF, 9 pF, 12.5 pF or 18 pF. Mismatching is one of the most common causes of transient response problems.

The load capacitance is the total capacitance that the crystal "sees" at its terminals:

CL = (C1 × C2) / (C1 + C2) + Cstray

Where C1, C2 are the external load capacitors (if present) and Cstray is the parasitic capacitance (PCB leads, IC pins, typically 1-5 pF).

Load capacitance too low: The crystal does not receive sufficient energy feedback → oscillation can fail.
Load capacitance too high: The oscillation amplitude is damped, the frequency shifts downwards and the power consumption increases.

Solution:

Use a crystal with exactly the CL value recommended in the MCU data sheet. Calculate external load capacitors: C_external = 2 × (CL - Cstray). Example: CL = 7 pF, Cstray = 2 pF → C_external = 10 pF per side. (Calculation:^{102/20+2=10pF} per C_ext.).

3. PCB layout error

Frequency: High - and often difficult to diagnose

The 32,768 kHz quartz operates with extremely low currents (nanoampere range). Any parasitic capacitance and any coupled interference can affect the oscillation.

Traces that are too long: Every millimetre adds parasitic capacitance (approx. 0.5-1 pF/cm).
Digital signals in the vicinity: Clock lines or SPI buses couple in interference.
Ground plane directly under the crystal: Increases the parasitic capacitance in multilayer PCBs.
Vias in the crystal area: Act as interference antennas.
Flux residues and moisture: Cause leakage currents - increased at low temperatures.

Solution:

Quartz directly next to the MCU pins (max. 5 mm), short symmetrical conductor tracks, guard ring with ground recess under the quartz, no signal lines between the quartz pins, clean PCB thoroughly after soldering.

4. missing or incorrect feedback resistor

Many MCU oscillator circuits require a high-impedance feedback resistor (Rf) in parallel with the crystal (typically 5-15 MΩ). It biases the inverter stage into its linear operating range. Some MCUs have this resistor internally (STM32, nRF52, ESP32), others require it externally (some MSP430 variants, certain 8-bit MCUs).

Solution:

Check the MCU data sheet to see whether an external Rf is required. If yes: typically 10 MΩ parallel to the quartz. If oscillation is problematic despite internal Rf: try external 15 MΩ.

5. overload of the quartz (drive level too high)

The 32,768 kHz tuning fork crystal is specified for a maximum drive power of typically 0.5-1.0 µW. Exceeding this leads to frequency drift, accelerated ageing and, in extreme cases, mechanical breakage of the resonator.

In practice, overloading occurs if there is no series resistor (Rd) for limitation.

Solution:

Check whether the MCU data sheet recommends a series resistance (Rd) (typically 47-470 kΩ). Measure the oscillation amplitude: it should be 200-600 mV peak-to-peak. Caution: Use 10:1 probes (10 MΩ) or better 100:1 - a 1:1 probe loads the oscillator so much that it can stop!

6. quartz was damaged during soldering

32.768 kHz tuning fork crystals are temperature-sensitive. If the soldering temperature is too high or the soldering time too long, the ESR can deteriorate, change the resonator frequency or cause the housing to lose its hermeticity.

Solution:

Strictly adhere to the soldering profile: Peak temperature max. 260 °C for max. 10 seconds (IPC/JEDEC J-STD-020). Hand soldering: max. 3 seconds at 350 °C, not directly on the housing. Do not exert any mechanical pressure on the quartz.

7 Incorrect software configuration

Frequency: High - especially when changing the MCU or during initial commissioning

With many modern MCUs, the 32.768 kHz oscillator is not automatically active after the reset.

Oscillator not activated: The LSE (Low Speed External) was not switched on in the clock tree.
Incorrect pin configuration: Pins configured as GPIO instead of oscillator inputs.
Timeout too short: The crystal can take 2-5 seconds to oscillate - especially at low temperatures.
Internal capacitances not configured: MCUs with internal trimming capacitances have not been set.
Incorrect oscillator mode: Crystal mode vs. external clock mode mixed up.

Solution:

Activate LSE oscillator correctly, set startup timeout generously (≥ 3 seconds), implement fallback to internal LSI. Use MCU configuration tools (STM32CubeMX, nRF Connect, Simplicity Studio).

8. temperature problems

The ESR of a 32,768 kHz quartz crystal is temperature-dependent and increases at low temperatures. A quartz crystal that reliably oscillates at room temperature can fail at -20 °C or -40 °C.

Solution:

Test the swing-on safety at the lowest operating temperature - not just at 25 °C. Use LRT crystals with low ESR. If in doubt: choose a larger housing (3.2 x 1.5 mm) that still offers sufficient reserve even at -40 °C.

9. mechanical damage or contamination

32,768 kHz tuning fork crystals have an extremely thin resonator. Mechanical shocks, excessive placement pressure during pick-and-place or ultrasonic cleaning can lead to microcracks.

Solution:

No mechanical pressure on the quartz housing.

10. the quartz is OK - but the measurement simulates a problem

Frequency: Very high when troubleshooting!

A standard 10:1 probe has 10-15 pF input capacitance. With a crystal with 6 pF load capacitance, this doubles to triples the load capacitance - enough to stop the oscillator.

Solution:

Do not measure directly on the quartz! Instead: Check the LSE ready flag in the software. If oscilloscope measurement necessary: Use 100:1 probe or active FET probe (< 1 pF). Alternatively: Configure MCU timer with 32.768 kHz clock and measure GPIO output.

Summary: The most common causes at a glance

#	Cause	Frequency	Solution (short version)
1	ESR of the quartz too high	Very high	Quartz with lower ESR (LRT), larger housing
2	Incorrect load capacitance	Very high	Adapt CL value to MCU requirement
3	PCB layout error	High	Short lines, guard ring, no sources of interference
4	Incorrect software configuration	High	Activate LSE, extend timeout, configure pins
5	Missing feedback resistor	Medium	Rf according to MCU data sheet (typically 10 MΩ)
6	Solder damage to the quartz	Medium	Maintain soldering profile, avoid mechanical stress
7	Overload (drive level)	Medium	Use series resistor (Rd)
8	Temperature problems	Medium	Worst-case test at Tmin, allow for ESR reserve
9	Measurement error (probe)	Very high*	Measure indirectly, use 100:1 sample
10	Mechanical damage	Low	Observe handling instructions

*When troubleshooting - not as the cause of the actual problem

Prevention is better than troubleshooting: five design guidelines

Rule 1 - Allow for ESR reserve: Select a crystal with ESR significantly below the MCU maximum value. Swing safety factor ≥ 5.

Rule 2 - Match load capacitance exactly: Adopt CL value from MCU data sheet, take parasitic capacitance into account.

Rule 3 - PCB layout with care: Quartz directly next to MCU pins, short symmetrical lines, remove flux residues.

Rule 4 - Worst-case testing: Check oscillation at lowest temperature and lowest supply voltage.

Rule 5 - If in doubt, choose larger: The 3.2 x 1.5 mm ceramic quartz with 50 kΩ ESR costs less and is more reliable than smaller alternatives.

Problems with swinging? We can help.

Our frequency experts will carry out transient response analyses and recommend the optimum crystal for your application. Contact us - we will analyse your circuit and find the right solution.

Product configurator 32kHz oscillating quartz crystal 3.2 x 1.5 mm / 2-pad LOW ESR

Product configurator 32kHz crystal oscillator 2.0 x 1.2 mm / 2-pad LOW ESR

Product configurator 32kHz crystal oscillator 1.6 x 1.0 mm / 2-pad LOW ESR

Cross reference search

MHz crystal search

Please call me back (with appointment)

Contact by e-mail

Request technical advice

All product designations and brand names mentioned are the property of the respective manufacturer and serve exclusively to describe the technical context.

Why is my 32,768 kHz crystal not resonating?

The problem that every developer knows

1. the ESR of the quartz is too high for the oscillator circuit

Frequency: Very high - the No. 1 cause

Why is this particularly critical at 32,768 kHz?

Solution:

2. incorrect load capacity (load capacity mismatch)

Frequency: Very high

Solution:

3. PCB layout error

Frequency: High - and often difficult to diagnose

Solution:

4. missing or incorrect feedback resistor

Solution:

5. overload of the quartz (drive level too high)

Solution:

6. quartz was damaged during soldering

Solution:

7 Incorrect software configuration

Frequency: High - especially when changing the MCU or during initial commissioning

Solution:

8. temperature problems

Solution:

9. mechanical damage or contamination

Solution:

10. the quartz is OK - but the measurement simulates a problem

Frequency: Very high when troubleshooting!

Solution:

Summary: The most common causes at a glance

Prevention is better than troubleshooting: five design guidelines

Problems with swinging? We can help.

Telephone contact

Write to us