<?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 writing operation is overlapped</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/71614/nrf52840-qspi-writing-operation-is-overlapped</link><description>Hi, 
 I&amp;#39;ve found an issue while writing data to QSPI flash memory on the nrf52840 DK board with sample application. 
 The issue is that the data is overwritten to 0x0 address if the start address is between 0xF1 and 0xFF when length is more than 16. </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 15 Feb 2021 18:44:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/71614/nrf52840-qspi-writing-operation-is-overlapped" /><item><title>RE: nRF52840 QSPI writing operation is overlapped</title><link>https://devzone.nordicsemi.com/thread/294475?ContentTypeID=1</link><pubDate>Mon, 15 Feb 2021 18:44:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:463b6a34-a185-4e0b-bd3a-db7c01a9197e</guid><dc:creator>Ben_nrf52840</dc:creator><description>&lt;p&gt;Hi Jorgen,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you for your response and I&amp;#39;ve confirmed it is only happened with non-word aligned start address. It works as expected from 0xF0, 0xF4, 0xF8 and 0xFC. I have to make a workaround for other addresses.&lt;/p&gt;
&lt;p&gt;Thanks again.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Ben&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 QSPI writing operation is overlapped</title><link>https://devzone.nordicsemi.com/thread/294470?ContentTypeID=1</link><pubDate>Mon, 15 Feb 2021 18:28:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:525dcd90-3839-4276-85cf-667f05d12c00</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;According to the QSPI peripheral documentation, the&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/ps_nrf52840/qspi.html?cp=4_0_0_5_18_9_13#register.READ.SRC"&gt;READ.SRC&lt;/a&gt;/&lt;a href="https://infocenter.nordicsemi.com/topic/ps_nrf52840/qspi.html?cp=4_0_0_5_18_9_13#register.WRITE.DST"&gt;WRITE.DST&lt;/a&gt;&amp;nbsp;registers must be Word-aligned, and the&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/ps_nrf52840/qspi.html?cp=4_0_0_5_18_9_13#register.READ.CNT"&gt;READ.CNT&lt;/a&gt;/&lt;a href="https://infocenter.nordicsemi.com/topic/ps_nrf52840/qspi.html?cp=4_0_0_5_18_9_13#register.WRITE.CNT"&gt;WRITE.CNT&lt;/a&gt;&amp;nbsp;registers must be a multiple of 4 bytes. 0xF2 is not word aligned, have you tested with&amp;nbsp;all&amp;nbsp;addresses between 0xF1 and 0xFF?&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>