SAADC with soft device and low-power mode

RE: SAADC with soft device and low-power mode

Carsten Wulff — Wed, 23 May 2018 04:53:11 GMT

Could you check if footnote 2 of the SAADC electrical specifications in the nRF52832 product specification fits your symptoms?

RE: SAADC with soft device and low-power mode

Jørgen Holmefjord — Tue, 22 May 2018 14:28:23 GMT

Again, I'm sorry for the (way too) long wait on solving this issue. This have been a tricky issue to debug, as some configurations cause this issue, while others do not. It have not been solved in future versions of driver/SDK, as I'm quite sure this is related to some timing issues in your application. I have not been able to reproduce the issue in other applications, and we have not gotten reports of other users having this issue.

I will try some more debugging, to see if I can find the root cause of the issue in your application.

RE: SAADC with soft device and low-power mode

trigerion — Tue, 22 May 2018 06:04:39 GMT

Is this the regular case that further investigation is proposed but nothing happens?

RE: SAADC with soft device and low-power mode

trigerion — Mon, 09 Apr 2018 20:53:12 GMT

Any further update? Is this fixed for newer versions?

RE: SAADC with soft device and low-power mode

Jørgen Holmefjord — Mon, 05 Feb 2018 15:36:56 GMT

Sorry about the slow reply, we will look more into what is causing this behavior.

RE: SAADC with soft device and low-power mode

trigerion — Wed, 24 Jan 2018 13:00:27 GMT

@Jørgen Holmefjord Well, can you please write some statement if this bug will be investigated?

RE: SAADC with soft device and low-power mode

trigerion — Tue, 19 Dec 2017 14:46:18 GMT

@Jørgen Holmefjord Well thanks for the hint but I would like to unterstand why such a behavior can occur. Will you look into this behavior in detail? Does not sound very faithful to me ...

RE: SAADC with soft device and low-power mode

Jørgen Holmefjord — Mon, 18 Dec 2017 15:47:19 GMT

Sorry for the late reply. It looks like the issue disapears if I remove call to either nrf_pwr_mgmt_run() or sd_app_evt_wait() in you main function. The function nrf_pwr_mgmt_run() does already contain call to sd_app_evt_wait(), you don't need both.

RE: SAADC with soft device and low-power mode

trigerion — Thu, 07 Dec 2017 07:57:10 GMT

@Jørgen Holmefjord Have you test the stripped down project for validation?

RE: SAADC with soft device and low-power mode

trigerion — Wed, 29 Nov 2017 21:19:04 GMT

I will try to generate a demo project to help to debug the case. Hope it won't vanish.

RE: SAADC with soft device and low-power mode

Jørgen Holmefjord — Mon, 27 Nov 2017 14:21:41 GMT

Could you elaborate more on what you mean by "looks more as a square instead of spikes"? Please post more details/code snippets of your SAADC setup/configuration and what the issues is.