Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/analogdevicesinc/codefusion-studio/llms.txt

Use this file to discover all available pages before exploring further.

The CodeFusion Studio Package Manager lets you download SDKs, toolchains, and plugins on demand — without reinstalling CFS. Each component is delivered as a versioned package that can be installed, updated, or removed independently. You can access the Package Manager from the VS Code Command Palette or from the cfsutil CLI, making it suitable for both interactive development and CI/CD automation.

​
Commonly Available Packages

The following packages are available for most CFS installations:
Package NameVersionPurpose
cfs_base_data_models2.2.0System Planner SoC configuration data
cfs_base_plugins2.2.0Workspace creation, System Planner, code generation
msdk2.2.0Bare-metal SDK for MAX32xxx and MAX78xxx
zephyr4.3.0Zephyr RTOS 4.3.0 for MAX32xxx/MAX78xxx
Only packages relevant to your account permissions are displayed. If no packages appear, all available packages may already be installed.

​
Install Packages from VS Code

1

Open the Command Palette

Press Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (macOS), or click the gear icon in the lower-left corner and choose Command Palette.
2

Run the install command

Type (CFS) Install Package and press Enter. A list of available packages appears.
3

Select and install

Choose the package you need. A progress window shows the installation status. When finished, a confirmation message appears.
Some packages require license acceptance before installation. If prompted, review the license agreement and select Accept or Accept All to proceed.

​
Install Packages from the CLI

Open a CFS Terminal in VS Code (View > Terminal, then select CFS Terminal from the dropdown), then use cfsutil pkg install: 
cfsutil pkg install <name>/<version>

​
Common install examples

# Install the base plugins package
cfsutil pkg install cfs_base_plugins/2.2.0

# Install CFS data models
cfsutil pkg install cfs_base_data_models/2.2.0

# Install Zephyr RTOS
cfsutil pkg install zephyr/4.3.0

# Install MSDK for MAX32xxx/MAX78xxx
cfsutil pkg install msdk/2.2.0

# Install all packages listed in a workspace manifest
cfsutil pkg install /path/to/workspace/.cfs/.cfsdependencies

​
Semantic version ranges

cfsutil pkg install supports semantic versioning ranges so you can allow compatible updates automatically:
Allows minor and patch updates within the same major version.
# Install latest 2.x.x version of cfs_base_plugins
cfsutil pkg install "cfs_base_plugins/^2.0.0"
Always wrap version strings containing special characters (^, ~, >=) in quotes to prevent shell interpretation issues.

​
Offline / local cache install

Use --local to install from the local cache without network access: 
cfsutil pkg install cfs_base_data_models/2.2.0 --local

​
License acceptance in CI

Use --acceptLicense to automatically accept license agreements in non-interactive environments: 
cfsutil pkg install msdk/2.2.0 --acceptLicense

​
Manage Installed Packages

​
List installed packages

# List all installed packages
cfsutil pkg list

# Filter by name pattern
cfsutil pkg list "zephyr*"

​
Search available packages

# Search all available packages
cfsutil pkg search "*"

# Search by name
cfsutil pkg search "msdk"

​
View package details

cfsutil pkg info zephyr/4.3.0

​
Uninstall a package

Check for dependents before uninstalling: 
# Check what depends on this package
cfsutil pkg local-consumers msdk

# Uninstall (name only, no version)
cfsutil pkg uninstall msdk

​
Delete cached packages

Uninstalled packages remain in the local cache. Remove them to free disk space: 
# Delete all cached (not installed) packages
cfsutil pkg delete "*"

​
Access Restricted Packages with myAnalog

Some SDKs and packages require authentication with your myAnalog account.
1

Log in to myAnalog

From the Command Palette, run (CFS) myAnalog Login, or from the CLI:
cfsutil myanalog login
A browser window opens for OAuth login. Use your Analog Devices account credentials.
2

Add the package remote

Your organization provides the remote name and URL. Add it with:
cfsutil pkg add-remote <remote-name> <url>
3

Authenticate the remote

Link the remote to your myAnalog session:
cfsutil pkg auth-remote <remote-name> --myanalog
4

Install restricted packages

Once the remote is authenticated, install packages as normal:
cfsutil pkg install <restricted-package-name>/<version>

​
Troubleshooting

Your myAnalog session may have expired. Check your status:
cfsutil myanalog status
If logged out, run cfsutil myanalog login and complete the browser flow again.
Remove cached packages and reinstall:
cfsutil pkg delete "*"
cfsutil pkg install <package-name>/<version>
As a last resort, delete the CFS data directory and reinstall all packages:
  • Linux: ~/.local/share/com.analog.cfs
  • macOS: ~/Library/Preferences/com.analog.cfs
  • Windows: %LOCALAPPDATA%\com.analog.cfs
After installing a new SoC package, restart VS Code. If the SoC still doesn’t appear, ensure cfs.catalogManager.checkForUpdates is enabled in VS Code settings. As a last resort, delete the catalog file and restart:
  • Linux: /home/<user>/cfs/<version>/.catalog
  • macOS: /Users/<user>/cfs/<version>/.catalog
  • Windows: C:\cfs\<version>\.catalog
If downloads fail or restricted packages disappear, run Manage Package Remotes from the Command Palette to reauthenticate or reconfigure remotes. You can also use cfsutil pkg list-remotes to verify configured remotes.

Build docs developers (and LLMs) love

Get started for freeTalk to us