<?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>SPI MOSI default high?  NRF SDK 12.2.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22936/spi-mosi-default-high-nrf-sdk-12-2-0</link><description>I am attempting to interface a Winbond flash device with the NRF52. The
 datasheet does not specify the idle state of MOSI when reading from the device. However, I cannot make the flash chip work with the NRF52. In the attached image, an Arduino successfully</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 17 Aug 2017 16:32:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22936/spi-mosi-default-high-nrf-sdk-12-2-0" /><item><title>RE: SPI MOSI default high?  NRF SDK 12.2.0</title><link>https://devzone.nordicsemi.com/thread/90227?ContentTypeID=1</link><pubDate>Thu, 17 Aug 2017 16:32:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:736641e5-4b02-4fa7-a099-46db44cdcc09</guid><dc:creator>MattyIce</dc:creator><description>&lt;p&gt;It turns out my issue was due to the full-duplex nature of the SPI driver. Namely, for every byte sent on the MOSI line, a byte is received on the MISO line. So if you send 4 bytes and want to read one byte, in response, you need to make the rx buffer 5 bytes long and read the 5th byte as the &amp;quot;response&amp;quot; from the slave.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPI MOSI default high?  NRF SDK 12.2.0</title><link>https://devzone.nordicsemi.com/thread/90226?ContentTypeID=1</link><pubDate>Thu, 17 Aug 2017 12:24:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6b945e46-133b-40e8-8e58-f2a1f1cde212</guid><dc:creator>Nick Bentzen</dc:creator><description>&lt;p&gt;I was not able to solve this problem - I did end up electrically inverting the MOSI signal (and flipped bits in code to compensate) and it didn&amp;#39;t solve my problem - turns out it was EMI.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPI MOSI default high?  NRF SDK 12.2.0</title><link>https://devzone.nordicsemi.com/thread/90225?ContentTypeID=1</link><pubDate>Thu, 17 Aug 2017 08:42:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:37ece06f-e015-4106-921a-aa0c592c73a2</guid><dc:creator>J&amp;#248;rn</dc:creator><description>&lt;p&gt;Unfortunately setting the MOSI pin high will not change the pins polarity between transmissions. The SPI hardware takes control of the pin, and it will keep the pin low between transmissions. After the SPI is uninitialized the pin will maintain its configuration (low) until the application changes this. The only way I can think of to achieve a high MOSI pin between transmissions is to unititialize the SPI between every transmission and &amp;quot;manually&amp;quot; set the pin high.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPI MOSI default high?  NRF SDK 12.2.0</title><link>https://devzone.nordicsemi.com/thread/90223?ContentTypeID=1</link><pubDate>Tue, 15 Aug 2017 16:40:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4f44ed5a-7d29-4e30-8318-9b4a9b80f636</guid><dc:creator>MattyIce</dc:creator><description>&lt;p&gt;@Turbo J, where is that change made?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPI MOSI default high?  NRF SDK 12.2.0</title><link>https://devzone.nordicsemi.com/thread/90224?ContentTypeID=1</link><pubDate>Tue, 20 Jun 2017 22:42:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:253ee088-01a8-4ad7-9c69-b3df3169aad5</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;Try setting the corresponding bit to &lt;code&gt;1&lt;/code&gt;in &lt;code&gt;NRF_GPIO-&amp;gt;OUT&lt;/code&gt;register.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>