SAADC: TASKS_CALIBRATEOFFSET shall only be used before TASKS_START or after EVENTS_END nRF52833

[maya_sa]

Hi. I was wandering if there is a difference if I put the TASKS_CALIBRATEOFFSET before TASKS_START , and vise versa.
However, I saw in this link: infocenter.nordicsemi.com/index.jsp that the TASKS_CALIBRATEOFFSET must come before the TASKS_START , and I am wondering why. (all I found out was that this is an anomaly inherited from the previous IC revision.
Thank you

[Karl Ylvisaker]

Hello,

I was wandering if there is a difference if I put the TASKS_CALIBRATEOFFSET before TASKS_START , and vise versa.

I am not sure I understand the question here - there is a difference if TASKS_CALIBRATEOFFSET is triggered after TASKS_START, as mentioned in the Errata description.

TASKS_CALIBRATEOFFSET must come before the TASKS_START , and I am wondering why. (all I found out was that this is an anomaly inherited from the previous IC revision.

Yes, as written in the Errata 237 that you reference; if you trigger TASKS_CALIBRATEOFFSET between TASKS_START and TASKS_END, then you will see unexpected samples written to your RAM. This is the reason why you will need to avoid triggering TASKS_CALIBRATEOFFSET between TASKS_START and TASKS_END.
The workaround for this errata - to avoid seeing unexpected samples written to RAM - is to only ever trigger TASKS_CALIBRATEOFFSET either before TASKS_START or after TASKS_END, i.e when the SAADC is not actively in use.

Please let me know if I misunderstood any part of your question.

Best regards,
Karl