English | 中文
CCES Tool — build Analog Devices CrossCore Embedded Studio (ADI CCES) DSP projects directly inside VS Code: one-click build/clean/rebuild, real-time diagnostics, IntelliSense integration, a graphical build-settings editor, plus tool panels for the chip package view, System Services and the linker memory map — no need to switch back to the CCES IDE.

Features
One-click headless build
- Build / Rebuild / Clean from the status bar or the command palette. Projects are imported and makefiles are generated headlessly via the CCES console launcher, then compiled with CCES
make.
- Works with moved projects — makefile infrastructure is validated before every build; if it references locations that no longer exist (project moved, CCES reinstalled, copied from another machine), it is regenerated automatically — the same thing the CCES IDE does before every build.
- Real-time diagnostics — ADI compiler/linker messages (
ccXXXX: error/warning) are parsed into the VS Code Problems panel with exact file/line locations.
- IntelliSense integration — include paths and preprocessor defines are parsed from the Eclipse
.cproject, the CCES toolchain system headers are added (which the compiler adds implicitly), and everything is fed to the C/C++ extension (ms-vscode.cpptools) through a custom configuration provider.
- Multi-chip support — ADSP-2148x / ADSP-2156x / ADSP-2159x / ADSP-2183x, each with its own CCES installation path. Dual-core projects: pick the core project to build.
Build-settings editor
A graphical panel to view/edit 150+ CCES build options (optimization, warnings, preprocessor, linker, MISRA, loader…) directly in the project's .cproject — tree layout matching the IDE Properties → Tool Settings page, IDE-style tabs for Processor Setting / Build Steps / Build Artifact / Parsers, and minimal-diff writes.
Core — chip package view
An interactive package view of the selected processor (ADSP-2159x and ADSP-2156x families, LPC/HPC 400-ball BGA and 120-lead LQFP): click any ball or lead to see its position, all mux functions and what the pin currently does in your project (parsed from the generated pinmux_config.c). In-use pins are green, free GPIOs gray, DAI (SRU) pins purple; the diagram supports Ctrl+wheel zoom, and the full reusable-IO list below highlights every pin claimed by the pinmux tool.

System Services (system.svc)
A structured, editable view of the project's system.svc: Installed Components, Startup Code, Cache Configuration, LDF and MCAPI as live forms (checkboxes, text fields, dropdowns where the value set is known) with Settings-style Cancel/Apply — edits are written back transactionally (all-or-nothing). The SRU page renders the DAI routing registers as grouped hex tables.

Memory Map viewer
A rich viewer for the build configuration's .map.xml: memory summary with usage bars, output/input section tree with sizes and shares, expandable symbol tables, sidebar navigation, and a sticky search bar with match navigation.

Pin & IO Resources
Port-grouped pin tables parsed from the system.svc pinmux configuration: GPIO name, routed peripheral function (badges) and a routed-peripherals summary.

Explorer integration
Optionally hides files excluded from the active build configuration and files not imported into the Eclipse project. An activity-bar sidebar groups all tool panels and follows the status-bar project/family selection.
Requirements
- A local CrossCore Embedded Studio installation (tested with CCES 3.0.1).
- VS Code C/C++ extension (
ms-vscode.cpptools) for IntelliSense.
Usage
Install the .vsix, then open the folder that contains your CCES Eclipse projects.
Use the status bar buttons (left → right):
| Button |
Action |
| project name |
Select the CCES project to build (Eclipse projects found in the workspace) |
Core: Auto |
Pick a chip family (ADSP-2148x / 2156x / 2159x / 2183x). Auto follows the project's -proc value |
| configuration |
Select the build configuration (Debug / Release / …) |
Build |
Incremental build (make all) |
Rebuild |
Clean + build |
Clean |
Remove build outputs |
Settings |
Open the build-settings editor |
Stop |
Stop the running build |
Open the CCES Tool view in the activity bar for the tool panels: Core (chip view), Pin & IO Resources, System Services (system.svc) and Memory Map (.map.xml).
Typical workflow: select project → select configuration → Build. IntelliSense refreshes automatically after selection and builds.
Per-chip CCES installation paths can be set in VS Code Settings (search ccesBuild).
Extension Settings
| Setting |
Description |
ccesBuild.idePath |
Default CCES installation path |
ccesBuild.idePathAdsp2148x / ...Adsp2156x / ...Adsp2159x / ...Adsp2183x |
Per-chip CCES installation path (empty = use default) |
ccesBuild.executableName |
Console launcher executable under idePath/Eclipse (default ccesc.exe) |
ccesBuild.workspaceSuffix |
Temporary headless workspace directory name (default ccesworkspace) |
ccesBuild.autoExclude |
Hide files excluded from the active build configuration |
ccesBuild.hideUnimported |
Hide files not imported into the Eclipse project |
ccesBuild.toolchainHint |
Toolchain family (affects IntelliSense defaults only) |
Found a bug or have a question? Email me a screenshot and I will follow up:
📧 fangcuiqun@163.com
License
MIT
中文
English | 中文
CCES Tool —— 在 VS Code 中直接构建 ADI(Analog Devices,亚德诺半导体)CrossCore Embedded Studio(CCES) DSP 工程,无需切换回 CCES IDE:一键编译/清理/重建、实时错误诊断、IntelliSense 智能提示集成、图形化编译设置编辑器,以及芯片封装视图、System Services、内存映射等工具面板。

