<?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>[mbed] I2C fails in a consistent pattern</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/12493/mbed-i2c-fails-in-a-consistent-pattern</link><description>I had a mbed firmware running on a ST Nucleo 64 that periodically query a sensor for data. It only use the I2C, a button interrupt and a LED for heartbeat. I ported it to a nRF51 target by changing the pin numbers. The firmware compiled just fine. And</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 11 Mar 2016 10:59:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/12493/mbed-i2c-fails-in-a-consistent-pattern" /><item><title>RE: [mbed] I2C fails in a consistent pattern</title><link>https://devzone.nordicsemi.com/thread/47343?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2016 10:59:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b16112ec-dc2c-464c-8136-8e84fe3b5851</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;None. I do not use that socket. The sensors are the four ICs lining up near the edge of the X-Nucleo shield. They are accessed via an I2C bus, which is what I am trying to do.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: [mbed] I2C fails in a consistent pattern</title><link>https://devzone.nordicsemi.com/thread/47342?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2016 10:54:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2cb24eaa-dc2a-4f53-9114-2416a4d0758d</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;I mean the 24-pin DIL socket&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: [mbed] I2C fails in a consistent pattern</title><link>https://devzone.nordicsemi.com/thread/47341?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2016 10:47:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:49b5518b-6b9f-4fff-adbf-46bc25f5b157</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;Sorry I guess I could have embedded an URL there instead of giving just the part number. While I make that quick edit I didn&amp;#39;t have time to think much about it.&lt;/p&gt;
&lt;p&gt;However I don&amp;#39;t understand your question. What do you mean by socket? In case this answer your confusion, both nRF51 and the X-Nucleo shield has Arduino UNO Rev 3 compliance connectors. Power would be supplied correctly to the shield and I2C lines would be aligned correctly as well.&lt;/p&gt;
&lt;p&gt;Going to update the questions with all these information now.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: [mbed] I2C fails in a consistent pattern</title><link>https://devzone.nordicsemi.com/thread/47340?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2016 10:19:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0e22438d-5a82-4513-9d30-0816da8dee32</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;Sounds like you had some bad and/or missing connections with your jumper wires.&lt;/p&gt;
&lt;p&gt;Remember that the X-Nucleo is an &lt;strong&gt;ST&lt;/strong&gt; product; nothing to do with Nordic. This is the &lt;strong&gt;Nordic&lt;/strong&gt; forum, so don&amp;#39;t assume that people here will know anything about it. Provide a link so that we can see what you&amp;#39;re talking about.&lt;/p&gt;
&lt;p&gt;I presume you mean this: &lt;a href="http://www.st.com/web/catalog/tools/FM116/SC1248/PF261191"&gt;www.st.com/.../PF261191&lt;/a&gt; ?&lt;/p&gt;
&lt;p&gt;But what are you plugging into the socket ... ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: [mbed] I2C fails in a consistent pattern</title><link>https://devzone.nordicsemi.com/thread/47339?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2016 09:24:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:53062104-6a90-4d97-9663-5fa4929c83db</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;I have updated the question now. My guess is that this would be more of a hardware issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: [mbed] I2C fails in a consistent pattern</title><link>https://devzone.nordicsemi.com/thread/47338?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2016 09:17:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88a4c9b9-1a03-4b75-a20a-b106c93a0b36</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;I actually found out something new, going to work on updating the question post now.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: [mbed] I2C fails in a consistent pattern</title><link>https://devzone.nordicsemi.com/thread/47337?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2016 09:16:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3c74e3b2-501b-4774-87ac-03dfae021f9d</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;I am sorry I was a bit ambiguous at that part. I mean the firmware itself runs fine. Functions are called correctly. UART debugging messages are printed out as expected.
However, I2C communication keep failing with a no slave ack.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: [mbed] I2C fails in a consistent pattern</title><link>https://devzone.nordicsemi.com/thread/47336?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2016 08:39:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4cd97da4-b177-4322-8efd-c01cc78ce177</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;What do you mean. &amp;quot;it runs on the nRF51-DK with no problem&amp;quot;? So what are you running on when you do get the problem?&lt;/p&gt;
&lt;p&gt;IF it&amp;#39;s consistent, it should be easy to debug: just look at what happens when it &amp;quot;works&amp;quot; and what happens when it fails - and spot the difference.&lt;/p&gt;
&lt;p&gt;For the symptoms you describe, I would be looking for timing issues and incomplete initialisation...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>