<?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>How could we improve flashing time?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/123813/how-could-we-improve-flashing-time</link><description>Hello, 
 We are using NRF5340 in our product and running automated hardware testing. As part of this process, we need to program the chip twice: once with a dedicated testing firmware, and a second time with the actual production firmware. One issue for</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 20 Aug 2025 14:12:20 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/123813/how-could-we-improve-flashing-time" /><item><title>RE: How could we improve flashing time?</title><link>https://devzone.nordicsemi.com/thread/546220?ContentTypeID=1</link><pubDate>Wed, 20 Aug 2025 14:12:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:28b8af81-97b3-4785-a52f-f178cab3f161</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Yes, I did not spot that there was a secotor erase there. On the nRF,&amp;nbsp;&lt;span&gt;chiperase&lt;/span&gt;&amp;nbsp;and recover&amp;nbsp; is much faster than sectore erase.&lt;/p&gt;
&lt;p&gt;Do you actually write to the QSPI flash when you program the application or not? If you do not, the QSPI frequency will not matter.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How could we improve flashing time?</title><link>https://devzone.nordicsemi.com/thread/546212?ContentTypeID=1</link><pubDate>Wed, 20 Aug 2025 13:48:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:67600cf6-e41f-4e26-82d9-540ca0efdada</guid><dc:creator>ppalant</dc:creator><description>&lt;p&gt;Hi, thank you for your input.&amp;nbsp;&lt;br /&gt;I set QSPI speed to 32M, but it makes no difference to total flashing time.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;However, we noticed that we can gain 20 seconds on CP_APPLICATION programming if we use --chiperase instead of --sectoreerase.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How could we improve flashing time?</title><link>https://devzone.nordicsemi.com/thread/546178?ContentTypeID=1</link><pubDate>Wed, 20 Aug 2025 11:54:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:545f704d-b308-4b98-868e-98315df531b7</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I see that the two steps that take the most time is step 3 where you erase the external flash, and step 5, where I assume most of the time is spent programming the external flash. I see on line 71 in the config file that you have set the QSPI speed to 2M.&amp;nbsp; Can you try increasing this?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>