zephyr/tests/drivers/adc/adc_accuracy_test
Khoa Nguyen 35d94de056 tests: drivers: adc: add support adc test app for ek_ra4m1
Add support adc_accuracy_test and adc_api test app
for ek_ra4m1 board

Signed-off-by: Khoa Nguyen <khoa.nguyen.xh@renesas.com>
2025-02-13 09:11:33 +01:00
..
boards tests: drivers: adc: add support adc test app for ek_ra4m1 2025-02-13 09:11:33 +01:00
src tests: drivers: adc_accuracy: add calibration before sampling 2024-10-23 17:02:17 +02:00
sysbuild/vpr_launcher tests: drivers: adc: adc_accuracy_test: Add nrf54h20dk_nrf54h20_cpuppr 2025-01-28 09:51:31 +01:00
CMakeLists.txt
Kconfig tests: drivers: adc: Correct the reference-mv in Kconfig 2025-02-07 14:46:00 +01:00
prj.conf
README.txt tests: drivers: adc: Change the property names in the overlay 2025-01-27 17:08:15 +01:00
testcase.yaml tests: drivers: adc: Enable ADC tests on Silabs dev kits 2025-02-03 19:51:46 +01:00

ADC accuracy test

This test checks that ADC readings match an expected value. It is
done using two approaches:

 - DAC source: a board DAC pin is set to a known value, which is then
 read on an ADC one. If they match, the test passes.

 - Reference voltage: an ADC channel is read and compared to an expected
 value.

For the DAC source, it is expected that DAC and ADC are connected. This
can be indicated for twister runs by setting the fixture "dac_adc_loop".
The test then sets DAC to half its resolution and reads the ADC to see
if they match. Note that DAC and ADC are expected to generate/read
voltage on the same range.

In the reference voltage case, the ADC is expected to be connected to a
known voltage reference, whose value is informed, in millivolts, at
property "reference-mv" from "zephyr,user" node. The test reads the ADC
to see if they match.