
C2000 IDE Assist is a Visual Studio Code and Code Composer Studio Theia/20 extension that enables various tools and features for C2000 MCUs.
Repo TexasInstruments/C2000-IDEA, read from GitHub 4 h ago. TexasInstruments has not joined Take My Repo.
TexasInstruments/C2000-IDEA is a public repo on GitHub by TexasInstruments. C2000 IDE Assist is a Visual Studio Code and Code Composer Studio Theia/20 extension that enables various tools and features for C2000 MCUs. It declares the BSD-3-Clause license on GitHub. It is written mainly in JavaScript, has 26 stars and last changed on 2026-11-17. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-22.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
C2000 IDE Assist is a Visual Studio Code and Code Composer Studio 20 extension that enables various tools and features for C2000 MCUs. It provides an easier way to develop, debug, and migrate C2000 application code with features available in your development environment.
For more in depth details about supported features and tool usage, see the C2000 IDE Assist Tool Features Guide
This tool is available in the CCS extension market place. You can also download the vsix file directly from GITHUB. https://github.com/TexasInstruments/C2000-IDEA. See detailed installation steps below.
The C2000-IDEA extension can be used with either a Code Composer Studio 20 or VSCODE development environment.
(Recommended) This software allows you to not only develop your code, but also build and debug your C2000 project.
Launch your chosen IDE
Open your C2000 projects and files from the Explorer tab of the side bar panel
Click on the Extensions tab of the side bar panel
All that is needed to install the C2000-IDEA extension is a VSIX file

