<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Openthread and TWI interface does not merge in GitHub openthread source OT-nRF52840.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/79033/the-openthread-and-twi-interface-does-not-merge-in-github-openthread-source-ot-nrf52840</link><description>Hello Team, 
 I am using the OT-nRF52840 source and working on the end device. I want to add the I2C(TWI) support in my end application, but as soon as I add any API it shows an error like the undefined reference to `nrfx_twi_init&amp;#39;. However, the TWI&amp;#39;s</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 30 Aug 2021 12:09:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/79033/the-openthread-and-twi-interface-does-not-merge-in-github-openthread-source-ot-nrf52840" /><item><title>RE: The Openthread and TWI interface does not merge in GitHub openthread source OT-nRF52840.</title><link>https://devzone.nordicsemi.com/thread/327207?ContentTypeID=1</link><pubDate>Mon, 30 Aug 2021 12:09:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:614b541c-54ea-4e98-ab17-4bcdf29fef59</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello Hardik,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Have you&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/drivers_nrfx_v2.5.0/index.html"&gt;looked at the nrfx documentation?&lt;/a&gt;&amp;nbsp;In the Introduction and configuration it states:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The purpose of nrfx is to make it possible to use the same set of peripheral drivers in various environments, from RTOSes to bare metal applications. Hence, for a given host environment, a light integration layer must be provided that implements certain specific routines, like interrupt management, critical sections, assertions, or logging. This is done by filling a predefined set of macros with proper implementations (or keeping some empty if desired) in files named:&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/drivers_nrfx_v2.5.0/group__nrfx__glue.html"&gt;nrfx_glue.h&lt;/a&gt;&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/drivers_nrfx_v2.5.0/group__nrfx__log.html"&gt;nrfx_log.h&lt;/a&gt;&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Templates of these files are provided in the&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/templates/"&gt;templates&lt;/a&gt;&amp;nbsp;subfolder. Their customized versions can be placed in any location within the host environment that the used compiler can access via include paths.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;In addition, the following locations should be specified as include paths ([nrfx] stands for the nrfx root folder location):&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;pre class="ui-code" data-mode="text"&gt;[nrfx]/
[nrfx]/drivers/include
[nrfx]/mdk&lt;/pre&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Let me know how that works for you.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>