<?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>NRFUTIL: Trace utility is not stable</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/115039/nrfutil-trace-utility-is-not-stable</link><description>I&amp;#39;m experiencing frequent crashes of the trace utility. 
 
 
 I understand the information provided is not sufficient to root cause the issue. 
 Perhaps there is a combination of options that can allow me to collect more usable logs?</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 30 Sep 2024 12:25:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/115039/nrfutil-trace-utility-is-not-stable" /><item><title>RE: NRFUTIL: Trace utility is not stable</title><link>https://devzone.nordicsemi.com/thread/504355?ContentTypeID=1</link><pubDate>Mon, 30 Sep 2024 12:25:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5419a61d-5c10-457b-b180-ff6ad7d8734d</guid><dc:creator>vytautas</dc:creator><description>&lt;p&gt;Understood. Thanks for the information.&lt;/p&gt;
&lt;p&gt;Please let me know when a fix is available.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRFUTIL: Trace utility is not stable</title><link>https://devzone.nordicsemi.com/thread/504349?ContentTypeID=1</link><pubDate>Mon, 30 Sep 2024 12:03:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a20e0343-81e6-49eb-abf8-bb8c43fba215</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hi, I had a colleague test&amp;nbsp;one more time with linux, and there does seem to be an issue with nrfutil. You should be able to collect modem traces through cellular monitor while waiting for a fix.&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRFUTIL: Trace utility is not stable</title><link>https://devzone.nordicsemi.com/thread/504121?ContentTypeID=1</link><pubDate>Fri, 27 Sep 2024 08:29:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2c21b57f-a866-4234-b873-23da4d047546</guid><dc:creator>vytautas</dc:creator><description>&lt;p&gt;Currently only 7.11.0 version is available for download for Linux (Running Debian)&lt;/p&gt;
&lt;p&gt;&lt;a id="" href="https://docs.nordicsemi.com/bundle/nrfutil/page/guides/installing.html"&gt;https://docs.nordicsemi.com/bundle/nrfutil/page/guides/installing.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a id="" href="https://www.nordicsemi.com/Products/Development-tools/nRF-Util"&gt;https://www.nordicsemi.com/Products/Development-tools/nRF-Util&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The trace utility version is the same.&lt;/p&gt;
&lt;p&gt;Where are the debug logs stored? I&amp;#39;m not getting them in stdout.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRFUTIL: Trace utility is not stable</title><link>https://devzone.nordicsemi.com/thread/504107?ContentTypeID=1</link><pubDate>Fri, 27 Sep 2024 08:14:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0856e39b-55e4-46d6-a77e-3948f51645fc</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;I used the command you provided. i was able to run it for a while, collecting 18k of data. Have not heard of this issue before, so will need to investigate more.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Here is my version&lt;br /&gt;&lt;br /&gt;&lt;pre class="ui-code" data-mode="text"&gt;oysa@NordicTechSupportM2 ~ % nrfutil --version 
nrfutil 7.13.0 (8289424 2024-07-01)
commit-hash: 82894242d19ff24a1541712312b3ea3af0ca8f85
commit-date: 2024-07-01
host: aarch64-apple-darwin
build-timestamp: 2024-07-01T07:34:47.247880000Z
classification: nrf-external

