This page covers release specific information of all components of Intel® System Debugger that are present in the Intel® System Bring-Up Toolkit and Intel® oneAPI IoT Toolkit. The debugger includes following tools:
- System Debug: This JTAG-based debug solution supports in-depth debugging and tracing of system software and embedded applications that are based on Intel® architecture. System Debug provides Windows* and Linux* hosted cross-debug solutions for software developers to debug Unified Extensible Firmware Interface (UEFI) BIOS, the Linux* kernel sources, and dynamically loaded drivers and kernel modules for devices that are based on Intel Atom®, Intel® Core™, and Intel® Xeon® processors.
- System Trace: Capture Intel® Management Engine (Intel® ME), BIOS, and some power management messages. The traditional and popular way to get BIOS logs is to wire out a serial port and get logs from a COM port. But it is only for BIOS messages. System Trace collects Intel® Converged Security and Management Engine (Intel® CSME) and BIOS messages with time stamps and puts them together in sequence. It is much easier for users to understand whether the issue they experience is caused by Intel ME or BIOS.
- Intel® Debug Extensions for WinDbg* (for Windows hosts and targets): This is an extension for the traditional Microsoft* Windows Debugger (WinDbg). The traditional WinDbg works with functional Windows debug drivers. But in some system hang cases, the debug driver is also malfunctioning and the WinDbg cannot execute further debugging. Intel Debug Extensions for WinDbg changes the debugging route to Intel® Direct Connect Interface (Intel® DCI). Even when the operating system is malfunctioning, Intel Debug Extensions for WinDbg can still be working at collecting information to enable analyzing error cases.
Supported Operating Systems
- Windows® 10
- Microsoft Windows Server* 2016 and 2019
- Ubuntu* 18.04 LTS
- Fedora* 30
Each Intel System Debugger tool has its own supported platforms. Depending on the platform to be debugged, the tools can provide several probe options for a connection:
- Intel® In-Target Probe (Intel® ITP) XDP3
- Intel® Silicon View Technology (Intel® SVT) Closed Chassis Adapter (CCA)
- Intel® Direct Connect Interface (Intel® DCI) USB Debug Class (DbC) cable
New in This Release - 2020 Beta
- Intel System Debugger started the transition phase from Python* 2.7 to Python 3. The transition to Python 3 will be finalized by end of 2019. The debugger ships both Python 2.7 and Python 3.6 versions during the transition phase until 2020.
- New platform support:
- 10th generation Intel® Core™ processor (formerly Ice Lake)
- 10th generation Intel Core processor (formerly Comet Lake)
- 10th generation Intel Core processor (formerly Amber Lake)
- Intel® Xeon® processor (formerly Cascade Lake)
- A new System Debug that is fully Eclipse* integrated has replaced the traditional stand-alone System Debug tool.
Intel® Debug Extensions for WinDbg*
- The support of Python* 2.7 for WinDbg has been deprecated and transferred to Python 3.
- Added system debugger support for targets with enabled hardware virtualization features (virtualization-based security and Microsoft Hyper-V).
- Platform security policy may inhibit debugger operations.
- Issue: In some platforms, the security policy may disable JTAG access to the CPU. This is intended to prevent reverse engineering. In this case, the Intel System Debugger successfully connects to the target, however, it cannot discover any CPUs on the JTAG bus and warns the user that no CPUs are available.
- Work-Around: To resolve this issue, ensure that that platform firmware has enabled access to the CPUs via JTAG. This is typically done by flashing a special debug firmware into the target. Also note that in some cases the CPU or CPU module may have physically disabled JTAG access, especially in production or near-production versions. In this case, work with the platform business unit to obtain a JTAG-enabled hardware.
- Various error messages referring to "Interview_Decoder" or "visa64.dll." For example: "Failed to load library <path_to_isd>\system_trace\bin\Interview_Decoder.dll." (Windows hosts only)
- Issue: If the host has IVI tools installed, then Intel® System Studio erroneously loads visa64.dll from C:\Windows\System32.
- Work-Around: There are two options:
- Temporarily remove C:\Windows\System32\visa64.dll or uninstall the IVI tools.
- Follow the instructions given in the link but be aware of the potential security implications.
Intel Debug Extensions for WinDbg*
- Compatibility issue with Intel Debug Extensions for WinDbg* while using the Windows 10 SDK:
- Issue: The WinDbg over Intel DCI plug-in is currently not compatible with the Windows 10 SDK starting at version 1809 (10.0.17763).
- Work-Around: Install the Windows 10 SDK, version 1803 (10.0.17134) or older versions.