Known Issues

Cannot launch Target Indicator, getting error about missing VCRUNTIME140_​1.dll / Cannot do any tracing with “Failed to load platform” error (Windows* host only)

Issue: This should not be an issue, but in case it appears - it means Microsoft* C++ Redistributables package is broken.

Workaround:

1. Go to “Add/Remove Programs”.

2. Uninstall all “Microsoft C++ Redistributables”.

3. Uninstall Intel® System Debugger.

4. Install Intel® System Debugger again.

Trace and debug operations on Alder Lake S require changes in platforms OS workaround settings

Issue: Power state transition (S5, S4, WR) with probe mode detection method TapPolling causes debug tool hang. Meanwhile, TapPolling is required for run control on targets with OS running. Starting with U2122 release, Intel® System Debugger NDA enables you to manage probe mode detection logic based on use cases.

Workaround: Follow instructions at <install_​dir>/documentation/tca/usage/connecting_​gui.html. Depending on your goals, complete step 7 as follows:

• For BIOS debugging or FW/SW tracing, select “Target runs no OS” (Default). Debugging and tracing on platform that does power transitions requires this option selected.

• For working with Architectural Event Traces (AET) or WinDbg over Intel® Direct Connect Interface (Intel® DCI), select “Target runs an OS”.

Disconnecting and reconnecting Intel System Debugger to Alder Lake S target with survivability flag enabled causes NorthPeak (NPK) hardware hang

Issue: During NPK tool disconnect and reconnect, NPK IP is power gated and then power un-gated and the default register value causes timeout and hang.

Workaround: Disable survivability mode if debugging across low power states is not required.

Low power debug is not supported for Alder Lake P due to missing Low Voltage Margining (LVM) overrides

Issue: Alder Lake P Best Known Configuration (BKC) does not support low power.

Workaround: N/A

Unicode error returned during target selection via console

Issue: When selecting a target with a command like trace.interactive_​setup(), an error like UnicodeEncodeError: ‘latin-1’ codec can’t encode character ‘u2122’ in position 24: ordinal not in range(256) is displayed.

Workaround: Before starting the console session, execute the following command:

• Windows: set PYTHONIOENCODING=UTF8

• Linux: export PYTHONIOENCODING=UTF8

Cannot connect Intel® System Debugger to Alder Lake P target with USB3 Debug Class (DbC)

Issue: Debug connection is not working with USB3 DbC connected to Alder Lake P. Reset break is also not functional.

Workaround: There are two ways to resolve connectivity issues with Intel System Debugger if USB3 DbC is detected:

• In the final step of establishing target connection (“Connection Summary” dialog box), expand the “Platform Debug Configuration” tab and uncheck the “Configure High Bandwidth Transport” box.

• Modify IFWI via Intel® Flash Image Tool (Intel® FIT) to enable USB2 port and avoid USB3 DbC detection.

Cannot establish USB DbC connection to debug the 10th generation Intel® NUC with Alder Lake M or Alder Lake P

Issue: When attempting to connect to the target using USB DbC, both Target Indicator and Windows* Device Manager report errors on the USB device (USB DbC probe).

Workaround: N/A

Target Indicator is not visible when being started on Linux* hosts with GNOME 3.26 and above (Linux* host only)

Issue: On Linux* hosts with GNOME 3.26 and above, the Target Indicator is not visible when being started because GNOME 3.26 removes the system tray that the Target Indicator heavily relies upon.

Workaround: You can start the Target Indicator executable with the --window-only (or short -w) flag, which makes the Target Indicator avoid using the system tray.

Cannot start the Target Indicator from a file explorer with older package versions (Linux* host only)

Issue: Starting the Target Indicator executable from a file explorer (for example, Nautilus) fails, since it is not recognized as an executable file.

Workaround: Upgrade the “file” package to a version higher than 5.36. Start the Target Indicator from the command line or via the provided application link (the package upgrade does not affect it). See the original bug report.

Reset causes libusb error and loss of run control on Linux* host

Issue : Warm or cold reset of the target connected to Comet Lake CPU/Comet Lake PCH-H (CML-S) in user interface or command line (ipccli) causes libusb error and loss of run control. Cold reset is necessary to connect to the target again.

