<?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 driver problem?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/18949/i2c-driver-problem</link><description>I am using PCA10040 evaluation board to test I2C connection. 
 I tried twi_scanner sample code in SDK 12. 
 I wired SCL and SDA pins to D0 and D1 to a PicoScope device.
 
 When the code was running, I captured signals from those two pins.
 
 
</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 13 Jan 2017 03:23:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/18949/i2c-driver-problem" /><item><title>RE: I2C driver problem?</title><link>https://devzone.nordicsemi.com/thread/73237?ContentTypeID=1</link><pubDate>Fri, 13 Jan 2017 03:23:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31fc785e-6566-4da3-ae95-a5752756e732</guid><dc:creator>djqtsg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;forget this question.&lt;/p&gt;
&lt;p&gt;The strange signal most likely is caused by PicoScope or my not properly using it; because even when I2C was working, I also captured funny clock and data signal.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>