<?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>i2C operation with SDK V2.9.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/119724/i2c-operation-with-sdk-v2-9-0</link><description>I have a production system running a modified asset_tracker_v2 sending temperature data to AWS. All is working fine with V2.5.0 on several hundred sensors. I am trying to upgrade to v2.9.0 and I ran into a problem with I2C. I have attached my prj.conf</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 14 Mar 2025 08:46:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/119724/i2c-operation-with-sdk-v2-9-0" /><item><title>RE: i2C operation with SDK V2.9.0</title><link>https://devzone.nordicsemi.com/thread/527331?ContentTypeID=1</link><pubDate>Fri, 14 Mar 2025 08:46:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c8fa519e-8a9d-488d-99d7-aaba8f106712</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>[quote user="tjm1"]Hakon yes that worked perfectly.[/quote]
&lt;p&gt;Glad to hear!&lt;/p&gt;
[quote user="tjm1"]Thank you for your quick response.[/quote]
&lt;p&gt;Always happy to help out!&lt;/p&gt;
&lt;p&gt;Hope you have a great weekend!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: i2C operation with SDK V2.9.0</title><link>https://devzone.nordicsemi.com/thread/527245?ContentTypeID=1</link><pubDate>Thu, 13 Mar 2025 16:20:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f74aa985-e577-4148-a737-b5a68d1e08e0</guid><dc:creator>Timothy</dc:creator><description>&lt;p&gt;Hakon yes that worked perfectly. Thank you for your quick response. This can be closed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: i2C operation with SDK V2.9.0</title><link>https://devzone.nordicsemi.com/thread/526880?ContentTypeID=1</link><pubDate>Wed, 12 Mar 2025 10:13:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c142c69e-4ee5-4fe2-8177-ad8fc105e349</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
[quote user=""]&amp;lt;err&amp;gt; os: r3/a4: 0x40009000[/quote]
&lt;p&gt;This is the base address of TWIM1 (and UARTE1/SPI*1), and it indicates that the fault is due to a permission issue.&lt;/p&gt;
&lt;p&gt;Could you try to disable TFM logging to see if this is the root of the issue? TFM uses uart1 by default, which&amp;nbsp;collides with your usage of i2c1.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CONFIG_TFM_SECURE_UART=n
CONFIG_TFM_LOG_LEVEL_SILENCE=y&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>