<?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>PSA: Nrfutil may not recover NRF5340 network core with 3rd party J-Link</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/126254/psa-nrfutil-may-not-recover-nrf5340-network-core-with-3rd-party-j-link</link><description>This one gets complicated as I cannot reproduce the problem with my original NRF5340 DK. 
 Steps to reproduce are trivially easy, but only fail when using my favourite OEM J-Link (Silicon Labs PCB4001) that has a display and an ethernet port. 
 nrfutil</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 22 Dec 2025 12:07:05 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/126254/psa-nrfutil-may-not-recover-nrf5340-network-core-with-3rd-party-j-link" /><item><title>RE: PSA: Nrfutil may not recover NRF5340 network core with 3rd party J-Link</title><link>https://devzone.nordicsemi.com/thread/557516?ContentTypeID=1</link><pubDate>Mon, 22 Dec 2025 12:07:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d0c61f9d-b665-4a67-96c4-a2b3bc6a249b</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thank you for reporting this. I will add it to our internal bug tracker. Since it&amp;#39;s working with nrfjprog but not nrfutil device I think it may be worth looking into it.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;
&lt;p&gt;EDIT: forgot to ask if Nrfutil device is up to date. You can run &amp;quot;nrfutil device --version&amp;quot; to check the version number (latest version at time of writing is v&lt;span&gt;2.15.7) and &amp;quot;nrfutil upgrade&amp;quot; to install the latest version.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;EDIT 2: developer requested error information from the &amp;quot;west flash --recover&amp;quot; command: &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&amp;quot;Yeah, would be good to understand why it fails here.&lt;/em&gt;&lt;/p&gt;
&lt;p data-renderer-start-pos="56"&gt;&lt;em&gt;They didn&amp;rsquo;t mention how it failed, could you ask them what error message they get in west flash --recover?&lt;/em&gt;&lt;/p&gt;
&lt;p data-renderer-start-pos="164"&gt;&lt;em&gt;Assuming it&amp;rsquo;s the recover step that fails (and not the programming step afterwards, or the app core recover later), it would be interesting to see the log in &amp;lt;USERHOME&amp;gt;/.nrfutil/logs/nrfutil-device.log from nrfutil device recover --core Network --log-level trace after they&amp;rsquo;ve put the network core in the state where it&amp;rsquo;s protected, and the same for nrfjprog --recover --log &amp;lt;path&amp;gt;.&amp;quot;&lt;/em&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>