saadc_event_handler not being called

RE: saadc_event_handler not being called

Tim — Mon, 04 Nov 2019 19:38:23 GMT

Solution: nrf_drv_saadc allows NULL for p_config in call to nrf_drv_saadc_init and uses default configuration. I'm using nrfx_saadc and nrfx_saadc_init requires non-NULL p_config. Issue resolved once I added:

    nrfx_saadc_config_t saadc_config = NRFX_SAADC_DEFAULT_CONFIG;

before calling nrfx_saadc_init and changed call to nrfx_saadc_init to:

    ret_code_t err_code = nrfx_saadc_init(&saadc_config, saadc_event_handler);

Thanks.

RE: saadc_event_handler not being called

AndreasF — Thu, 31 Oct 2019 07:30:52 GMT

Hi.

I made this ticket private then, please share your project when you have time :-)

Best regards,

Andreas

RE: saadc_event_handler not being called

Tim — Thu, 31 Oct 2019 04:21:15 GMT

Thanks Andreas. I'm currently looking at this post and simple example to see if I can figure it out. If no success, I will kindly accept your offer to look at my project (privately). I'll followup here in the next days.

Thanks, -Tim

RE: saadc_event_handler not being called

AndreasF — Wed, 30 Oct 2019 13:36:24 GMT

Hi.

Could you share the project you have so I can reproduce the issue?

I can make the ticket private if you only wish to share it with a Nordic employee :-)

Best regards,

Andreas

RE: saadc_event_handler not being called

Tim — Tue, 29 Oct 2019 16:37:59 GMT

Sure Andreas, sdk_config.h attached. Thanks for you help.

devzone.nordicsemi.com/.../74106.sdk_5F00_config.h

RE: saadc_event_handler not being called

AndreasF — Tue, 29 Oct 2019 11:41:40 GMT

Hi agian Tim.

Could you share the whole sdk_config.h file with me so I can see the configuration you're using?

Best regards,

Andreas

RE: saadc_event_handler not being called

Tim — Mon, 28 Oct 2019 17:41:28 GMT

Thanks Andreas. First, I checked and all err_codes returned from SAADC calls and all are 0. Then I added a debug statement to read_battery_voltage() to see if SAADC is busy:

void read_battery_voltage()
{
    NRF_LOG_DEBUG("nrfx_saadc_is_busy() is %d",nrfx_saadc_is_busy());

    ret_code_t err_code;
    err_code = nrfx_saadc_sample();
    APP_ERROR_CHECK(err_code);
}

and surprisingly it is busy (result is 1). The read_battery_voltage() routine exits normally and the main loop resumes. I'm just learning SAADC and I don't fully understand what nrfx_saadc_buffer_convert does. Seems I have a buffer of size 2 (static nrf_saadc_value_t adc_buf[2]) and I've seen some posts stating that you have to call nrfx_saadc_sample() once for each byte of the buffer. I tried adding a second call to nrfx_saadc_sample() and still saadc_event_handler(...) is not being called.

Advanced thanks for any support.

RE: saadc_event_handler not being called

AndreasF — Mon, 28 Oct 2019 09:48:51 GMT

Hello Tim.

[quote user=""]The app calls read_battery_voltage() in response to a message sent from the connected BLE central (iOS app). saadc_event_handler(...) is never called.[/quote]

Have you tried to debug and see where the code stops since you say the event handler is never called?

Best regards,

Andreas