<?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>Issue recovering nRF5340 Audio DK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/124562/issue-recovering-nrf5340-audio-dk</link><description>Hi All, 
 
 I have an nRF5340 Audio DK which has problem with the network core. When I connect the USB to board or try to recover the board the MCU light at the bottom of the board continuously blinks. I have tried recovering the board with nrfjprog described</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 16 Oct 2025 19:09:35 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/124562/issue-recovering-nrf5340-audio-dk" /><item><title>RE: Issue recovering nRF5340 Audio DK</title><link>https://devzone.nordicsemi.com/thread/551754?ContentTypeID=1</link><pubDate>Thu, 16 Oct 2025 19:09:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b05043be-87b7-4d8c-8147-02aa24bfb47b</guid><dc:creator>kumareshdhotrad</dc:creator><description>&lt;p data-start="56" data-end="318"&gt;I&amp;rsquo;ve identified the root cause. It turned out to be due to multiple J-Links connected simultaneously along with several active VS Code instances. The GDB servers launched by VS Code were interfering with each other and putting the J-Links into an unstable state.&lt;/p&gt;
&lt;p data-start="320" data-end="440"&gt;After closing all VS Code instances, the J-Links reset properly and I was able to recover the boards without any issues.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue recovering nRF5340 Audio DK</title><link>https://devzone.nordicsemi.com/thread/551748?ContentTypeID=1</link><pubDate>Thu, 16 Oct 2025 17:29:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cd9eb981-431b-4eda-9bd3-2f8b19b28d05</guid><dc:creator>kumareshdhotrad</dc:creator><description>&lt;p&gt;I have entered this state again. Disconnecting the board for a while and reconnecting did not help. Neither did opening the Jlink commander.&lt;br /&gt;&lt;br /&gt;I get these logs:&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;PS D:\Work\nRF\5340\nrf5340_audio\unicast_server_binaries&amp;gt; nrfutil device list&lt;br /&gt;1050193515&lt;br /&gt;Product J-Link&lt;br /&gt;Board version PCA10121&lt;br /&gt;Traits usb, jlink, seggerUsb, devkit&lt;/p&gt;
&lt;p&gt;Supported devices found: 1&lt;/p&gt;
&lt;p&gt;PS D:\Work\nRF\5340\nrf5340_audio\unicast_server_binaries&amp;gt; nrfutil device recover --core Network --serial-number 1050193515&lt;br /&gt;&lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/274c.svg" title="X"&gt;&amp;#x274c;&lt;/span&gt;&amp;nbsp;Failed to recover 1050193515, Timed out waiting for response from worker. Error: One or more recover tasks failed:&lt;br /&gt; * 1050193515: Timed out waiting for response from worker. (Generic)&lt;/p&gt;
&lt;p&gt;PS D:\Work\nRF\5340\Pendant\nrf5340_audio\unicast_server_binaries&amp;gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue recovering nRF5340 Audio DK</title><link>https://devzone.nordicsemi.com/thread/550976?ContentTypeID=1</link><pubDate>Thu, 09 Oct 2025 08:31:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8473bdaf-ffbc-4d69-a56e-8f308099eddb</guid><dc:creator>SableHarrington</dc:creator><description>&lt;p&gt;It seems your nRF5340 recovery issue may relate to corrupted boot memory. Using a reliable EEPROM like &lt;a href="https://www.ovaga.com/products/detail/m27c512-90c1"&gt;M27C512-90C1&lt;/a&gt; can help ensure stable firmware storage during recovery processes. Its consistent read/write performance supports dependable data retrieval, minimizing bootloader errors when flashing the board or restoring the network core through nrfjprog or nrfutil commands.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue recovering nRF5340 Audio DK</title><link>https://devzone.nordicsemi.com/thread/550222?ContentTypeID=1</link><pubDate>Tue, 30 Sep 2025 14:07:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:15b23c06-3aa6-4e2d-93cc-8a6deb9d858d</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Thank you for the update.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue recovering nRF5340 Audio DK</title><link>https://devzone.nordicsemi.com/thread/550214?ContentTypeID=1</link><pubDate>Tue, 30 Sep 2025 13:55:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:923e6242-1af6-4daf-9c4e-90746aad5fb7</guid><dc:creator>kumareshdhotrad</dc:creator><description>&lt;p&gt;Hi Dejan,&lt;br /&gt;&lt;br /&gt;Apologies for the delayed response. I tired recovering the device a few hours later which worked.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue recovering nRF5340 Audio DK</title><link>https://devzone.nordicsemi.com/thread/549691?ContentTypeID=1</link><pubDate>Wed, 24 Sep 2025 12:57:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b9480c0b-03fa-46a1-a48c-3f4c92b45703</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi, &lt;br /&gt;&lt;br /&gt;Have you tried to use nrfutil for recovery?&lt;br /&gt;&lt;br /&gt;&lt;pre class="ui-code" data-mode="text"&gt;nrfutil device recover --core Network
nrfutil device recover&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>