<?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>Getting RTT Logging with J-Link Probe and nRF54L15DK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/123079/getting-rtt-logging-with-j-link-probe-and-nrf54l15dk</link><description>It would be extremely useful to get the HCI Traces (BLE) of my nRF54L15 boards. Documentations: Embedded HCI Tracing For simplicity&amp;#39;s sake, here is my setup: - nRF54L15DK - Segger J-Link Debugger - J-Link Adapter CortexM - 10-pin 2x5 Socket-Socket 1.27mm</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 22 Jul 2025 13:53:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/123079/getting-rtt-logging-with-j-link-probe-and-nrf54l15dk" /><item><title>RE: Getting RTT Logging with J-Link Probe and nRF54L15DK</title><link>https://devzone.nordicsemi.com/thread/543213?ContentTypeID=1</link><pubDate>Tue, 22 Jul 2025 13:53:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fba173c2-2256-4e0a-833f-30aca574976d</guid><dc:creator>Kazi Afroza Sultana</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&amp;#39;&amp;#39;&lt;br /&gt;&lt;span&gt;- Find a way to use the VCOM0 (The serial port that doesn&amp;#39;t end with a 3)&amp;#39;&amp;#39;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;yes, in principle you can do this, dedicate one UART (e.g., VCOM0) for HCI tracing and other one is for your application logs. You need to configure your firmware so that the HCI trace output is routed to the UART instance connected to VCOM0.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;#39;&amp;#39;But I can&amp;#39;t seem to get the J-Link Probe to work with&amp;#39;&amp;#39;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;For the second one, you can check that you are using the latest version of the jlink RTT software and debugger is correctly connected to the PC.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;To capture and decode these traces, you should use the&amp;nbsp;&lt;code dir="ltr"&gt;btmon&lt;/code&gt;&amp;nbsp;tool from BlueZ with the&amp;nbsp;&lt;code dir="ltr"&gt;--jlink&lt;/code&gt;&amp;nbsp;option, specifying your device and serial number. For example:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;pre class="ui-code" data-mode="text"&gt;btmon --jlink nRF54L15_xxAA,&amp;lt;your_jlink_serial_number&amp;gt;&lt;/pre&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>