Is I2C0 incompatible with SPIM3 in SDK14,S140?https://devzone.nordicsemi.com/f/nordic-q-a/31073/is-i2c0-incompatible-with-spim3-in-sdk14-s140Recently,I use the SDK14 to develop the project,the initial project is in the content &quot;SDK14/examples/peripheral/twi_scanner/pca10056&quot;, Then and the spi example in the content of &quot;SDK14/examples/peripheral/spi/pca10056&quot;, I make some changes APP_ERROR_CHECKen-USTelligent Community 13Wed, 07 Mar 2018 00:40:31 GMTRE: Is I2C0 incompatible with SPIM3 in SDK14,S140?https://devzone.nordicsemi.com/thread/123151?ContentTypeID=1Wed, 07 Mar 2018 00:40:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2cd3e7dc-2fd6-495f-8993-4a3b74859119Milk<p>I have fixed this problem,The reason is the variable &quot;m_cb&quot; just have one element,but the program visited it&#39;s the second element</p><div style="clear:both;"></div>RE: Is I2C0 incompatible with SPIM3 in SDK14,S140?https://devzone.nordicsemi.com/thread/122852?ContentTypeID=1Mon, 05 Mar 2018 14:23:36 GMT137ad170-7792-4731-bb38-c0d22fbe4515:861e4c87-1592-4e1b-aafc-89657a990735Martin Lesund<p>Are you aware of the two <a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.nrf52%2Fdita%2Fnrf52%2Ferrata52840.html&amp;cp=2_0_1" rel="noopener noreferrer" target="_blank">errata</a>s&nbsp;for the SPIM3 and their workarounds?&nbsp;&nbsp;</p> <ul> <li><a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.nrf52840.EngC.errata%2Fdita%2Ferrata%2FnRF52840%2FEngineeringC%2Flatest%2Fanomaly_840_174.html&amp;cp=2_0_1_0_1_14" rel="noopener noreferrer" target="_blank">SPIM3 events incorrectly connected to the PPI</a></li> </ul> <p></p> <ul> <li><a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.nrf52840.EngC.errata%2Fdita%2Ferrata%2FnRF52840%2FEngineeringC%2Flatest%2Fanomaly_840_193.html&amp;cp=2_0_1_0_1_21" rel="noopener noreferrer" target="_blank">SPIM3 does not generate EVENTS_END and halts if suspended during last byte</a></li> </ul> <p></p> <p><em>Also you could, define &quot;DEBUG&quot; in the preprocessor defines, turn off optimization, set a breakpoint at line 73 in &quot;app_error.c&quot;, and run a debug session to find out what &quot;APP_ERROR_CHECK&quot; returns. (<a href="https://devzone.nordicsemi.com/f/nordic-q-a/10729/my-device-is-freezing-and-restarting" rel="noopener noreferrer" target="_blank">more</a>)</em></p><div style="clear:both;"></div>