HFXO does not work on nRF52832

RE: HFXO does not work on nRF52832

silvio3105 — Tue, 18 Mar 2025 00:25:02 GMT

The problem is fixed. HFXO caps are 8pF.

I could not get advertise to start so I decided to move component by component from one PCB to another. I moved MCU + VDD caps, HFXO + caps and ANT.

I did not know DEC1, DEC3 and DEC4 are needed for MCU to work properly. I thought they are needed for DC/DC setup. My bad.

RE: HFXO does not work on nRF52832

silvio3105 — Sun, 16 Mar 2025 14:30:12 GMT

https://docs.nordicsemi.com/bundle/ps_nrf52832/page/clock.html#d910e8036

Here it says 4pF.
I will contact Epson about this crystal.

RE: HFXO does not work on nRF52832

hmolesworth — Sat, 15 Mar 2025 16:26:37 GMT

Perhaps try a different crystal; the part number TSX-3225 32.0000MF20X-W0 does not match the part number format on the data sheet. As an aside, nRF52832 pin capacitance is 3pF (as used in my formula), not 4pF, but it doesn't make much difference.

CPAD Pad capacitance 3 pF

RE: HFXO does not work on nRF52832

silvio3105 — Sat, 15 Mar 2025 12:04:38 GMT

Tried 4pF, 8pF(stack od 2x4pF in parallel) and 20pF(2x4pF + 12pF in parallel) - still cannot start it.

I belive CL is 7pF as stated in datasheet. Calculated caps with "((8+4+1)*(8+4+1))/(2*(8+4+1))" - from nRF52832 clock section.

C = C1 = C2

(C + Cpin + Cs)^2 / (2 * (C + Cpin + Cs))

Cs = 1pF
Cpin = 4pF

Result is 6.5pF which is close to 7pF from datasheet.
Connection is tested, solders on MCU pins look good.

Kazi Afroza Sultana

RE: HFXO does not work on nRF52832

silvio3105 — Thu, 13 Mar 2025 22:33:06 GMT

Mouser says 7pF https://hr.mouser.com/ProductDetail/Epson-Timing/TSX-3225-32.0000MF20X-W0?qs=f9yNj16SXrLFb%2FNL%252B2Lczg%3D%3D

Datasheet says 7pF to infinity

DigiKey says 12pF https://www.digikey.com/en/products/detail/epson/TSX-3225-32-0000MF20X-W0/7731972

I made mistake with not including 4pF for Cpin.
For 7/5pF caps have to be 4pF while for 12/5pF caps have to be 14pF, according to this calculator - https://ecsxtal.com/crystal-load-capacitance-calculator/

Seems like CL is 7pF since I guess 12pF will be enough for 12pF CL.

RE: HFXO does not work on nRF52832

hmolesworth — Thu, 13 Mar 2025 16:53:36 GMT

The data sheet for that crystal implies 7pF CL although the Mouser listing states 12pF, so 12pF load caps are not correct in either case.

CL = (CaCb)/(Ca+Cb) + Cstray where Ca=Cb=12pF+Cpin=15pF and Cstray (not pins) say 1pF
= 8.5pF

CL = (CaCb)/(Ca+Cb) + Cstray where Ca=Cb=9pF+Cpin=12pF and Cstray (not pins) say 1pF
= 7pF

If the Mouser description of 12pF is correct then try 19pF

CL = (CaCb)/(Ca+Cb) + Cstray where Ca=Cb=19pF+Cpin=22pF and Cstray (not pins) say 1pF
= 12pF

RE: HFXO does not work on nRF52832

silvio3105 — Thu, 13 Mar 2025 16:03:10 GMT

Mine app stucks at while loop.

RE: HFXO does not work on nRF52832

hmolesworth — Thu, 13 Mar 2025 15:51:24 GMT

Most useful, we will adopt this. For other users it may be helpful to do the measurement in uSecs:

   NRF_TIMER1->PRESCALER = 4; // Time in uSecs when using 1MHz timer clock. fTIMER = 16 MHz / (2^PRESCALER)

RE: HFXO does not work on nRF52832

rmptxf — Thu, 13 Mar 2025 15:01:05 GMT

This is how we get the startup time on NCS.

NRF_TIMER1->BITMODE = TIMER_BITMODE_BITMODE_32Bit << TIMER_BITMODE_BITMODE_Pos;
NRF_TIMER1->TASKS_CLEAR = 1;
NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
NRF_TIMER1->TASKS_START = 1;
NRF_CLOCK->TASKS_HFCLKSTART = 1;
while(NRF_CLOCK->EVENTS_HFCLKSTARTED == 0);
NRF_TIMER1->TASKS_CAPTURE[0] = 1;

LOG_INF("HF Clock has started. Startup time: %d uS", NRF_TIMER1->CC[0]);

RE: HFXO does not work on nRF52832

rmptxf — Thu, 13 Mar 2025 14:57:01 GMT

We also run into a similar issue, and the start time was more than a 1ms on best cases (not even fixed).

What should we do in that case of high start time?

RE: HFXO does not work on nRF52832

silvio3105 — Thu, 13 Mar 2025 14:49:32 GMT

I can but I'm not sure how.
It could be this problem since sometimes(very rare) app starts but BLE advertise does not work. App works but I cannot find the device in Nordic's mobile app.
I have QFAAE0 chip.

Btw. App stucks at while loop because event is zero. How errata 68 relates with this problem?

RE: HFXO does not work on nRF52832

Kazi Afroza Sultana — Thu, 13 Mar 2025 14:29:06 GMT

Hello,

We have an [68] CLOCK: EVENTS_HFCLKSTARTED can be generated before HFCLK is stable errata that could be relevant to your issue. If EVENTS_HFCLKSTARTED starts before HFCLK is started.

Can you check the Crystal start-up time of your 32MHz?