Skip to content

2.4.0 Release Notes

Source

CodeFusion Studio source can be found on GitHub under tag V2.4.0.

What's new

The following are some of the new features and enhancements introduced in version 2.4.0.

CLI

New commands

  • cfsutil ai e2e: Runs the full AI model workflow in one step: compatibility check, optional profiling, workspace creation with build, and flash and serial capture on hardware. By default, the command converts captured TEF traces into CodeFusion Studio reports; use --no-create-reports to skip.
  • cfsutil convert: Converts a TEF profiling trace into a CodeFusion Studio report (.cfsreport).
  • cfsutil validate config: Validates a CFS workspace or a standalone .cfsconfig file against the schema and reports errors and warnings. Supports --workspace, --input, --verbose, and --format flags. The command also reports pin-conflict for incompatible physical-pin assignments, control-invalid for persisted pin-control errors, and control-invalid-value when an unconditional peripheral control value violates its type, range, or pattern constraints. These checks fail the command (critical) when a data model is available for the SoC; validation falls back to schema-only checks (warning) when it isn't.
  • cfsutil validate dependencies: Checks that packages declared in the workspace and project dependency manifests are installed at compatible versions. Alias cfsutil validate deps. Supports --format flag.
  • cfsutil pkg path: Retrieves the absolute filesystem path of an installed package by name.
  • cfsutil telemetry: Manage telemetry preferences from the command line with cfsutil telemetry enable, cfsutil telemetry disable, and cfsutil telemetry status. The CLI displays the privacy disclosure during consent and in human-readable status output, including the data collected and the locally stored usage identifier, and explains the local check used to distinguish ADI-internal from external use. The CLI prompts for consent on its first interactive run and never sends telemetry in CI or other non-interactive environments. For details, refer to Telemetry.

New flags

  • cfsutil pkg install — --tar: Install a package from a local tarball using --tar, without downloading it from a package server.
  • cfsutil tasks run — --timeout and dependency-aware failure messages: Use --timeout with --capture to stop a serial port capture session automatically after the specified number of seconds, measured from when the task completes successfully. Omit the flag, or set it to 0, to capture until you stop it manually. When a task fails and the workspace declares unmet package dependencies, the failure message lists the unmet packages and points to cfsutil validate dependencies. Task execution is never blocked or delayed by dependency validation.
  • cfsutil ai workspace create — --set: Set model fields, such as enabled, in the new workspace with --set key=value. Repeat the flag to set multiple fields.

Behavior changes

  • cfsutil ai model — paths and URLs stored as provided, and identifier collision detection: cfsutil ai model add stores its --model, --dataset, and --network-config values as provided in the .cfsconfig file. cfsutil ai model update does the same for model, dataset, and networkconfig values passed through --set. Enter relative paths relative to the workspace root, and run these commands from the workspace root because cfsutil ai build resolves relative paths from there. Both commands also reject a model when the normalized C identifier for its Name or optional Symbol collides case-insensitively with either identifier from another model in the same workspace.
  • Verbose and quiet output: cfsutil commands are moving to consistent -v/--verbose and -q/--quiet behavior. For details of the extra output, see the command page.

Breaking changes and deprecations

  • JSON output envelope: cfsutil commands are moving to a standard {ok, command, data, warnings, errors} envelope for --format json output. For the list of commands, see JSON output envelope. If you have scripts that parse --format json output from these commands, update them to read results from data. Some commands also changed the shape of their results; see the command page for details.
  • cfsutil socs export — --gzip removed: The --gzip flag has been removed.
  • CLI flag collisions — short-flag deprecations: The short flags for several commands collided with the global -v/--verbose and -f/--format flags and are deprecated in favor of the long-form variants: cfsutil pkg list (-f → --filter), cfsutil elf symbols (-f → --full), cfsutil ai workspace create (-f → --skip-compat), and cfsutil socs export (-v → --version).

System Planner

  • SRU Config — new tab: Configure Signal Routing Unit (SRU) connections graphically for SHARC-FX processors, replacing manual register-level configuration.
  • Peripheral Allocation — SHARC-FX peripheral configuration: Assign and configure peripherals such as UART, SPI, SPORT, TWI, and DMA on SHARC-FX processors. Code generation creates the matching driver configuration headers and adds the required drivers to the project build.
  • Pin Config:
    • Fixed-function pins and configuration display: Fixed-function pins on SHARC-FX peripherals, such as DAI0, now display their physical pin mappings. Enable and Configure controls appear only for pins that support those actions. This behavior also applies to peripherals that contain a mix of assignable and fixed signals, such as SYS. In the configuration sidebar, the Configuration and Code Generation Plugin sections appear only when they contain applicable controls.
    • Pin description editor: Peripherals that allow assignment at the pin level, such as GPIO, now show a Details section in the configuration sidebar with a Description field for documenting the purpose of the pin.
  • Manage AI Models:
    • Renamed tab: The Embedded AI Tools tab in System Planner has been renamed to Manage AI Models. Functionality is unchanged.
    • Identifier collision detection: Adding or updating a model reports This identifier is already in use by another model when the normalized Model Name or Symbol for data value (when set) collides case-insensitively with either value from another model in the workspace.
    • Reports saved to your project: Compatibility and profiling reports now save to the reports folder of the project assigned to the same core as the model, instead of always saving to the temp directory.

