Cannot start the Target Indicator on Linux* OS

The screen is empty or the following message is returned:

Error: Unable to initialize GTK+, is DISPLAY set properly?

Solution

Launch the Target Indicator with the -w parameter. See an example below:

/opt/intel/oneapi/system_debugger/latest/target_indicator/bin$ ./TargetIndicator -w

Cannot Connect the Closed Chassis Adapter (CCA) to Target Using USB3

Connection attempt runs into a timeout.

Solutions

• Use a USB2 (non-SuperSpeed) Type A to Type B cable to connect the CCA to the host.

• Use the cable shipped with the Closed Chassis Adapter (CCA)

Closed Chassis Adapter (CCA) is not Recognized by Windows* OS

Cause

Intel® Direct Connect Interface (Intel® DCI) drivers are not properly installed.

Solution

In the Windows Device Manager, search for a device called Intel USB CCA Debug Class Devices. If it is not set up, contact customer support (see details in Intel® System Debugger Release Notes).

Connection to Target Takes Long and Fails with a Timeout Message

Cause

If OpenIPC detects an old firmware on the CCA, it updates the firmware automatically during the first connection to the target. In some cases, connection procedure may run into a timeout and display error messages on the Eclipse* console. The old firmware is only updated at the first connection. All subsequent connections should run smoothly.

Solution

If you ran into a timeout, do the following:

1. Close Eclipse* and kill OpenIPC connections (if any).

2. Unplug the CCA adapter.

3. Plug-in the CCA adapter.

4. Start Eclipse* and follow the connection procedure again.

Eclipse Console Shows an IPC API Error Message

For example:

• IPC API library is not initialized

• Error, IPC is NOT ready - failed to connect

Solution

Make sure the target is connected correctly using an Intel® Direct Connect Interface (Intel® DCI) USB 3.x Debug Class debug cable (yellow or orange connectors).

Board is not Booting Completely to UEFI Shell

Solution:

Try restarting (power off/power on) the board several times until it boots to UEFI.

Advanced: Using IPC CLI to Configure OpenIPC Connection

The default and recommended way of establishing target connection using the Target Connection Assistant (TCA) is described in the corresponding section.

However, you can use the IPC command line interface (IPC CLI) to run and configure OpenIPC sessions if:

• TCA does not detect your running OpenIPC session as expected

• You are used to working with the IPC CLI.

In any of the cases above, follow the steps below to establish target connection:

1. Launch IPC CLI:

   1. Navigate to the installation root directory and run isd_​shell.bat (for Windows* OS host) or isd_​shell.sh (for Linux* OS host).

   2. In the opened command line, run ipccli and configure the OpenIPC session as required.

      For instructions on using the IPC CLI, call help() from the command line or refer to the IPC CLI documentation located at:

      • For Windows* OS host: <install_​dir>\system_​debugger\<version>\tools\python3\Lib\site-packages\ipccli\html

      • For Linux* OS host: <install_​dir>/system_​debugger/<version>/tools/python3/lib/python3.x/sitepackages/ipccli/html

2. When your OpenIPC instance is running, launch the Intel® System Debugger. From the installation root directory, run iss_​ide_​eclipse-launcher.bat (for Windows* OS host) or iss_​ide_​eclipse-launcher.sh (for Linux* OS host) and proceed with remaining steps.

Eclipse Console shows a problem with locales packet

When trying to connect to local target with IDE buttons, Eclipse launchs an error window with the the sugestion to install locales package

Solution: sudo locale-gen en_​US en_​US.UTF-8 sudo dpkg-reconfigure locales

export LC_​ALL=en_​US.UTF-8