https://devzone.nordicsemi.com/f/nordic-q-a/12519/twi-issueHello, I have a capricious component on my TWI bus, and sometimes my nRF52 do an infinite loop in file nrf_drv_twi.c in this loop while (!nrf_twim_event_check(p_twim, evt_to_wait)) { ... } Why I have no done and no error ? Could it be possibleen-USTelligent Community 13Wed, 10 Aug 2016 10:50:51 GMThttps://devzone.nordicsemi.com/thread/47474?ContentTypeID=1Wed, 10 Aug 2016 10:50:51 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0244fb29-72b2-4fc2-b43e-65070c7d1671Ole Bauck<p>For reference here is the new question: <a href="https://devzone.nordicsemi.com/question/90325/possible-bug-i2c-stuck/">devzone.nordicsemi.com/.../</a></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/47473?ContentTypeID=1Wed, 10 Aug 2016 09:12:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:449f4924-fdd9-48f7-85d6-42aac61372aeElena<p>Hi. I&#39;m having the same problem. Usually, but not always, the SDA line remains constantly low. My only way to recover the I2C peripheral is to reset the CPU. Are there news about this behaviour??? Thanks in advance. Elena</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/47476?ContentTypeID=1Tue, 15 Mar 2016 10:37:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:cddab074-1513-4dba-945b-6722e8a89d9bFabien Comte<p>I know i am in master but it&#39;s very close.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/47477?ContentTypeID=1Tue, 15 Mar 2016 10:35:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3cd00e9b-cd82-418a-8217-c6e60b49f438Fabien Comte<p>Symptoms are very similar to [30] TWIS &quot;In TX (READ command), SCL and SDA are pulled low and further communication is blocked.&quot;</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/47478?ContentTypeID=1Mon, 14 Mar 2016 13:39:23 GMT137ad170-7792-4731-bb38-c0d22fbe4515:956bc7e5-352d-4028-8823-4d56534a72ddOle Bauck<p>What errata? Bitbanging seems like a bad solution, the hardware peripheral should work.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/47472?ContentTypeID=1Mon, 14 Mar 2016 13:10:33 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d8b592c1-81c9-4233-b066-3bcc24f625eeFabien Comte<p>Thank you for your help.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/47475?ContentTypeID=1Mon, 14 Mar 2016 13:10:20 GMT137ad170-7792-4731-bb38-c0d22fbe4515:475c5773-9843-485d-a19e-1a829cb5621bFabien Comte<p>Migration to bitbanging fixed my issue.</p> <p>I guess that I was touched by the errata (nRF52 is in rev C)</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/47471?ContentTypeID=1Mon, 14 Mar 2016 12:56:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:303ee972-4ee4-46ff-b029-c979e0305fa3Ole Bauck<p>Sounds strange. Have you captured the TWI lines to see if the STOP/SUSPENDED condition happens? Do the code work if you use handler? I assume you have not modified the driver or are touching any of the NRF_TWIM or NRF_TWI registers?</p><div style="clear:both;"></div>