Using SAADC in nRF Connect SDK

RE: Using SAADC in nRF Connect SDK

Karl Ylvisaker — Fri, 15 Oct 2021 16:24:19 GMT

[quote userid="91630" url="~/f/nordic-q-a/80685/using-saadc-in-nrf-connect-sdk/334405#334405"]

Thank you very much for your help, this works.

And thank you for a detailed explanation!

[/quote]

No problem at all, Emir - I'm happy to help! :)

Please do not hesitate to open another ticket if you should encounter any issues or questions in the future.

Good luck with your development!

Best regards,
Karl

RE: Using SAADC in nRF Connect SDK

enukic — Fri, 15 Oct 2021 15:21:33 GMT

Hi Karl

I completely missed that #define. I thought I needed to use device_get_binding() to get to the arduino_adc: analog-connector from the device tree. I was trying something like:

#define ADC_IN(i) DT_INST(i,ardunio_uno_adc)
#define ADC_1 ADC_IN(1)

const struct device *adc_dev;
adc_dev = device_get_binding(ADC_1);

I guess I still need some documentation reading.

Thank you very much for your help, this works.

And thank you for a detailed explanation!

Best regards

Emir

RE: Using SAADC in nRF Connect SDK

Karl Ylvisaker — Fri, 15 Oct 2021 14:37:32 GMT

Hello,

[quote user=""]Can anyone guide me through how can I set different AIN pin to be used(let's say AIN4) in this example?[/quote]

In this particular example you should be able to change the AIN pin to sample by changing the 15th line of main.c from:

#define ADC_1ST_CHANNEL_INPUT NRF_SAADC_INPUT_AIN0

#define ADC_1ST_CHANNEL_INPUT NRF_SAADC_INPUT_AIN4

[quote user=""]I still don't understand how the whole device tree thing works, and I believe this would require some changes to the device tree.[/quote]

Yes, the device tree is a structure to familiarize with in its own, but in essence it is what Zephyr draws from when you for example set CONFIG_UART=y in prj.conf - this will make Zephyr initialize the UART peripheral, using the default parameters gotten from the device tree. This way, each board can have its own device tree, with different default mappings and configurations, while all you have to do in Zephyr to make use of it is CONFIG_*=y.
If this then needs reconfiguring or modification you will have to modify the device tree file directly.

Please do not hesitate to ask if any part of this should be unclear, or in the case that you've got any other questions!

Best regards,
Karl

RE: Using SAADC in nRF Connect SDK

enukic — Thu, 14 Oct 2021 14:25:07 GMT

Maybe I should also mention that the target board is nRF52840DK