Build and profiling

  • West Editor — new editor: Open the west.yml manifest of a west workspace that you manage in a graphical editor. View the current status of each project, search and filter projects, edit revisions and groups, and turn groups on or off.
  • AI Hardware Profiling:
    • Clean & Build: The AI Hardware Profiling view now uses the standard build task for your project by default and adds Clean & Build to rebuild the AI application from scratch after editing code.
    • Runtime Profile Report: For captures that generate a .tef file, selecting Stop also creates a Runtime Profile Report (.cfsreport) alongside it and opens the report automatically. The report shows measured latency, throughput, and per-layer timing from the target hardware.
  • Profiling:
    • Instrumentation trigger and stopper functions: Set the functions that start and stop Application Callgraph instrumentation directly in System Planner, using the new Trigger Function and Stopper Function fields on the Profiling tab.
    • Zephelin live tracing: Stream trace data to the Zephelin Trace Viewer while the capture runs, instead of saving .ctf and .tef files for later viewing. Turn on Enable Zephelin Live Tracing in the Trace Configuration view to monitor CPU load, memory usage, and AI inference timing in real time over UART or USB.
  • Tasks — dependsOn support: Add a dependsOn property to a custom task in cfs.tasks.json to run one or more other tasks first when you run the task from the CodeFusion Studio Actions view or with cfsutil tasks run.

Debugging

  • Debug with SEGGER Ozone — per-core actions: The Actions panel shows a separate Debug with Ozone (<core>) action for each Ozone-capable core (Arm Cortex-M and RISC-V), so you can open the debugger for a specific core from either the Workspace context or a core context. Cores that don't support Ozone, such as SHARC-FX, no longer show the action.
  • GDB Toolbox — SHARC-FX fault analysis: The Analyze Faults script supports SHARC-FX targets. During a halted debug session, it reads and decodes the SHARC-FX exception status registers and prints a fault summary.

AI-assisted development

  • AI-Assisted Development Skills — workspace bootstrap and AI model evaluation: Three new skills extend what your AI assistant can do: cfs-workspace-bootstrap sets up a workspace and checks that your environment is ready to build; cfs-ai-evaluation evaluates an AI model on a connected ADI board; and cfs-ai-report turns the results into an engineering report. They are available in GitHub Copilot, Claude Code, OpenAI Codex, and other supported agents. In this release, the skills have been tested only on the MAX32690 EvKit. Other processors are untested, and results on them might be incomplete. For installation and usage, see AI-Assisted Development Skills. If you installed the skills for Claude Code or another agent with CodeFusion Studio 2.3.0, update them to get the new skills. See Update the skills.
  • AI Debug Assistant:
    • Chat participant and source-search interfaces removed: The @cfs-debug GitHub Copilot chat participant has been removed. The MCP debug_search_source tool and source-search-and-debug prompt have also been removed; use the file-search capabilities of your AI client instead. Use the CFS MCP debug server for AI-assisted debugging with GitHub Copilot Agent Mode, Claude Code, or another MCP-compatible AI client.
    • Automatic client connection: When you start the CFS MCP debug server, the built-in MCP client in VS Code connects automatically, so debug tools are ready to use in GitHub Copilot Agent Mode without an extra manual step.

Package Manager

  • Manage package remotes — Remotes tab: The new Remotes tab in the Package Manager lists your package remotes. You can add custom remotes, enable or disable any remote, change the authentication of a custom remote, and delete a custom remote without using the command line.
  • View installed package contents — Packages view: The new Packages view in the CodeFusion Studio sidebar lets you browse, search, and filter the contents of installed packages. By default it shows the packages your workspace depends on.
  • Check for package updates — update notifications: CodeFusion Studio now notifies you when newer versions of the installed workspace packages are available. You can also check on demand with the (CFS) Check for Package Updates command.
  • cfspkg:// Git protocol: west can now clone a package installed with the Package Manager into your own application by using a cfspkg://<name>/<version> URL in west.yml. The package must already be installed and must be a Git repository.
  • Install packages — dependency conflict detection: The review summary screen now checks whether the packages you selected pull in incompatible versions of the same package — whether that package is one of your direct selections or a dependency they share — and reports the conflict before you accept licenses. The disputed package is highlighted, and Continue is unavailable until you resolve the conflict. See Dependency conflicts between selected packages for recovery steps.