Workaround: Use the Intel® DCI USB DbC2 instead of USB DbC3 on the port used for the debug connection. You can configure this in the Intel® Flash Image Tool (Intel® FIT)

1. Launch the Intel® FIT (obtained from Intel® Validation Internet Portal) and change the following settings within your current configuration:

   • Debug > Direct Connect Interface Configuration > Direct Connect Interface (DCI) Enabled > Yes

   • Debug > Early USB DBC over Type-A Configuration > USB2 DbC port enable > USB2 Port <X>

     where X identifies the post number. Depending on the target, set the following value:

     • 1 - to enable USB2 DbC on the vertical USB type-A port on CML-U DDR4 boards

     • 3 or 4 - to enable USB2 DbC on either of the two stacked USB type-A ports respectively on CML-U LP3 boards

     • 8 - to enable USB2 DbC on the vertical USB type-A port on CML-S boards with CMP-H or CNP-H chipset.

2. Build the image and flash the target with the new image.

Disconnecting a probe crashes the target (Windows* host only)

Issue: Intel® Silicon View Technology (Intel® SVT) Closed Chassis Adapter (CCA) and Intel® In-Target Probe (Intel® ITP) - XDP3 probes are supporting hot plug/unplug from a target, whereas for Intel® DCI DbC the connection is bidirectional. If a probe connection is lost, the debugger reports a Power Loss event.

Workaround: If the target was running, reconnect the probe (the disconnection has no effect on the running target). If the target was halted, reboot the target and restart the debugging session (the debug context is lost).

Platform security policy might inhibit debugger operation

Issue: In some platforms, the security policy might disable JTAG access to the CPU. This is intended to prevent reverse-engineering. In this case, the Intel® System Debugger will successfully connect to the target, but will not be able to discover any CPUs on the JTAG bus and will report that no CPU is available.

Workaround: Ensure that that platform firmware has enabled access to the CPUs via JTAG. You can do it by flashing a special “debug” firmware into the target. In some cases the CPU or the CPU module might physically disable JTAG access, especially in production or near-production versions. In this case, please work with the platform business unit to obtain a JTAG-enabled hardware.

Issue: When you attempting to archive Intel® DAL logs using the commands itp.daldebugloggerlevel("default") followed by itp.loggerarchive(), a “Permission Denied” error is printed.

Workaround: Before every execution of the commands above, navigate to <install-dir>\tools\DAL_​<version> and modify the PublicLogging.log4net file to replace “DALBase.log” with a location where you have write permissions (for example, C:\Temp\DALBase.log).

Cannot connect Intel® System Debugger to Raptor Lake CPU / Alder Lake PCH-S target with Intel® In-Target Probe (Intel® ITP) - XDP3

Issue: Debug connection is not working with Intel® ITP XPD3 connected to Raptor Lake CPU / Alder Lake PCH-S.

Workaround: Use a different debug probe (see Supported Platforms and Probes for available connection options).

Reset Break issues on Granite Rapids and Meteor Lake

Issue: Reset break does not work on properly Granite Rapids and Meteor Lake platforms. Planting and hitting reset break does not work reliable. Once it may work, other times it may fail sporadically to halt all cores.

Workaround:

• Meteor Lake users can try to use Intel® System Debugger 2246.

• For Granite Rapids there is currently no workaround.

Resume or step from Software Breakpoint issue on Granite Rapids D

Issue: Resume or step from Software Breakpoint issue on Granite Rapids D does not work properly. An attempt to resume execution or perform a step on a target halted in a Software Breaks does not work properly an can lead to a MCA exception.

Workaround: Use should use Hardware Breakpoints instead of Software Breakpoint.

Installation of DFLaunch fails

Issue: Installation of DFLaunch fails and the installer rolls back the installation.

Workaround: Check if there are existing virtual environments in DFLaunch with dfmanager and remove defect ones. Afterwards retry the installation.

Intel® PT Trace may contain incorrect data with “Incomplete PT Segment” warning

Issue: Target configured with Single Range Output larger than 4KB may cause incorrect output values to be recorded in Processor Trace (PT).

Workaround:

• Change BIOS configuration in “Intel Advanced Menu -> Debug Settings -> Advanced Debug Settings -> Processor Trace Output Schema” to ToPA Output (Table of Physical Addresses) instead of Single Range Output.

• Avoid using PT with Single Range Output schema larger than 4KB.