<?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>nRF51822  s110 + TWI Crashes</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/11906/nrf51822-s110-twi-crashes</link><description>I&amp;#39;m testing out TWI on pins 24/25 and I get a crash when I attempt to do a TWI transfer and I find myself in: WDT_IRQHandler () 
 I&amp;#39;m using much of the example code: 
 APP_TWI_INIT(&amp;amp;m_app_twi, &amp;amp;config, MAX_PENDING_TRANSACTIONS, err_code); 
 app_twi_transfer_t</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 02 Aug 2016 23:50:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/11906/nrf51822-s110-twi-crashes" /><item><title>RE: nRF51822  s110 + TWI Crashes</title><link>https://devzone.nordicsemi.com/thread/45111?ContentTypeID=1</link><pubDate>Tue, 02 Aug 2016 23:50:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:28f61623-909d-4a17-aca1-a6aa32ad2231</guid><dc:creator>ypearson</dc:creator><description>&lt;p&gt;Yeah, didn&amp;#39;t use APP_TWI&lt;/p&gt;
&lt;p&gt;static nrf_drv_twi_t m_twi_0 = NRF_DRV_TWI_INSTANCE(0);&lt;/p&gt;
&lt;p&gt;nrf_drv_twi_t * register_access_init(uint8_t twi_instance)
{
err_code = nrf_drv_twi_init(&amp;amp;m_twi_0, 0, 0, NULL);
nrf_drv_twi_enable(&amp;amp;m_twi_0);&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;return &amp;amp;m_twi_0;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;}&lt;/p&gt;
&lt;p&gt;Also, there may have been a conf file that was modified to get it working (forgot the exact details).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF51822  s110 + TWI Crashes</title><link>https://devzone.nordicsemi.com/thread/45110?ContentTypeID=1</link><pubDate>Tue, 02 Aug 2016 23:48:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e81879fa-270a-4313-a7ab-caa050f7fe23</guid><dc:creator>ypearson</dc:creator><description>&lt;p&gt;Yeah, didn&amp;#39;t use APP_TWI&lt;/p&gt;
&lt;p&gt;static nrf_drv_twi_t m_twi_0 = NRF_DRV_TWI_INSTANCE(0);&lt;/p&gt;
&lt;p&gt;nrf_drv_twi_t * register_access_init(uint8_t twi_instance)
{
ret_code_t err_code;
err_code = nrf_drv_twi_init(&amp;amp;m_twi_0, 0, 0, NULL);
//APP_ERROR_CHECK(err_code);
nrf_drv_twi_enable(&amp;amp;m_twi_0);&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;return &amp;amp;m_twi_0;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;}&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF51822  s110 + TWI Crashes</title><link>https://devzone.nordicsemi.com/thread/45109?ContentTypeID=1</link><pubDate>Mon, 25 Jul 2016 09:48:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d77063df-674a-4579-82cb-1f8e160e41c5</guid><dc:creator>Eliot Stock</dc:creator><description>&lt;p&gt;@ypearson I&amp;#39;ve seen something quite similar on a custom board with an nRF51822, S130, SDK 11. Did you ever get to the bottom of this?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF51822  s110 + TWI Crashes</title><link>https://devzone.nordicsemi.com/thread/45108?ContentTypeID=1</link><pubDate>Tue, 16 Feb 2016 12:10:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f2214db7-5009-4ffe-b906-5f56e3ee092c</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Are you using the DK or a custom board? On the DK, pin 24 is connected to VDD via a LED and a resistor.&lt;/p&gt;
&lt;p&gt;Can you disable the watchdog, disable compiler optimization and define &lt;code&gt;DEBUG&lt;/code&gt; in the project/Makefile, then &lt;a href="https://devzone.nordicsemi.com/blogs/821/an-introduction-to-error-handling-in-nrf5-projects/"&gt;run the debugger&lt;/a&gt;? If the code ends up in a loop in the error handler, you can extract the file, line and return code of the error. If not it would be useful to step through the code and see where the problem occurs.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>