https://devzone.nordicsemi.com/f/nordic-q-a/90015/adding-i2c-twi-eeprom-access-to-existing-spi-accessWe do have an eeprom accessed over the SPI, and works well. Need to add an option to access also the I2C eeprom. Adding to the project nrf_drv_twi,c, nrfx_twi.c, nrfx_twim.c - do I need to use both nrfx_twi.c and nrfx_twim.c? During compilationen-USTelligent Community 13Fri, 15 Jul 2022 12:33:45 GMThttps://devzone.nordicsemi.com/thread/377198?ContentTypeID=1Fri, 15 Jul 2022 12:33:45 GMT137ad170-7792-4731-bb38-c0d22fbe4515:078bd969-8f85-4068-85da-d0e2e8a088f4Simonr<p>Hi</p> <p>The SPI and TWI do indeed share instances, so you have to use another TWI instance than SPI instance. I don&#39;t think we have any specific examples using both, but we have separate SPI examples and TWI examples. It should be sufficient to move the TWI init function + driver and library files into your existing project and make sure you use a different TWI instance. Depending on what functions you want to use from the nrfx TWI drivers, you choose if you want just the nrfx_twi.c or the nrfx_twim.c (or both).</p> <p>Best regards,</p> <p>Simon</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/377116?ContentTypeID=1Fri, 15 Jul 2022 08:45:45 GMT137ad170-7792-4731-bb38-c0d22fbe4515:daee4060-843f-473f-9e79-57c7124e9357pkoenig<p>Most helpful would be a sample application for the Segger studio initializing SPI0 and TWIM1.&nbsp;<br />I am concerned about the twi includes not picking up the defines.</p><div style="clear:both;"></div>