<?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>VSCode RTT terminal not working for NRF54L15</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/120142/vscode-rtt-terminal-not-working-for-nrf54l15</link><description>Hello, 
 
 I am unable to use the Segger RTT terminal built into the nRF Connect SDK for VSCode Extension pack with the nRF54L15DK. 
 
 I have configured my project with the following configuration to log via RTT: 
 
 
 When I connect an RTT terminal</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 04 Nov 2025 15:35:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/120142/vscode-rtt-terminal-not-working-for-nrf54l15" /><item><title>RE: VSCode RTT terminal not working for NRF54L15</title><link>https://devzone.nordicsemi.com/thread/553337?ContentTypeID=1</link><pubDate>Tue, 04 Nov 2025 15:35:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90b22ef3-939a-4cc8-abe4-fa11615d1339</guid><dc:creator>BertL</dc:creator><description>&lt;p&gt;Okay thanks! It is not a super big deal, but&amp;nbsp;would be cool if it can be solved. :)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: VSCode RTT terminal not working for NRF54L15</title><link>https://devzone.nordicsemi.com/thread/553193?ContentTypeID=1</link><pubDate>Mon, 03 Nov 2025 15:16:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:51e899d7-9ac7-4994-80ec-ea5a90def539</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I do not have a simple workaround that can be used now, but we have discussed this internally and will work to improve it. I cannot say when it will be done, though.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: VSCode RTT terminal not working for NRF54L15</title><link>https://devzone.nordicsemi.com/thread/553154?ContentTypeID=1</link><pubDate>Mon, 03 Nov 2025 12:21:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:643995f8-b1ac-4d1c-b784-0223c43bf1e5</guid><dc:creator>BertL</dc:creator><description>&lt;p&gt;I&amp;#39;m using nrfConnect 3.1.1 and&amp;nbsp;J-Link V8.66, but if I start rtt logging I still get the error &amp;quot;&lt;strong&gt;The selected device NRF54L15_XXAA is unknown to this version of the J-Link software&lt;/strong&gt;&amp;quot;. When I manually select&amp;nbsp;NRF54L15_M33&amp;nbsp;in the pop-up dialog,&amp;nbsp;logging works correctly, but I have to do this every single time when I start the rtt log. Is there a way to store this setting somewhere?&lt;br /&gt;&lt;br /&gt;Flashing works fine, I only have this issue with the RTT log.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: VSCode RTT terminal not working for NRF54L15</title><link>https://devzone.nordicsemi.com/thread/529110?ContentTypeID=1</link><pubDate>Wed, 26 Mar 2025 15:13:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:09693283-1f30-4f5a-93b4-10c2c85c3c84</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;J-Link v8.22 is not yet supported, and I recommend you use 8.10f for now. With this you can get RTT logging to work also in VS Code, but you have to manually select the device type like this when selecting RTT:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1743001977437v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Then you should see the RTT log appear,as shown here with the Bluetooth peripheral UART sample:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1743002025674v2.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>