https://devzone.nordicsemi.com/f/nordic-q-a/42189/combine-two-different-twi-into-a-single-functionHi! I am using nrf52840,sdk 14.2,Keil IDE I am using bmp180 and mpu6050 sensors. In proximity code,I have integrated both sensors separately,It works fine. But while combining two sensor codes,I have a problem because both have different twi functionen-USTelligent Community 13Mon, 07 Jan 2019 08:47:09 GMThttps://devzone.nordicsemi.com/thread/164164?ContentTypeID=1Mon, 07 Jan 2019 08:47:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b50c6a3d-77e7-40af-b709-6cfa4a3e9fb7awneil<p>The standard approach is to have a <em><strong>layered</strong></em> approach:</p> <p><a href="https://en.wikipedia.org/wiki/OSI_model">https://en.wikipedia.org/wiki/OSI_model</a></p> <p><a href="https://www.webopedia.com/quick_ref/OSI_Layers.asp">https://www.webopedia.com/quick_ref/OSI_Layers.asp</a></p> <p>That way, you separate the basic hardware operations - START condition, Addressing, ACK, NAK, transferring bytes - from the specific details for each sensor.</p> <p>You will also need to make sure that&nbsp;your code for one sensor doesn&#39;t try to use the bus while your code for the other sensor is using it!</p> <p>EDIT</p> <p>The Nordic <a href="https://www.nordicsemi.com/Software-and-Tools/Development-Kits/Nordic-Thingy-52" rel="noopener noreferrer" target="_blank"><strong>Thingy</strong> </a>has several slaves on its I2C bus - so you could look at how that handles it ...</p> <p>I would suggest that you work this out first <em><strong>without</strong> </em>the added complication of BLE.</p> <p>The I2C specification is here:&nbsp;<a href="https://www.nxp.com/docs/en/user-guide/UM10204.pdf">www.nxp.com/.../UM10204.pdf</a></p><div style="clear:both;"></div>