<?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>J-link(vesion is V7.56b) download problem</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/81292/j-link-vesion-is-v7-56b-download-problem</link><description>Can I write a J-link flash algorithm by myself? Is there any open source Flash download algorithm for reference? When I call west Flash --recover, I can skip the 4K flash space in 1M flash without erasing it 
 
 And why can&amp;#39;t I find the download algorithm</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 02 Nov 2021 12:29:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/81292/j-link-vesion-is-v7-56b-download-problem" /><item><title>RE: J-link(vesion is V7.56b) download problem</title><link>https://devzone.nordicsemi.com/thread/337082?ContentTypeID=1</link><pubDate>Tue, 02 Nov 2021 12:29:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6dc4f06b-609b-44cb-89e0-747bbb629c2f</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I suggest you ask Segger about writing flash algorithms yourself. Also, I cannot say what these files you refer to are used for in ST devices.&lt;/p&gt;
&lt;p&gt;I wonder though, what is the real issue here?&amp;nbsp;What is it you are not able to do, or what is not working the way you expected? Please elaborate.&lt;/p&gt;
&lt;p&gt;Without understanding the root issue here, I wonder if the problem is that you see that after doing recover the flash is not empty, is that the case? If so, that is correct, and is because when you do recover a small piece of code is written to the device which unlocks the debug port to allow future programming and debugging. If the device flash is&amp;nbsp;empty this will not be possible without a new recover, due to the APPROTECT mechanism in the nRF5340.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>