<?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>IoT SDK connect  TWI(I2C) ??</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/9436/iot-sdk-connect-twi-i2c</link><description>[Dev Env] 
 nRF51 DK 
 IoT SDK 0.8 
 IoT SoftDevice 
 [Question] 
 anybody help me. 
 In Iot SDK can&amp;#39;t access TWI interface?
any Sample ?? 
 HardFault_Handler (/attachment/fbd403f1c1c47dcb2a8365c80f82a589) 
 bool twi_master_init(void)
{
.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 25 Sep 2015 13:19:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/9436/iot-sdk-connect-twi-i2c" /><item><title>RE: IoT SDK connect  TWI(I2C) ??</title><link>https://devzone.nordicsemi.com/thread/34831?ContentTypeID=1</link><pubDate>Fri, 25 Sep 2015 13:19:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e3a18f2a-e53d-4c3c-af97-ec32d311ff24</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;PPI is a restricted peripheral, and in earlier versions of the softdevice, that causes direct access to it to cause a hardfault. There are sd_ functions to access the PPI channels safely, you should use those.&lt;/p&gt;
&lt;p&gt;However .... that hack for using a PPI channel to stop the TWI device was only ever needed for the 1st version chips with the anomaly that the TWI shortcut didn&amp;#39;t work, that was fixed in version 2 of the chips, a long, long time ago and there&amp;#39;s no need to use a PPI channel at all any more. You can change it to use the now-working shortcut - or switch to the more-recent nrf_drv_twi.c if you have recent-enough hardware to run it on.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>