https://devzone.nordicsemi.com/f/nordic-q-a/77173/how-do-i-include-nrfx-drivers-in-an-nrf-connect-sdk-projectI&#39;ve been trying to write a simple I2S loopback project for the nRF5340DK board using SES. Zephyr&#39;s documentation doesn&#39;t list I2S as a supported peripheral for this device, so I think I need to use the nrfx_i2s driver. I&#39;ve enabled Modules-&gt;hal_nordicen-USTelligent Community 13Tue, 06 Jul 2021 20:02:18 GMThttps://devzone.nordicsemi.com/thread/318860?ContentTypeID=1Tue, 06 Jul 2021 20:02:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fa92a7c6-3e84-4266-aae8-5b5736532b34JB_Teufel<p>Nevermind.&nbsp; In the process of reducing it to a minimal example for further troubleshooting, I realized it was specifically this definition that was the issue, and that I was calling the macro incorrectly.&nbsp; It looks like the API changed between the nRF5 17.0 SDK, where I borrowed the example code, and the nrfx drivers.&nbsp; Supplying the pins as arguments resolved this for me.&nbsp; Sorry about the confusion.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/318858?ContentTypeID=1Tue, 06 Jul 2021 19:29:01 GMT137ad170-7792-4731-bb38-c0d22fbe4515:be2bec7f-6721-48e9-9172-c2684d17a882JB_Teufel<p>One thing I forgot to mention is that SES is aware of the h file.&nbsp; If I right click in main and mouse over &quot;Go to included file&quot;, #include &lt;nrfx_is2.h&gt; is in the list, and I&#39;ve confirmed that it opens an h file with the definition of NRFX_I2S_DEFAULT_CONFIG.</p><div style="clear:both;"></div>