<?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/I2C with SDK 11 (long transfers)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/11230/twi-i2c-with-sdk-11-long-transfers</link><description>Hi, 
 I would like to use my NRF51DK with SDK11 and SD130 to control my SSD1306 OLED screen over TWI/I2C. 
 To refresh the OLED screen, we have to send it the whole display buffer in one transfer. All was working great under SDK9 and SDK10 (SD110) in</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 16 Nov 2016 05:07:46 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/11230/twi-i2c-with-sdk-11-long-transfers" /><item><title>RE: TWI/I2C with SDK 11 (long transfers)</title><link>https://devzone.nordicsemi.com/thread/42161?ContentTypeID=1</link><pubDate>Wed, 16 Nov 2016 05:07:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e7b4edf9-5454-49da-a219-04428b878cf4</guid><dc:creator>bg2bkk</dc:creator><description>&lt;p&gt;Hi，Arnaud, I change uint8_t to uint16_t but it seems to not work properly. I change all the related length in file nrf_drv_twi.c in SDK11，So what wrong with me ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TWI/I2C with SDK 11 (long transfers)</title><link>https://devzone.nordicsemi.com/thread/42160?ContentTypeID=1</link><pubDate>Sun, 17 Jan 2016 11:13:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ef9e2a83-2058-45ac-9418-2966afc91dff</guid><dc:creator>Arnaud Nelissen</dc:creator><description>&lt;p&gt;Thank you, I got it to work by, as you said, changing uint8_t length related attributes to uint16_t !&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TWI/I2C with SDK 11 (long transfers)</title><link>https://devzone.nordicsemi.com/thread/42159?ContentTypeID=1</link><pubDate>Mon, 11 Jan 2016 14:53:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:44069f40-3bbf-4eb8-be4b-e39cf88bf5b9</guid><dc:creator>&amp;#216;yvind Karlsen</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Right you are. In this case I think your best bet is to use the old driver from SDK 10. Hopefully it is not too complicated to port or alternately you can use SDK 10. The reason the new driver now only supports 255 bytes per transaction in order to be compliant with the 255 bytes per transaction limit on the EasyDMA. If you are using nRF51 you may be able to fix your problem by changing the length parameter from uint8_t to uint16_t as nRF51 does not have EasyDMA for TWI.&lt;/p&gt;
&lt;p&gt;TWI slaves can have trouble recieving multiple start signals, this may be what is causing your error.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>