https://devzone.nordicsemi.com/f/nordic-q-a/126644/pointer-to-documentation-pleaseIn the past, I&#39;ve been told I can bypass a lot of the Zephyr nonsense and use the HAL layers of the nRF Connect SDK directly. So if I want to use what was called nrfx_twim_xfer in old SDK, what is the equivalent of that in nRF Connect SDK? Can you pointen-USTelligent Community 13Wed, 21 Jan 2026 15:14:32 GMThttps://devzone.nordicsemi.com/thread/559292?ContentTypeID=1Wed, 21 Jan 2026 15:14:32 GMT137ad170-7792-4731-bb38-c0d22fbe4515:670f16b8-a097-4a1a-8e26-c142a133061fRandy Lee<p>Nuts.&nbsp; I was hoping, based on other conversations, that I could bypass a lot of the plain stupid things zephyr does but it looks like there is way too much tentacles running around to do that reliably.</p> <p>well... back to the drawing board.&nbsp; Thanx anyway.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/559286?ContentTypeID=1Wed, 21 Jan 2026 15:00:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:18fedd9c-19c6-44d4-a528-0f4d8524496eTurbo J<p>There is close to zero overhead for I&sup2;C devices when using zephyr drivers. The bus is dead slow on its own. I strongly recommend learning how to use zephyr drivers first, including the DTS overlay stuff.</p> <p>There is probaly no more accurate documentation online. Your best bet is to&nbsp;<em>read the source code.</em> Remember that you have&nbsp;<em>working</em> zephyr drivers to copy from available.</p> <p>And if you try running your own code its very easy to get bitten by the zephyr drivers - which have interrupts enabled for example. DTS overlay is a non-trivial task here!</p><div style="clear:both;"></div>