<?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>nRF52840 QSPI XIP and standby</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/33393/nrf52840-qspi-xip-and-standby</link><description>I have been investigating the possibility of using the QSPI external flash peripheral on our NRF chip. After doing a typical qspi read command, the external flash chip would go back to standby mode which uses about 85uA. After doing a xip_function, which</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 26 Apr 2018 07:41:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/33393/nrf52840-qspi-xip-and-standby" /><item><title>RE: nRF52840 QSPI XIP and standby</title><link>https://devzone.nordicsemi.com/thread/129874?ContentTypeID=1</link><pubDate>Thu, 26 Apr 2018 07:41:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:646b76b4-398a-43a7-8374-0eae23f63747</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi, QSPI will not go into standby and also the external Flash will not go into standby since the CSN line is kept low by the peripheral. A timeout that puts the QSPI into standby when there is no XiP operation for a certain time is a good feature request, but not implemented in any product so far.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The only workaround that we could imagine is to use a timer/RTC as a watchdog. The CPU needs to clear/restart it from time to time. If it timeout it can trigger TASKS_DEACTIVATE on the QSPI. But then there also needs to be code to activate and initialize it again. Not very nice, but maybe worth for long times between XiP accesses.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 QSPI XIP and standby</title><link>https://devzone.nordicsemi.com/thread/129850?ContentTypeID=1</link><pubDate>Wed, 25 Apr 2018 19:37:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2592f2d6-6c06-4e3b-b6a1-7e6180c51987</guid><dc:creator>changjo</dc:creator><description>&lt;p&gt;I want to elaborate that I am trying to conserve power. I would like to know the expected behavior of the QSPI XIP peripheral after doing xip operation. Specifically does the QSPI peripheral go into standby mode between xip operations? If not is there a workaround fix that can get the QSPI to do standby?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 QSPI XIP and standby</title><link>https://devzone.nordicsemi.com/thread/129202?ContentTypeID=1</link><pubDate>Fri, 20 Apr 2018 22:42:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a79ae305-b1c7-47e2-9d6f-edee0609769a</guid><dc:creator>changjo</dc:creator><description>&lt;p&gt;For the application, the execute in place may be used for indeterminate amount of time depending on how much code will be off loaded. Therefore knowing when to uninit or put deep power down mode will be difficult. Also to put deep sleep or uninit in every location would be quite a task. If there was a work around that the QSPI can self managed is something more preferable.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 QSPI XIP and standby</title><link>https://devzone.nordicsemi.com/thread/128939?ContentTypeID=1</link><pubDate>Thu, 19 Apr 2018 10:22:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:673d419c-e12f-41bd-ba27-62b762ed7efc</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;The best solution would be to uninit QSPI when it is not in use. You could also test deep power down mode &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52840.ps/qspi.html?cp=2_0_0_5_18_6#deep_power_mode"&gt;http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52840.ps/qspi.html?cp=2_0_0_5_18_6#deep_power_mode. &lt;/a&gt;In addition you should check that CS is deselected.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 QSPI XIP and standby</title><link>https://devzone.nordicsemi.com/thread/128546?ContentTypeID=1</link><pubDate>Mon, 16 Apr 2018 22:06:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7fb52ff2-f041-4de0-b192-4b4740b04018</guid><dc:creator>changjo</dc:creator><description>&lt;p&gt;I have tested out the workaround but this does not fix the issue I have. The anomaly 122 workaround is for un-initializing the qspi chip. Whereas the situation I am referring is in between xip operations, I would like the qspi chip to go into standby.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 QSPI XIP and standby</title><link>https://devzone.nordicsemi.com/thread/128449?ContentTypeID=1</link><pubDate>Mon, 16 Apr 2018 11:50:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f30cf16b-98f0-4544-8c95-812947441b05</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;Did you implemented the workaround mentioned in &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52840.Rev1.errata/dita/errata/nRF52840/Rev1/latest/anomaly_840_122.html?cp=2_0_1_0_1_7"&gt;anomaly 122&lt;/a&gt;?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>