<?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 driver: MISO driving low.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/35399/spi-driver-miso-driving-low</link><description>Hello, I&amp;#39;m trying to port my code for driving spi memory (S25FL256S) from nRF51822 to nRF52840. I&amp;#39;m using nRF52840 Preview DK, S140 and SDK 15.0.0. On nRF51 I used custom PCB (spi memory works fine) and SDK V810. I have connected SPI memory to nRF52840</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 17 Aug 2018 11:19:59 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/35399/spi-driver-miso-driving-low" /><item><title>RE: SPI driver: MISO driving low.</title><link>https://devzone.nordicsemi.com/thread/144684?ContentTypeID=1</link><pubDate>Fri, 17 Aug 2018 11:19:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7a1c5c60-a5dc-4778-a85e-3af49ccbaf51</guid><dc:creator>M_VLV</dc:creator><description>&lt;p&gt;Thanks for advice.&lt;/p&gt;
&lt;p&gt;I have just set MISO line in high level after initialization SPI and data become same as on nrf51.&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPI driver: MISO driving low.</title><link>https://devzone.nordicsemi.com/thread/136132?ContentTypeID=1</link><pubDate>Thu, 14 Jun 2018 10:50:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c672135f-46d1-492a-81b6-75546ac25278</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
[quote user=""]I.e. I send request for&amp;nbsp;&lt;span&gt;ID (REMS)&lt;/span&gt;&amp;nbsp;and I got responce&lt;em&gt;&lt;strong&gt; 0x00, 0x00, 0x01, 0x18&lt;/strong&gt;&lt;/em&gt; instead &lt;strong&gt;&lt;em&gt;0xFF, 0xFF, 0x01, 0x18&lt;/em&gt;&lt;/strong&gt;.&lt;br /&gt;Whatever, I thought, correct data still incoming. &lt;br /&gt;But when I tried go futher on code&amp;nbsp;to&amp;nbsp;make test read-write-read data on flash,&amp;nbsp;code is not working anymore. I suppose, this is because different behaviour of MISO line in comparation with nRF51.[/quote]
&lt;p&gt;According to the datasheet that you linked to, the first two bytes are high-impedance (ie: could float high or low), so they should be discarded anyway. It is purely random that they are read as 0 on the nRF51 and 0xFF on the nRF52.&lt;/p&gt;
&lt;p&gt;Have you tried scoping the SPI lines to see if there is any difference between the two implementations that could explain that it stops working on the nRF52 device?&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>