What was the LF_SRC_RC clock fix between SDK 11 and SDK 14?

RE: What was the LF_SRC_RC clock fix between SDK 11 and SDK 14?

Petter Myhre — Mon, 20 Nov 2017 09:51:02 GMT

Yes, NRF_SDH_CLOCK_LF_XTAL_ACCURACY is used, it is a bit misleading I agree, and I have reported this to developers. Have you set NRF_SDH_CLOCK_LF_XTAL_ACCURACY to NRF_CLOCK_LF_XTAL_ACCURACY_500_PPM?

RE: What was the LF_SRC_RC clock fix between SDK 11 and SDK 14?

Aaron — Thu, 16 Nov 2017 17:10:43 GMT

Yes, we saw disconnects (on iPhone only) with 16/2 on SDK11/S132 2.0.0 that were fixed by changing it to 12/0. With another slightly different device (both containing nRF52832 chipsets without crystals) running SDK14.1.0/S132 5.0.0 with 16/2 there are no disconnects on iPhone. Changing 16/2 to 12/0 fixed the problem but added 5 uA. How is the RC oscillator accuracy set in 5.0.0? Is NRF_SDH_CLOCK_LF_XTAL_ACCURACY used?

RE: What was the LF_SRC_RC clock fix between SDK 11 and SDK 14?

Petter Myhre — Thu, 16 Nov 2017 16:11:19 GMT

And just to clarify, you did get the disconnects with 16/2 on SDK11/S132 2.0.0 right?

RE: What was the LF_SRC_RC clock fix between SDK 11 and SDK 14?

Petter Myhre — Thu, 16 Nov 2017 12:52:37 GMT

Are you saying you are seeing this on one of many devices?

This is not really about SDK, it is about SoftDevice, in the SDK11 S132 2.0.0 is used, in SDK14.1 S132 5.0.0 is used.

If you see the migration document of S132 5.0.0 you can see that the RC oscillator accuracy now can be set, previously it was fixed to 250 ppm. Maybe you have set it to 500 ppm?

A setting of 500 ppm would also increase the average current consumption, because the slave RX window would have to be larger, to account for larger clock drift.