🎉 TriCore v6.3r1p10 available! We're happy to announce the public patch release of TASKING VX-toolset for TriCore v6.3r1p10. Contact us

Linux: Install winIDEA 9.12.288

26-Sep-2025

These instructions explain how to install winIDEA on Ubuntu using Wine.

They were tested with Ubuntu and Kubuntu 12.04, 13.10, and 14.04 using Wine 1.4, 1.5, and 1.6. Other Linux distributions are supported as long as WineHQ is available (installation steps may differ slightly).


Configuration steps

1. Install Wine and MS redistributable.

$ sudo apt-get update
$ sudo apt-get install wine
$ winetricks vcrun2008


2. Install winIDEA 

a. Prepare the installation directory where winIDEA will be installed:

$ mkdir -p "<winIDEA-install-dir>"
$ cd "<winIDEA-install-dir>"


Example:

$ mkdir -p ~/winIDEA/winIDEA9_12_184  &&  cd ~/winIDEA/winIDEA9_12_288


b. Download and run the winIDEA installation script:

$ wget http://www.isystem.com/downloads/winIDEA/setup/installWinIDEA.sh
$ chmod +x installWinIDEA.sh

 

If you want a version other than the latest, open the script and change the version number in the variable WINIDEA_DISTRO. Run the installation script:

$ sudo ./installWinIDEA.sh

The script will ask several questions to customize the installation.


c. Start winIDEA. If you've created a link during installation in  /usr/local/bin folder, run:

$ winidea


 Otherwise run:

$ "<winIDEA-install-dir>"/winidea.sh


Technical details

WINEDLLPATH environment variable

The folder containing the winIDEA executable (winidea.exe) must be included in WINEDLLPATHThis variable is usually set automatically in winidea.sh.

Manual run example:

$ cd <winIDEA-install-dir>
$ export WINEDLLPATH=`pwd`


Confirm the value:

$echo $WINEDLLPATH
/home/<user>/<winIDEA-install-dir>


Udev rules for USB access

To access USB devices, create the file /etc/udev/rules.d/isystem-itag.rules with the following content:

ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="06f9", OWNER="<yourUserName>"

Replace <yourUserName> with your actual username.

Detach and reattach the BlueBox device so the rule takes effect. This file is normally created during installation.


Launching winIDEA manually

Run winIDEA:

$ cd <winIDEA-install-dir>
$ ./winidea.sh

 If you see Permission denied, check your udev rules and ensure your username is correct.


Configure winIDEA hardware communication

Inside winIDEA, go to Hardware | Hardware | Communication and select your BlueBox device in the USB combo box.


Troubleshooting

Enable USB logging

Set the environment variable to enable logging:

export ISYSTEM_LIBUSB_LOGGING=1

This generates a usb.log file in the directory where winIDEA was started. Send this file to Technical Support for analysis.


Missing Communication tab

If the Communication tab is missing in the Hardware dialog:

  • Ensure icusbcomm.dll.so is present in the winIDEA folder.
  • Confirm WINEDLLPATH points to the absolute path of <winIDEA-install-dir>.


Device not recognized in winIDEA

If the BlueBox is attached and powered but not visible in winIDEA:

1. Check if the system detects it:

lsusb

2. If it appears in the output but not in winIDEA, review your udev rules.


2. If there is no Communication tab in the Hardware dialog, then your icusbcomm.dll.so was not found. Check the presence of the library in the winIDEA folder and the setting of WINEDLLPATHWINEDLLPATH must be set to the absolute path of <winIDEA-install-dir>.

3. If the BlueBox device is turned on and attached to your computer, but it does not show up in drop-down list, them most likely udev rules are not set properly. First, make sure that the device is recognized by

   the system:

$ lsusb


If you can see the device in this output, but not in winIDEA, check udev rules and read on.

  

Udev rule notes

Dynamic device management is handled by udev.

Create a rules file, e.g.:  /etc/udev/rules.d/isystem-usb.rules.

The filename can be arbitrary, but must have the .rules extension.


Example rule:

ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="06f9", OWNER="<userName>"


If needed, you can also specify a custom node name:

ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="06f9", ATTR{idProduct}=="d001", OWNER="<userName>", NAME="iTagSTM32"

The original /dev/bus/usb node ownership does not change. The rule takes effect after unplugging/plugging the device. No restart is required.


More resources

Was this answer helpful?