https://devzone.nordicsemi.com/f/nordic-q-a/5658/nrf9e5-i2cHi, 1- Many MCUs, including NRF9E5, have specialized communication ports like UART or SPI. Why not I2C? I assume that every pin can be programmed for any communication protocol if hardware allows. 2- I would like to use NRF9E5 in my project whereen-USTelligent Community 13Tue, 24 Feb 2015 15:27:08 GMThttps://devzone.nordicsemi.com/thread/19825?ContentTypeID=1Tue, 24 Feb 2015 15:27:08 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b260da4f-7f9a-4e97-b51d-e2bb3a8aab08Mustafa AYDIN<p>Thanks for the revealing answer and the link. Additionally, I plan to use a very small size led screen which uses I2C. So there is nothing high speed and I think a SW I2C also OK with that, as long as it provides an overage I2C.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/19824?ContentTypeID=1Tue, 24 Feb 2015 13:14:12 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1d9ed4a4-7af2-44ee-8c9d-d42e83a94bfcJon Gunnar<p>Hi,</p> <p>The nRF9E5 is not equipped with a hardware I2C interface, but it is possible to use the GPIOs and implement a software I2C. There is an example of this in the nRF9E5 firmware example pack here: <a href="https://www.nordicsemi.com/eng/nordic/download_resource/10787/4/59166513">www.nordicsemi.com/.../59166513</a> This SW I2C can be sufficient if you just want to read sensor data now and then. If you have sensors that requires high data speed, you should use SPI instead.</p><div style="clear:both;"></div>