<?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>update i2cdevlib from nrf51 to nrf52</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/23172/update-i2cdevlib-from-nrf51-to-nrf52</link><description>HI, i m working in a project using mpu6050 and hmc5883l in same chip and nrf52832. indeed, i see that guys face many problem with twi connexion. so i decided to create a self library for twi connexion inspired from jrowberg library, But luckly i find</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 03 Jul 2017 12:20:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/23172/update-i2cdevlib-from-nrf51-to-nrf52" /><item><title>RE: update i2cdevlib from nrf51 to nrf52</title><link>https://devzone.nordicsemi.com/thread/91154?ContentTypeID=1</link><pubDate>Mon, 03 Jul 2017 12:20:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f143ed0-f34f-47c1-976e-166598f88562</guid><dc:creator>omar </dc:creator><description>&lt;p&gt;thanks for your help, i fixed the problem.i update the library to be adapted to NRF52 and it s working very well.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: update i2cdevlib from nrf51 to nrf52</title><link>https://devzone.nordicsemi.com/thread/91155?ContentTypeID=1</link><pubDate>Mon, 03 Jul 2017 12:14:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:68c934eb-678b-44ae-bcbf-e41e5219cd84</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Fixed your link. Have you asked the developer if he could add support for nRF52? What is the issue with the TWI driver in the SDK? The library you linked seem quite simple, and still use the driver. It should be quite simple to setup the same functionality with the TWI driver directly in the SDK.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: update i2cdevlib from nrf51 to nrf52</title><link>https://devzone.nordicsemi.com/thread/91156?ContentTypeID=1</link><pubDate>Mon, 03 Jul 2017 00:21:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0aa97fd1-d4ce-4178-a2af-2a407704703d</guid><dc:creator>Nguyen Hoan Hoang</dc:creator><description>&lt;p&gt;Your link does not work but you can try the &lt;a href="https://embeddedsoftdev.blogspot.com/p/ehal-nrf51.html"&gt;EHAL library via this blog.&lt;/a&gt;.  It has very simple i2c, uart, spi drivers that work with different MCU including nRF51, nRF52832, nRF52840 and others such as LPC11xx, LPC17xx...&lt;/p&gt;
&lt;p&gt;This &lt;a href="https://motsai.com/products/neblina/"&gt;is link&lt;/a&gt; shows a real life use of the i2c, uart &amp;amp; SPI driver from EHAL.  There are multiples devices connecting together on the nRF52, nRF51 &amp;amp; Freescale.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>