

Hi
This sounds very much like the internal 32.768 kHz RC oscillator waking the HF clock up for calibration every 8 seconds. The RC oscillator will be used if the optional external 32.768 kHz crystal is not in the design of your device. I know the Laird modules don't come with these at least, but it should be possible to add one if you are developing a PCB design yourself.
What SDK and SDK version are you using for your project?
Best regards,
Simon
Is there a way to disable that completely? Or maybe only allow the cal to occur at other longer intervals or to occur only when specifically invoked? I see in nRF52832_OPS_v0.6.3.pdf 23.11 the RTC is only supposed to use 0.1uA, which would be acceptable, but would like to reduce or eliminate the amount of power used by the cal cycle. (assuming that is what the issue is)
Hi
In order to make sure the oscillator doesn't drift too much to break with the BLE specification, it is strongly recommended that the calibrations occur at least every 8 seconds. You're free to play around with the NRF_SDH_CLOCK_LF_RC_CTIV and NRF_SDH_CLOCK_LF_RC_TEMP_CTIV defines in the sdk_config.h of your project (I assume you're using the nRF5 SDK) which is where you set how often SoftDevice calibration should be done when the RC oscillator is in use. Setting both to 0 should disable the calibration entirely, but then you won't be able to do much in terms of BLE.
The RTC is the Real Time Counter module, and not the same as the RC oscillator which is one of the LF clock sources you can use for the nRF52832. I also see you're referring to some very old documentation, and I recommend you refer to the latest version of the nRF52832 product specification (v1.8)
I see that you tried uploading a picture or link as well, but this seems to be broken as we're not able to open it on our end.
Best regards,
Simon
We are using version nRF5 SDK16.0.
Both of the NRF_SDH_CLOCK defines you mentioned are set to 0 in the sdk_config.h file.