- Joined Jan 5, 2016
Hi, to save precious cycles I'd like to avoid interrupting after each ADC acquisition. Sometimes I'm round-robining, other times I'm just repeatedly sampling the same ANx to ensure I have the most up-to-date measurement for some other async function. Is there any risk of dirty reads if I just reference the appropriate ADC1BUFx when the result is consumed rather than using intermediary variables? I don't see any mention of such a risk in the family reference below. However when I have attempted this in the past I have noticed 0's coming thru occasionally, but I can't be sure this wasn't some other bug in my code. At the time I just backed away assuming it was a dirty read but now reading the docs I think it was more likely my bug.