ERROR: Could not start kernel debugging using exdi: Class not registered

Cause

The ExdiIPC.dll file was not registered correctly.

Solution

Register the .dll file as follows:

1. Go to the <install-dir>\system_​debugger\<version>\windbg-ext\iajtagserver\intel64 directory.

2. Run the regsvr32 ExdiIPC.dll command.

ERROR: Could not start kernel debugging using exdi: Specified module could not be found

Cause

The ExdiIPC.dll file was removed after the registration.

Solution

Reinstall the add-on and make sure that it is available at <install-dir>\system_​debugger_​<version>_​nda\windbg-ext\iajtagserver\intel64\ExdiIPC.dll

ERROR: Could not start kernel debugging using exdi: Win32 error 0x87. The parameter is incorrect

regsvr32 "<install-dir>\system_debugger\<version>\windbg-ext\iajtagserver\intel64\ExdiIpc.dll".

ERROR: No probe found. Please check probe connection and power

Cause

Connection between the host and the probe is not correctly established. The probe is powered off or out of order.

Solution

Check the host connection to the probe and the probe power. Also, check if the probe drivers are correctly installed and working.

ERROR: No active threads detected

Cause

• Connection between the target and the probe is not correctly established.

• The probe is powered off or out of order.

Solution

• Check the target connection to the probe and the target power.

• Reset the target if locked.

ERROR: could not import runpy module / ModuleNotFoundError: No module named ‘runpy’

Cause

The system with Intel® System Debugger installed has not been cleaned.

Solution

Remove the folder C:\Users\<username>\AppData\Local\Intel\windbg-ext-venv and restart WinDbg.

WinDbg* is frozen

Cause

WinDbg is scanning memory to establish the connection. This can take several minutes. If the WinDbg break was issued at the wrong time, the scanning process takes about 10 minutes.

Solution

Wait until the scanning is done.