<?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>Could not connect to target when use GDB debug in VSCode</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/124514/could-not-connect-to-target-when-use-gdb-debug-in-vscode</link><description>Hi, 
 nRF54L15 DK + VSCODE + nRF connect for VSCODE, 
 I test example peripheral_uart, when click debug to start debugging with GDB，it show error： 
 
 
 
 Starting: &amp;quot;C:\Program Files\SEGGER\JLink_V794a\JLinkGDBServerCL.exe&amp;quot; -if SWD -speed 4000 -device</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 23 Sep 2025 09:03:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/124514/could-not-connect-to-target-when-use-gdb-debug-in-vscode" /><item><title>RE: Could not connect to target when use GDB debug in VSCode</title><link>https://devzone.nordicsemi.com/thread/549504?ContentTypeID=1</link><pubDate>Tue, 23 Sep 2025 09:03:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:46507833-5cd9-4d99-8fa2-d7627341b541</guid><dc:creator>Priyanka</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Glad to hear that you got it working. Official J-Link support for nRF54L15 was added only recently, so older packs (like v794a) might not recognize the device name.&lt;/p&gt;
&lt;p&gt;Also, VS Code’s nRF Connect debugger doesn’t use Zephyr’s runner scripts, so edits there won’t affect the extension’s debug session.&lt;/p&gt;
&lt;p&gt;-Priyanka&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Could not connect to target when use GDB debug in VSCode</title><link>https://devzone.nordicsemi.com/thread/549373?ContentTypeID=1</link><pubDate>Sun, 21 Sep 2025 15:00:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6562a717-965b-4cad-b68f-35328e4f4730</guid><dc:creator>lkb</dc:creator><description>&lt;p&gt;&lt;span&gt;But earlier, I modified parameters in&amp;nbsp;&lt;/span&gt;&lt;code class="hyc-common-markdown__code__inline"&gt;zephyr\scripts\west_commands\runners\jlink.py&lt;/code&gt;&lt;span&gt;. Why didn&amp;#39;t it take effect? Why did the parameters remain the same when starting GDB?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Could not connect to target when use GDB debug in VSCode</title><link>https://devzone.nordicsemi.com/thread/549372?ContentTypeID=1</link><pubDate>Sun, 21 Sep 2025 14:55:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cc330d57-868b-461e-a602-57ae55717d9c</guid><dc:creator>lkb</dc:creator><description>&lt;p&gt;&lt;span&gt;The issue has been resolved. I installed JLINK V870 and it worked.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>