External rail-to-rail 32K clock - internal xtal driver damaged?

RE: External rail-to-rail 32K clock - internal xtal driver damaged?

run_ar — Fri, 11 Jun 2021 08:06:38 GMT

You can change to 500ppm in sdk_config.h. change #define NRF_SDH_CLOCK_LF_ACCURACY 1

Also note that there are multiple entries for *LF_SRC that need to be updated: NRF_SDH_CLOCK_LF_SRC, NRFX_CLOCK_CONFIG_LF_SRC and CLOCK_CONFIG_LF_SRC

Not sure why there should be a baudrate error due to the LF SRC. This would be derived from the HF clock. So you might want to check that it is using the crystal and not the HFRC.

RE: External rail-to-rail 32K clock - internal xtal driver damaged?

Anders Nelson — Tue, 01 Jun 2021 13:05:03 GMT

Hey, thanks for your response! I configured the LFRC to run and BLE works now. I'm now having trouble with the bootloader not responding to the PC - is it possible there is a baudrate error due to use of the LFRC?

Where can I find the area to change for a 500ppm tolerance?

Thanks!

RE: External rail-to-rail 32K clock - internal xtal driver damaged?

run_ar — Tue, 01 Jun 2021 10:30:40 GMT

Hi,

It is possible that the inputs can be damaged. But you could still try to use the LFRC and see if BLE works. remember to also change the ppm setting to 500ppm for the clock.