<?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>Possible bug in TWI HW</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/3891/possible-bug-in-twi-hw</link><description>Hi 
 I&amp;#39;m having a strange behaviour when using the TWI HW peripheral for reading from an I2C device. My application tries to read one byte from a register in a I2C device. As background: 
 -I2C address: 0x55
-Register address: 0x0A
-Expected value</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 25 Sep 2014 14:37:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/3891/possible-bug-in-twi-hw" /><item><title>RE: Possible bug in TWI HW</title><link>https://devzone.nordicsemi.com/thread/14000?ContentTypeID=1</link><pubDate>Thu, 25 Sep 2014 14:37:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e6cca6e0-540f-48fb-884a-ec73a28926ef</guid><dc:creator>Elena</dc:creator><description>&lt;p&gt;Hi MatBB&lt;/p&gt;
&lt;p&gt;I desisted about using the TWI peripheral and now I&amp;#39;m using the TWI SW to implement an I2C bus by using two GPIOs. Now it is working correctly.&lt;/p&gt;
&lt;p&gt;Thanks for your help&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible bug in TWI HW</title><link>https://devzone.nordicsemi.com/thread/13999?ContentTypeID=1</link><pubDate>Tue, 23 Sep 2014 13:50:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d4a0e0ba-2206-478b-aade-8cdfaf74d8ff</guid><dc:creator>Matt Barr</dc:creator><description>&lt;p&gt;I had trouble with TWI + softdevice and found this forum posting to be very useful:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/question/15743/nrf51822-s110-problem-with-i2c-to-mpu9150/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In Stefan&amp;#39;s answer you&amp;#39;ll find a link to twi_hw_master_sd.c. I had trouble with link failures using twi_hw_master.c from the 6.0.0 SDK, these problems cleaned up after switching to the _sd version.&lt;/p&gt;
&lt;p&gt;I do still see some apparent clock mis-behavior, but it appears as a shortened clock low time associated with a NAK:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/3326.Capture.PNG" alt="image description" /&gt;&lt;/p&gt;
&lt;p&gt;The TWI master configured for 250 kHz operation, this shows an attempted access to a slave device that is not present. Fortunately the 1.1 us clock low time is well above the minimum clock low time for our slave devices and this isn&amp;#39;t causing any problems.&lt;/p&gt;
&lt;p&gt;If you are not already using it, you might try twi_hw_master_sd.c. I started a test yesterday that accesses a TWI slave every 100 ms under timer/scheduler control. TWI interface and BLE stack both survived the night.&lt;/p&gt;
&lt;p&gt;Best Regards and Good Luck!&lt;/p&gt;
&lt;p&gt;Matt&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>