SAADC Driver Issues

RE: SAADC Driver Issues

abkirchhoff — Mon, 05 Dec 2016 15:10:54 GMT

Jorgen, Thanks for following up. Let me know when you hear back. Austin

RE: SAADC Driver Issues

Jørgen Holmefjord — Mon, 05 Dec 2016 14:33:09 GMT

Sorry for not answering you quicker. I have reported the issues internally to the developers, and will get back to you as soon as I hear back. There seems to be a missing if case to handle this special case.

RE: SAADC Driver Issues

abkirchhoff — Fri, 04 Nov 2016 15:38:04 GMT

For issue 2, the issue only occurs if my buffer size is one and I only use one active ADC channel. I will update my post.

RE: SAADC Driver Issues

abkirchhoff — Fri, 04 Nov 2016 15:35:34 GMT

Eddie, You nailed it. I defined m_cb.adc_state as volatile and the abort issue (issue 1) is fixed. Thanks.

Issue 2 still remains (for any optimization level).

RE: SAADC Driver Issues

Eddie — Fri, 04 Nov 2016 15:29:47 GMT

For the first issue, can you try declaring m_cb.adc_state as volatile?

RE: SAADC Driver Issues

abkirchhoff — Fri, 04 Nov 2016 15:01:26 GMT

Jorgen,

Thanks for looking into this. I have uploaded an example project that demonstrates the two issues. The example is in examples/peripheral/saadc. Normally the example prints an ADC result once a second. I added two definitions in main.c that if enabled will run code to display the selected issue. I used the arm5_no_packs project. I had to add DEBUG and DEBUG_NRF_USER to the project definitions to get issue 1 to occur.

Austin

RE: SAADC Driver Issues

Jørgen Holmefjord — Fri, 04 Nov 2016 13:33:58 GMT

Hi, I ported this example to SDK12. I could not reproduce the first issue. Can you post some code (or preferrably, upload the whole project) showing how you configure and initialize the SAADC? I have not heard of this issue before. Is the second issue only occuring if optimization is set to level 3 aswell?