3.1. Installation and Setup

3.1.1. System Requirements

Because CCStudio runs as an extension, your system must first meet the requirements for Visual Studio Code itself.

In addition, CCStudio for VS Code is a 64-bit application and will not run on 32-bit operating systems. This release was validated on:

Operating System

Supported Versions

Windows

Windows 11 64-bit, Windows 10 64-bit

Linux

Ubuntu 26.04 64-bit, Ubuntu 24.04 64-bit, Ubuntu 22.04 64-bit

macOS

macOS 26 (Tahoe), macOS 15 (Sequoia), macOS 14 (Sonoma) — Arm®-based Macs only

Note

Unlike CCStudio™ IDE, CCStudio for VS Code does not currently support Intel-based Macs, even with Rosetta.

3.1.2. Installing CCStudio for VS Code

CCStudio for VS Code is installed like any other VS Code extension:

  1. Open the Extensions view in VS Code (Ctrl+Shift+X).

  2. Search the Marketplace for CCStudio.

  3. Select the CCStudio for VS Code extension and click Install.

_images/ccsvsc_install-extension.png

Note

Searching the Marketplace for "CCStudio" may also return other, unrelated TI extensions. Make sure to install the one named exactly CCStudio for VS Code.

Installing the main CCStudio for VS Code extension (ccstudio) automatically installs the following required companion extensions:

  • CCStudio AI (ccstudio-ai) — AI-powered development support.

  • CCStudio Debug (ccstudio-debug) — debugging support for TI devices, including the Memory and Disassembly views.

  • TI Cortex Debug (ccstudio-openocd) — a TI-maintained fork of the Cortex-Debug extension, providing target communication over JTAG/SWD and the XPeripherals, Cortex Live Watch, and xRTOS views.

  • CCStudio Project (ccstudio-project) — project management and builds.

  • CCStudio SysConfig (ccstudio-sysconfig) — SysConfig support.

  • CCStudio StartHub (ccstudio-starthub) — SDK download and example project creation.

  • CCStudio TargetLink (ccstudio-targetlink) — Connects development tools to TI target devices through a local service.

The first time CCStudio starts, it downloads additional tools it needs in the background (such as OpenOCD, GDB/LLDB, CMake, Ninja, and Node.js), which requires some additional free disk space and a network connection.

Watch the notification toast in the lower-right corner of the window to track the download progress:

_images/ccsvsc_install-tools.png

Important

Wait for the Installing dependencies notification to finish before continuing.

3.1.3. Install the XDS110 Debug Probe Driver

To debug on a LaunchPad™ or any board with an XDS110 debug probe, XDS110 driver must be manually installed on your computer.

Note

If you already installed the XDS110 driver, skip this step.

The XDS110 installer is one of the tools CCStudio downloads in the background the first time it starts.

Important

Wait for the Installing dependencies notification to finish before you install the driver. If you run the installer too early, it might not be there yet or might be incomplete.

Open the folder below for your operating system and run the XDS110 installer, ti_xds110_setup_*.

OS

Installer folder

Windows

%LOCALAPPDATA%\Texas Instruments\CCSVSC\resources\debug_*\debug-probes

Linux

~/.config/Texas Instruments/CCSVSC/resources/debug_*/debug-probes

macOS

~/Library/Application Support/Texas Instruments/CCSVSC/resources/debug_*/debug-probes

The debug_* folder name includes a version number, so it might differ on your computer.

  • Windows — run ti_xds110_setup_*.exe

  • Linux — run ti_xds110_setup_*.bin

  • macOS — unzip ti_xds110_setup_*.app.zip, then run installbuilder.sh from inside the unzipped app: ti_xds110_setup_*.app/Contents/MacOS/installbuilder.sh

Follow the installer prompts. When it finishes, connect your device.