When the C2000-IDEA extension has finished installing, you should see a new icon added to the main side bar panel.
Note: You may need to restart your IDE after installation if the new icon doesn't appear after a couple minutes.
While this isn't a required setup step, running project detection for all of the projects in your CCS workspace (or VSCODE folder) will enhance the usage of many of the C2000-IDEA tools features by keeping track of which C2000 device each file is being developed for and only providing suggestions and support for peripherals relevant to the specific device. Many features alternatively allow the user to input their C2000 device each time a feature/command is invoked, or you may set up a default device in the Extension properties.
All features of the C2000-IDEA tool support driverlib projects for GEN 3 or GEN 4 C2000 devices. Select features include support for bitfield project files and specific GEN 2 C2000 devices. For a list of all available devices and project types supported per feature, please see section x of the Application Report (https://www.ti.com/lit/pdf/SPRADL6). Most features can be accessed via buttons in the extension Tree View inside one of the four panes. Alternatively, all features can be run by invoking their related commands in your IDE by inputting Ctrl+Shift+P and typing in the name of the command. A more in depth list of all available features and their associated commands are listed in the Application Report ((https://www.ti.com/lit/pdf/SPRADL6). The below will go over the features available with buttons in the Tree View panes.
The C2000-IDEA tab has the following panes:
The C2000-IDEA targeted collateral delivery features will autogenerate collateral links relevant to the files and text you are actively editing in your IDE. Once the extension has been installed and (optionally) project detection has been run, this feature will begin populating with related links while you open and edit different files. No additional steps are needed to enable these features.
The following steps can be used to detect all device registers in a file for improved understanding of example code and seamless code development. Register vision is available for both driverlib and bitfield code register accesses.
The below code assistance features can aid in code development by autogenerating template application code and providing direct links to register descriptions during development.
The following steps can be used to generate template code to read or write to a C2000 device register using driverlib register accesses.
The following steps can be used to generate a template ISR function definition for an interrupt in the ePIE (C28x) or PIPE module (C29x).
The following steps can be used to help migrate a driverlib project across C2000 devices.

C2000-IDEA includes built-in Model Context Protocol (MCP) server support, which allows AI coding assistants to interact directly with your C2000 projects — reading project settings, running migration analysis, querying device TRM data, and executing full device-to-device migration workflows — all from within a natural-language conversation.
What is an MCP server? MCP (Model Context Protocol) is an open standard that lets AI agents call tools hosted by applications. When the C2000-IDEA MCP servers are running, your AI assistant gains access to C2000-specific tools it can invoke automatically as it helps you work.
The following AI coding assistants work with C2000-IDEA out of the box:
| AI Assistant | Platform |
|---|---|
| Claude Code | CLI / VS Code |
| GitHub Copilot (Agent mode) | VS Code |
| Cursor | Cursor IDE |
| OpenAI Codex CLI | CLI |
You do not need to edit any config files by hand. The extension provides
C2000-IDEA: Register IDEA MCP and C2000-IDEA: Register TI ASM MCP commands that
prompt for the tool you are using and write the correct MCP configuration file automatically.
The IDEA MCP server is the primary interface. It gives your AI assistant access to C2000-IDEA tools such as project listing, migration report generation, and bitfield-to-driverlib conversion.
To enable:
Ctrl+Shift+P or Cmd+Shift+P on macOS)C2000-IDEA: Enable IDEA MCPC2000-IDEA: Check IDEA MCP — it will display the server URL (http://localhost:55001/mcp) when activeTo stop the server: Run C2000-IDEA: Disable IDEA MCP from the Command Palette.
Default URL: http://localhost:55001/mcp
You can change the port or host in VS Code / CCS Settings (Ctrl+,) by searching for c2000-idea:
| Setting | Default | Description |
|---|---|---|
c2000-idea.ideaMcp.port |
55001 |
Port the IDEA MCP server listens on |
c2000-idea.ideaMcp.host |
localhost |
Host address the IDEA MCP server binds to |
Run C2000-IDEA: Register IDEA MCP from the Command Palette and select the tool you are
using. The extension writes the correct MCP configuration file for that tool automatically —
.mcp.json (Claude Code), .cursor/mcp.json (Cursor), .vscode/mcp.json (GitHub Copilot), or
.codex/config.toml (OpenAI Codex CLI). No manual editing required.
Power users: If you prefer to configure the server yourself, run
C2000-IDEA: IDEA MCP Instructionsfor a copy-ready snippet.
The TI ASM MCP server gives your AI assistant on-demand access to TI device Technical Reference Manuals (TRM) — including register definitions, bit-field descriptions, and peripheral documentation. This is especially useful during device migration when the assistant needs to verify register-level intent before constructing a replacement.
To enable:
C2000-IDEA: Enable TI ASM MCPTo stop the server: Run C2000-IDEA: Disable TI ASM MCP from the Command Palette.
Default URL: http://localhost:55000/mcp
| Setting | Default | Description |
|---|---|---|
c2000-idea.mcp.port |
55000 |
Port the TI ASM MCP server listens on |
c2000-idea.mcp.host |
localhost |
Host address the TI ASM MCP server binds to |
Register with your AI assistant:
Run C2000-IDEA: Register TI ASM MCP and select your tool — same flow as Step 1. (Power
users: C2000-IDEA: TI ASM MCP Instructions prints a manual snippet.)
Once both MCP servers are enabled and registered, your AI assistant can perform a complete, end-to-end C2000 device migration — from importing the source project all the way to a clean build on the target device — with minimal manual steps.
This is a deeper capability than the manual migration check. It creates a fully migrated target project, touching compiler settings, SysConfig, header files, source symbols, and linker files.
| Source → Target | Status |
|---|---|
| F28x → F28x (e.g., F28003x → F28P55x, F2837xD → F28P65x) | ✅ Fully supported |
| F28x → F29x | 🚧 Coming soon |
Note: The device names F28003x (source) and F28P55x (target) used throughout this section and the diagram below are illustrative examples only. You can use any supported C2000 source and target device pair. Refer to the Supported Migration Paths table for the list of supported combinations.
The AI agent drives a structured 6-phase workflow (Phase 0 pre-flight + Phases 1–5). Each phase uses the IDEA MCP and supporting MCP servers to inspect the project, apply changes, verify the result, and log progress before moving to the next phase.
flowchart TD
START(["▶ Start Migration\nUser: Migrate my F28003x project to F28P55x\nusing the C2000-IDEA AI migration workflow"])
PROBE["🔍 Phase 0 — Pre-flight Check\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nProbe 1: call get_projects() — test IDEA MCP reachability\nProbe 2: call getProducts() — test CCS Project MCP\nProbe 3: call list_devices() — test TI ASM MCP (soft warning)\nProbe 4: call listFiles() — test CCS SysConfig MCP (soft warning)\nGit check: confirm clean working tree · recommend migration branch\n✔ All probes pass → record session context · proceed to Phase 1\n✘ Hard stop on IDEA MCP or CCS Project MCP failure:\n Command Palette → C2000-IDEA: Enable IDEA MCP\n Then re-register MCP and retry probe"]
P1["📦 Phase 1 — Project Import and Baseline\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n1.1 Validate source project name and target device inputs\n1.2 Discover source project → device · SDK paths · build config\n1.3 Identify SDK type and resolve C2000Ware path\n1.5 Import universal driverlib example for target device\n1.6 Build imported starter → confirm zero compile errors\n1.7 Rename project to target device name e.g. myproject_f28p55x\n1.8 Rebuild renamed project → confirm build still passes\n1.9 Create c2000-migration.md append-only audit log\n Records: source device · target device · active build config TBD"]
P2["⚙️ Phase 2 — Build Settings Alignment\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n2.0 Identify active build config e.g. CPU1_FLASH or Debug\n Record confirmed config in c2000-migration.md\n2.1 Align compiler flags to target device SDK\n2.2 Update predefined device symbol F28003x → F28P55x\n2.3 Update include paths source SDK path → target SDK path\n2.4 Update linker flags stack · heap · map-file\n2.5 Detect linker CMD style CMD module vs plain .cmd\n2.6 Copy application source files to target project\n2.10 Read-back diff — verify all applied settings"]
P3["🔧 Phase 3 — SysConfig Migration 3A + 3B\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n3A.1 Copy source .syscfg file into target project directory\n3A.2 Open target .syscfg · record source module list for audit\n3A.3 Ensure device_support module present add if missing\n─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─\n3B.1 Migrate device → select target device and package\n3B.2 Coverage audit → flag modules silently dropped by migrate()\n3B.3 Fix configuration errors iteratively\n3B.4 Normalize CMD module to match source linker style\n3B.5 Error gate after CMD normalization → save and close\n3B.6 Verify SysConfig outputs wired into CCS project build"]
P4PRE["⬇️ Phase 4.pre + 4.0 — Preparation\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n4.pre Download migration guide HTML to target project dir\n On failure: prompt user to download via Chrome/Edge\n4.0a Ask user: #ifdef shared codebase or clean replacement?\n4.0b Scope report via get_project_migration_report()"]
P4H["📄 Phase 4A — Header File Migration per file\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n4A.1 Replace all #include paths containing source device name\n4A.2 Update device macro guards #ifdef F28003x → #ifdef F28P55x\n4A.3 Complex fixes: render_migration_guide_section(htmlPath, anchor)\n4A.4 Verify no stale source-device include paths remain"]
P4S["📝 Phase 4B — Source File Migration per file\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n4B.1 Run get_device_migration_report → fix each flagged issue\n Complex fixes: render_migration_guide_section(htmlPath, anchor)\n4B.2 GPIO remapping check on every .c file\n4B.3 Build after migration report is clean\n4B.4 Fix any build errors · defer cross-file errors to 4C\n4B.5 Repeat until clean build for this file"]
P4C["🔁 Phase 4C — Final Sweep and Build Verification\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n4C.1 Re-run migration report on all migrated files\n Complex fixes: render_migration_guide_section(htmlPath, anchor)\n4C.2 Regression baseline check near all fix sites\n4C.3 Resolve deferred cross-file build errors from 4B\n4C.4 Two-pass clean rebuild first cleans objects · second verifies\n ✔ PASS → proceed to Phase 5\n ✘ FAIL → dispatch Phase 4D build error triage"]
P4D["🔨 Phase 4D — Build Error Triage dispatched only on FAIL\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n4D.1 Collect current build error list via buildProject()\n4D.2 Classify each error:\n A: missing include or file-not-found\n B: undefined symbol\n C: deprecated or renamed API\n D: linker/memory-map deferred-manual\n4D.3 Apply fixes for categories A–C\n Uses get_device_migration_report for authoritative fixes\n4D.4 Rebuild and evaluate max 3 triage iterations\n4D.5 Record results · return build status to orchestrator"]
P5["📊 Phase 5 — Report and Hardware Verification\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n5.1 Final clean build skip if Phase 4C PASS in same session\n5.2 Structured summary: per-file table · unresolved symbols\n5.3 SysConfig status · SDK version change logged\n5.4 Bitfield register scan → flag legacy .bit/.all for follow-up\n5.5 Hardware verification checklist\n H1 Clock tree config H2 GPIO pinout and mux\n H3 Peripheral base addr H4 Interrupt routing PIE/PIPE\n H5 Memory map linker H6 Power domains analog subsystem\n H7 Boot mode device cfg H8 Debug interface JTAG"]
DONE(["✅ Migration Complete\nTarget project builds clean on target device\nFull audit log recorded in c2000-migration.md\nMigration report and hardware checklist exported"])
START --> PROBE
PROBE --> P1
P1 --> P2
P2 --> P3
P3 --> P4PRE
P4PRE --> P4H
P4H --> P4S
P4S --> P4C
P4C -->|"PASS"| P5
P4C -->|"FAIL"| P4D
P4D --> P5
P5 --> DONE
style START fill:#C00000,color:#ffffff,stroke:#8B0000,stroke-width:2px
style PROBE fill:#404040,color:#ffffff,stroke:#202020,stroke-width:1px
style P1 fill:#1F497D,color:#ffffff,stroke:#17375E,stroke-width:1px
style P2 fill:#17375E,color:#ffffff,stroke:#0F243E,stroke-width:1px
style P3 fill:#215732,color:#ffffff,stroke:#17401E,stroke-width:1px
style P4PRE fill:#7B3F00,color:#ffffff,stroke:#5C2E00,stroke-width:1px
style P4H fill:#7B3F00,color:#ffffff,stroke:#5C2E00,stroke-width:1px
style P4S fill:#7B3F00,color:#ffffff,stroke:#5C2E00,stroke-width:1px
style P4C fill:#5C2E00,color:#ffffff,stroke:#3D1E00,stroke-width:1px
style P4D fill:#8B0000,color:#ffffff,stroke:#5C0000,stroke-width:1px
style P5 fill:#4B0082,color:#ffffff,stroke:#320057,stroke-width:1px
style DONE fill:#215732,color:#ffffff,stroke:#17401E,stroke-width:2px
Prerequisites (do this once): Complete the Setup Checklist below — install CCS 20, C2000-IDEA, and your AI assistant; enable both MCP servers; and register them with your agent.
Safety tip (Git users only): If your C2000 application project is version-controlled in Git, commit your current changes and create a new branch (e.g.,
git checkout -b migration-to-f28p55x) before starting, so you can roll back easily. If your project isn't in Git, you can skip this.
Start the migration — just ask your AI assistant:
Example prompt (substitute your own source and target device names): "I have a C2000 F28003x project. Please migrate it to F28P55x using the C2000-IDEA migration workflow."
The AI assistant will:
get_projects()c2000-migration.md log and a final migration reportIf the AI assistant does not start the workflow automatically, invoke the migration skill directly with its slash command:
/c2000-idea
If your project uses legacy bitfield register access patterns (AdcRegs.ADCCTL1.bit.ADCBGPWD = 1), your AI assistant can convert these to modern driverlib function calls (ADC_setPowerMode(...)) for the same device.
Run this before device migration. Converting bitfield code to driverlib first reduces noise in the device migration report and produces a cleaner result.
Ask your AI assistant:
"My F28003x project uses bitfield register accesses. Please convert them to driverlib calls using C2000-IDEA."
The assistant uses the get_bitfield_to_driverlib_migration_report IDEA MCP tool to identify all bitfield patterns and generate driverlib replacements. Results are shown with file locations and suggested fixes.
For technical details, see docs/skills/c2000-idea/references/bitfield-to-driverlib-migration.md.
This section provides a complete, step-by-step guide for setting up the C2000-IDEA AI migration on your local computer, including how to handle common proxy and network issues.
| Step | Action | Details |
|---|---|---|
| 1 | Install CCS 20 | Required to build and manage C2000 projects. Download from ti.com/tool/CCSTUDIO |
| 2 | Install C2000-IDEA | See Installing C2000-IDEA |
| 3 | Install your AI assistant | See the Supported AI Assistants table above |
| 4 | Enable IDEA MCP server | Command Palette → C2000-IDEA: Enable IDEA MCP (or click MCP Servers in the status bar) |
| 5 | Enable TI ASM MCP server | Command Palette → C2000-IDEA: Enable TI ASM MCP (or click MCP Servers in the status bar) |
| 6 | Register both MCP servers | Run C2000-IDEA: Register IDEA MCP and C2000-IDEA: Register TI ASM MCP, then select your tool |
| 7 | Open your project workspace | Open your C2000 project folder in CCS 20 or VS Code |
| 8 | Start the migration | Ask your AI assistant (see How to Start a Migration) |
Register both servers as described in Step 1 — Enable the IDEA MCP Server and
Step 2 — Enable the TI ASM MCP Server: run C2000-IDEA: Register IDEA MCP
and C2000-IDEA: Register TI ASM MCP, then select your tool when prompted.
If your machine is behind a corporate proxy or firewall, you may encounter connectivity issues between your AI assistant and the C2000-IDEA MCP servers running on localhost. The following covers the most common scenarios.
http://localhost:55001/mcpSymptom: The agent reports the MCP tool is unavailable or times out on tool calls.
Root cause: Some AI agents route HTTP requests through the system proxy. Many corporate proxies do not forward localhost / 127.0.0.1 requests correctly, causing the connection to fail.
Resolution — add localhost to the proxy bypass list:
Windows (System Proxy):
localhost;127.0.0.1;::1VS Code / CCS (settings.json):
"http.noProxy": "localhost,127.0.0.1,::1"
Environment variable (all platforms):
NO_PROXY=localhost,127.0.0.1,::1
Possible causes and resolutions:
| Cause | Resolution |
|---|---|
Port 55001 already in use by another process |
Change the port: open VS Code Settings (Ctrl+,), search c2000-idea.ideaMcp.port, set a free port (e.g., 55011), then re-enable the server and update your agent config |
| Windows Firewall blocking the port | Add an inbound exception in Windows Defender Firewall for TCP port 55001 on localhost |
| Agent config has the wrong URL | Run C2000-IDEA: Check IDEA MCP in the Command Palette — it displays the exact URL the server is listening on. Update your agent config to match |
Root cause: The MCP servers are registered but the agent session was started before the config was applied.
Resolution:
C2000-IDEA: Check IDEA MCPC2000-IDEA: Register IDEA MCP and re-select your tool to rewrite the config fileExpected behavior. The IDEA MCP server and TI ASM MCP server are hosted by the C2000-IDEA VS Code extension. They run only while CCS 20 or VS Code is open with the extension active. If you close the IDE, the servers stop.
Recommendation: Keep CCS 20 or VS Code open throughout your AI migration session. Re-enable the servers if they stop:
C2000-IDEA: Enable IDEA MCP (or click MCP Servers in the status bar → select IDEA MCP)C2000-IDEA: Enable TI ASM MCP (or click MCP Servers in the status bar → select TI-ASM MCP)Root cause: Some corporate VPN clients route all traffic including localhost through the VPN tunnel, breaking local MCP connections.
Resolution:
127.0.0.1, localhost, and ::1 to the split-tunnel exclusion list in your VPN clientlocalhost:55001 and localhost:55000127.0.0.1) by setting c2000-idea.ideaMcp.host to 127.0.0.1 in VS Code SettingsQuick reference — proxy bypass values to configure across all tools:
localhost,127.0.0.1,::1
TexasInstruments/C2000-IDEA is a public repo on GitHub by TexasInstruments. C2000 IDE Assist is a Visual Studio Code and Code Composer Studio Theia/20 extension that enables various tools and features for C2000 MCUs.
It declares the BSD-3-Clause license on GitHub.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-11-17. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
This repository contains FreeRTOS kernel source/header files , kernel ports and demos for C2000 devices

Edgeai TIDL Tools and Examples - This repository contains Tools and example developed for Deep learning runtime (DLRT) offering provided by TI’s edge AI solutions.

Industry-leading SAR and Delta-Sigma ADCs with easy-to-use design resources to enable premium performance

TI MCU+ SDK core source code repository with drivers, protocol stacks and example applications