The slow SPI transfer and interrupt issuehttps://devzone.nordicsemi.com/f/nordic-q-a/35484/the-slow-spi-transfer-and-interrupt-issueHello tech support! I am using the built-in SPI to transfer the data. Also, I adopted the &quot;timer&quot; example in the SDK for handling the SPI transfer. However, it seems that the SPI may be too slow and too much time is spent in the interrupt. When theen-USTelligent Community 13Sun, 17 Jun 2018 19:32:46 GMTRE: The slow SPI transfer and interrupt issuehttps://devzone.nordicsemi.com/thread/136457?ContentTypeID=1Sun, 17 Jun 2018 19:32:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:cb7bd3c7-7be6-415d-afb2-9f4788f2d071J&#248;rgen Holmefjord<p>Hi,</p> <p>Please provide more details on the issue.</p> <ul> <li>How do you configure SPI? How/what are you transferring?</li> <li>What are you doing in the interrupts? Is the issue with long handling of interrupt with timer or SPI?</li> <li>What do you mean when you say the &quot;string would be destroyed and fragmented&quot;? Can you provide logic trace showing this behavior?</li> <li>Which SDK version are you using?</li> </ul> <p>Softdevice will always have highest priority for handling timing-critical events. If you have a lot of BLE activity, this could cause delayed handling of SPI events.</p> <p>Best regards,<br />Jørgen</p><div style="clear:both;"></div>RE: The slow SPI transfer and interrupt issuehttps://devzone.nordicsemi.com/thread/136436?ContentTypeID=1Sat, 16 Jun 2018 20:49:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bbadccd3-e62b-4b8e-be34-cbd88044ae51Turbo J<p>NRF52 has SPIM peripherial, which can use DMA. </p> <p>No idea why the transmitted data would be damaged - this may be an unrelated problem, e.g. stack overflow.</p><div style="clear:both;"></div>