<?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>TWI Init/Uninit Driver Bug</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/11511/twi-init-uninit-driver-bug</link><description>I have an application that uses many TWI buses, on many pins of the nRF51. I handle this by initializing/uninitializing a single TWI bus for different transactions. I ran into the issue where the TWI driver would get stuck in &amp;quot;transfer_in_progress&amp;quot; every</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 05 Oct 2016 14:15:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/11511/twi-init-uninit-driver-bug" /><item><title>RE: TWI Init/Uninit Driver Bug</title><link>https://devzone.nordicsemi.com/thread/43530?ContentTypeID=1</link><pubDate>Wed, 05 Oct 2016 14:15:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1bb9e06a-db8c-4e25-a68b-703df4c6af34</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The intended procedure to start any I/O peripheral is to:
CONFIGURE-&amp;gt;ENABLE-&amp;gt;START
And in the reverse order to stop any I/O peripheral:
STOP(wait for event)-&amp;gt;DISABLE(-&amp;gt;RECONFIGURE)&lt;/p&gt;
&lt;p&gt;All HW modules is based on this principle.&lt;/p&gt;
&lt;p&gt;If the I/O peripheral use a shared reseource with another peripheral also used by the application, then you need to carefully check all configuration settings when it is failing, in case you depend on a default value that might have changed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TWI Init/Uninit Driver Bug</title><link>https://devzone.nordicsemi.com/thread/43529?ContentTypeID=1</link><pubDate>Tue, 04 Oct 2016 16:04:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:676e1f22-87ca-494d-8def-e2c969bc459d</guid><dc:creator>Carl</dc:creator><description>&lt;p&gt;I ran into kind of the same problem with SDK v11 (nRF52).&lt;/p&gt;
&lt;p&gt;In the beginning I initialize and enable TWI, tx and rx works fine.
After deinitializing and reinitializing (to change the frequency), tx does not work anymore.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s stuck in function twi_tx_start_transfer(...) of driver nrf_drv_twi.c in the loop while(twi_transfer(...)) at line 450.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TWI Init/Uninit Driver Bug</title><link>https://devzone.nordicsemi.com/thread/43528?ContentTypeID=1</link><pubDate>Mon, 01 Feb 2016 12:45:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:63e218f0-47d4-4c07-b44b-4ace041dfbed</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I do not know if there is still a similar issue in the current SDK, but from what I can see the TWI driver is completely rewritten for SDK 11.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>