When you start tracing, you must specify the input and output options. The following table lists the available options for nrfutil trace stm:
| 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. |
--input-jtrace-serial-number <SERIAL_NUMBER> |
Input | Input J-Trace PRO or J-Trace PRO Cortex-M serial number to read trace data from a connected nRF54H20 device. STM trace data is read from the Trace Port Interface Unit (TPIU) and streamed to a localhost socket. Requires J-Trace PRO or J-Trace PRO Cortex-M debugger connected to nRF54H20's TPIU 19-pin port. Only supported for nRF54H20. |
--output-raw <PATH> |
Output | Output the trace data to raw (binary) file format. |
--output-ascii <PATH> |
Output | Output the trace data to ASCII file format (plain text). Note: The nordic-log-stm-dict snippet in Zephyr does not support the ASCII output format. |
--stdout <OUTPUT_TYPES> |
Output | Output the trace data to standard out. Select between one or more output types, separating each value with comma. Possible values: binary, network, ascii, tls. |
Note
If you already have a binary trace data file and would like to have it in a different format, you can convert the file.