<
- For a complete list, check the document [SLAU647](https://www.ti.com/lit/slau647)
- XDS110: Standalone XDS110 [TMDSEMU110-U](https://www.ti.com/tool/TMDSEMU110-U), LaunchPads with built-in XDS110 technology
- The XDS110 EnergyTrace HDR Add-on [TMDSEMU110-ETH](https://www.ti.com/tool/TMDSEMU110-ETH) is also supported
- XDS100: v1, v2 and v3
- XDS200: USB [TMDSEMU200-U](https://www.ti.com/tool/TMDSEMU200-U), LAN [XDS220](http://www.spectrumdigital.com/xds220-usb-ethernet-jtag-emulator/)
- TM4C/Tiva/Stellaris ICDI as well as CC3200 LaunchPad
- Spectrum Digital: XDS560v2 [TMDSEMU560V2STM-UE](https://www.ti.com/tool/TMDSEMU560V2STM-UE), XDS ProTrace [TMDSEMUPROTRACE](https://www.ti.com/tool/TMDSEMUPROTRACE)
- Blackhawk: XDS560v2 USB [TMDSEMU560V2STM-U](https://www.ti.com/tool/TMDSEMU560V2STM-U), XDS560v2 Ethernet
- SEGGER J-Link
- Not all TI devices are supported. Check [Segger's device list](https://www.segger.com/products/debug-probes/j-link/technology/cpus-and-devices/overview-of-supported-cpus-and-devices/)
## Not Supported ##
- MSP430: MSP-FET430PIF (Parallel port), Launchpads and Experimenters kits that use eZ430 technology such as Chronos, [MSP-EXP430G2](https://www.ti.com/tool/MSP-EXP430G2) and [MSP-EXP430FR4133](https://www.ti.com/tool/MSP-EXP430FR4133) LaunchPads.
- **Note:** the [MSP-EXP430G2ET](https://www.ti.com/tool/MSP-EXP430G2ET) is supported.
- For a complete list, check the document [SLAU647](https://www.ti.com/lit/slau647)
- Stellaris ICDI based on FTDI
- Blackhawk: USB2.0, XDS560 PCI, XDS560T, XDS510, USB560, USB560m, USB560bp
- Spectrum Digital: XDS510, XDS560R, Parallel Port emulators
- Texas Instruments: XDS560 PCI, XDS510 ISA
- In general vendors are not supporting PCI, ISA or parallel port emulators on Linux
For information on a specific debug probe please contact the manufacturer.
# Distribution Validation #
CCS is validated on a defined set of Linux distributions. Typically these are active Ubuntu LTS versions.
CCS 11.x is validated on:
- Ubuntu 20.04 LTS
- Ubuntu 18.04 LTS
# Installation Instructions #
CCS requires a 64-bit distribution of Linux. 32-bit distributions are not supported with current versions of CCS.
CCS has dependencies on several libraries being installed on the system. The CCS installer will run a dependency check for these and inform the user of any missing dependencies.
Example:
Please resolve **all** unresolved dependencies reported by the installer before continuing with the installation.
<font color="#FF0000"><b>IMPORTANT!</b></font> TI performs testing on actively supported Ubuntu LTS distributions <b>only</b>. For other versions of Linux distributions, consider these releases as <b>unsupported</b> and <b>untested</b> with CCS.
<br>
<font color="#FF0000"><b>NOTE</b></font>: Certain older SDKs and Compiler installers could hang when installing on a system with glibc2.26 and greater. While the component is installed correctly, the installer doesn't exit. In order to complete your installation of the component, kill off the hanging installer and remove the downloads folder from the <installdir>/eclipse directory, if it exists.
<font color="#FF0000"><b>NOTE</b></font>: it is possible to install CCS as a superuser using sudo (gksu is not recommended), which automatically adds all the required driver udev rules at the end of the process. However this requires extra steps for regular operation of CCS as a regular user. Check the application note [Configuring CCS for multiuser](./application_notes/appnote-configuring_ccs_for_multiuser.html) for details.
- When installed as superuser using sudo, CCS must be run at the same privilege level to install updates.
- When installed and run as superuser using sudo, there may be some IBus warning messages that appear in the terminal. These messages can be ignored, as they will not impact the execution of CCS. This can be avoided by specifying <tt>sudo -H</tt> when running the CCS installer.
### After Installation ###
If CCS was installed as user, then it is necessary to run the driver install script after the installation is complete:
- go to <CCS_INSTALL_DIR>/ccs/install_scripts
- <tt>sudo ./install_drivers.sh</tt>
## Ubuntu 20.04 LTS ##
- update system: <tt>sudo apt update</tt>
- install dependent libraries: <tt>sudo apt install libc6-i386 libusb-0.1-4 libgconf-2-4 libncurses5 libpython2.7 libtinfo5</tt>
- install CCS
- if CCS was installed as user then run the driver install script
- go to <CCS_INSTALL_DIR>/ccs/install_scripts
- <tt>sudo ./install_drivers.sh</tt>
# Proxy server considerations #
Certain functions of Code Composer Studio require access to the Internet. In general, this works well for connections that do not require a proxy server, but in certain cases its use is mandatory by the corporate IT department.
Linux poses a challenge to configure proxy servers due to the nature of its various components and where they inherit its settings. For example, it is not uncommon to have a web browser fully connected to the internet while the aptitude or yum utilities (used to install system features or dependencies) is unable to do so.
In this case, it is important to observe a few aspects during CCS setup and runtime.
- The proxy server configuration can be set during the installation options. This is critical for a successful install if using the On-demand installer (web installer), as each component must be downloaded individually.
- The system update utility (apt, yum, etc.) has its own configuration files to set up a proxy, typically text files under the subdirectory /etc. To properly configure these utilities, please refer to your distro instructions.
- The system wide proxy setting is usually accessible via the GUI of choice (Gnome, KDE, etc.) and is normally present under the Network settings. This setting is inherited by the Eclipse features of Code Composer Studio, namely the ability to access its update sites to update the various components of an install (compilers, emupack, etc.)
- The shell environment variable <tt>http_proxy</tt> (and its counterparts <tt>https_proxy</tt> and <tt>ftp_proxy</tt> not used by CCS) are inherited by the browser built into Code Composer Studio to access its online content and download the various SDK packages. In general this environment variable is set at the system wide shell init script (<tt>/etc/bash.bashrc</tt>, for example) but this can also be set by each user on its local shell <tt>~/.bashrc</tt>.
- The scope where this configuration will reach is highly dependent on the install and definitely some experimentation is necessary.
- In this case, experimentation can be done by setting the environment variable exclusively during the invocation of Code Composer Studio from a command line. For example, from a bash shell the proxy environment variable can be set prior to running CCS as:
**user@host:~/ti/ccs1100/ccs/eclipse$** <tt>http_proxy=myproxy.mycompany.com:80 ./ccstudio &</tt>
<!-- End of markdown source -->
<div id="footer"></div>
]]>