Porting Project from SDK12.2 to SDK14.1, SAADC issue

RE: Porting Project from SDK12.2 to SDK14.1, SAADC issue

rms — Mon, 20 Nov 2017 20:29:45 GMT

I think I figured it out. I was using the GPIOTE peripheral to handle the power off button. I turned the log for the GPIOTE peripheral on, and saw that as soon as I initialized it would detect the power button event right away. My PWR_OFF line on the device has a capacitor that keeps the unit on for a 6+ seconds, this was probably keeping my unit alive and the SAADC acting strange.

This was my original code

nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(false);
in_config.pull = NRF_GPIO_PIN_PULLUP;

err_code = nrf_drv_gpiote_in_init(PWR_SW, &in_config, power_button_interrupt_handler);
APP_ERROR_CHECK(err_code);

nrf_drv_gpiote_in_event_enable(PWR_SW, true);

I set the GPIOTE to high accuracy and it stopped registering the power button event at initialization.

nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(true);
in_config.pull = NRF_GPIO_PIN_PULLUP;

err_code = nrf_drv_gpiote_in_init(PWR_SW, &in_config, power_button_interrupt_handler);
APP_ERROR_CHECK(err_code);

nrf_drv_gpiote_in_event_enable(PWR_SW, true);

This is my power_button_interrupt_handler, I also started calling the sd_power_system_off from here after setting the PWR_OFF line which wasn't done before

void power_button_interrupt_handler(nrf_drv_gpiote_pin_t pin, nrf_gpiote_polarity_t action)
{
greenLED_blink_stop();
NRF_LOG_INFO("POWER_BUTTON_HANDLER");
nrf_gpio_pin_write(LED_RED,LED_ON);
NRF_LOG_FINAL_FLUSH();
nrf_drv_gpiote_out_set(PWR_OFF);

ret_code_t err_code;
// Go to system-off mode (this function will not return; wakeup will cause a reset).
err_code = sd_power_system_off();
APP_ERROR_CHECK(err_code);
}

RE: Porting Project from SDK12.2 to SDK14.1, SAADC issue

rms — Mon, 20 Nov 2017 16:40:44 GMT

A note on the SAADC conversion value, with -O3 after flashing the program it will give the expected value but after one reset it gives a wrong value

** After -O3 Flash (right after flashing it runs fine), value around 400ish

Triggering battery level update...
<info> saadc: Function: nrf_drv_saadc_init, error code: NRF_SUCCESS.
<info> saadc: Channel initialized: 0.
<info> saadc: Function: nrf_drv_saadc_channel_init, error code: NRF_SUCCESS.
<info> saadc: Conversion value: 437, channel: 0.
<warning> saadc: Function: nrf_drv_saadc_sample_convert, error code: NRF_SUCCESS.
<info> saadc: Channel denitialized: 0.
<info> saadc: Function: nrf_drv_saadc_channel_uninit, error code: NRF_SUCCESS.

*** After reset of -03 Flash (after resetting once, the SAADC conversion values stay like this), value around 8ish or 65530ish

Triggering battery level update...
<info> saadc: Function: nrf_drv_saadc_init, error code: NRF_SUCCESS.
<info> saadc: Channel initialized: 0.
<info> saadc: Function: nrf_drv_saadc_channel_init, error code: NRF_SUCCESS.
<info> saadc: Conversion value: 8, channel: 0.
<warning> saadc: Function: nrf_drv_saadc_sample_convert, error code: NRF_SUCCESS.
<info> saadc: Channel denitialized: 0.
<info> saadc: Function: nrf_drv_saadc_channel_uninit, error code: NRF_SUCCESS.

Triggering battery level update...
<info> saadc: Function: nrf_drv_saadc_init, error code: NRF_SUCCESS.
<info> saadc: Channel initialized: 0.
<info> saadc: Function: nrf_drv_saadc_channel_init, error code: NRF_SUCCESS.
<info> saadc: Conversion value: 65530, channel: 0.
<warning> saadc: Function: nrf_drv_saadc_sample_convert, error code: NRF_SUCCESS.
<info> saadc: Channel denitialized: 0.
<info> saadc: Function: nrf_drv_saadc_channel_uninit, error code: NRF_SUCCESS.