oysa@NordicTechSupportM2 ~ % nrfutil trace --version
nrfutil-trace 2.11.0 (8fa6588 2024-09-18)
commit-hash: 8fa6588c66efdcebc2676bf7c393cb5036184f7f
commit-date: 2024-09-18
host: aarch64-apple-darwin
build-timestamp: 2024-09-19T06:23:01.954159000Z
classification: nrf-external&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Could you try running with --log-level debug i.e.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;nrfutil trace lte --log-level debug --input-serialport /dev/ttyACM1 --output-pcapng wireshark-$(date +%s).pcapng&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRFUTIL: Trace utility is not stable</title><link>https://devzone.nordicsemi.com/thread/503990?ContentTypeID=1</link><pubDate>Thu, 26 Sep 2024 13:01:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93952628-dd33-4e51-b2f2-64d60122f2bb</guid><dc:creator>vytautas</dc:creator><description>&lt;p&gt;I recently installed the trace and device utilities.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;nrfutil-trace is already the newest version (2.11.0)
nrfutil-device is already the newest version (2.5.4)
[00:00:01] ###### 100% [Upgrade packages] Upgrade packages&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t think I&amp;#39;ve updated nrfutil itself. Is it was of the Nordic command line tools package?&lt;/p&gt;
&lt;p&gt;For some additional context, it doesn&amp;#39;t crash immediately. Here&amp;#39;s an example:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 8.5K Sep 26 14:57 wireshark-1727351557.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  36K Sep 26 15:52 wireshark-1727352383.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 2.8K Sep 26 16:37 wireshark-1727356319.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  14K Sep 26 17:26 wireshark-1727357939.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 4.8K Sep 26 18:22 wireshark-1727360906.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 1.6K Sep 26 18:50 wireshark-1727364236.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  18K Sep 26 20:05 wireshark-1727365903.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  480 Sep 26 20:17 wireshark-1727370429.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 1.1K Sep 26 20:27 wireshark-1727371105.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  20K Sep 26 21:26 wireshark-1727371694.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  792 Sep 26 21:38 wireshark-1727375313.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  608 Sep 26 21:59 wireshark-1727375962.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  400 Sep 26 22:03 wireshark-1727377168.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;    0 Sep 26 22:03 wireshark-1727377413.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  412 Sep 26 22:09 wireshark-1727377496.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  284 Sep 26 22:13 wireshark-1727377823.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  160 Sep 26 22:15 wireshark-1727378049.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  416 Sep 26 22:20 wireshark-1727378151.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  160 Sep 26 22:21 wireshark-1727378479.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 2.4K Sep 26 22:44 wireshark-1727378638.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  288 Sep 26 22:50 wireshark-1727379871.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;    0 Sep 26 22:51 wireshark-1727380286.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 7.5K Sep 27 00:13 wireshark-1727380310.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  22K Sep 27 01:42 wireshark-1727385249.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 8.4K Sep 27 02:36 wireshark-1727390577.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 2.9K Sep 27 02:46 wireshark-1727393853.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  28K Sep 27 03:44 wireshark-1727394442.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 2.8K Sep 27 04:19 wireshark-1727397999.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;    0 Sep 27 04:20 wireshark-1727400040.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 9.0K Sep 27 05:14 wireshark-1727400065.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 2.2K Sep 27 05:20 wireshark-1727403352.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 1.1K Sep 27 05:25 wireshark-1727403679.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  916 Sep 27 05:31 wireshark-1727404007.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt;  924 Sep 27 05:37 wireshark-1727404335.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 4.4K Sep 27 06:13 wireshark-1727404662.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 1.1K Sep 27 06:23 wireshark-1727406847.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 4.5K Sep 27 07:25 wireshark-1727407437.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 5.6K Sep 27 08:10 wireshark-1727411249.pcapng
-rw-r--r--  1 &amp;lt;REDACTED&amp;gt; &amp;lt;REDACTED&amp;gt; 7.5K Sep 27 09:13 wireshark-1727413913.pcapng
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;I ran the command in a&amp;nbsp;while loop. Whenever it crashed, it would immediately create a new trace. You can look up the file creation times above to understand the frequency a bit better.&lt;/p&gt;
&lt;p&gt;Could you post how you ran the trace utility? I can try running it the same way.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRFUTIL: Trace utility is not stable</title><link>https://devzone.nordicsemi.com/thread/503975?ContentTypeID=1</link><pubDate>Thu, 26 Sep 2024 12:13:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:146cb0ec-bf22-4f69-9391-bd99ecae9e80</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello,&amp;nbsp;&lt;br /&gt;&lt;br /&gt;I&amp;#39;ve tested on my macbook and another linux device, and was not able reproduce. Have you updated you nrfutil?&lt;br /&gt;&lt;br /&gt;KInd regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>