<?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 communication doesn&amp;#39;t work</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8577/twi-communication-doesn-t-work</link><description>Hello, 
 I&amp;#39;m writing a driver for an I2C device (it&amp;#39;s an external led driver).
My current code executes following steps ... 
 First I changed I2C configuration : 
 static const nrf_drv_twi_config_t twi_config = {
.frequency = NRF_TWI_FREQ_400K,</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 07 Aug 2015 06:20:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8577/twi-communication-doesn-t-work" /><item><title>RE: TWI communication doesn't work</title><link>https://devzone.nordicsemi.com/thread/31371?ContentTypeID=1</link><pubDate>Fri, 07 Aug 2015 06:20:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b7bdc11f-19af-4469-826a-881677e07638</guid><dc:creator>&amp;#216;yvind Karlsen</dc:creator><description>&lt;p&gt;Yes, you set the RX and TX pin for UART as a part of the initialization call, see &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk51.v9.0.0/structapp__uart__comm__params__t.html?cp=4_1_0_6_7_2_0"&gt;this infocenter page&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TWI communication doesn't work</title><link>https://devzone.nordicsemi.com/thread/31369?ContentTypeID=1</link><pubDate>Thu, 06 Aug 2015 15:18:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7993d60c-6df0-47f5-867f-4e9f3bb52092</guid><dc:creator>Alex</dc:creator><description>&lt;p&gt;Yes, change for any unused. If you are using nRF51 DK development board you can use RTT for console debugging.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TWI communication doesn't work</title><link>https://devzone.nordicsemi.com/thread/31370?ContentTypeID=1</link><pubDate>Thu, 06 Aug 2015 15:15:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:84acc935-2ec7-4091-8583-9cc4b101cf98</guid><dc:creator>ppatierno</dc:creator><description>&lt;p&gt;I just discovered that I setup UART an the RX_PIN_NUMBER is 11 ... like the SCL !!
I started from the ANCS example so never modified it. Is it possibile to change the RX_PIN_NUMBER with any other pins for using UART ? (I need it for console debugging)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TWI communication doesn't work</title><link>https://devzone.nordicsemi.com/thread/31368?ContentTypeID=1</link><pubDate>Thu, 06 Aug 2015 15:04:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1c507b03-ad29-46a4-9325-c7cbb28b0ffd</guid><dc:creator>Alex</dc:creator><description>&lt;p&gt;Is there anything else connected to SCL line on your PCB?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TWI communication doesn't work</title><link>https://devzone.nordicsemi.com/thread/31367?ContentTypeID=1</link><pubDate>Thu, 06 Aug 2015 14:50:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6ca16874-b2e1-473f-815c-42b792aa9edf</guid><dc:creator>ppatierno</dc:creator><description>&lt;p&gt;Yes I&amp;#39;m sure. Using oscilloscope I see two strange things : I execute my code only one time but the signals changes continuously (the trigger on the oscilloscope is always active) and the SCL clock isn&amp;#39;t a period signal and it&amp;#39;s not about 400 KHz as frequency it seems to be as Mhz signal&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TWI communication doesn't work</title><link>https://devzone.nordicsemi.com/thread/31366?ContentTypeID=1</link><pubDate>Thu, 06 Aug 2015 14:23:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:592d8967-2c4a-4dde-9503-46833e6bbe69</guid><dc:creator>Alex</dc:creator><description>&lt;p&gt;Have you used correct IO pins for TWI according to your hardware?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TWI communication doesn't work</title><link>https://devzone.nordicsemi.com/thread/31365?ContentTypeID=1</link><pubDate>Thu, 06 Aug 2015 13:01:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b5f7227a-f48c-4142-ad70-6f42f4d40563</guid><dc:creator>ppatierno</dc:creator><description>&lt;p&gt;I just realized that the nrf_drv_twi_tx function return 3 as error code so NRF_ERROR_INTERNAL. How can I check what&amp;#39;s the internal error ? (I&amp;#39;m working in blocking mode).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>