Can't stop SAADC

RE: Can't stop SAADC

Alaa — Thu, 12 Apr 2018 08:41:30 GMT

Thank you. This worked in addition to adding timer_uninit and ppi_uninit. Like so:

void start_adc()
{
    saadc_sampling_event_init();
    saadc_init();
    saadc_sampling_event_enable();
}

void stop_adc()
{
    nrf_drv_timer_disable(&m_timer);
    nrf_drv_timer_uninit(&m_timer);
    nrf_drv_ppi_channel_disable(m_ppi_channel);
    nrf_drv_ppi_uninit();
    nrf_drv_saadc_abort();
    nrf_drv_saadc_uninit();
    while(nrf_drv_saadc_is_busy());
}

RE: Can't stop SAADC

Jørgen Holmefjord — Tue, 10 Apr 2018 13:53:09 GMT

This should be sufficient:

Stop anything triggering the sample task (timer, PPI, etc.).
Call nrf_drv_saadc_abort().
Call nrf_drv_saadc_uninit().
Call you SAADC+channels init function.
Start whatever triggers sample task.

RE: Can't stop SAADC

Alaa — Tue, 10 Apr 2018 13:06:53 GMT

Sorry I'm confused. Can you please tell me what's the proper way and the right order of operations to stop and restart ADC?

Thank you very much

RE: Can't stop SAADC

Jørgen Holmefjord — Mon, 09 Apr 2018 13:28:16 GMT

nrf_drv_saadc_abort should stop the SAADC and any ongoing conversions, but if you are setting up new buffers and triggering sampling, you will still get callbacks. You should check the error codes from nrf_drv_timer_disable and nrf_drv_ppi_channel_disablein stop_adc, to make sure the sampling is actually stopped, before aborting and uninitializing the SAADC.

Error 133 (0x0085) means NRF_ERROR_MODULE_ALREADY_INITIALIZED. If do not uninit the PPI driver, it would be expected that you get this error when calling nrf_drv_ppi_init.

RE: Can't stop SAADC

Alaa — Sun, 08 Apr 2018 06:43:12 GMT

Hi Jorgen,

Thanks for the reply.

I prefer to keep the double buffer so I tried the abort method. Calling nrf_drv_saadc_abort() alone doesn't stop the adc callback. It keeps triggering with constant value 1024. And then if I call my function start_system() again, I get a hard fault from nrf_drv_ppi_init() (133 error).

I also tried calling nrf_drv_saadc_uninit() after aborting - this did stop the callback, but I got the same hard fault (133)

RE: Can't stop SAADC

Jørgen Holmefjord — Wed, 04 Apr 2018 14:43:35 GMT

Hi,

The SAADC driver will always be in the busy state when a buffer is setup for conversion (by calling nrf_drv_saadc_buffer_convert). It will not help to only disable double buffering, you also need to remove the second buffer.

You have two alternatives:

Call nrf_drv_saadc_abort to remove the buffers and stop any ongoing sampling. This will trigger the STOP task and put the driver in IDLE state when STOPPED event is received.
Disable double buffering, as you describe above, and only call stop_adc in your SAADC event handler when you receive a DONE event, but before you call nrf_drv_saadc_buffer_convert to setup the buffer for conversion again.

Best regards,
Jørgen