功能特性
一键无头编译
- 状态栏或命令面板执行 Build / Rebuild / Clean。工程通过 CCES 控制台启动器无头导入并生成 makefile,再用 CCES 自带
make 编译。
- 支持移动过的工程:每次构建前校验 makefile 基础设施,若引用了已不存在的位置(工程移动、重装 CCES、从别的机器拷贝),自动删除并重新生成——与 CCES IDE 每次构建前的行为一致。
- 实时诊断:ADI 编译/链接消息(
ccXXXX: error/warning)解析进 VS Code 问题面板,精确到文件与行号。
- IntelliSense 集成:解析
.cproject 中的头文件路径与宏定义,自动补充 CCES 工具链系统头文件目录(编译器隐式添加、.cproject 中没有的),通过自定义配置提供器喂给 C/C++ 扩展(ms-vscode.cpptools),消除头文件红色波浪线。
- 多芯片支持:ADSP-2148x / ADSP-2156x / ADSP-2159x / ADSP-2183x,每个芯片可配置独立的 CCES 安装路径;双核工程可选择构建核一/核二子工程。
编译设置编辑器
图形化查看/修改 150+ 项 CCES 编译选项(优化、告警、预处理、链接、MISRA、Loader…),直接写回工程 .cproject——树形布局与 IDE Properties → Tool Settings 一一对应,带 Processor Setting / Build Steps / Build Artifact / 解析器等 IDE 属性页标签,写回最小化改动。
Core —— 芯片封装视图
所选处理器的交互式封装视图(支持 ADSP-2159x 与 ADSP-2156x 家族,LPC/HPC 400 球 BGA 与 120 脚 LQFP):点击任意球/引脚即可查看位置、全部复用功能以及当前在工程中的用途(解析生成的 pinmux_config.c)。在用引脚绿色、空闲 GPIO 灰色、DAI(SRU)紫色;芯片图支持 Ctrl+滚轮缩放;下方全量可复用 IO 表以黄底标出 pinmux 占用的引脚。

System Services(system.svc)
工程 system.svc 的结构化可编辑视图:Installed Components、Startup Code、Cache Configuration、LDF、MCAPI 全部为活表单(勾选框、文本框、取值已知处的下拉框),配 Settings 风格 Cancel/Apply——编辑事务性写回(要么全部成功要么全部不写)。SRU 页将 DAI 路由寄存器渲染为分组十六进制表。

内存映射查看器
构建配置 .map.xml 的富查看器:Memory 汇总表带使用率进度条、输出段/输入段树(大小与占比)、可展开符号表、侧边栏导航,以及带匹配导航的吸顶搜索栏。

Pin & IO 资源
从 system.svc pinmux 配置解析的按端口分组引脚表:GPIO 名称、路由的外设功能(徽章标记)与已路由外设汇总。

资源管理器集成
可选隐藏当前构建配置排除的文件、未导入 Eclipse 工程的文件。活动栏侧边栏集中所有工具面板,并跟随状态栏的工程/芯片家族选择联动。
环境要求
- 本机已安装 CrossCore Embedded Studio(实测 CCES 3.0.1)。
- VS Code C/C++ 扩展(
ms-vscode.cpptools,用于 IntelliSense)。
使用方法
安装 .vsix 后,用 VS Code 打开包含 CCES 工程的文件夹。
使用状态栏按钮(从左到右):
| 按钮 |
功能 |
| 工程名 |
选择要构建的 CCES 工程(自动扫描工作区中的 Eclipse 工程) |
Core: Auto |
选择芯片系列(ADSP-2148x / 2156x / 2159x / 2183x);Auto 跟随工程 -proc 值 |
| 配置名 |
选择编译配置(Debug / Release / …) |
Build |
增量编译(make all) |
Rebuild |
清理后重新编译 |
Clean |
清理编译产物 |
Settings |
打开编译设置编辑器 |
Stop |
停止当前构建 |
在活动栏打开 CCES Tool 视图使用工具面板:Core(芯片视图)、Pin & IO 资源、System Services(system.svc)、内存映射(.map.xml)。
典型流程:选工程 → 选配置 → Build。选择与构建完成后 IntelliSense 自动刷新。
各芯片的 CCES 安装路径在 VS Code 设置中配置(搜索 ccesBuild)。
扩展设置
| 设置项 |
说明 |
ccesBuild.idePath |
默认 CCES 安装路径 |
ccesBuild.idePathAdsp2148x / ...Adsp2156x / ...Adsp2159x / ...Adsp2183x |
各芯片独立的 CCES 安装路径(留空使用默认) |
ccesBuild.executableName |
idePath/Eclipse 下的控制台启动器(默认 ccesc.exe) |
ccesBuild.workspaceSuffix |
无头构建临时工作区目录名(默认 ccesworkspace) |
ccesBuild.autoExclude |
隐藏当前构建配置排除的文件 |
ccesBuild.hideUnimported |
隐藏未导入 Eclipse 工程的文件 |
ccesBuild.toolchainHint |
工具链系列(仅影响 IntelliSense 默认值) |
支持与联系
发现问题或有疑问?欢迎发邮件附截图反馈,我会跟进处理:
📧 fangcuiqun@163.com
许可证
MIT