On Target Trace: Capture trace capture directly on device under test

Collecting traces is fundamental step to debug firmware and software. Traditionally Intel(R) System Trace Tool required that the user use Host and Target system to capture firmware, software, and hardware traces. Connecting Host to a target allows to collect boot logs and trace across low power, but challenging for collecting traces in automaton pools, for in-field test pools or small factor devices with single USB connector. On-Target Trace was developed to address limitation of host-based trace capture. Within new capability we split trace use cases into two buckets.

1. Host based solution aim to trace boot (pre-OS) and traces across power states (S4, S5) and low power. Recommended to be used by platform debug engineers, BIOS, CSME developers for active development and triage.

2. An on-target solution to collect logs during the OS working state, with limitations for S4 and low power. Recommended to be used in in-field validation and automation, by driver developers, audio, graphics, AI developer to get driver logs in correlation with firmware.

Since on target doesn’t require Host system connection, it doesn’t depend on Intel® Direct Connect Interface (Intel® DCI) enablement and can be enabled as standalone item as part of token management knob.

The on-target solution requires installation of the ITH driver. Follow ITH driver installation

On-Target Trace is part of Target Agent and deployed with the Intel(R) System Trace Tool as console tool. In order to start using On-Target script, open ISD_​shell and type intel_​ontarget_​trace

To get started with Target Agent, select trace sources, memory size and action.

Execute action on click Enter.

Depending on selected action, capture will be saved to file and decoded if requested.