https://devzone.nordicsemi.com/f/nordic-q-a/66928/zephyr-i2c-locked-into-ebusyThe crux of the problem is that my Zephyr I2C port is getting locked into EBUSY, and What are possible reasons for this How do I fix it Context: I&#39;m currently trying to port Zephyr onto the Arduino Nano 33 BLE. I2C0, which is connected toen-USTelligent Community 13Tue, 06 Apr 2021 11:23:44 GMThttps://devzone.nordicsemi.com/thread/303114?ContentTypeID=1Tue, 06 Apr 2021 11:23:44 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d29f50a5-58d3-4fda-8584-e4a9b3a8a7bdLeowt<p><span>Possibly related</span><br /><br /><span><a href="https://devzone.nordicsemi.com/f/nordic-q-a/73628/i2c-gets-stuck-with--ebusy-if-i2c_-function-calls-timeout-on-zephyr-ncs-for-nrf52840">devzone.nordicsemi.com/.../i2c-gets-stuck-with--ebusy-if-i2c_-function-calls-timeout-on-zephyr-ncs-for-nrf52840</a></span></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/274120?ContentTypeID=1Fri, 09 Oct 2020 23:13:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:59fee66b-7cb9-4c85-96fb-364c59015d70saltyJeff<p>Figured it out, it was a hardware issue. For some reason they decided to use 2 extra GPIO pins:<br /><br /></p> <p>One to power the pullup resistors, and one to provide power to the IC&#39;s</p> <p>The solution was to just drive both of those up.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/274036?ContentTypeID=1Fri, 09 Oct 2020 12:31:27 GMT137ad170-7792-4731-bb38-c0d22fbe4515:82a9ea99-eb51-407d-aaa7-e6deb1f10a5fSimonr<p>Hi</p> <p>I suspect this is due to the Arduino Nano 33 BLE does not include the external LF clock that is used by default in NCS. Please try adding these clock configs in prj.conf to use the internal RC oscillator instead.</p> <p><pre class="ui-code" data-mode="c_cpp">CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y CONFIG_CLOCK_CONTROL_NRF_K32SRC_250PPM=y</pre></p> <p>Best regards,</p> <p>Simon</p><div style="clear:both;"></div>