<?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>QSPI Flash compatibility W25M02GVZEIG</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/71383/qspi-flash-compatibility-w25m02gvzeig</link><description>Hi, I&amp;#39;ve got our custom board with W25M02GVZEIG and I want to be able to read it out in a way that is fast and works with XIP. It&amp;#39;s ok if it takes more time to write. 
 So far, it looks like there is no compatible addressing mode. Opcode 0x6B and 0xEB</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 12 Feb 2021 11:11:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/71383/qspi-flash-compatibility-w25m02gvzeig" /><item><title>RE: QSPI Flash compatibility W25M02GVZEIG</title><link>https://devzone.nordicsemi.com/thread/294131?ContentTypeID=1</link><pubDate>Fri, 12 Feb 2021 11:11:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:707b0242-ffa8-4350-ba54-b8088fa9f3bf</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Looking further into this, I&amp;#39;m not sure that the flash chip is fully compatible with the QSPI interface, see &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/48845/compatibility-between-qspi-driver-and-winbond-w25m02gw-flash-memory"&gt;this thread&lt;/a&gt; for some similar questions.&lt;/p&gt;
&lt;p&gt;I tested the XIP example in our SDK with the on-board flash chip on the nRF52840 DK, and I cannot find a matching instruction format in the datasheet you provided:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/860x111/__key/communityserver-discussions-components-files/4/3365.qspi_5F00_xip_5F00_logic.png" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: QSPI Flash compatibility W25M02GVZEIG</title><link>https://devzone.nordicsemi.com/thread/293445?ContentTypeID=1</link><pubDate>Mon, 08 Feb 2021 22:35:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c384a429-9d8f-417f-8b62-eea28f71e35e</guid><dc:creator>HurleyResearch</dc:creator><description>&lt;p&gt;Thanks so much for your reply, I&amp;#39;ve got another question and could use your expertise. &lt;/p&gt;
&lt;p&gt;If I use continuous read mode (BUF=0), the address bits are all dummy.&lt;/p&gt;
&lt;p&gt;I assume that XIP will map the external flash data to the nRF5340 memory space (read only of course). Will I still be able to access the external flash memory the same as the internal flash memory, by simply using it like any other memory location? I&amp;#39;m failing to see how the nRF will know where (at which address) in external flash, to read, when I attempt to access a given address within the XIP mapped space.&lt;/p&gt;
&lt;p&gt;Any hits will be appreciated, but I will go ahead and experiment with continuous read (BUF=0) mode. Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: QSPI Flash compatibility W25M02GVZEIG</title><link>https://devzone.nordicsemi.com/thread/293399?ContentTypeID=1</link><pubDate>Mon, 08 Feb 2021 16:03:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a990e9c3-964a-45cd-be85-dc33fdf95718</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;If I read the datasheet of the flash device correct, the&amp;nbsp;&amp;quot;Instruction Set Table 1&amp;quot; in section&amp;nbsp;8.1.2 seems to match the nRF5340 QSPI documentation. According to the datasheet, you should be able to set the flash chip in&amp;nbsp;Continuous Read mode by writing the&amp;nbsp;BUF = 0, even if you have the xxIG model which powers up with&amp;nbsp;BUF = 1.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>