Using SAADC for 2 channels, burst mode, current consumption remains constant after nrf_drv_saadc_uninit call

RE: Using SAADC for 2 channels, burst mode, current consumption remains constant after nrf_drv_saadc_uninit call

Tony Kobet — Thu, 01 Dec 2022 17:13:35 GMT

This appears to have worked. Thanks very much.

RE: Using SAADC for 2 channels, burst mode, current consumption remains constant after nrf_drv_saadc_uninit call

Nguyen Hoan Hoang — Thu, 01 Dec 2022 03:58:23 GMT

This is undocumented. Power it off with

*(volatile uint32_t *)((uint32_t)NRF_SAADC + 0xFFC) = 0;

Just make sure after that to power it back on by writing 1 before initializing it again

RE: Using SAADC for 2 channels, burst mode, current consumption remains constant after nrf_drv_saadc_uninit call

Tony Kobet — Wed, 30 Nov 2022 20:13:30 GMT

Added the errata workaround and it did not have any effect.

With regard to the HFXO, is there something about using the SAADC's burst mode that would cause it to run continuously after acquiring a sample and uninitializing the SAADC?

RE: Using SAADC for 2 channels, burst mode, current consumption remains constant after nrf_drv_saadc_uninit call

Sigurd — Wed, 23 Nov 2022 14:30:29 GMT

Hi,

[quote user=""]What we are observing is that the current consumption increases to ~450uA when the ADC takes the first reading, and then stays at that level after the SAADC is un-initialized.[/quote]

It could be that you are running in this errata: https://infocenter.nordicsemi.com/topic/errata_nRF52810_Rev3/ERR/nRF52810/Rev3/latest/anomaly_810_246.html

Try adding the errata workaround, and see if that affects the current consumption.

alternatively, it could be that the HFXO is running?