Installer

  • Smaller, more flexible installation: Install toolchains and SDKs separately through the Package Manager, reducing the initial installer download and allowing you to install only the components you need. See Commonly available packages for the toolchain and SDK packages that replace the removed installer components. The setup wizard copies the CodeFusion Studio extension VSIX to your system, installs OpenOCD for ADI processors, and can install ADI ICE Drivers on Windows.
  • Set the SDK path — automatic extension host restart: Changing the SDK path, either in the cfs.sdk.path setting or with Choose SDK path, restarts the VS Code extension host automatically to apply the new path. You no longer need to restart VS Code.
  • SHARC-FX on Linux — new host support: You can now create, build, and debug SHARC-FX projects on Linux. When run with root privileges, the installer automatically configures USB permissions for ICE emulators.

Development platforms and tools

  • Support for Zephyr RTOS 4.4.2 Get started with Zephyr RTOS 4.4
  • Support for the MSDK Get started with MSDK
  • Support for the ADSP-2183x/SC83x SHARC-FX family (Windows and Linux only)
  • Compiler and debug support is available for Zephyr (Arm Cortex-M only) and MSDK (Arm Cortex-M and RISC-V) on supported MAX32xxx and MAX78xxx microcontrollers, and SHARC-FX (ADSP-2183x/SC83x family).

Software component versions available for CFS 2.4.0

Toolchains and SDKs are no longer included in the installer. Install them with the Package Manager. For the full list of packages, see Commonly available packages.

Package Version Notes
gnu_arm_toolchain 14.3.1 GCC toolchain for 32-bit Arm® targets
gnu_riscv_toolchain 14.2.3 GCC toolchain for RISC-V targets
msdk 2.4.0 Part support and examples for MAX32xxx and MAX78xxx microcontrollers
cortex-m_sharcfx_sdk 1.0.0 SDK for the Cortex-M33 core on SHARC-FX targets
xtensa_sharcfx_toolchain 15.5.2 Xtensa toolchain for the SHARC-FX cores
zephyr 4.4.2 Real-time operating system for MAX32xxx and MAX78xxx microcontrollers
zephyr_arm_toolchain 1.0.3 GCC-based toolchain for Zephyr RTOS

Host architecture support

CodeFusion Studio is supported on the following host operating systems:

  • Windows 11 (64-bit)
  • macOS 15 and macOS 26 (ARM64)
  • Ubuntu 22.04 and 24.04 (x86-64)

Earlier or newer OS versions might work but are not officially supported.

Target architecture support

Processor support is unchanged in this release. For the full list of supported processors and their feature support, see supported processors.

Known issues and limitations

  • Zephelin profiling — not available on MAX32657 and MAX32658: The Zephyr 4.4.0 package for these processors does not include Zephelin (modules/zephelin). Do not enable the Zephelin Profiler in System Planner for MAX32657 or MAX32658 projects. The Zephyr Single Core TensorFlow AI Inference Profiling template is no longer offered for MAX32657. To deploy and run a model on MAX32657, use the Zephyr Single Core TensorFlow AI Model template.
  • Zephelin live tracing — fails to start with zephyr/4.4.2: The zephyr/4.4.2 package contains Zephelin revision 77ade5b, whose backend can't find the Zephyr repository. When Enable Zephelin Live Tracing is turned on, selecting Start Capture displays an error that begins with Failed to start Zephelin backend. To work around this issue, clone Zephelin at revision 2ffa839 and point the Zephelin Trace Viewer extension at the clone, as described in Advanced: Set up the Zephelin backend manually.
  • OpenOCD — adi-mpdbgagent.cfg not supported: The OpenOCD interface scripts folder (<cfs-install-dir>/Tools/openocd/share/openocd/scripts/interface) includes adi-mpdbgagent.cfg, which was added with an upstream OpenOCD update. It does not support any processor in CodeFusion Studio 2.4.0, and you can ignore it.
  • SHARC-FX — xt-nm error during flash and erase: On Windows and Linux, the CFS: flash (sfx), CFS: flash (m33), CFS: erase (sfx), and CFS: erase (m33) tasks for SHARC-FX targets report an error because they cannot find xt-nm. On Windows, the error is xt-nm.exe is not recognized as the name of a cmdlet, function, script file, or operable program. On Linux, the error is /bin/xt-nm: No such file or directory. You can ignore these errors. The operation falls back to default values, and the flash or erase completes successfully.