What is the EVENTDONE of SAADC oversampling?

RE: What is the EVENTDONE of SAADC oversampling?

Jørgen Holmefjord — Mon, 26 Oct 2020 10:03:59 GMT

The averaging is performed in the peripheral, before the result is written to the buffer. The buffer will only hold the 10 result samples, not all 40 samples used for averaging.

RE: What is the EVENTDONE of SAADC oversampling?

DL_November — Mon, 26 Oct 2020 02:06:55 GMT

Thanks for the reply.

[quote userid="14926" url="~/f/nordic-q-a/67552/what-is-the-eventdone-of-saadc-oversampling/276566#276566"]To sum up, the result is ready for use when you get this event in the driver, all oversampling is completed.[/quote]

Then, for the case of SAMPLES_IN_BUFFER = 10 and x4 oversampling, NRF_DRV_SAADC_EVT_DONE appears as averaged 10 values from the 40 samples are stored in the buffer, right?

RE: What is the EVENTDONE of SAADC oversampling?

Jørgen Holmefjord — Fri, 23 Oct 2020 08:20:38 GMT

Hi,

It is important to distinguish between the events generated by the peripheral (EVENTS_END/EVENTS_DONE/EVENTS_RESULTDONE), and the software events passed to the application from the driver (NRF_DRV_SAADC_EVT_DONE).

From the peripherals perspective, the DONE event means that a single sample is completed, but no result is yet ready if oversample is enabled. When the averaged result by the oversampling mechanism is ready, the peripheral will generate the RESULTDONE event, but at this point, the result is not yet transferred from the peripheral to the sample buffer in RAM. The result is first available in the RAM buffen when the END event is generated by the peripheral.

The naming of the software event from the driver may be a bit confusing, as the NRF_DRV_SAADC_EVT_DONE event in actually triggered when the driver receives the NRF_SAADC_EVENTS_END event from the peripheral. To sum up, the result is ready for use when you get this event in the driver, all oversampling is completed.

Best regards,
Jørgen