The command uses the following structure:
nrfutil trace stm [--database-config ARG] [--input-file PATH] [--input-serialport ARG] [--input-jtrace-serial-number SERIAL_NUMBER] [--output-raw PATH] [--output-type ARG] [--keep-configuration] [--help]
| Long | Short | Values | Description |
|---|---|---|---|
--database-config |
ARG |
Map from core to custom database configuration file path. Accepted format: core_id:path,core_id2:path2 ... |
|
--input-file |
PATH |
Input file to read trace data from. | |
--input-serialport |
ARG |
Specify serial port to use (COM for Windows, /dev/ttyACM devices for Linux, and /dev/tty devices on macOS).You can also specify custom serial port options in 'key=value' pairs with comma separation. For example, 'port=COM1,baud_rate=115200'. These are the valid input pairs: * baud_rate=INTEGER (default: 115200) * data_bits=INTEGER (default: 8) * flow_control=none |
|
--input-jtrace-serial-number |
SERIAL_NUMBER |
Input J-Trace PRO or J-Trace PRO Cortex-M serial number to read trace data from a connected nRF54H20 device. If enabled, STM trace data is read out from the Trace Port Interface Unit (TPIU) and streamed to a localhost socket. This requires that a J-Trace PRO or J-Trace PRO Cortex-M debugger is connected to the nRF54H20's TPIU 19-pin port.The output can be stored to a file: see '--output-*' alternatives. This is only supported for nRF54H20. |
|
--output-raw |
PATH |
Output the trace data as bytes to file. | |
--output-type |
ARG |
Output traces with a specific type. | |
--keep-configuration |
- | Save the temporarily generated trace collection configuration file. It will be stored in the current directory. | |
--help |
-h |
- | Print help (see a summary with -h). |