<?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>Not able to access debug port via jlink</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/126054/not-able-to-access-debug-port-via-jlink</link><description>nrfjprog -c 125 --recover --log [error] [ Client] - Encountered error -102: Command connect_to_emu_with_snr executed for 406 milliseconds with result -102 ERROR: Unable to connect to a debugger. [error] [ Worker] - An unknown error. ERROR: JLinkARM DLL</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 10 Dec 2025 09:29:50 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/126054/not-able-to-access-debug-port-via-jlink" /><item><title>RE: Not able to access debug port via jlink</title><link>https://devzone.nordicsemi.com/thread/556647?ContentTypeID=1</link><pubDate>Wed, 10 Dec 2025 09:29:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5604af54-5429-40ba-b331-9ef15a76ea0d</guid><dc:creator>Syed Maysum Abbas Zaidi</dc:creator><description>&lt;p&gt;Hi, I checked your log file and it shows J-Link debugger itself is detected and configured correctly But when it tries to access the nRF53 debug port, all debug port register writes fail with -1, and JLINK_IsConnected() reports that the probe is not connected to a valid target. This indicates that the PC to J Link path is fine, but the J-Link cannot communicate with the nRF53’s debug port at all.&lt;br /&gt;&lt;br /&gt;That is mostly caused by a hardware connection or power issue on the target side. Could you please check the following:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;For reliable SWD debugging with J Link, you should power the custom board so that VDD is around 3.0–3.3 V, and connect that same VDD to the debugger’s VTref pin.&lt;/li&gt;
&lt;li&gt;Verify SWD wiring (SWDIO, SWDCLK, GND, VTref), connector orientation and no series resistors or level shifters should be on SWD lines.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Kind Regards,&lt;br /&gt;Syed Maysum&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Not able to access debug port via jlink</title><link>https://devzone.nordicsemi.com/thread/556567?ContentTypeID=1</link><pubDate>Tue, 09 Dec 2025 14:06:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4647996f-c00e-4335-811f-a565fd6af7e2</guid><dc:creator>Nagari Gopal</dc:creator><description>&lt;p&gt;Hii, using custom board of nrf53 series. Programming debug is showing, but not able to access or write the firmware.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If i try using the nrf connect programmer, its showing like this&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;2025-12-09T14:03:46.872Z INFO Selected device with the serial number 000601001636&lt;br /&gt;2025-12-09T14:03:46.872Z INFO Using nrfutil device to communicate with target via JLink&lt;br /&gt;2025-12-09T14:03:46.896Z DEBUG Sending event &amp;quot;programmer: device selected&amp;quot;&lt;br /&gt;2025-12-09T14:03:46.896Z DEBUG Sending event &amp;quot;programmer: running nrfutil device&amp;quot;&lt;br /&gt;2025-12-09T14:03:47.051Z DEBUG Sending event &amp;quot;programmer: running nrfutil device&amp;quot;&lt;br /&gt;2025-12-09T14:03:47.175Z INFO Reading readback protection status for Application core&lt;br /&gt;2025-12-09T14:03:47.176Z INFO Reading readback protection status for Application core 0%&lt;br /&gt;2025-12-09T14:03:47.345Z INFO Reading readback protection status for Application core 50%&lt;br /&gt;2025-12-09T14:03:47.345Z INFO Reading readback protection status for Application core 50%&lt;br /&gt;2025-12-09T14:03:47.458Z ERROR Failed &amp;quot;reading readback protection status for application core&amp;quot;. Error: code: 1, description: Generic, message: Batch task protection-get failed, Device error: Setting the debug port SELECT register failed while powering up sys and debug regions (Unknown Error in J-Link DLL (error code =-1)).&lt;/p&gt;
&lt;p&gt;This might indicate that the debug port is unavailable. Please double-check device power supply and SWD lines, and that SWD isn&amp;#39;t disabled&lt;br /&gt;2025-12-09T14:03:47.487Z ERROR Error: Failed with exit code 1.&lt;br /&gt;One or more batch tasks failed:&lt;br /&gt; * 601001636: Device error: Setting the debug port SELECT register failed while powering up sys and debug regions (Unknown Error in J-Link DLL (error code =-1)).&lt;br /&gt; &lt;br /&gt; This might indicate that the debug port is unavailable. Please double-check device power supply and SWD lines, and that SWD isn&amp;#39;t disabled (Generic)&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Message: Batch task protection-get failed, Device error: Setting the debug port SELECT register failed while powering up sys and debug regions (Unknown Error in J-Link DLL (error code =-1)).&lt;/p&gt;
&lt;p&gt;This might indicate that the debug port is unavailable. Please double-check device power supply and SWD lines, and that SWD isn&amp;#39;t disabled.&lt;br /&gt;2025-12-09T14:03:47.487Z ERROR Error: Failed with exit code 1.&lt;br /&gt;One or more batch tasks failed:&lt;br /&gt; * 601001636: Device error: Setting the debug port SELECT register failed while powering up sys and debug regions (Unknown Error in J-Link DLL (error code =-1)).&lt;br /&gt; &lt;br /&gt; This might indicate that the debug port is unavailable. Please double-check device power supply and SWD lines, and that SWD isn&amp;#39;t disabled (Generic)&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Message: Batch task protection-get failed, Device error: Setting the debug port SELECT register failed while powering up sys and debug regions (Unknown Error in J-Link DLL (error code =-1)).&lt;/p&gt;
&lt;p&gt;This might indicate that the debug port is unavailable. Please double-check device power supply and SWD lines, and that SWD isn&amp;#39;t disabled.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>