<?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>A strange question about qspi</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/55657/a-strange-question-about-qspi</link><description>Hi,Master: 
 Platform: nrf52840 
 Bluetooth protocol stack: s140 
 When using qspi to communicate with external flash (communication speed 32M), occasional qspi communication exceptions occur in the product, or when a hand touches the IO1 pin, this phenomenon</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 20 Dec 2019 13:54:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/55657/a-strange-question-about-qspi" /><item><title>RE: A strange question about qspi</title><link>https://devzone.nordicsemi.com/thread/226586?ContentTypeID=1</link><pubDate>Fri, 20 Dec 2019 13:54:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5c373dc4-0a0d-4224-8b6c-02551eb71d07</guid><dc:creator>outspace</dc:creator><description>&lt;p&gt;ok,thank you very much.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: A strange question about qspi</title><link>https://devzone.nordicsemi.com/thread/225979?ContentTypeID=1</link><pubDate>Tue, 17 Dec 2019 19:46:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:27a33edd-ab0a-4297-bf46-2c013a7ea596</guid><dc:creator>Kenneth</dc:creator><description>[quote user="outspace"]The qspi peripheral will automatically control the DIR_OVERRIDE control output direction,and INPUT_OVERRIDE also controls the connection of INPUT to the input buffer, right?[/quote]
&lt;p&gt;Yes. This is fully handled in hardware by the peripheral automatically when enabled.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: A strange question about qspi</title><link>https://devzone.nordicsemi.com/thread/225782?ContentTypeID=1</link><pubDate>Tue, 17 Dec 2019 04:32:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:426a9981-c4ac-4596-aadc-bea10bdef4a2</guid><dc:creator>outspace</dc:creator><description>&lt;p&gt;Thank you very much for your professional answer,In response to the above question 2:&lt;/p&gt;
&lt;p&gt;The qspi peripheral will automatically control the DIR_OVERRIDE control output direction,and INPUT_OVERRIDE also controls the connection of INPUT to the input buffer, right?Is the qspi write the red line 1 in the picture, and the read is the blue line 2 in the picture&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/3603.aaa.png" /&gt;?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: A strange question about qspi</title><link>https://devzone.nordicsemi.com/thread/225711?ContentTypeID=1</link><pubDate>Mon, 16 Dec 2019 15:27:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9274bd7f-86ed-47d1-a97d-366cfd2b0d3d</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;If you set the PSEL registers of a peripheral and enable the peripheral, then it is the peripheral that control those PSEL pins. You still may consider using nrf_gpio to have control over the drive strength and/or if you want to enable pull up/down on the pins, also you can set at the same time the disconnect/input/output state of the pins should fall back to when disable the peripheral. In other words it is a good idea to call nrf_gpio to set the PSEL pins to the state they should be in when the peripheral is both enabled and disabled (inactive). Pull up/down if enabled is approx 13kohm.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: A strange question about qspi</title><link>https://devzone.nordicsemi.com/thread/225692?ContentTypeID=1</link><pubDate>Mon, 16 Dec 2019 14:23:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:02129287-afb5-4945-8828-f57c679c5967</guid><dc:creator>outspace</dc:creator><description>&lt;p&gt;Hi，Kenneth&lt;/p&gt;
&lt;p&gt;Thank you very much for your answer. I want to trouble you a little bit more. Can you answer the questions I, 2, 3, 4 specifically asked?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: A strange question about qspi</title><link>https://devzone.nordicsemi.com/thread/225688?ContentTypeID=1</link><pubDate>Mon, 16 Dec 2019 14:16:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:60e3c163-95ef-450b-b5b5-7a4c581b7cd7</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I expect that gpio standard drive strength is not sufficient here to meet 32MHz fall and rise times, so you can&amp;#39;t use&amp;nbsp;&lt;span&gt;S0S1, but need to use H0H1 (high drive) when configure qspi pins.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;br /&gt;Kenneth&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>