nRF52833 send analog data using saadc to nrf connect app

RE: nRF52833 send analog data using saadc to nrf connect app

Sigurd Hellesvik — Tue, 27 Dec 2022 13:52:59 GMT

Hi,
I will continue helping with this case.

If you are going to use the ADC fromt he nRF Connect SDK, I recommend doing it the "Zephyr Way" instead for writing directly to registers.

The Zephyr RTOS use the Devicetree to keep track of which peripherals are used, and which gpio are used, to make sure that nothing overlaps.

To learn more about nRF Connect basics, drivers and the devicetree , see https://academy.nordicsemi.com/.

For an example on how to use the SAADC, see our Battery measurement sample.

Regards,
Sigurd Hellesvik

RE: nRF52833 send analog data using saadc to nrf connect app

tiny_l — Thu, 22 Dec 2022 18:18:45 GMT

Karl,

I want to use the nRF Connect SDK - I am using a zephyr example for peripheral_uart and relying on the nus documentation and samples from the nRF Connect documentation. The enables from the nrf5 SDK of the sdk_config.h was an error on my end, but everything else is nRF Connect SDK from what I can gather.

RE: nRF52833 send analog data using saadc to nrf connect app

tiny_l — Thu, 22 Dec 2022 16:33:20 GMT

Can you share examples for how to do what I intend with the nRF Connect instead since this seems to be the standard going forward?

RE: nRF52833 send analog data using saadc to nrf connect app

Karl Ylvisaker — Fri, 09 Dec 2022 09:20:13 GMT

Hello,

I notice that you seem to be using the nRF5 SDK while the documentation you reference for the NUS is made for the nRF Connect SDK which is likely part of the issue here.
The documentation for the nRF5 SDK can be found here.
Please see this statement regarding the two SDKs, and why we recommend that all new projects use the nRF Connect SDK.

Please see this example as a reference for how you could send SAADC measurements over the NUS service using the nRF5 SDK.

A small side-note when working with the nRF5 SDK is also that you should only have 1 *_ENABLED defined for each peripheral. If both are defined at the same time, the driver will revert to using the configuration set with the legacy define. In essence, if you have both SAADC_ENABLED and NRFX_SAADC_ENABLED defined in your sdk_config.h then the driver will overwrite the NRFX_SAADC_* configurations you have made, with the SAADC_* configurations.

Best regards,
Karl