https://devzone.nordicsemi.com/f/nordic-q-a/83735/only-i2c-nodes-accepted-in-soc-i2c-40004000Hi, Hope you can help. With a nrf52840dk development kit arriving tomorrow. We tried to make a start with a nRF52840 dongle, which we eventually want to use. Connected to a MACREFDES117# Maxim Integrated Heart-Rate and Pulse Oximetry Monitor Developmenten-USTelligent Community 13Wed, 19 Jan 2022 11:57:43 GMThttps://devzone.nordicsemi.com/thread/348483?ContentTypeID=1Wed, 19 Jan 2022 11:57:43 GMT137ad170-7792-4731-bb38-c0d22fbe4515:69d0b8e3-535a-47cd-933f-3106cbaf2bb1Emerson Warwick<p>Correct. The compiler compiles&nbsp;ok. Thanks.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/348330?ContentTypeID=1Tue, 18 Jan 2022 14:49:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a773eb4c-f280-4ae5-b3ba-727adaa36752Hung Bui<p>Hi Andy,&nbsp;</p> <p>As far as I can see the compiler will not give a warning when you compile, correct&nbsp; ?</p> <p>The naming is just to avoid confusion that we are going to use the i2c driver from Zephyr but instead uses the nrfx driver ( also in this case we are naming the peer device, not the local device itself)<br />I don&#39;t think it&#39;s a big problem. You can change the name to <span>i2c-device:nRF52840</span><span>@</span><span>28 as well.&nbsp;</span></p><div style="clear:both;"></div>