<?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 spi master transfer uncertain delay between bytes</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/13556/nrf51822-spi-master-transfer-uncertain-delay-between-bytes</link><description>Hi, 
 I am using nRF51822 spi as a master to communicate with the AFE. Four bytes need to transfer each read or write process. I use nRF51_SDK_10.0.0_dc26b5e. 
 Configuration: 
 NOTE: Blocking mode is used
void spi_master_init(void)
{
uint32_t err_code</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 02 May 2016 12:26:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/13556/nrf51822-spi-master-transfer-uncertain-delay-between-bytes" /><item><title>RE: nRF51822 spi master transfer uncertain delay between bytes</title><link>https://devzone.nordicsemi.com/thread/51719?ContentTypeID=1</link><pubDate>Mon, 02 May 2016 12:26:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:040d8db3-bbe7-498a-b85e-43a2b22bcf9d</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Have you used the spi example from the latest nRF5 SDK v11? See \examples\peripheral\spi&lt;/p&gt;
&lt;p&gt;To make it blocking set event handler to NULL when calling nrf_drv_spi_init(). Do you see the same delay with this example?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF51822 spi master transfer uncertain delay between bytes</title><link>https://devzone.nordicsemi.com/thread/51718?ContentTypeID=1</link><pubDate>Sat, 30 Apr 2016 02:10:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7b7382de-035b-4455-899e-f1c9661c16d4</guid><dc:creator>Jason</dc:creator><description>&lt;ul&gt;
&lt;li&gt;Yes, I want to use blocking mode. I don&amp;#39;t want to return during spi transfer.&lt;/li&gt;
&lt;li&gt;I don&amp;#39;t program the softdevice stack, and also don&amp;#39;t initialize ble_app_initial. Additionally, I write a simple spi transfer, write one byte, read one byte and wait for NRF_SPI_EVENT_READY event, I found even in byte-by-byte transfer, the NRF_SPI_EVENT_READY event would delayed uncertain. I agree with what you mentioned, there may higher level interrupts, but I don&amp;#39;t know what would be ?&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF51822 spi master transfer uncertain delay between bytes</title><link>https://devzone.nordicsemi.com/thread/51720?ContentTypeID=1</link><pubDate>Fri, 29 Apr 2016 11:18:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5d5ff135-7bcc-4bc4-8c74-6c24293c95b7</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi, &amp;quot;Blocking&amp;quot; means that the nrf_drv_spi_transfer() will not return until the transfer is done. However the execution might still be interrupted by higher level application interrupts and/or softdevice events. Could this explain your observation?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>