<?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>Issue seen with nRF52840 and SPI (Master) Receving Bytes</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22771/issue-seen-with-nrf52840-and-spi-master-receving-bytes</link><description>Hi everyone, 
 I am seeing an issue where the SPI (master) ignores the first byte of RX buff and begins storing the received bytes from RxBuff[1] instead of RxBuff[0]. In addition to ignoring the first RX byte, the first clock cycles for RxBuff[0] is</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 17 Jun 2017 21:11:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22771/issue-seen-with-nrf52840-and-spi-master-receving-bytes" /><item><title>RE: Issue seen with nRF52840 and SPI (Master) Receving Bytes</title><link>https://devzone.nordicsemi.com/thread/89523?ContentTypeID=1</link><pubDate>Sat, 17 Jun 2017 21:11:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d71cc1a9-01a3-45b5-a66f-358875028d73</guid><dc:creator>Jay</dc:creator><description>&lt;p&gt;Ah, that makes sense! Thank you for your answer. I am currently using the SDK 13 and the issue I described (which is not an issue after reading your answer) makes sense since the the MISO pin is set to pulldown. So, when I send via MOSI, I will always get 0x00 (i.e., making it look like first RX byte is &amp;#39;ignored&amp;#39;).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue seen with nRF52840 and SPI (Master) Receving Bytes</title><link>https://devzone.nordicsemi.com/thread/89522?ContentTypeID=1</link><pubDate>Wed, 14 Jun 2017 09:27:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a1681920-0084-4f35-87d0-db6bdc0fe1ce</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi Jay,&lt;/p&gt;
&lt;p&gt;SPI protocol is full duplex, meaning it can transmitt and receive at the same time. You should not see (# TX + # RX) cycles, but MAX(# TX, # RX) cycles. Since you tell the driver you want to receive 4 bytes, you will see 4 cycles. The first cycle will be both transmitt and receive cycle.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m not able to reproduce the other issue you describe, using you code and the SPI example in SDK 13.0.0. Which example and SDK version are you using?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>