<?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>Supper Weird I2C faliture</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/92386/supper-weird-i2c-faliture</link><description>Hey Devzone community 
 I have a super weird I2C problem. 
 While configuring, everything is fine - however, when I&amp;#39;m trying to use the I2C API read_register and write_register functions, I&amp;#39;m getting the 0X0BAE0001 error (Internal error), which corresponds</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 30 Sep 2022 14:45:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/92386/supper-weird-i2c-faliture" /><item><title>RE: Supper Weird I2C faliture</title><link>https://devzone.nordicsemi.com/thread/388820?ContentTypeID=1</link><pubDate>Fri, 30 Sep 2022 14:45:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:85f20e10-8576-44e0-a31b-764668f074df</guid><dc:creator>Meh</dc:creator><description>&lt;p&gt;Well.&lt;/p&gt;
&lt;p&gt;I tried scanning for different sensors, and the target DEVKIT for that specific sensor appears defective.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Supper Weird I2C faliture</title><link>https://devzone.nordicsemi.com/thread/388742?ContentTypeID=1</link><pubDate>Fri, 30 Sep 2022 10:59:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4ed2e075-c596-48ee-a0cc-f76f77572294</guid><dc:creator>Michal</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Have you checked the connection with a logic analyzer or an oscilloscope?&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/zephyrproject-rtos/hal_nordic/blob/master/nrfx/drivers/nrfx_errors.h#L70"&gt;0x0BAE0001 error&lt;/a&gt; means &amp;quot;T&lt;span&gt;WI error: Address not acknowledged.&amp;quot;, which is when your I2C peripheral returns a NACK, because of a wrong I2C address.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;There was also an &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/75770/i2c_nrfx_twi-error-0x0bae0001-occurred-for-message-0"&gt;earlier case&lt;/a&gt; with that error, where it was a hardware issue.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Michal&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Supper Weird I2C faliture</title><link>https://devzone.nordicsemi.com/thread/388635?ContentTypeID=1</link><pubDate>Thu, 29 Sep 2022 18:38:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c259bc8c-215a-474b-b5b5-7cb74e5a0653</guid><dc:creator>Meh</dc:creator><description>&lt;p&gt;Anyone?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>