<?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>nRF52832 SPI dummy clock cycles after TX (SDK v14.2.0)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/30286/nrf52832-spi-dummy-clock-cycles-after-tx-sdk-v14-2-0</link><description>Hi, 
 I am using the nRF52832 on a custom PCB and I am interfacing it with a flash memory chip through SPI. 
 I am testing the SPI communication using the spi example (nRF52 SDK 14.2.0\examples\peripheral\spi). 
 Using an oscilloscope I can see that each</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 07 Feb 2018 13:14:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/30286/nrf52832-spi-dummy-clock-cycles-after-tx-sdk-v14-2-0" /><item><title>RE: nRF52832 SPI dummy clock cycles after TX (SDK v14.2.0)</title><link>https://devzone.nordicsemi.com/thread/120113?ContentTypeID=1</link><pubDate>Wed, 07 Feb 2018 13:14:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f631685-a18a-451a-ae2b-9e560220691b</guid><dc:creator>Lorenzo</dc:creator><description>&lt;p&gt;Thank you very much&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52832 SPI dummy clock cycles after TX (SDK v14.2.0)</title><link>https://devzone.nordicsemi.com/thread/120112?ContentTypeID=1</link><pubDate>Wed, 07 Feb 2018 13:10:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a21eadfb-9656-4edb-9c46-c3c5b8d17f00</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;Err&amp;nbsp; - your&amp;nbsp; tx buffer is an&amp;nbsp; array of ints, so they are each 4 bytes long little endian. So you&amp;#39;re asking for 4x2 = 8&amp;nbsp; bytes to be clocked out and so you get all 4 bytes of each integer, the top 3 of which are zero in your case. If you want to clock out 2 bytes, use uint8_t not&amp;nbsp; int.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You&amp;nbsp; are getting exactly what you programmed.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>