https://devzone.nordicsemi.com/f/nordic-q-a/52810/saadc-problemHi, I&#39;m working on a simple SAADC acquire in scan mode. I create the two following function: I was able to init and read the adc without problem. If I remove the 5 us delay in the read_adc() funciton the firmware stop to work. In debug modeen-USTelligent Community 13Wed, 02 Oct 2019 12:44:37 GMThttps://devzone.nordicsemi.com/thread/213002?ContentTypeID=1Wed, 02 Oct 2019 12:44:37 GMT137ad170-7792-4731-bb38-c0d22fbe4515:cdc8eb98-02fc-40e3-9a9b-784f1dd06381AndreaSYN<p>Perfect</p> <p>I follow the erratas and I fix it.</p> <p>Thanks a lot,</p> <p>Andrea.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/212987?ContentTypeID=1Wed, 02 Oct 2019 11:55:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e467cb05-ff0b-4ed0-9278-8a9c1e7b4785J&#248;rgen Holmefjord<p>Hi,</p> <p>I think this behavior is caused by errata <a href="https://infocenter.nordicsemi.com/topic/errata_nRF52832_Rev2/ERR/nRF52832/Rev2/latest/anomaly_832_178.html?cp=3_1_1_0_1_45">[178] SAADC: END event firing too early</a>. If you increase TACQ to 10 us, the application seems to run as expected without the delay. Triggering the STOP task after offset calibration also seems to solve the issue. This workaround will also fix errata 86 that I have linked below.</p> <p>Note that you should not need to trigger the STOP task after you are done sampling. When you receive the END event, you will need to trigger the START task again to start the SAADC so this should be equivalent to the STOPPED event.</p> <p>Also, make sure to check out these other erratas that may affect your application:</p> <ul> <li><a href="https://infocenter.nordicsemi.com/topic/errata_nRF52832_Rev2/ERR/nRF52832/Rev2/latest/anomaly_832_74.html?cp=3_1_1_0_1_14">[74] SAADC: Started events fires prematurely</a></li> <li><a href="https://infocenter.nordicsemi.com/topic/errata_nRF52832_Rev2/ERR/nRF52832/Rev2/latest/anomaly_832_86.html?cp=3_1_1_0_1_23">[86] SAADC: Triggering START task after offset calibration may write a sample to RAM</a></li> <li><a href="https://infocenter.nordicsemi.com/topic/errata_nRF52832_Rev2/ERR/nRF52832/Rev2/latest/anomaly_832_150.html?cp=3_1_1_0_1_40">[150] SAADC: EVENT_STARTED does not fire</a></li> </ul> <p>Best regards,<br />Jørgen</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/212951?ContentTypeID=1Wed, 02 Oct 2019 09:32:50 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d06d1653-9d71-49a3-b036-f583303c02ebAndreaSYN<p>Also I notice that if I configure only one channel so SAADC is in One-shot mode the delay is not needed.</p><div style="clear:both;"></div>