Listing modem trace input and output options

nRF Util

tags
nRF Util

When you start tracing, you must specify the input and output options. The following table lists the available options for nrfutil trace lte:

Option Type Description
--input-file <PATH> Input Input file to read trace data from
--input-serialport <SERIALPORT> Input Specify serial port to use (COM for Windows, /dev/ttyACM devices for Linux, and /dev/tty devices on macOS).
Supports custom serial port options in 'key=value' pairs with comma separation.
--output-pcapng <PATH> Output Output the trace data to PcapNG file format.
--output-pcapng-stdout Output Output the trace data to PcapNG format on standard output (stdout). Use this option to pipe capture data to other tools, such as Wireshark. Supports the same --pcapng-filter option as --output-pcapng.

Note: On Windows, PowerShell below v7.4 does not correctly handle piping or redirecting binary data from standard output. As a result, the PcapNG data may be malformed and might not open correctly in Wireshark. Use PowerShell v7.4 or later, or write output to a file with --output-pcapng instead.
--pcapng-filter <FILTER> Output Specify packets to include in the PcapNG file as a comma-separated list of packet types.
--output-raw <PATH> Output Output the trace data to raw (binary) file format.
--output-wireshark <WIRESHARK_EXECUTABLE> Output Output the trace data into a Wireshark named pipe, providing the path to Wireshark.

Note

If you already have a binary trace data file and would like to have it in a different format, see Converting trace data.