SAADC low power SDKv13.0.0 and S132

RE: SAADC low power SDKv13.0.0 and S132

Otavio Borges — Mon, 17 Jul 2017 18:10:19 GMT

Changing priority to APP_IRQ_PRIORITY_LOW seemed to solve the problem. I'm performing a 24h test, but so far no error. Thank you Jørgen.

RE: SAADC low power SDKv13.0.0 and S132

Jørgen Holmefjord — Mon, 17 Jul 2017 15:08:35 GMT

In general it is not recommended to do time-consuming tasks in the callback. Do you get the assertion if setting SAADC priority to APP_IRQ_PRIORITY_LOW?

RE: SAADC low power SDKv13.0.0 and S132

Otavio Borges — Fri, 14 Jul 2017 14:32:00 GMT

Through the routine of updating battery voltage the only peripheral I access directly is SAADC. To update the adv. data I use sd_rand_application_vector_get to generate an random dummy, and then ble_advdata_set. SAADC interrupt priority was set to APP_IRQ_PRIORITY_HIGH, considering that ADC routines take a while, could this have been generating the fault assertions?

RE: SAADC low power SDKv13.0.0 and S132

Jørgen Holmefjord — Fri, 14 Jul 2017 14:15:45 GMT

The low power SAADC example only use RTC2 to trigger sampling through PPI. The low power part comes from disabling the SAADC between samples, and use low power RTC over TIMER for sampling. Please make sure you are not using any resources required by the softdevice.

RE: SAADC low power SDKv13.0.0 and S132

Otavio Borges — Fri, 14 Jul 2017 12:43:51 GMT

Jørgen, That's not the issue. I use an external RTC to trigger SAADC sampling (through GPIOTE IRQ). I think I misunderstood the connection between RTC0 and SAADC. On my perception SAADC low power used RTC0, through PPI, as clock source.

I've tried using SAADC without the low power config, but I'm still getting assertion faults from SD.

RE: SAADC low power SDKv13.0.0 and S132

Jørgen Holmefjord — Fri, 14 Jul 2017 07:18:24 GMT

The nRF52 SAADC low power example use RTC2 for sampling. Have you changed the configuration in sdk_config.h?