RE: Porting Project from SDK12.2 to SDK14.1, SAADC issue

rms — Fri, 17 Nov 2017 01:16:54 GMT

I tried with the DEBUG compiler flag with -03 but it still resets with any info, as soon as I start IR sensors notification. this is what I see

Triggering battery level update...
<info> saadc: Function: nrf_drv_saadc_init, error code: NRF_SUCCESS.
<info> saadc: Channel initialized: 1.
<info> saadc: Function: nrf_drv_saadc_channel_init, error code: NRF_SUCCESS.
<info> saadc: Conversion value: 7, channel: 1.
<warning> saadc: Function: nrf_drv_saadc_sample_convert, error code: NRF_SUCCESS.
<info> saadc: Channel denitialized: 1.
<info> saadc: Function: nrf_drv_saadc_channel_uninit, error code: NRF_SUCCESS.
<info> app: Connected.

2nd run without connecting

RAM Start: 20002140
BLE init
<info> app: Fast advertising.
After init
Triggering battery level update...
<info> saadc: Function: nrf_drv_saadc_init, error code: NRF_SUCCESS.
<info> saadc: Channel ini▒

After I connect and start notifications it resets with no info after these lines. If I just let it run without connecting it resets on its own after a small time. By the way the conversion value is very small its normally around 400ish for the battery when it is working correctly

SAADC module disabled, all SAADC code commented out, -O0 DEBUG & -O3 ok

SAADC module enabled, but all SAADC code commented out, -O0 DEBUG & -O3 ok

SAADC module enabled, only battery SAADC code un-commented , -O0 DEBUG Ok, -O3 reset forever

I will try to use non-blocking instead to see what happends

RE: Porting Project from SDK12.2 to SDK14.1, SAADC issue

rms — Thu, 16 Nov 2017 20:30:11 GMT

I just noticed something APP_TIMER_CONFIG_OP_QUEUE_SIZE was 20 in my last project it was changed to 10 when I changed my SDK. I changed it back to 20 and now it seems working and also put some protection to see if SAADC is already in use. I have other timers didnt mention it above which dont use the SAADC.

Now it runs fine in -O0 DEBUG with the debugger attached. If I try to run -O0 DEBUG without the debugger attached I get this

<error> app: ERROR 3735928559 [Unknown error code] at ../../nRF5_SDK_14.1.0_1dda907/components/drivers_nrf/pwm/nrf_drv_pwm.c:375

I am using the PWM to blink an LED, which indicates if it is shutting down or powered on

With -O3 it still exhibits the reset behavior

RE: Porting Project from SDK12.2 to SDK14.1, SAADC issue

rms — Thu, 16 Nov 2017 15:27:55 GMT

Hey Jørgen, I have NRF_LOG enabled with DEBUG, and have SAADC log enabled. I never get error returns from the SAADC log. The weird thing that happens is before the reset problem happens, the SAADC will return really high or really low reading before the reset. Like a reading of 15.

And no I do not have a way of knowing if the the SAADC is already initialized, should I use a mutex or similar to protect the SAADC as a resource?

Another weird thing is this exact setup gave me no problems with previous SDKs

RE: Porting Project from SDK12.2 to SDK14.1, SAADC issue

Jørgen Holmefjord — Thu, 16 Nov 2017 15:15:29 GMT

Are you pausing the always-running timer when you do the on-demand sampling of the SAADC, or make sure that the other timer handler does not try to initialize the SAADC when it is already initialized by the other? If the chip restarts, it have ended up in the error handler, where the default recovery is to reset the chip. If you enable NRF_LOG and defined the preprocessor symbol DEBUG, the error handler in SDK 14.1 should print the error code and info about that caused the function, if you are not able to reproduce it while debugging.