<?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>Two-wire interface does not work together with Bluetooth</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/1854/two-wire-interface-does-not-work-together-with-bluetooth</link><description>Hi! 
 I am using nRF51822 evaluation kit and connecting it as a master to a pair of I2C-devices (using twi_hw_master.c). Everything works well, but when I integrated the TWI (I2C) example code with the Nordic example ble_app_hrs (hear rate monitor) the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 12 Mar 2014 14:05:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/1854/two-wire-interface-does-not-work-together-with-bluetooth" /><item><title>RE: Two-wire interface does not work together with Bluetooth</title><link>https://devzone.nordicsemi.com/thread/8034?ContentTypeID=1</link><pubDate>Wed, 12 Mar 2014 14:05:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:77bbb2a7-bba6-4d7c-b1e2-f383f8569e9e</guid><dc:creator>Jarmo</dc:creator><description>&lt;p&gt;On the chip there was actually QFAAC0, so it&amp;#39;s actually the first revision...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Two-wire interface does not work together with Bluetooth</title><link>https://devzone.nordicsemi.com/thread/8033?ContentTypeID=1</link><pubDate>Wed, 12 Mar 2014 13:18:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f84d38d4-0a0b-4802-a59f-cad237f49254</guid><dc:creator>Jarmo</dc:creator><description>&lt;p&gt;Thanks, our order code is 949-NRF51822-QFAA-R7, so it looks like it is the second revision, right?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Two-wire interface does not work together with Bluetooth</title><link>https://devzone.nordicsemi.com/thread/8032?ContentTypeID=1</link><pubDate>Wed, 12 Mar 2014 12:35:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9679ec46-9240-4f4b-b829-3a72fcde8c99</guid><dc:creator>Ole Morten</dc:creator><description>&lt;p&gt;The different revisions of the chip is shown in both the PAN and the PCN, and you can identify a chip by looking at its chip markings.&lt;/p&gt;
&lt;p&gt;In summary, on a 256 kB nRF51822 anything later than QFAAFA on the second line are second revision chips.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Two-wire interface does not work together with Bluetooth</title><link>https://devzone.nordicsemi.com/thread/8031?ContentTypeID=1</link><pubDate>Wed, 12 Mar 2014 09:58:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:274eea63-fea2-45db-a7dc-cec7b99ef634</guid><dc:creator>Jarmo</dc:creator><description>&lt;p&gt;How can we check which revision we have in our Evaluation Board? Also, we have just ordered our custom PCBs and would need to check what is the revision of the chips that will be installed on them.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Two-wire interface does not work together with Bluetooth</title><link>https://devzone.nordicsemi.com/thread/8030?ContentTypeID=1</link><pubDate>Tue, 11 Mar 2014 20:37:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6bca3c04-3876-4a05-81dd-1913adfdf1ac</guid><dc:creator>Jarmo</dc:creator><description>&lt;p&gt;Thanks for the quick answer! I will examine the thing tomorrow.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Two-wire interface does not work together with Bluetooth</title><link>https://devzone.nordicsemi.com/thread/8029?ContentTypeID=1</link><pubDate>Tue, 11 Mar 2014 14:51:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e499833-19b6-4a51-a4c2-d9cdc1c40ba3</guid><dc:creator>Ole Morten</dc:creator><description>&lt;p&gt;This has been covered at length here before, so I&amp;#39;d recommend you to browse around a little, for instance looking at &lt;a href="https://devzone.nordicsemi.com/index.php/using-i2c-gpiote-interrupt-with-soft-device-enabled"&gt;this question&lt;/a&gt;, or one of the multiple others &lt;a href="https://devzone.nordicsemi.com/index.php/search?query=twi&amp;amp;option=com_easydiscuss&amp;amp;view=search&amp;amp;Itemid=479"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;However, I just finished a quick example of how the TWI can be used with the softdevice on second revision chips, and that example is available &lt;a href="https://github.com/NordicSemiconductor/nrf51-ble-app-lbs/tree/twi-display-5.1.0"&gt;here&lt;/a&gt;, including a modified version of twi_hw_master.c, taking advantage of the working SHORTS on second revision chips.&lt;/p&gt;
&lt;p&gt;If you use first revision chips, you should instead follow the suggested workaround in the question I linked to above, using the sd_ppi_* interface.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>