https://devzone.nordicsemi.com/f/nordic-q-a/118979/possible-conflict-with-i2s-and-saadc-channel-0Hi I have a fully functional addressable LED driver interface using I2S + app_timer. This code has been functional for a long time by itself. I just added the SAADC example to read AIN4 and AIN5 with PPI and TIMER2 (tried TIMER3 as well). Upon furtheren-USTelligent Community 13Tue, 18 Feb 2025 08:39:16 GMThttps://devzone.nordicsemi.com/thread/523421?ContentTypeID=1Tue, 18 Feb 2025 08:39:16 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a3b69dba-2e77-46c0-ac27-742a1b02d0b9Hung Bui<p>Hi,&nbsp;<br />I&#39;m taking over the ticket from Håkon since you are using legacy SDK.&nbsp;<br /><br />Could you give some more debug information regarding the issue ? I&#39;m not aware of any known issue about I2S and SAADC.&nbsp;<br /><br /></p> <p>You mentioned no cooperating, could you elaborate a bit more ? It&#39;s important to pin point where the issue is.&nbsp;<br /><br />If you disable I2S do you still see the issue ?&nbsp; Have you checked the AIN0 pin to see if there is anything suspicious&nbsp; ?&nbsp;<br /><br /><br /></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/523313?ContentTypeID=1Mon, 17 Feb 2025 14:25:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:323f6e77-88c5-46f5-883a-64369334ff8ams360<p>I&#39;m using nrf52840 and nRF SDK 17.1</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/523274?ContentTypeID=1Mon, 17 Feb 2025 13:15:56 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1542139f-6430-4f83-9b39-559680d06b86Elfving<p>Hello,</p> <p>What SoC and NCS version are you using?</p> <p>Regards,</p> <p>Elfving</p><div style="clear:both;"></div>